Category: Design Management

  • Of cover letters

    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.

    Skimming level

    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.

    Skimming level of the recruitment process
    A diagram showing the criteria that acts as a screen or filter in the skimming level of the recruitment process.

    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).

    Relevance

    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)?

    Quality

    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.

    Conclusion

    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 topwhen 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.

    [ntt_percept page=”avaloq-open-positions”]

  • Bilas and feedback

    This week, the UX design team is having our regular bilas (bilateral meetings) which, undoubtedly, is one of the most important part of Avaloq’s culture. Bilas serve a wide range of benefits from an unstructured kwentuhan to an avenue for the team to express what’s working and what could be better in terms of our daily work experience. This activity strengthens the bond among designers and empowers us in paving our career paths in the organization.

    Feedback

    It is feedback that we get the most out of during bilas. Knowing that everything is going well with a person is a welcome relief, especially during this pandemic. On the other hand, feedback on how we are with our projects and collaborations is essential to the quality of our work and its outcome.

    Here’s a simple guide for a constructive 1:1 discussion of feedback inspired by Scrum’s Sprint Retrospective.

    Feedback discussion guide
    A diagram showing guide questions to ask during a 1:1 feedback discussion.

    Feedback sources

    Needless to say, any kind of feedback is better than no feedback at all. The source of the feedback is as important as the quality of the feedback itself.

    Holistic feedback sources
    A diagram showing a holistic sources of feedback.

    Starting from one’s self, a self-assessment could be done then work outwards — from your own team towards cross-functional teams. The important thing to remember is relevance — the feedback must be coming from a collaborator or a person who has worked (or currently working) with you in a project.

    Conclusion

    Happy to be working with self-starters and a proactive UX design team. We catch and remedy difficulties and hindrances early on through our constant feedback activities and of course, through the openness of everyone.

    [ntt_percept page=”avaloq-open-positions”]

  • Organizations need guideposts. They need an outline; employees need to know each day when they wake up why they’re going to work. This outline should be short and sweet, and all encompassing: Why do you exist? What motivates you? I call this a mantra — a three or four-word description of why you exist.

    Guy Kawasaki
  • A Two-Week Timeframe

    Recently, I’ve been drafting a Project Communications Framework that will guide the design team in handling design projects—from alignments to presenting our works. Committing to a timeframe is one important aspect and here’s a visualization of it.

    See the Pen A Two-Week Timeframe by Brian Dys (@briandys) on CodePen.

  • Designing a Design Team

    Notes

    • Roles & Capabilities
    • Culture
    • Skills & Personalities
    • Reliable & Resilient
    • Flexibility in the Roles
    • Learning other areas
    • Do not design in an assembly line — always have a view of the bigger picture

    The Interview

    • Passion. What motivates them?
    • Curiosity. Are they willing and prone to ask important questions, especially before they start creating?
    • Communication. How do they articulate the problems they’re working on? How do they help others understand the solutions they’re considering?
    • Engagement. What’s their view of the design process? What steps do they take to approach it?
    • Autonomy. Are they able to understand the big vision and work toward it? Are they pushing the team forward with new insightful ideas, or are they dragging it behind by needing to be told what to do next?
    • Reveal themselves — strengths and weaknesses

    The Tests

    • Technical
    • Problem-solving Capabilities
    • Take–home Tests regarding a real-life problem they have
    • Criteria
      • Design concept
      • Structure
      • Consistency
      • Problem solving
      • Creativity
      • Presentation

    References

  • Please Stand Up!

    Voyager Stand-Up
    Feet standing in a circle for a stand-up meeting.

    Here’s a simple yet effective activity we have here at Voyagerstand-up meetings.

  • Working with Chikka Design Team

    Karin Alody Chan was part of Chikka Design Team as front-end designer. She has graduated from the position and currently pursues web design. This is her essay from an exit interview.


    Working with Chikka Design Team has given me an opportunity not just to grow in terms of career but also with personal development.

    Before I started working at Chikka, I didn’t have any confidence with my design and front-end skills because I know that I was a bit behind with all the new stuff that has been going on with the design industry, but because I’m passionate with what I do, I decided to challenge myself to be open to new things.

    Everyone in the team has their specialization and common knowledge when it comes to UI/UX but this didn’t hinder them to learn new things and make design as a lifestyle. I like that we’re open to discussion and our team lead wants us to be innovative. I felt like I was in college because of the environment – in college we were trained to have the courage to talk about our design ideas and  be able to defend our designs – like every detail should have a purpose and not just design something and put it in an empty space as filler. That’s what I felt with the team.

    I am grateful that I was part of it. What I learned is that being humble is the most important thing you need to have if you’re working for a company because we learn to admit to ourselves that we’re not right all the time. I know there were times that maybe I try to defend my designs too much but it has taught me that sometimes it’s okay to just listen and accept other people’s perspective.

    I think that this is, so far, the best team I have ever been to. I hope everyone the best of luck in the near future.