• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

UXwanabe

Learn how to get into UX and grow your design career

  • Home
  • Blog
  • Podcast
  • About

UX

How to plan a successful career in UX

May 2, 2021 by Tim Chan

I was invited as one of the panelist to my friend Michael Tam’s experience design course to share my industry experience to a group of UX students. Michael had sent me a list of questions beforehand and I have written down the answers I prepared. I thought it would be quite interesting to share it here because I always see myself as a better writer than a presenter!

I am the guy on the far right

How did you first enter into Expereince Design?

I wrote about that in my old post here.

Tips on First Steps/Interviews

First step is to acquire the knowledge you need. For me, the most effective way of doing this is by doing 2 things right — Read books & Ask smart questions.

Read — A lot of UX leaders before our time has put in the time to condense their life time learning into a consumable format, just read it! When I speak to a lot of wannabe UX designers, it amazed me how little people are willing to spend the time to absorb the knowledge that will actually help them get a job, most are just looking for a shortcut to get into UX. Let me be very clear, taking 1 or 2 course DOES NOT make you a qualified UX designer. The lack of basic UX knowledge is the main reason UX students is not able to define the problem they are trying to solve clearly or are trapped into solving the wrong problems. If you are solving the wrong problem, it doesn’t matter how good your UI or prototype is.

Ask smart questions — This requires you to have the self-awareness of understand the difference between:

  1. Things you don’t know the answer to and would be able to figure it out on your own vs…
  2. Things you don’t know the answer to and would not be able to figure it out on your own even if you try.

Never ask questions that you can figure out on your own. Senior designers like to help people in their shoes, but you should also respect their time. Good question demonstrates that you have done the work to try find answer in the first place and had but in the time to think about the specific in kind of help you needed.

Bad question: I have no design background, how can I become a UX designer? (JUST GOOGLE IT????)

Good question: I am a marketer whom recently took a UX design course and is very eager to become a UX designer. I am keen to position my knowledge in planning marketing activities as a way to standout to future employer that I understand service design and is able plan user activities. I am wondering if you were in my shoes, am I doing the right thing, if not, what would you do differently?

If you could go back in time, what’s the one thing you’d tell/change your younger self?

I would leave the start up job early because I reached my plateau very quickly and I felt too comfortable. I would also be more consistent about writing and sharing about UX because writing helps bring me clarity on my thoughts, and it also helps to demonstrate my expertize and establish a personal brand.

Me giving comments on the student’s presentation

How to plan a Successful Career in this industry

Have a clear defined action plan on how to reach the next step in your career. Lets say you want to be a senior designer, how? Well, you need to find out what companies are looking for in a senior designer. Learn what senior designers do, learn how to do that thing and do it. Do online research on jobs ad and identify what are the gaps between skills you have vs what soft/hard skills is needed for the next step, then come up with a detailed plan (I recommend monthly) on how to close that gap.

Show the plan to you boss and invite them to be part of the process, most importantly, make them accountable. Say something like “I plan to be a senior designer in 2 years time, here is the plans I came up with that can help the company, the design team and myself grow, is there anything you would like to edit?”. Then, update them constantly during your regular catch up meetings. When the time comes, it is very hard for them to say no to you for the promotion when you have met the criteria you set together with your boss.

What are some of the best moves you have seen some young designers have made?

The best young designers I have seen have a strong personal brand, they made themselves stand out among others. They…

  1. share their lessons learn along the way — Who are you and what is your story? For example “I am an auditor turning in UX designer” will be an interesting one (Listen to my podcast if you haven’t already). Make sure you communicate your story clearly in your Linkedin , your portfolio and every other form of communication! Start sharing everything you learn in the UX bootcamp on every social media as much as possible (read this book). Linkedin, articles on Medium, you own blog, twitter, Instagram stories and whatever you can think of. Not many people do this, it takes hard work and it is preciously why you should do it because it helps you get noticed, it shows that you are driven.
  2. built a strong network and add value to the community — Contributing to the local UX community and offer your help in their events. Winners always wants to help winners. Let people know you are interesting in UX for real, not just some wannabe that is slightly interesting in UX and wasting everybody’s time. Start inviting people out for coffee or on Zoom call. If people see that you are committed and driven, they will remember you and who knows? You might meet your future manager or employer in the design group, if they like you, they will also refer to their hiring manager friends, this happens all the time.

Experience Design & Business

How did you learn to define the real (design/or not) problems for a client/business?

If the problem is real, people will find a work around or a hack to do that thing. Microsoft Excel team just looks at what popular macros people are creating and they will get a list of burning painpoints. If it is a good to have or not a real painpoint, people won’t do anything about it.

Tips on handling non-designers’ challenging me?

Different situation requires different strategy to handle. My quick tip is to assume good intention from stakeholders and take the time to listen to the question behind the question.

Are they asking you because they have their own agenda? Are they saying things just because they want to sound smart? Are they genuinely interested? Or do they want to do this as a power play (boss want to show who is in control)?

