The Curse of Knowledge in UX Teams
The curse of knowledge does more damage to design communication than any skills gap. Once you know something, you can’t imagine not knowing it, and your reasoning goes unrecorded as a result.
How to Map User Journey States Instead of Screens
Mapping user journeys as sequences of screens misses the structural reality of how services behave. Here is a practical method for mapping journey states and why it produces more resilient designs.
Why Behavioural Modelling Is the UX Skill Most Teams Never Formally Develop
UX teams are trained to structure information, reduce friction, and improve clarity. Very few are trained to formally model behavioural structure. Here’s why that gap matters and what fills it.
Why User Journeys Are Systems of States, Not Linear Flows
Thinking of user journeys as flows misses the structural reality of how services behave. Learn why state-based thinking produces more resilient, trustworthy digital services.
Why Static Design Tools Cannot Model User Behaviour
Figma and flow diagrams are excellent for screens. But user behaviour happens between screens; in the transitions, the hesitations, the returns. Here’s what static tools miss and why it matters.
What Users Assume When You Don’t Explain System Behaviour
When digital services don’t explain what just happened, users fill the gap themselves and they usually assume the worst. Here’s how to make invisible system behaviour legible.