Frame the actual job
Start with the person, the constraint, and the consequence.
A feature brief is not yet a problem definition. I identify who needs the outcome, what currently breaks, and which constraint will govern the design.
Make the choice legible
Compare options against the constraint that matters.
Architecture and product scope are decisions, not aesthetics. I write down the alternatives and the reason one deserves to survive.
Ship a complete path
Deliver the narrowest useful end-to-end outcome.
The release includes the interface, responsible system layers, failure paths, and enough evidence to know that the user’s job is actually supported.
Close the loop
Use real behavior to decide what changes next.
Usage, support signals, and operational friction refine the next decision. The product gets sharper without accumulating ornamental scope.