Rex Wong (VP of research @ JP Morgan), Ellen Wong(UX/UI Manager @ AXA), me (Product Design Lead @ HSBC), Micahel Tam (Global Associate Design Director @ IBM iX)

Do you think you have imposer syndrome?

All the time. I had it every step of my designer journey, from before I got a UX job, I felt like a fraud, to when I actually got a job, all the way to getting a promotion as a UX manager to lead, I constantly feel like I am winging it.

Over time though, I started to “become comfortable being uncomfortable”, this means I expected it — imposer syndrome is like my old friend. The sign of having imposer syndrome means that I am growing in the right direction that I needed. If I don’t feel it occasionally, I might not be pushing myself hard enough or the job doesn’t offer me enough challenge.

I talked about imposer syndrome in early days of the career with my friend Anindita Saha (Service Design Lead at HSBC) in my podcast. Below is a transcript of what we talked about:

I remember I had written my CV…my very short CV at the time, on the top of my CV, I’ve written my name. In the second line, was supposed to say User experience designer. I remember I wrote down “user experience designer”, and then deleting it. Then writing it again, and deleting it. I was going back and forth about writing it. It took me 2 weeks to write down “user experience designer” and save it as a PDF.

This was 2012 in Hong Kong, UX was not a big thing yet. No one really knows what it is but I knew I needed to write it because if I didn’t, people will be very confused as to what I was trying to do. I felt like such a fraud, writing those words — user experience designer — second line of my CV, because I didn’t feel like I had enough experience to write those words down.

When I sent out my first job application, I was terrified. I had the impostor syndrome like “Oh my God, I’m writing this word down and what if I don’t live up to that terminology? What if I’m not embodying this term the way that it’s expected if someone actually interviewed me or even give me a job?”

I was terrified, but I had two minds. I had my terrified side of me and I had the logical side of me. The logical side of it was “if you don’t write this down, no one is going to know that you want this job, and then they can figure out whether you can do the job or not.”

It was really hard because normally what’d you put on your CV, is first you interviewed for that company and if you got the job, you got a title. Then you can put that title in your CV. For us, we have to make up our own title. We haven’t actually worked on a real job as a UX designer, so it was a very terrifying experience because we’re used to somebody else giving us that title, someone else giving us that label. Like you are this rather than us saying to ourselves, I am a [fill in the blank].

I think this is what we need — every individual needs to be able to say “I am this” not because somebody else tells me that I am, but because I know that I am, or at least I believe that I am. I want to be this, and you work towards that. If you want to be that person, you need to say it to yourself. It’s not something that we’re taught to do, we’re told we are something because somebody tells us that we are, and that’s wrong.

Future Trends in Experience Design

Where do you see the industry is going? How shall I get myself ready? Where do you see your future self would venture into?

I can’t predict trend, if I could, I would have already be rich with the bitcoins I should have bought! With that said, I think we should all focus on having a strong foundation ready such that whatever the “new big thing” is coming, we will be in the position to apply our knowledge to it.

If that answer doesn’t satisfy you and you are the kind of person that like to chase trend, another way I would answer this is you can start to pay attention to job boards occasionally to get a sense of what is coming and see is there something that you would like to learn, then proceed to acquire that knowledge.

For example, if you see there starts to be more chatbot designers job around and you are interested, then go ahead to build a chatbot on your own. Then when the trend actually became real, you will be away ahead of other people and would be in a position to say to your potential employer that you have done it vs other people that claims they would be able to learn it on the job.


I have a podcast called UXwanabe. A show that explores how to get into UX and navigate your design career in Hong Kong. The podcast is my attempt to solve the problem for the lack of resources for the local UX community in Hong Kong, you should check it out!

Filed Under: Career development, Most popular Tagged With: UX, UX Design

How to design your own UX process

August 7, 2020 by Tim Chan

If you search for “UX process”, you can find thousands of articles written on this topic. As a new UX person joining a team with no established process, you might be struggled on whom process to follow. I have been there before, and it was confusing.

The problem with following someone else’s framework is that it hardly sticks in your mind and it is easy to misuse it if you don’t fully understand it (As everyone worked in an “Agile” environment can testify). Since each company’s internal process and its UX maturity is different, it is hard to just pick one popular UX process and follow it.

In this article, I am going to walk you through a list of questions you should ask yourself in order to lead a design project from start to finish, and also explain why these questions are important. Based on these questions, you can form your own process that will suit yourself and your company.

Lets deep dive into this.

What problems are we solving?

Before you start designing anything, you need to understand WHY are you doing what you are being asked to do. If you don’t know what you are trying to solve, you can’t judge whether your design solves the problem or not.

Sometimes we are scared to ask why, the environment might make us feel like it is not politically correct to do so because it feels like we are questioning decision from higher up. Our boss might say or think “Why are you asking why? Do you think I made the wrong call? Can’t you just do as I say?”

