Strategy / Guide

Before you build: a better project brief

↗

Define the problem, the audience and success before choosing a technology stack.

Describe the customer problem in plain language. Identify who has the problem and how they solve it today.

List the essential launch tasks separately from later ideas. Agree on a small set of measurable outcomes.

Document integrations, data ownership, access requirements and ongoing support expectations early.

Plan a review with real users before release. Feedback is most useful when there is still time to improve the experience.