Product craft · September 2026
Sequence is the product.
A useful feature can still fail when it arrives before a person understands why it matters.
In short
People do not experience a screen as a collection of features; they experience it as a sequence. What did I see first, what did I understand, and what was I asked to give up before I got anything back? Every request has a cost: a phone number asks for trust, a permission asks for confidence, and a long setup asks people to imagine value they have not felt yet. Putting every requirement up front makes a system convenient for itself; sequencing it around what a person can understand now makes it usable. I use three questions. What must be clear now: the reason, the action and the consequence, in plain language. What can wait: important but not urgent requests, asked later. What should stay human: unusual, high-stakes or emotional situations need a clear route to a person. Like a good article, give the point first and the detail when it is needed.
Product teams often describe a screen as a collection of things: a form, a dashboard, a prompt, a menu, a button. A person experiences it as a sequence. What did I see first? What did I understand? What was I asked to give up before I got anything back?
That difference is where much of product quality lives.
Information is not neutral.
Every request has a cost. A phone number asks for trust. A permission request asks for confidence. A long setup flow asks a person to imagine a future value before they have felt any present value.
When we put every requirement at the front, we make the system convenient for itself. When we sequence it around what a person can reasonably understand now, we make the system usable.
The three questions I use
What must be clear now?
The person needs an answer to the immediate decision. Give them the reason, the action, and the consequence in plain language.
What can wait?
Some information is important but not urgent. Asking later can be more respectful and more effective than asking early.
What should stay human?
Not every branch needs automation. When a situation is unusual, high-stakes, or emotionally loaded, a clear route to a person is part of the design.
Why this is an editorial problem
A good article does not start with every footnote. It starts with the idea that makes the rest worth reading. Product should work the same way: give the person the point first, then invite them into the detail when they need it.