Decorative image on: Consider what are you trying to solve

The problem with the word “Why” is that it is not welcoming, it feels like an interrogation. It focuses on questioning the person that made the request instead of the intention of the task. Instead, I advocate for using the word “What”. Consider the following:

1. Why are you using blue?

2. What are you trying to achieve by using blue?

“Why” seems like you are questioning someone’s decision, it can be interpreted as “Blue is a bad choice” where “What” invites for participation, it is a discussion: “What is your goal and how does blue help you achieve it?”. Now that we are comfortable asking What, here are some things you should ask when a task is handed to you:

  • What problem are we trying to solve and for whom? What are the pain-points?
  • What do users currently do without our solution? Did they invent some workarounds? This is an important question because if your problem is real and painful enough, people will try to find a workaround for it. Conversely, if you don’t see a workaround, the problem probably is not painful enough. Microsoft Excel does this really well. They basically look at what popular micro is being created and added it to their next release. This exercise helps you eliminate the imaginary problem like “some people might find this annoying” and give you a glimpse on how your design might end up. Sometimes your user’s hacky workaround is a great solution that requires minor modification.
  • What triggers us to solve this problem now? Understand the thought process of your boss will help you greatly as you can tie it to how you present your work. When you understand your boss better, you can feel his frustration or her urgency, and it helps you to avoid presenting a solution that takes 3 months to build when what you boss wants is a hot fix in 2 weeks.

Output

By the end, you should produce some sort of documentation that outline:

  • Why this project exists
  • What are the requirements

I like to add this knowledge into a document called a Project brief and keep it in a share drive such that there is a single source of truth, and I would also email stakeholders as well to keep everyone on the same page. Surprisingly, once it is written down, things become more concrete, and stakeholders are less likely to change their mind.

What is the scope?

Nothing gets done if there is no deadline. There is always room for improvement, there is always the next “minor polishing”. This article itself is also a product of setting a deadline and just hit the publish button whether I like it or not.

Decorative image on: Schedule

I can always come back for the typo or add a picture or two, but if I don’t publish anything, no one can read it, and I can’t add value to anyone’s life. For your project, get everyone involved and ask:

  • How much time do we have? Are we expecting a quick-win or a total redesign? There is no point in designing the perfect solution that takes 2 months if you only have 2 weeks to work on it. Instead, spend your time coming up with a perfect 2 weeks solution.
  • What does good enough look like? When do we know when to stop? At a minimum, your design should satisfy some bare-bone goals. i.e. The user should be able to add items to their cart. Any other good to have stuff like “comparison feature” or “add to my favorite” are Good-to-haves.
  • What use-cases or target user is not covered as part of this project? Having alignment on what you are not doing is just as important as knowing what needs to be done. Make sure this is well communicated to your stakeholders to avoid an unpleasant surprise in the future. e.g. Boss: I thought we are also curing cancer with this release and have already told the higher-ups, now I need to get everybody OT to work on this!

Output: MVP documentations, Out of scope documentation

Has anyone solved this problem before?

There is always more problems to solve than time available, as a smart designer, you want to avoid reinventing the wheel. First, you need to find out has the wheel already been invented. This means:

  • Look inward. Internally, has any teams within your organization faced this problem and solved this? Is it applicable to your case? Is there something we can reuse? Failure to do this step is how inconsistent designs, duplicated pattern and wasted effort occurs. If you company is big enough, someone else from another department has probably solved this before. Make sure they are aware your project exist and talk to them.
  • Externally, how did other companies solve this problem? This goes without saying, if you work in a FinTech, look for what other Fintech company is doing, if you work in e-commerce, look at what other similar company is doing and so on. What can we learn from them? What can we apply to our case? What are they not doing well that should we avoid?

Output: Case-study, Lesson-learned

How does the existing stuff work?

If you are adding a new feature on top of an existing design, you better know how the thing works inside out, or you might break things. Look at existing documentations, play around with the live site, and speak to developers to find out about any tricky logic, interactions or quick fix from the past that has been put together that is vulnerable to big changes.

Decorative image on: Two guys discussing on a document

What is our solution?

Now we start to design the actual thing. You can create sketches, lo-fi wireframe or hi-fi designs, prototypes…etc. It really depends on what you think is best for your company. During this process, consider:

  • What are the different scenarios and use cases? What would your design look in other languages? What does it look like on different screen sizes? Different platforms?
  • What happens when users don’t follow “the right way?” Have we covered all edge cases? If users can add one item to the basket, can they add 300? What does it look like if they do that? Do we allow it? If not, how does the UI convey that to the user? How long are items stored in the basket? Do we need to tell that information to the user? Why or Why not?
  • What are our rationales to make certain decisions? Throughout the design process, we are going to learn a lot of things and make a lot of decisions, are we just going to let that sit in our brain or are we going to make the effort to document it such that other designers and future generations can benefit from our lessons?
  • If we propose this design, does it also impact other areas of the existing design? Who needs to know about this? Other designers? Other developers? Other product managers? Do they have resource to support you?

