Stop jumping into prototypes too soon
· 1 min read · UX Design, Product Design
Before we start sketching screens or building flows, there's one critical thing to address: complexity.
UX design isn't just about making things look clean or feel smooth. It's about understanding – what the system does, who it's for, what the user actually needs, and where the friction lives.
When we jump into prototyping without unpacking complexity, we risk building something that looks great but doesn't work well.
Recently I looked through a portfolio from a design lead with decades of experience. His recent dashboard project? The Figma file showed this process: grab a few Dribbble shots, make a quick low-fidelity prototype of a screen, then polish the UI.
This is not UX. There was no exploration of users, no mapping of system complexity – just assumptions about what should be on the screen.
- Who are the users, really?
- What are they trying to accomplish?
- What are the moving parts behind the scenes?
- How do they all connect?
If we don't answer these questions first, prototypes become guesswork.
Design is not decoration. It's problem-solving. And that starts with clarity – not Figma.
More writing
Where does intelligence belong?
Most AI briefs say “add an assistant”. The better question is where AI should help, and how much. Five rules for designing AI into a complex product, with an example from KNIME.
AI UXExperience architectureProduct DesignAssistant usage is not the metric. Resolution is.
Teams measure AI features by how often people use them. That rewards the wrong design. Five behaviours that tell you whether an intelligence layer is doing its job, and how to instrument them from the first release.
AI UXMetricsProduct Design