FDE Foundations · Module 3: Problem Framing & Scope
Writing the One-Page Brief
The one-page brief is the engagement's contract: problem, users, in and out of scope, success measures, constraints, risks. One page forces decisions.
10 min reading
Objectives
- Write a brief with problem, users, scope, success, constraints, risks
- State out-of-scope items explicitly
- Get explicit sign-off from the sponsor
The sections
A working brief has six short sections:
- Problem. One sentence with a number, from discovery.
- Users. Who touches the system and what they need.
- In scope. What you will deliver, stated as capabilities.
- Out of scope. What you will not deliver, named explicitly. This section prevents the slow drift that kills timelines.
- Success measures. The primary metric and guardrails with baselines and targets.
- Constraints and risks. Environments, access windows, security requirements, and the top three risks with owners.
Why one page
A page is short enough that the sponsor actually reads it and disagreements surface now rather than at delivery. If it does not fit on one page, the engagement is two engagements; split it and phase it.
Sign-off is a decision, not a courtesy
The brief is done when the sponsor replies with an explicit yes and the out-of-scope list is acknowledged. Silence is not sign-off. Changes after sign-off go through the change process you define in the same document.
The brief is not bureaucracy. It is the cheapest place to discover that two people want different systems.
Quick check
An optional 2-3 question self-check. Answers never leave your device, are not stored, and never count toward any assessment.
Exercise
Write a one-page brief for a fictional engagement: automating supplier invoice reconciliation at a mid-size retailer. Include all six sections, each under 60 words.
Pass criteria
Six sections present, out-of-scope names at least three items, success measures carry numbers, and the whole brief fits one page.