Presentation - Week 3 from Khah and Esperanza
Your role will change your role as a ui ux designer will change depending on the company you work at, and your day to day will change depending on this role
specialized roles too, researcher, ui design, etc will all change depending on company structure product
plumbing, everyone has used one but there will be differences depending on culture and the layout of the bathroom (or 2 bathrooms). UI is similar to this, but in different context architecture intention of experience vs the function of the space / reality of the constraints the bathroom may already exist, and your goal is to improve the bathroom within constraints
you also have to be mindful of the people who have already used this product how can we improve this experience
good function is inherently invisible, you only question it when it doesn't work when designing a product,
you always need text input to function in a specific way, everything else needs to be the same.
always look at how other people are solving problems as opposed to reinventing the wheel, you don't want to confuse people when using your design
for example when inputting a credit card, you are expected to put in numbers not text, so you give a number keyboard as opposed to alphabet keyboard
it's not real until its in production - e.g. it's a 3d model of a bathroom vs being in a bathroom
when you start designing get your context right, understand what your users want to achieve.
before designing you need to know how other people are doing the same thing currently
even if it is a beautiful ui, the importance is the function, creating an experience is the priority
usually in software people will work divided, typically with product designers, product team, software engineers, users, and other designers within the team
make sure your products are usable and solving an actual issue it's easy to fall into designing a beautiful ui idea, but I didn't consult my software team, and this idea isn't feasible or possible.
it's all about teamwork design engineering product relationship is a collaboration the best results come from a shared understanding of the goal or outcome because then you can figure out the steps of how to get there together
when working with people with a diverse skillet, its much easier to create a better outcome double diamond design process
strong opinions loosely help, the things that will help for a good outcome are understanding the process of design things that help are research, types of documentation
product design dkes not equal design tools, not figma or sketch or photoshop, etc tools only become more important the closer you are to actually making something
paper and pencil is still your best first port of call
Google / slack / confluence / whimsical / Figma / framer / Github
complexity of communication it's one of the most important and trickiest parts of design, especially with remote work and timezones
many times you will be a one man team, or you will manage multiple teams sometimes you won't work end to end, and you will primarily managing, or if you have less designers than required that you are not a bottle neck
it's not all about visual artefacts its about the unsexy things that you need to get good at, you need to be good at research, mapping, diagramming states (password failure, email states, etc.), writing, documentation, domain expertise (understanding what you're working with)
you may not have face to face time, so having good documentation so other people can understand what's happening witnour speaking to them is important
work from anywhere , huge international time zone differences of your colleagues coworkers
tldr product design activities are actually quite varied:
teamwork makes the dream work
get better at finding balance
