Before You Build

A founder hears repeated customer complaints and asks for an app. Six decisions sit between that request and a responsible build. This series works through them using a continuing fictional distributor example, so you can see how the question changes as evidence and operating constraints come into view.

The six decisions

• Understand the problem — identify the task, failure point and consequence.
• Test the need — choose an uncertainty and a test that could change the investment.
• Decide what comes first — map dependencies before assigning dates.
• Understand development cost — compare the full scope and operating commitment.
• Choose a delivery setup — name the decision, delivery and operating owners.
• Plan a realistic first release — define a complete useful task and what to learn after launch.

How to use the path

Bring one live idea, product question or process difficulty. Each lesson ends with a tangible output. Work through the sequence with colleagues, or open the lesson that matches the decision currently blocking you. Write down what you observed, what someone reported, and what you still assume.

The example is fictional and illustrates a reasoning method, not a client result. The lessons do not replace a domain assessment, technical design or a commercial case. No login is required and reading progress is not saved; bookmark the lesson you need.

When you need to compare options in one meeting, use the decision worksheet. For the argument in one place, read the open guide.