I got click-bailed by this article again because I’m like, “whutttttt?!”
But there’s a strong takeaway: CONTEXT IS EVERYTHING.
- Physical context
- Social context
- Internal context
- Technical context
- Task context
- Temporal context
You want to ask your users questions to understand where they are coming from with their response to why they like or dislike something. Sometimes, you may need to guide your users to where you want them to be – that might mean asking them what stands out to them first, what their feelings are looking at it, what might be missing, and where things might have fallen short.
“You can find more problems in half a day than you can fix in a month”
– Steve Krug, a quote from Rocket Surgery Made Easy
You know you’re getting old when you watch TikTok videos on Youtube instead of TikTok… But at least I don’t have to make an account and get all my personal data stolen 🤡
Anywho, people like to know the difference between UX Designers and Software Engineers, and chunbuns delivered.
Tips and resources to help you get started (from 2017 but lots of still relevant content)
- Familiarize yourself with UI principles
- Learn the creative UX process
- Develop your eye for design
- Read design articles every day
- Design fake projects
- Learn the latest web design tools
- There’s more listed here in the article but I think Figma is far more superior at this point
- Mentor and get mentored
How can we get better at asking the right questions in order to solve the right problems? I turned to this lovely book which promises just that.
When starting any design project, you’ll have many questions on your mind. The problem you’re thinking about might not be the same as what your users are encountering.
I learned from this book that good questions:
- Encourage respondents to answer beyond single-worded responses like ‘yes’ or ‘no’.
- Offer users the ability to tell a story and describe their experience
Check out A More Beautiful Question to enhance this core life skill.
This one’s for advanced Figma users & teams.
Designer Josh Hardwood explored how to roll your own file automation plugin to do stuff like the following:
- Create your document page structure
- Insert a cover component with dynamic user information and date
- Insert an optional page heading component, with title and description
This would simplify your setup process so you can jump into designing versus manually setting up your Figma file each time. Can be a big time saver, especially for larger design teams that need to stay consistent.
[DESIGN CASE STUDY SPOTLIGHT]
Designer: Simon Pan
Case Study: Perfecting the Pickup
This case study is about how Uber transformed from a black car service for 100 friends in San Francisco to a global transportation network.
Why this case study is awesome:
- Screen evolution – you can see the changes that improved Uber through the years
- Designer involvement – Simon explains who was a part of the team and how long the project was worked on
- Research and details – there’s an overwhelming amount of research and detail written in this case study… Just WOW.
Simon Pan previously worked as a designer on Uber and Amazon Prime Music. This case study about Uber was super extensive and you get to learn so much about all the different decision-making points that go into the known and loved app today.
Since it was so long, it’d be lovely if there was a way to return to the top of the case study page or have a floating size nav with the sections hyperlinked. I had to scroll a bunch to skim through the content!