Concept and draft
It starts with research. From that comes a prototype you can actually use, tested by the people who will later work with it. This repeats over several rounds.
Between the commission and the first line of code lies the phase that decides whether the right thing gets built. It is the shortest and the most consequential.
Process
It begins with user research. I gather data about the target group or analyse what is already there. From that comes a proposed concept, and from the concept, as early as possible, a prototype that people can actually use.
I take this prototype to the people who will later work with it, collect their feedback and rebuild it. That takes several rounds, not one. Anyone who stops after the first has paid for the prototype and left the insight behind.
At the same time I check what can be built and what can be run afterwards. Feasibility and cost-effectiveness have a say along the way, not only at the end.
Result
You get a draft you can put in front of someone, and the findings from the tests: what worked, what did not and what was changed as a result.
The most common outcome is something considerably simpler than what we started with. Talking to users early means cutting features rather than building them.
Limits of this phase
I do not write a specification that ends up in a drawer. A document nobody reads costs more than a prototype somebody tries out.
The finished design does not belong in this phase either. What is made here looks deliberately unfinished, because a draft that looks like a product gets feedback on colour instead of substance.
Frequent questions
How long does this phase take?
That depends on how much is already settled. The number is in the scope from the first conversation. This is the phase where you save the most if you bring groundwork with you.
Can we skip this phase?
If it really is settled what should be built, yes. But it is settled less often than it seems.