Project charter and outcome map

From investment rationale to bounded authorization

A useful project starts with a defined problem rather than an extensive activity list. In our fictional training network, “we need a modern system” proposes a solution before establishing the need. Ask where booking breaks down, who is affected and what evidence exists. Duplicate registrations or uneven appointment allocation may be the real issue. Improving the current procedure could cost less than buying a replacement. A business case therefore describes the current situation and intended outcome, then compares credible alternatives, including continuing without the proposed change. That alternative is a comparison baseline, not an instruction to ignore the problem: it exposes the costs of delay and the risks retained by doing nothing.

The business case explains why investment is justified. A project charter authorizes the undertaking and establishes initial boundaries and authority. A management plan explains how the team will deliver and control it. A small organization may combine these functions in a short document, but they remain distinct. Signing a document does not create unavailable resources, and a detailed plan cannot replace proper authorization. A concise charter states purpose, the main deliverable, preliminary success criteria, sponsor, project manager, decision authority, milestones, assumptions, constraints and major risks. Initiation does not require every activity to be known. It requires clarity about what has been authorized and which decisions are still outstanding.

At a decision gate, compare current evidence with the justification and choose whether to continue, change, pause or stop under explicit authority. Money already spent does not prove that further spending is worthwhile, although future closure commitments still belong in the comparison. Record the decision, reasoning, approver and assumptions underlying the next step. A lower demand forecast should not be concealed to protect the project’s image. Orderly termination can be a responsible choice rather than a moral failure by the team. The intended result of initiation is an explainable beginning: an evidenced need, a justified option, bounded authorization and ownership of subsequent verification.