Why Big Ears?
Before you open Figma, open your ears. A user request isn’t always the root problem. Good UX research means listening to what users say, what they do, what they struggle with, what they expect—and what they don’t say.
Before you open Figma, open your ears. A user request isn’t always the root problem. Good UX research means listening to what users say, what they do, what they struggle with, what they expect—and what they don’t say.
Complex products often hide complex organisations behind them. But users shouldn’t have to understand your teams, departments, systems or processes just to complete a task.
A polished interface can make weak information feel stronger. From rankings and precise numbers to photographs and professional typography, visual cues can influence how credible information feels.
What if your interface didn’t need to explain what users should do? A Mercedes-Benz newspaper campaign turned a printed steering wheel into an intuitive interaction — a simple example of affordance in action.
UX interviews aren’t just testing what you know. They’re testing how you think. Here are 10 common UX interview questions and a practical way to prepare: build five adaptable stories around difficult problems, research insights, disagreements, changed decisions, and measurable outcomes.
That’s the power of good UX: designing for real-world context, using clear affordances, and making actions feel obvious before users have to think about them.
Your users don’t know how your system works. They know how they think it works.
This week’s Free Resource Wednesday is a practical UX Interview Questions & Frameworks cheat sheet to help you prepare with more structure and confidence.
A UX flow doesn’t end when the user completes the task. The real experience continues through feedback, system status, and the next step. Here’s why designers should stop at “Done” and start asking: “Okay… now what?”
Users don’t experience your interface in isolation. They experience the entire journey. Explore what public-service UX can teach us about designing for real needs, hiding complexity, inclusion, testing, and continuous improvement.
A journey map isn't a collection of screens. It's a way to understand the user's experience — their goals, actions, touchpoints, thoughts, emotions, pain points and opportunities.
Relevance > completeness.