Output: End-to End user flow, High-level sketch, Decision log, Interactive prototype

How do we know our solution works?

A design proposal is considered feasible when it, at a minimum:

  • Achieves the business goal
  • Can be built within a reasonable time-frame
  • Can be understood by the user

This means two types of people need to look at our work:

  • Internal people — Stakeholders
  • External people — Customers/Users
Decorative image on: A women thinking

Has our internal people agreed to this?

Do developers thinks your design is feasible? Does it require a big change to existing code base? How long would it take? Are there other simpler way to achieve 80% of the result but can take much less time?

Do other designers think we are following the established guidelines? If the design is not part of the guideline, do we need to update the guidelines?.

Do product people think the design achieved their goal? Do brand people think the design is on brand? If you are working on FinTech or highly regulated industry, have you consulted Subject Matter Experts or Legal or any relevant people to make sure your design complies to regulations? e.g. Can you create a One-click to order button?

How much time does the approval process take from all of these people mentioned above? Did the project plan take into account the back and forth? One of the major reason for project slip is that project plan failed to recognize that takes time for people to come into consensus. This won’t happen to you as a smart designer, you will make sure to bring this up during meetings and talk to the right people.

Output: Review session, approval log

Do customers understand our design?

Normally, we want to make sure the answer is Yes to this question before the product goes live. Until we test our designs to the real people who are going to use it, the designs are not validated and we are living in our own bubbles.

In a lot of companies, testing is always thought as a luxury, but the nature of it doesn’t change. Users has to test it no matter what. If you don’t test the design before launch, the shift just became after launch. We are testing the live product to real customers instead of prototypes. Anyway, if we are commit to test before launch, we need to figure out:

  • What format do we want to test? Sketches? Lo-fi/Hifi wireframes? Prototype?
  • Who to test? How long does the recruiting takes? How many people do we need? Who runs the test?
  • How much time does it take for us to organize the findings? How do we present our findings? In what format? To whom? What do we expect to do with our findings?

Output: Usability testing

What do people downstream need?

Now that our designs are ready, it is time to send it to someone else to work on it. Branding people might want to pick the right images, copywriters need to know which area needs copy. In an ideal case, everybody required to make the project happen are involved during the inception of design, if not, we need to spend some time to explain to them how the thing works.

Decorative image on: People discussing around a document

Consider: When will they need it? In what format? Are there enough time for them to review the design and ask questions? For example, you need to tell them:

  • For Copywriter, this area needs a new copy, and we are trying to tell the user about how x works
  • For Branding people, this area needs some stock photo, and we are trying to do y
  • For Developers, this area we are re-using existing component and this area requires new ones, and this is how the animation should work

In some companies, someone else is charged of figuring this out for you, but if that someone does not exist, it is on you. In essence, make sure people downhill knows what it is expected of them and in a format that they understand.

Output: Final UX & UI specifications.

How do you know the design is properly implemented?

Once developers has build something, how are you going to find out it looks and works as you specified? Do you communicate with QA people on what to look out for?

If you are going you review the build, how will you do it? Are you going to eye-ball it? Or use Chrome Developers tools to look at the elements? What if it is a mobile app? What tools should you use than?

How much time do you need for the review? Where do you report the bugs? How do you report the bugs? Are everything tracked and documented?


That’s everything I can think of that requires you to think about when you want to see through a design from beginning to launch. Hope this article helps you in your process and please leave a comment if you have any questions.

p.s. I am aware that product development is a continuous cycle and the design shouldn’t stop when a product is launched. But as the scope of this article is about seeing through from start to launch, what after launch is out of scope.

Filed Under: Framework, Most popular Tagged With: Design, Process, User Experience, UX, Ux Process

How to find the right kind of mentors as a junior designer

July 3, 2020 by Tim Chan

I see this mistake a lot when it comes to design mentorship program. Junior people all wants to talk to the most senior person in the room, but are oblivious of the fact that such approach will have a limited benefit to their career development. This is a mistake because contrary to your intuition, picking a less senior person as a mentor is probably the better choice.

Here is why it is not a good idea to find someone with 20 years of experiences as a mentor when you first started out:

Although they can offer you general direction for your career, they far too removed from what is was feel like when they first started.

I learned this the hard way after trying to offer advise to someone that was trying to get into UX. When faced with a situational question, I realized that I started to mix up what I did versus what I will probably do, my memory was fading away. After all, it was almost 8 years ago since I got into UX.

I certainly lost touch on how it was like as a junior designer. The struggle had now became a distanced memory. Though I can still offer reasonable advise, they certainly did not come from my best thought output. If my advises were a tool to be used in a battle, it would be a rusty dinner knife instead of a sharp Samurai sword.

