Clarity Before Capability

The instinct in most product rooms is to start with capability. What can we build? What does the technology allow? These are reasonable questions, but they are the second questions.

The first question is about clarity: what do people need to understand before they can make a good decision? Not what do they want, not what do they need built — but what do they need to know?

Getting this wrong early creates a specific kind of debt. Not technical debt. Trust debt.

The pattern I keep encountering: teams that skip the clarity question don’t just build the wrong thing. They build the right thing at the wrong moment — when no one is ready to receive it.

[Full essay to be written.]