{"id":8018,"date":"2017-04-13T09:23:31","date_gmt":"2017-04-13T08:23:31","guid":{"rendered":"https:\/\/marvel7077.wpengine.com\/?p=8018"},"modified":"2020-11-05T15:16:34","modified_gmt":"2020-11-05T15:16:34","slug":"things-new-ux-designers-know-entering-workplace","status":"publish","type":"post","link":"https:\/\/marvelapp.com\/blog\/things-new-ux-designers-know-entering-workplace\/","title":{"rendered":"Things New UX Designers Should Know Before Entering the Workplace"},"content":{"rendered":"

Whether you\u2019ve graduated from a short course or a degree, when you first enter the workplace you\u2019ll learn 100 times more than you\u2019d ever imagine. Sure, you\u2019ll learn more techniques and practises, but the soft skills you\u2019ll pick up are just as valuable. You\u2019ll learn more about yourself, others and how to deal with certain situations (think office politics).<\/p>\n

<\/div>
<\/svg><\/div>

\"When you first enter the workplace you\u2019ll learn 100 times more than you\u2019d ever imagine.\"<\/p><\/span><\/blockquote>\n

For the past year I\u2019ve been keeping a list of things that I\u2019ve learnt. I soon realised that I wished I knew these lessons from the start. In attempts to extend a helping hand to my fellow UXe\u2019rs out there, I wanted to share my learnings. So here are some things I\u2019ve learnt since working as a UX designer in the corporate world.<\/p>\n

Designing Ways of Working<\/h1>\n

\u00a0\"1-tduclgkncu7f1ll3apmk9q\"<\/a><\/h2>\n

Don\u2019t be afraid to say\u00a0yes.<\/h2>\n

Don\u2019t let the fear of the unknown deter you from taking on something new. If the chance to work on a new project comes up jump at the opportunity to get involved. Even if you don\u2019t know much about it or it seems too complex. Taking on challenges will allow you learn new things and grow as a designer.<\/p>\n

Don\u2019t jump into using Sketch straight\u00a0away.<\/h2>\n

Always take a step back and do the necessary research before even touching wireframes<\/a>. I know this is an obvious one, but it\u2019s easy to forget sometimes. The discovery phase will make your life a lot easier when you start defining and designing.<\/p>\n

Get feedback often and as early as you\u00a0can.<\/h2>\n

Don\u2019t sit on screens for too long without showing your team mates or users. Another person\u2019s feedback may push your design in a completely different direction. Never get attached, you might like the design, but the design isn\u2019t for you.<\/p>\n

When going into a critique, be prepared.<\/h2>\n

Regardless if its a casual or formal critique, a person has made time in their busy day for you. Have the courtesy and show them designs and screens that are open, organised and ready to go.<\/p>\n

Don\u2019t be afraid to say\u00a0no.<\/h2>\n

You might be given an impossible deadline or a workload that will be too much. It\u2019s ok to speak up and voice your concerns. Saying no is far more respectable saying yes and then not being able to deliver. You can\u2019t do everything and you can\u2019t please everyone.<\/p>\n

Something will always come up last minute. Think on your feet and be adaptable.<\/h2>\n

At some point you\u2019ll need to drop everything you\u2019re working on. You may need to redesign something else or get a different piece of work out that wasn\u2019t planned. While we take steps to avoid this, it\u2019s always a possibility.<\/p>\n

Don\u2019t be afraid to put your foot down if something critical is being overlooked or written\u00a0off.<\/h2>\n

Sometimes things can get overlooked by accident or on purpose. So it\u2019s in your best interest to stay above things even after they\u2019re signed off. If you see something that you know isn\u2019t right, speak up and make it known. I\u2019ve stopped things completely happening before because I made noise about it. If I hadn\u2019t, it would have slipped through and make a huge negative impact.<\/p>\n

Work with developers early to discover all edge\u00a0cases.<\/h2>\n

Doing this will save you a lot of headaches later down the track. Get the developers involved during the design phase. They\u2019ll be able to inform you about what every edge case could be. It could also bring up possible limitations and opportunities. Design solutions for these before a handover occurs.<\/p>\n

Think and plan first, then prototype for\u00a0testing.<\/h2>\n

Before building anything, take a moment to think about what you want to get out of the testing session. If you\u2019re lucky enough to have a UX researcher on your team, chat to them about what the best method may be and write out the user journey with them. Following a plan, will make your life easier and save you a lot of time.<\/p>\n

Stakeholders might try to give you the solution rather than the problem they want to\u00a0solve.<\/h2>\n

A project should always begin with a problem or a goal, not a solution. If a stakeholder tells you what feature they want, push back and find out why <\/em>they want it. Use research and quantitative data to find the best solution for the problem. If you can prove it and show evidence, stakeholders will change their mind and get onboard.<\/p>\n

<\/p>\n

Team and\u00a0Culture<\/h1>\n

\"1-wbjunby7lpfokkptbvystq\"<\/a><\/p>\n

Choose your team, not just the company\u2019s name.<\/h2>\n

I can\u2019t stress enough how important the people you work with are. People often fall into the trap of choosing a company based on it\u2019s name looking good on their resume. Soon they realise that the processes and culture isn\u2019t that great, so they fall behind. Surrounding yourself with good people who care about design as much as you do will help you learn, grow and become a better designer. For me, I want to do the best job I can to support the team and help them shine as well.<\/p>\n

There\u2019s nothing wrong with asking for help, but try to solve it for yourself\u00a0first.<\/h2>\n

Don\u2019t suffer in silence if the answer is a quick question away. But, before you ask, take a moment to think about the answer. Can you solve this on your own by doing a quick search? People will appreciate that you\u2019ve attempted to solve it on your own first. But if you\u2019ve exhausted your options, just ask!<\/p>\n

Find a person that you feel comfortable asking \u2018stupid\u2019 questions.<\/h2>\n

In my team we have a \u201cthere\u2019s no such thing as a stupid question\u201d policy. This is another reason why team is so important. There\u2019s some questions I definitely wouldn\u2019t ask in front of a stakeholder, however I\u2019ll ask my teammates later on in private.<\/p>\n

Organise team social events and have\u00a0fun.<\/h2>\n

Work hard, play hard and celebrate your achievements. Group outings are a fantastic way to strengthen the bond between teammates and build friendships. Just don\u2019t do anything too stupid.<\/p>\n

<\/p>\n

Working with\u00a0others<\/h1>\n

\"1-3u8o8puogv_qh5smxgzrxg-1\"<\/a><\/p>\n

There will always be that one asshole in the workplace.<\/h2>\n

Assholes will be assholes, but look at the bright side. You\u2019ll discover how to interact with, and handle situations involving different types of people. All experiences both positive and negative will add to your personal development. Just remember the line, and don\u2019t let them get away with it if they cross it.<\/p>\n

If a developer or major stakeholder asks a question about a design that you\u2019re unsure of avoid saying \u201cI don\u2019t\u00a0know\u201d.<\/h2>\n

It\u2019s better to say \u201cI\u2019ll get back to you on that\u201d or \u201clet me confirm with my colleagues\u201d. This is especially important if your new. \u201cI don\u2019t know\u201d may bring about a lack of confidence in you within the larger team you\u2019re working with. If you can, deflect the question, figure it out, then get back to them with the right answer, rather than the wrong one.<\/p>\n

Always explore a stakeholder\u2019s feedback, even if you don\u2019t think it will\u00a0work.<\/h2>\n

Never shut down a stakeholder\u2019s idea in a meeting. Just write it down in your meeting notes and say something along the lines of \u201cthat\u2019s interesting, we\u2019ll give that a go and explore it further\u201d. Always follow through and explore their idea, you never know unless you try. If it\u2019s really not ideal, mock it up and prove to them why it doesn\u2019t work otherwise they\u2019ll keep nagging you for it.<\/p>\n

You can\u2019t always win. Pick and choose your\u00a0battles.<\/h2>\n

There will be cases when a stakeholder will make a final call on want the design will be. While you might not agree with the decision, sometimes you need to compromise. If this happens, make it clear that you don\u2019t recommend the move, but ultimately its their call. Working with users and business<\/em> is just part of the job.<\/p>\n

Ask a few developers the same question.<\/h2>\n

Sometimes I\u2019ll consult with a few developers. There\u2019s been cases where I\u2019ll get a different response each time. One person might say it can be done, while the other says it can\u2019t. In this case, you need to dive deeper. Figure out if its a time issue, technical issue or a \u201cit sounds too hard, so I\u2019ll just say no\u201d issue. Unfortunately it can happen. In reality, anything is possible, it just comes down to time and money.<\/p>\n

<\/p>\n

Learning and\u00a0Skills<\/h1>\n

\"1-lg9i1c0__7-joufkovff_a-1\"<\/a><\/p>\n

Plan a \u2018hour of power\u2019 for yourself to focus on something other than\u00a0work.<\/h2>\n

No I\u2019m not implying that you should sit on Facebook instead of working. The hour of power is a time that you\u2019ve allowed yourself to work on something that will improve your skills. For example, you could study something you\u2019re interested in on Coursera<\/a>. Try out a new prototyping tool. Do some tutorials to sharpen up your skills. Knock up some concept designs or do some research into design trends and UI. This will allow you to stay engaged and mix up your day.<\/p>\n

Learn about how the back end code\u00a0works.<\/h2>\n

As you work with developers you\u2019ll naturally pick up how the backend systems work. Although it\u2019s best to take initiative and learn more about it so you can communicate better with them. I\u2019d recommend writing down any words that you\u2019ve overheard and don\u2019t understand. Then google them or ask someone afterwards, thus forming a mini glossy of words as you go.<\/p>\n

Make presenting easier for yourself by being prepared.<\/h2>\n

As a UX designer<\/a> you need to be able to effectively communicate your designs. I find this easier do to when I\u2019m prepared and have a plan. Jot down what the key points you want to say are. The order in which you\u2019ll be showing the work and what key take aways you\u2019re looking to get out of the meeting. Consciously think about what you\u2019re saying and what you\u2019re going to say next. Take it slow, relax and be clear.<\/p>\n

This article was originally published on Alana's Medium page<\/a>.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

Whether you\u2019ve graduated from a short course or a degree, when you first enter the workplace you\u2019ll learn 100 times more than you\u2019d ever imagine. Sure, you\u2019ll learn more techniques and practises, but the soft skills you\u2019ll pick up are just as valuable. You\u2019ll learn more about yourself, others and how to deal with certain situations (think office politics). “When… Read More ￫<\/a><\/p>\n","protected":false},"author":121,"featured_media":8028,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-8018","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-resources"],"acf":[],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\n\n\n\n\t\n