Hi, I’m Brian Dys — a photographer from the inside looking out · a composer entangled in electronic music · a UX designer · a spouse, a parent, & everything in between.
Last month, I’ve wrapped-up with the 4th part of a talk that I’ve shared with the UX design team: Documenting your work as a designer. This topic tackles the other side of design work (and any work, in general), which is documenting your experiences and learnings from projects.
- Part 1: The whys and hows – anchor the documentation activity on a purpose
- Part 2: The process – making sense of the documentations and keeping them meaningful
- Part 3: The case of the briefcase & showcase – curations
- Part 4: The work – getting your hands dirty
The talk goes from abstract concepts towards concrete steps in starting a portfolio curation. What each of us actually produced were our top 3 highlights of last year.
This year is brighter at Avaloq as we’re growing within UX design team and others as well.
See if there is a good fit?
- The Nirvana fallacy: when perfectionism leads to unrealistic solutions
- An Invisible Cost of College: Parental Guilt
- How to avoid layout shifts caused by web fonts
- A Few Thoughts On Writing
- Ideas That Changed My Life
- Optimistic UI Patterns for Improved Perceived Performance
- 1,000 True Fans? Try 100
- Alternatives to Spinners on the Web
- Why do we need to be right?
This is the week that I’ve went back to digest two week’s worth of curious readings — from design to stock market to psychology.
- Jootsing: the art of jumping out of the system
- Chamath Palihapitiya closes GameStop position, but defends investors’ right to sway stocks like pros
- The service-based design org
- Culture-based user interface design
- Design and Science
- Validation is a mirage
- Why Tailwind Isn’t for Me
- The Aesthetic-Usability Effect
- Are Meaningful Daily Activities Linked to Well-Being?
- Please Stop Calling Things Archives
- Shopatainment: Video Shopping as Entertainment
Jaycelle requested me to change the color of her blouse from red to mustard. It’s easy with an app, that’s true. However, before all those algorithms and automations, there was a semi-manual way of doing it — using selective colors in Photoshop.
Music: Tweakers by Brian Dys
Got a scanned or photographed signature with a messy background? Here’s an easy way of enhancing it to be in PNG with a transparent background.
In Adobe Photoshop:
- Resize the long side of the image to 1920px or higher
- Image → Adjustments → Threshold
- Select black-only via Alpha Channel
- Make BG transparent and save as PNG
Music: Scrap by Brian Dys
This week at Avaloq, I officially re-wore my hiring manager cap for the UX design team, as we’ve officially published our open positions. I spent the latter part of the week reviewing applicants and determining who among them are candidates.
Appreciate all of you, designers (and you, one industrial designer, and also you, one visual merchandiser), for submitting your applications. Recruitment is still in its initial phases, so keep ’em coming!
So, what goes on in the process of having an application go from an applicant to candidate status? Let’s go over the surface of the skimming level of the recruitment process.
The goal of skimming is to prepare a group of applications for evaluation and deliberation. At this point, the objective aspect of it is the presence of two things: the résumé and portfolio — one cannot do without the other in order to have a balanced basis for moving forward with an application.
The objective-subjective part, on the other hand, is determining if the résumé and portfolio’s relevance and quality fit the bill. The criteria is essential to the objectivity of the process and in itself is subjective as well because it is based on our organization’s culture, team’s mandate, and my professional approach as a hiring manager, among others.
This is not a black and white approach either because even without a portfolio, if an application fits the criteria, it is put on hold pending completion of the tandem (résumé and portfolio).
At this early stage, the relevance of the résumé and portfolio pertains to the position being applied for (or with other available design positions).
- Is the work (includes personal) experience relevant (both in the field and number of years)?
- Are the portfolio items relevant (presence of UI designs and UX case studies)?
Bear in the mind that the recruitment is specific to the UX design team. Needless to say, a basic expectation is to be impressed by résumés and portfolios that are themselves designed — both information architecturally and visually.
- Is the résumé conducive to easy-understanding of the person’s strengths?
- Is the résumé visually-pleasing?
- Is the presentation of portfolio items conducive to easy-understanding of the person’s strengths (written descriptions and background information are essential)?
- Is the presentation of portfolio items visually-pleasing?
- Is the portfolio itself visually-pleasing?
Once an application fit the criteria, it gets a candidate status. Candidates are evaluated and deliberated along with others in the same category (e.g., associate category is separate from senior category). Skimming, true to the word itself, is a quick and reliable activity; still, a thorough process ensues in the next level — starting again with the candidate’s résumé and portfolio.
I know, the title says, Of cover letters because that idea inspired me to write this article (although it is mostly about skimming). Cover letter, it is cherry on top — when it is intended for the specific position being applied for (in contrast with a generic one). In my experience, a particular application with a specific cover letter is like hearing the person introduce themselves — in which, I would gladly listen.
A cover letter is not part of our requirements or criteria, though. An important note is that a strong application is holistic in its approach in propositions (i.e., job applications) and that includes a specific cover letter, a well-designed resume, and a cohesive portfolio.