My brain has been preoccupied by current matters. My skills sets has been transformed to serve the managerial role, such as how to manage a UX team, setting design directions, stakeholder managements…etc. Those are the things that I have been thinking, living and breathing everyday. Those are the things I am most qualified to talk about and can have meaningful contribution to the conversation for anyone wants to discuss on such matter, or is interested to grow into this role. Anything else, I am not best person to talk to.

Who to look for instead

To gain the most from your mentorship program, you should look for someone that is just one level above you, someone that has just done it, or is currently doing it. For example, if you want to get into UX with no design background, talk to junior designers that just landed their job. If you are a junior designer, seek mentorship from a Senior Designer instead of the Director of UX.

Seek out the “just made it” person if you want immediate actionable advice, and the seasoned veteran if you want general guiding principle for life. Don’t mix up the two, or you will be wasting your time and theirs. Hope this helps!

Filed Under: Career development Tagged With: Mentor, UX

What it’s like working in Agency, Startup & Corporate

May 2, 2020 by Tim Chan

An illustration of a group of people chatting

Picking an industry is hard when you first started out as a UX designer as you hardly know anything about them. It is even harder in Asia, as there weren’t many resources that is written around this region.

Having born and raised in Hong Kong, and have worked in Agency, Startup and Corporate, I want to share with you my personal experience and feeling on what it is like working in there, such that you have more idea to help you make a decision. Remember to not just take my word for it as every company is different.

Agency

Pros

Exposure to clients — The advantage of being an outside firm is that you can navigate around the client’s corporate structure and have chances to meet and present your design to C-level stakeholders directly. This forces you to become good at public speaking and if you can impress clients, you will be on a smooth path to promotion.

Experience the whole UX design process — You will have the opportunity to run user interviews, do prototyping, run usability tests… all the standard UX process. The reason you get to do all that is because nowadays firms charge clients for all these activities, so it is good for you that you can put all these UX artifacts into your portfolio.

Huge earning potential — The salary is competitive, and there is also opportunities to earn more. When you become a manager, your job became a sales person with design background, and you will have to fulfill a quota and bring in clients. You get commissions a for the clients you bring in and if you are good, the earning potential is much greater than working in-house.

Perks — To retain people, the company is willing to spend money on events such as boat trips, Hackathons, game nights…etc. There are also a lot of learning resources that you can tap into, if you have the time to read it.

Exposure to different projects — You don’t have to worry about getting bored or feeling stuck working on the same project for too long because there is always variations on the type of clients that comes from different industries.

A morden agency office
Photo credit: The Secret Little Agency

Cons

Stressful— Agencies in Hong Kong can be very stressful. Leaving work at 10 p.m. and working on holidays/weekends is not uncommon. I have had the unfortunate experience to witness someone worked 30 hours straight and another person worked until 4 am to prepare for a client presentation.

Workaholic culture — People in agencies are willing to give up their personal time to get things done. They would take weekends into account as workdays, and I have also seen people asking for manager’s permission to leave work “early” at 7 p.m.

Poor project management —For an agency, taking in all the clients they can when the market is good is all that matters. Higher up decides the deliverable date with clients and designers where not part of the project planning meeting. This leads to the firm taking in more then they can digest, and as a result the downstream suffers from impossible timeline.

Improper UX deliverable — On the surface, UX designer gets to do standard UX process such as user research. However, these activities are often not completed in a professional manner due to the lack of formal training on UX methodologies and lack of time to properly digest and analyse research findings. In the end, it just became a checkbox item in the deliverable that says “we done it”.

Lack of knowledge sharing — Due to the stressful environment, turn-over rate is really high. The consequences of this is that knowledge is not well documented and passed on. People are forced to keep reinventing the wheel on occurring problems such as “Techniques on handling clients” or “How to run workshop” since they don’t know what is the best way to do things.

Unclear project goals—People that pitches the deal to the client, the designers that do the work, and the people that represent the client are all different group of people. Hence, communication problem occurs as designers has no idea what the sales people sold to the clients. What is the project goal? What is the customer’s pain-point? The answer usually exist in vague form such as “The goal is to rebuild the client’s website and the pain-point is the website is really outdated”. In this kind of environment, designers is nothing more than glorified pixel monkey.

Startup

AirBnB office
Photo credit: AirBnB

Pros

Get to wear many hats — In a startup, there isn’t a lot of people around, so you get to do a lot of things. Apart from design, you might have to work on the project plan, write copies and even do a little bit of QA. It gives you the learning opportunity to understand the different kind of jobs that contributes to make a software company work.

Flat culture —There very few layers in the chain of command, this means quick decision making process and often times this is what a UX designer need because this gives them the freedom to try new things, fail, and iterate their design.

Rapid promotions — It is much easier to get a promotion because there are not many people around, and startups is often more generous to offer promotion as a way to retain their employees, as an alternative to huge salary raise and as an incentive to make employee stay longer.

