Start with a decision, not a feature list
A useful brief explains what needs to change. “Build a dashboard” describes a format. “Help account managers identify unanswered requests before the end of the day” describes a problem. Identify the person, the decision and the information they need. This gives design and engineering a shared purpose.
Describe the journey and its exceptions
Write the normal sequence in plain language: a request arrives, someone checks it, an owner is assigned, and the outcome is recorded. Then add exceptions. What happens when information is missing, an approval is withdrawn or an external system is unavailable? These details often determine more work than the main screen.
Make acceptance observable
Replace “fast and easy to use” with a small set of concrete checks. Who can access each view? What data is shown? Which actions must leave a record? Include examples using fictional data. Agree how the delivered work will be reviewed, who can approve it and how defects will be distinguished from new requests.
Put boundaries around the first release
A first release should solve a complete, bounded problem. Separate essentials from useful later additions. List dependencies, available systems and decisions that are still open. A clear exclusion is not a weakness; it prevents an estimate from silently becoming a different project.
Prepare a short handover pack
Bring a process sketch, sample outputs, the people who will review the work, and any known deadline or budget constraints. Avoid sending production credentials or personal datasets during an initial enquiry. Access and data-sharing arrangements belong in a controlled onboarding process.
Practical guidance. Each engagement is tailored to the circumstances; specialist legal, tax or regulatory questions should be addressed with an appropriate professional.