Digital development starts with the gap, not the format.
The website, app or system is often downstream of a more important question: what needs to change?
Development decision
A request can arrive as a website, app or system. The useful starting point is earlier: what has changed in the business, what is being held back, and what the current setup no longer carries.
That distinction matters because the format can be obvious while the real development need is not. A new front may depend on a position that has not been decided. A workflow may need definition before software. A product request may become smaller once the first version has clear edges.
The work is therefore to define the change before choosing how much to build. Keep what already holds, name what must move, and make the first version prove something specific.
The build follows that decision. It should not be the decision.
Related development
The first version gets its edges before development begins: what it is for, what it must prove and what deliberately waits.
Define complete before development begins