Encourage innovation — For startups, they are still figuring out what is the direction for the company, so the culture encourages innovation and coming up with new ideas. It is much easier to get management approval on trying out new technology or new frameworks.

Flexible working hours —Most startups don’t need your physical present, for that reason, more and more company has allowed their workers to work on flexible hours and work from home as long as work is delivered on time.

Cons

Low pay —Unlike Sicilian Valley or the western scene, startup around here is not known for their high pay, according to Startups HK:

Hong Kong startups will start off at HK $15,000 for fresh grads / junior level and will pay up to $60,000 per month for advanced designers, which works out to about US $23,000 and $93,000 a year respectively.

That’s why they usually make up for it in coffee machines, ping pong table, snacks, couches and beer Friday etc.

Weak brand —If your the startup is not well-known, people don’t know what you do and might also have wrong perception on your design ability because startup tends to have a more relaxed hiring restriction compared to big companies. i.e. People with less or no formal design experience is hired

Lack of structure —A company that is just starting out will not have a strong structure. You will be expected to figure things out on your own with no guidance. Oftentimes you will not be able to get the feedback you want when you needed it. For example, it is impossible to gain any good design feedback if your manager is not a trained designer.

Lack of resources — Startup usually does not have a lot of spare resources to go around, so sometimes they will not be able to pay for the seminar you want to go to or spend money on usability testing, less bonuses…etc.

Lack of Job security — Unlike an establish corporation, a startup can go out of business any time if they run out of funding or fail to find product market fit.

Work gets repetitive — In a startup, you might be only working on one product or one app. This can get boring pretty quickly after 1 or 2 years.

Lack of growth — Because of the small team size, the likelihood of meeting someone smarter than you is much smaller compared to a company with a bigger team size. In the worse case scenario, you are the smartest UX in your design team, and that severely limits your ability to grow.

Corporate

A photo with a group of people holding gears

Pros

Resources — Corporate has money. They can afford to invest in their designers on luxurious items such as paying them to go to conferences (e.g. Nielson Norman Conference), setting up a design system team, creating a UX copy writing team, or even hire a team of researchers. This helps to take some of the burden off the UX designers and everyone can also learn from the experts from these areas.

Brand — A big corporate with a good brand helps people to understand who you are and what you are capable of. Working in a well respected company quickly implies your ability.

Well paid — Smart people can command high salary, and big corporate can afford to pay them that amount and that also benefits you. This also means you have a higher chance to work with smart people compared to small companies that couldn’t afford them.

You can specialize — In a small company, you might have to wear many hats, for example, UI design, copy writing, and run your own research. This may not be ideal if you prefer to focus on just doing one thing. In a big company, things are more specialized and you get to go deep on a subject.

Change jobs without leaving the company — With so many products and projects with their own budget and management team, a big company can be seen a collection of mini-companies. If you are not happy with where you are, you can apply to other teams and start fresh without the hassle of leaving the company.

Good perks — Above market norm on paid vacation days, good coverage on medical, insurance, housing allowance…etc.

Big impact of your work— As a designer’s own satisfaction, it feels good to know that your work that can be used by a lot of people.

Cons

Everything is slow— Project often involves multiple stakeholders and decision makers, and this inevitably slow things down and impact the efficiency. Project takes at least 3 months to complete compared to 3 weeks in a startup. For those that are impatient, this may feel incredibly slow.

Work on a small part — You become a small cog in a big machine, this means that sometimes you are working on a small part of the product or doing changes on existing design, instead of building brand new product for features from scratch.

Politics —This is inevitable when the place is full of people. It is common to see people fighting for attention & resource. You don’t have to be a part of it, but you must learn the rule of the game, and how to deal with it.

Difficult to get recognition — In a big company, one must work extra hard to gain noticed, otherwise you boss might never know what you do (or even that you exist). If your work is not recognized, it is very hard to get a promotion.

Illustration of 2 person connecting with each other

Conclusion

Depending on your UX journey and what you want in life right now, there are two strategies you can use in terms of finding the best industry that suits you:

  • Prioritize getting a UX title
  • Prioritize learning

Prioritize getting a UX title

If your resume doesn’t say you are a UX designer, you can basically forget about big corporate and agencies if you go through the front-door of applying online. You will never get pass HR. If you knew someone inside or you can strategically reach out to the hiring manager, that is another story.

Generally speaking, you would have better luck to work in a startup as the barrier of entry is much lower. Here is how I rank the difficulty of getting into each of these industries with zero design related background.

  1. Startup
  2. Agency
  3. Corporate

Prioritize learning

If the most important thing for you right now is to grow, you should start with a big corporate with a mature UX team. Corporate has the right structure, people and resources to help you achieve that goal. Be careful though, just because you are dealing with a big company, it doesn’t mean the UX team and its process is well established. Make sure you find out about their UX team size before you apply.

