You are working at the wrong altitude

The wrong problem, beautifully

Three weeks into a redesign. The pixels are clean. The system is coherent. Then someone asks a question in a review that drops your stomach. You have been solving the wrong problem beautifully. Every designer with enough years has this story. The failure is not one of craft. It is one of altitude.

Which bucket are you in

Shreyas Doshi's Product Work Allocation framework sorts every piece of work into four buckets: differentiators, table stakes, incrementals, and embarrassments. Most design time lands on incrementals — small improvements to things that already work. The differentiators, the features that actually change competitive position, get leftover attention. The Kano Model adds a time dimension: today's differentiator decays into tomorrow's table stake silently, without anyone noticing. If you are not actively monitoring which bucket your work falls into, you are probably polishing something that stopped mattering.

Name the layer first

Jesse James Garrett's Five Planes of UX — Strategy, Scope, Structure, Skeleton, Surface — provide the altitude map. A surface-level fix cannot solve a structural problem. A beautiful button redesign will not help if the information architecture underneath it routes users to the wrong place. The first question is always: which plane is actually broken? Name the layer before you open the design tool.

Execution versus vision

Jenny Wen distinguishes two modes of design work: execution support and short-horizon vision. Execution support means helping the team ship what has already been decided. Short-horizon vision means identifying what should be built next. Both are real work. The failure is not recognizing which mode the current problem demands. A vision response to an execution problem wastes time. An execution response to a vision problem wastes potential.

Make altitude visible

Teresa Torres's Opportunity Solution Tree enforces this discipline structurally. Start with the desired outcome. Branch into opportunities — the unmet needs and pain points that could move that outcome. Branch opportunities into possible solutions. Branch solutions into experiments. The tree forces you to name the problem before proposing the fix. It makes altitude visible.

Diagnose before you design

Diagnosis before design. Name the layer. Name the bucket. Name the mode.