From business need to a clear project brief.
Five decisions that turn a business objective into a shared brief for design, engineering and delivery.
- 01Business purpose
- 02Defined scope
- 03Delivery plan
01 / Describe the intended change
Describe the work that should become easier, clearer or more dependable. Identify who does it today, where the process causes difficulty and what should happen differently. “Customers should be able to submit a complete project enquiry” establishes an outcome that both a business owner and an engineer can discuss. Pages, features and integrations can then be considered in relation to that outcome. Keep the opening brief concise, explain the purpose of each proposed capability and record the decisions that remain open.
02 / Walk through one complete journey
Follow one representative task from first contact to resolution. For an enquiry, consider how a visitor understands the service, chooses the relevant subject, submits their details and receives confirmation. Continue into the organisation: who reviews the request, what information do they need and how does the response reach the customer? This gives each interface a purpose and makes handovers between people and systems visible. Document the normal journey alongside a few meaningful exceptions, such as incomplete information or a request that needs another team.
03 / Make constraints visible
Bring the practical conditions into the brief early. Which existing systems must remain? Who owns the content and data? Which languages, devices and approval steps matter? Is the first release tied to a particular business event? Distinguish confirmed requirements from assumptions and questions that need investigation. For each unresolved dependency, name the responsible person and the next decision. A shared view of these constraints gives the team a sound basis for comparing implementation options and deciding what belongs in the first release.
04 / Define how the work will be accepted
Write acceptance criteria as conditions someone can check. A visitor can complete the agreed journey on a phone. A submitted enquiry is saved and receives an accurate confirmation. An authorised team member can retrieve the information needed for review. Each criterion should connect a starting condition with an expected result. Agree who will accept the work and which examples they will use. When priorities change, these criteria provide a reference for discussing the effect on functionality, delivery and the agreed scope.
05 / Plan for the day after launch
Establish how the solution will be operated after handover. Name the people responsible for content, access requests, software updates and support. Agree how changes are approved and what continuing support includes, with implementation and ongoing responsibilities set out clearly in the proposal. A useful brief leaves room for engineering judgement while giving the business and delivery teams a shared basis for decisions. It should be clear enough to commission the next stage, review progress and understand what successful handover involves.