However, big corporate is hard to get into as they prefer to hire people with more experience. In that cases, consider going after agencies. While it maybe stressful and demanding, you get to learn a lot of the soft skills such as presentation skills and the art of addressing stakeholders concern, which will be useful for the rest of your career.

Now if everything else fails, go for startups where the barrier of entry is lower. You still get to learn and do a lot of different things such as research, where in a big company it will be considered as someone else’s job.

Filed Under: Career development, Job interview Tagged With: Careers, Review, User Experience, UX

Decision log

April 16, 2020 by Tim Chan

Imagine joining a UX team as the new designer wanting to learn about the product. There are two ways you can do it without taking your colleague’s time: you study the live product, or you read documentations about it. The most common form of design documentations are Wireframes. However, a wireframe only tells you part of truth, it tells you what design decisions has been made, it tells you the what, but it doesn’t tell you the why.

When we work on a project, we would have made a lot of design decisions based on user needs, stakeholder needs, research findings, time constrains, technology limitations.. the list goes on and on. If we don’t document these decisions down, we will be in a dangerous position where important project knowledge exists only in some designer’s memory. If that designer has moved on, the knowledge will be lost forever.

Without understanding the why, designers are forced to guess why things were designed that way. Every time we make a change, it is a gamble. The only solution is to systematically document project decisions, such that if future designers decides to make a change, they will have the right tools and context to help them make an informed decision. Let me introduce a tool that not only minimize design risks, but can also help you build a more mature UX organization — The Decision Log.

Benefits of a Decision Log

A decision log helps us to:

  • Remember things — When we write decisions down, we made sure we will have a reliable source of truth we can always refer back to it without forgetting it
  • Save time — By documenting what worked and what doesn’t, we made sure future designers will not waste time exploring dead-ends
  • Avoid going into circles — When we are exploring design options, it is easy to go back to square one and forget why we discarded it. When decisions is clearly documented, we made sure this won’t happen
  • Past on knowledge to others — When knowledge is written down, we are slowly building a library of knowledge where everyone can benefit and absorb it on demand

How to create a Decision Log

A decision log is a simple one pager document that sits inside the project folder. It has 3 components:

  • Screenshot
  • Decisions made
  • Rationale

That’s it. It really is that simple, now that every design you made is traceable and other people will no longer need to guess why you made that decision. The concept is not novel, our best friend — Developers does it all the time when they add comments to their code. Similarly, you should start writing a Decision log entry whenever a decision is made that will significantly impact the design, and you continue to do it through the project.

When in doubt, err on the side on over communication. The bad case scenario of writing something obvious is that readers ignores your sentence. The worse case scenario of not documenting a rationale is that you also forgot why you made that decision, then that information is lost forever.

Conclusion

As agile development and the introduction of Sprint has became the norm in every technology company, people seems to forget the true essence of the methodology is to learn quickly, not just do things quickly. The most efficient way to record and pass on that learning is to write it down. I hope you give this method a try and I can’t wait to hear from you the results!

Filed Under: Framework Tagged With: Product, User Experience, UX

Why I write

March 1, 2019 by Tim Chan

Last week my friend Costin asked me why I write. It was at that moment I realized I have never gave this question a deep thought that it deserved. So in the spirit of understanding myself a bit more, I have decided to find out why I write. I hope if you read it to the end, I would have somewhat convinced you to give writing a shot. Seriously, it is really fun!

This article serves 2 purposes:

  • To give me clear purpose on why I write
  • To remind myself why I started and motivate me even when I don’t feel like writing (which is every single day!)

Why do I write?

1. I want to contribute to the community

When I was a wanabe designer trying to break into the UX field, there were a lot of resources out there that helped me started and I eventually got into where I am today working in a profession that I am proud of. I am really grateful for those who shared their knowledge before me because if they didn’t, I might have never became a designer.

As I became a more seasoned designer, I came to realize that if no one continues to share what they learn and contribute to the community, the cycle of knowledge will die off. The responsibility now falls onto me to help those that were in the my shoes and help them succeed, such that our community will continue to thrive and our accumulated knowledge will be greater than those before our times.

2. Writing makes me think more clearly

As I experience life, I form observations and I form opinions. Sometimes I figured an explanation to something. Some ideas are insightful and I want to share them to the world. The problem is, such thoughts are disorganized in my head, it requires massaging. If I try to communicate my raw thoughts to the public, no one will understand me and I have wasted an opportunity.

If I want to communicate better, I have to organize my thoughts. Writing is a powerful tool to help me achieve that because writing demands structure and clarity. It forces me think hard on how to sell an idea to an audience where they can’t ask follow up questions. After reading my words, the reader either gets it or they don’t. I have one shot.

The act of writing my thoughts down forces me to solidify the fuzzy concept in my head, which in turn trains me to think more clearly in the long run.

3. Writing is good for my career

