Market mapping, customer interviews, support tickets, competitor teardowns. Out of it: the patterns that keep recurring, and a shortlist worth solving.
Flows, wireframes and interface design answering what discovery surfaced. Decisions get written down as they are made, so the reasoning outlives the project.
Working prototypes in front of real users rather than pictures of them. What survives gets built first; what does not is recorded as tested and rejected.
Design and engineering in the same cycle, not a handover between them. Edge cases, states and interaction detail specified where they are needed.
A deliberate launch with instrumentation already in place, so the first week produces behaviour rather than opinions.
Real usage goes back into the roadmap: what people actually did, which changes moved the number, and which ones get reversed.
Positioning, messaging, and the search and AI visibility that decides whether you get found at all. The promise made is one the first session delivers.
Systems, playbooks and documentation, so the team keeps its pace after I step back. Written where the work happens, not filed where nobody opens it.
A written record of what was expected, what happened, and what changes next time — the input to the next cycle, not a retrospective nobody reads.
