1.1Project origin & scoping note
The essentials in 30 seconds
- Every project is born from a need: clarify the problem before imagining the solution.
- The scoping note sets context, stakes, objectives and constraints: alignment on the "why".
- Reflex: a short note, validated by decision-makers — otherwise the project starts on a misunderstanding.
Running mini-case — Bilal gets a fuzzy request
Bilal, project manager in a 25-person distribution SME in Algiers, gets from the owner: "we need stock software, sort it out". Instead of rushing in, he spends a week questioning warehouse staff and the accountant, then writes a one-page scoping note: frequent stockouts, wrong inventories, objective and constraints. The owner validates it — the project starts on the real problem, not an intuition.
This same case runs through the course, the diagram, the script and the 48h challenge — and continues in 1.2, 1.3, 1.4 and 1.5.
1. Clarifying the need
Every project is born from a need: a problem to solve, an opportunity to seize, an obligation to meet. Before rushing in, you must formalize this need to make sure you solve the right problem.
That is the role of the scoping note: a short document setting out the project's context, stakes, objectives and major constraints.
2. The first structuring deliverable
The scoping note aligns stakeholders on the "why" and the broad lines of the "what". It avoids the classic trap of a project launched on a misunderstanding.
Well written, it serves as a reference throughout the project and as the basis for the charter (section 1.5).
🔎 Concrete example — 🔎 Concrete example — The problem before the solution
Scoping means questioning.
Request: "we need a mobile app".
Scoping: which problem? for whom? what expected benefit?
→ sometimes the real solution is not the one initially requested.Outcome: a project started on the right problem.
Reflex: get the note validated by decision-makers.
Section vocabulary
- Need / need statement
- The problem or opportunity behind the project, to clarify before any solution.
Simple example: The stockouts and wrong inventories Bilal found in his Algiers SME.
What it is not: the already-decided solution ("we need software").
Reflex: restate every request as "which problem? for whom?"
- Scoping note
- Short initial document: context, stakes, objectives, rough scope, constraints. Aligns stakeholders.
Simple example: The page Bilal gets the owner to sign before consulting vendors.
What it is not: a twenty-page detailed specification document.
Reflex: one page, validated in writing, before any costing.
- Context
- The situation justifying the project: what is happening, why act now.
Simple example: Three stockouts this quarter and a 12% wrong inventory at Bilal's.
What it is not: a vague urge to "modernize" with no triggering fact.
Reflex: date and quantify what makes the project urgent.
- Stake
- What is at stake: the expected benefit or the risk to avoid. Gives meaning and justifies investment.
Simple example: Sales lost every month and unhappy clients for Bilal's SME.
What it is not: a slogan ("excellence") with no concrete gain or risk.
Reflex: translate the stake into money, time or avoided risk.
- Constraint
- A limit imposed on the project (budget, schedule, regulation, resources) to know from the start.
Simple example: The capped budget and end-of-June deadline imposed on Bilal.
What it is not: a negotiable wish discovered along the way.
Reflex: list known constraints in the note, not after.
In practice — In practice — Writing a scoping note
- State the REAL need in one sentence, separating the problem from the solution (the "why" before the "what").
- Write the context (why now?) and stakes (what benefit, what avoided risk?).
- Set the targeted objectives and rough scope (what the project will broadly cover).
- List known major constraints (budget, schedule, regulatory) and key stakeholders.
Ready-to-say script — getting the note validated by the decider (1 min)
"Here is my understanding on one page: the problem is stockouts and wrong inventories; the stake is sales lost every month; the objective is reliable stock by end of June. Tell me what is wrong or missing — once validated, this note becomes our shared reference."
Say to the sponsor, note in hand: get the problem validated before talking solution.
Copy-paste template — one-page scoping note
NEED (the problem, not the solution): _______________
CONTEXT (why now?): _______________
STAKES (benefit / avoided risk): _______________
TARGETED OBJECTIVES: _______________
ROUGH SCOPE: _______________
CONSTRAINTS (budget, schedule, rules): _______________
STAKEHOLDERS: _______________
VALIDATED BY (name + date): _______________Small business / small project
Even for a two-week project: half a page is enough — need, objective, main constraint — validated by a simple written "OK".
Remote / multi-site
Remotely, misunderstanding costs double: send the note before the meeting and get each point validated aloud, not by silence.
Algerian SME
Bilal gets the owner himself to validate: in an SME where everything is decided at the top, a note unsigned by the boss is worthless against daily urgencies.
External client request
The note becomes a quote appendix: what it contains commits both parties and protects against "but I thought…".
✓ Best practices
- Separate the problem (need) from the envisioned solution.
- Get the note validated by the sponsor and requester.
- Keep it short: it is a reference, not a specification document.
✗ Common pitfalls
- Jumping straight to the solution without clarifying the need.
- Launching the project without decision-maker validation.
- Confusing scoping note (short) with specification document (detailed).
Key takeaways
- Every project is born from a need: clarify the problem before the solution.
- The scoping note sets context, stakes, objectives and constraints.
- It aligns stakeholders on the "why".
- It is the initial reference, basis of the project charter.
48h Challenge — apply tomorrow
State the need of a real project in one sentence (the problem, without the solution) and get it validated by the decider. If it holds, roll out the template above. 20 minutes is enough.
- I can explain the scoping note in one sentence.
- I've stated a real need, separating problem from solution.
- My note (or need) was validated by the decider.
Frequently asked questions
Scoping note, specification document, charter: what is the difference?
The scoping note is the short initial document setting out the need and broad lines. The specification document details precise requirements (the "what" in detail). The project charter (section 1.5) formalizes the launch and mandates the project manager. They chain from most general to most detailed. Each has its role: the note aligns on the why, the specification document fixes the precise what, the charter gives authority to act.
Who writes the scoping note?
Often the project manager in close connection with the sponsor and requester (internal or external client). The key point is validation by decision-makers: this validation turns an idea into an officially supported project with a clear mandate. Writing can be collaborative, but alignment responsibility lies with the project manager.
What is the scoping note for?