When I write online, I am demonstrating the following skills and attribute to my future employers:

  • I am a disciplined person and I am passionate about design. Publishing articles consistently takes a lot of time and commitment (1 article every month), it is not an easy task and one must therefore be very passionate and disciplined about it. My collection of design articles is the result of the standard I set for myself. I am a man for my word so you can trust me to hit deadlines.
  • I am knowledgeable about business & design. By sharing everything I know about business and design openly, my readers will have a clear idea on the knowledge I have in these areas. After all, one must thoroughly understand the topic before one can talk in depth and explain it in a laymen-friendly way.
  • I am a good communicator. Each pieces of article is my attempt to sell my thoughts to my readers. It is perfect demonstration on my ability to make arguments, explain concepts and sell ideas.

4. Writing helps me practice for interviews

Sometimes during interviews, I would get asked insightful questions that I have never thought of. That does not mean I am not smart enough, it just means I have never gave those question any thought, or I have never considered things from a different lens.

Now if I spend time to write down my answers here, it allows me to explore the answer a little bit deeper and it becomes more memorable to me. If I ever felt the need for rehearsals before an interview, I can also come back to look for things I wrote.

5. Writing makes me happy

Humans are most happy when we encounter a state of flow. As a creative person, writing puts me in the state of flow where I am so immerse of the task and have totally neglect my surroundings. I felt constantly challenged in finding different ways to express myself, while in the same-time making sure I can make my point across to my readers. It is a perfect challenge that matches my ability.

It is especially rewarding to know when someone has found my writing useful, or even reached out to me to ask for more advise. This means that I have successful achieved my goal to add value to the community, this makes me a very happy person 🙂

6. Writing offloads my memories

I have a lot of ideas, and a lot of answers to a lot of questions. If I don’t write things down, I have to come up with an answer to the same question over and over again. Keeping all my answers in the brain slowly turns them into fuzzy, messy and disorganized thought, it gets lost very easily.

The brain is not built for remembering things, it is for solving problems. When I document my thoughts down, I am putting old problems that I have solved aside such that my brain has space for new problems that comes to my way.

7. Writing is good for my personal brand

I come from Hong Kong, a place where UX is still in its infancy. Most knowledgeable UX person in Hong Kong are westerners. That is understandable because UX originates from those countries.

Almost all my knowledge about UX were acquired from leaders from the west and I look up to them, but they don’t just magically become leaders overnight. They were leaders because they share everything they learn through articles, books or talks. They slowly build up their brand one step at a time.

In order for the UX scene to grow in Hong Kong, we can’t constantly rely on oversea experts to teach us what to do, that would only carry us so far. If we truly want to grow the UX scene and has a chance to catch up with the west, we need thought leaders of our own. We need someone local. This is where I see as an opportunity for me to come in.

Once I share everything I know and have added value to the community, over time, I would be seen as an expert and have build up my personal brand. It would open more doors to opportunities, it will give new comers someone to aspire to, and we as a community would be in a better position to drive changes in the Hong Kong UX scene.

Who do I write for?

I write for 2 targeted groups in my mind.

1. Wanabe designers

They are interested into UX and have probably read some books or have taken a lesson or two about UX. For this group, I want to teach them how they can become an UX designer, but I won’t teach them the basic knowledge of UX, that is their job to figure that out.

This group of people want to know that it is possible to become an UXer and they want someone that can guide them through the process. My focus would be to teach them exactly what steps they should take that can help them land their first UX job. Some topics that will benefit this group:

  • how to prepare for your portfolio
  • how to job hunting and find the right UX jobs
  • how to prepare for the interview
  • how to networking
  • how to be confident even if you think you are not qualified — A mind set that would help you succeed.

2. Seasoned UX designers

The second group is seasoned UX designers. They have been working in the field for 2-3 years now and they are looking for knowledge that can help them climb the rank. This group wants to become a better designer such that they can take on more responsibility. Some topics that will benefit this group:

  • How to gain management support/ buy in from stakeholders
  • How to create and communicate your design process
  • How to advance to Senior UX/ Management
  • How to drive organization change
  • How to align design vision
  • How to create design principles
  • How to communicate better with programmers

Conclusion

This article is written mainly for the benefit of myself, but if you have made it this far to the article, I hope I have made you understand the benefit of writing and how it will help your career. And if this inspires you to start writing, Haleluia! Leave a comment and share with me what you wrote!

Filed Under: Personal Tagged With: UX

  • Go to page 1
  • Go to page 2
  • Go to page 3
  • Go to Next Page »

Primary Sidebar

UXwanabe newsletter

About

Hi, I am Tim Chan, I want to help 10,000 people get into UX!

Previously, I spent 4 years working as a Product Design Lead at HSBC.

I’ll share my experiences, mindset & strategies on how to climb the design ladder on my newsletter.

Recent Posts

  • 2022 in Review
  • 10 Lessons I learned working in a global bank as a designer
  • Evidence based imposter syndrome framework
  • Graduate advice for UX students
  • How to plan a successful career in UX
Copyright ©2023 UXwanabe · All rights reserved