The most consequential project decisions are often made before the project manager is formally authorised to act.
A project charter can feel like the beginning. It names the project, establishes authority and gives delivery a formal starting point. Yet by the time a charter exists, many of the choices that will shape the project have already been made.
Someone has identified a need, opportunity, problem or obligation. A preferred response may already have emerged. Expectations have begun to form. Budgets may have been discussed. Stakeholders may have taken positions. An executive sponsor may already be advocating for an outcome. In some cases, a deadline has been announced before the work has been understood.
This is why leaders should not treat project initiation as an administrative prelude to “real” project management. It is an investment decision process in which the organisation decides what problem deserves attention, which response is worth pursuing, how much uncertainty is acceptable and what organisational capacity will be committed.
The Strategic Context
The supplied project-management study material identifies many possible sources of projects: a new business objective, legislation, client demand, market change, technology, an incident, an audit finding, a supplier issue or an internally generated improvement idea. It also distinguishes internal initiatives from externally driven projects.
That breadth matters. The source of a project affects the logic by which it should be judged.
A compliance project may have weak direct financial return but strong legal or operating necessity. A customer-driven project may strengthen revenue but overload a constrained engineering function. A technology initiative may improve capability but create new operating dependencies. An audit-driven project may reduce exposure without creating a visible commercial benefit.
The same project-management machinery cannot answer whether each of those initiatives deserves approval. That is an executive and portfolio question.
The study material also emphasises that projects operate inside an organisational environment of culture, governance, infrastructure, technology, resource availability, capabilities and established processes. These conditions can determine whether a theoretically attractive initiative is actually executable.
The practical implication is simple: a project does not enter an empty system. It enters a living organisation with existing priorities, politics, commitments, constraints and habits.
What Leaders Commonly Misread
A common mistake is to assume that once the project has been approved, the earlier decision process is no longer relevant.
It remains highly relevant because the project manager inherits the consequences of those earlier choices.
If the original need was poorly defined, the project may optimise the wrong outcome. If the option analysis was narrow, delivery may be locked into an inferior solution. If key stakeholders were excluded, resistance may appear later as a “change-management issue”. If resource assumptions were unrealistic, schedule pressure may be blamed on execution rather than on the approval decision.
Another common mistake is to treat the charter as the document that justifies the project. In the source material, the charter is better understood as the formal authorisation of a project and the authority to apply organisational resources. The justification is developed earlier through proposals, feasibility work, business cases, recommendations or other initiation documents.
These are different decisions.
A third mistake is to focus only on the project boundary. The supplied project-boundary model separates the sponsor and project inputs from the management processes that occur inside the project and from the end users and organisational process assets that sit beyond delivery. The strategic lesson is that the project boundary is narrower than the value boundary.
Reframing the Issue
The better question is not, “How do we start this project correctly?”
It is:
What sequence of decisions must be sound before the organisation deserves to call this a project?
That reframing moves initiation from documentation to decision quality.
It forces leaders to consider four layers before authorisation:
- Trigger: What changed, or what opportunity appeared?
- Strategic relevance: Why does the issue matter to the organisation now?
- Option logic: Why is a project the preferred response, and why this project concept?
- Commitment logic: What people, funding, authority and organisational attention are we prepared to commit?
The distinction is important because not every problem should become a project. Some issues may be better addressed through operations, policy, procurement, process management or by doing nothing.
The Decisions That Shape Delivery Before Delivery Begins
Define the trigger without prematurely defining the solution
An organisation may begin with “we need a new system”, when the underlying problem is poor data quality, fragmented accountability or an inefficient workflow. Once the solution is embedded in the problem statement, alternatives become artificially narrow.
Good initiation preserves the distinction between the need and the preferred response long enough to test alternatives.
Understand who benefits, who pays and who carries the disruption
The study notes repeatedly emphasise stakeholder identification and the possibility of conflicting expectations. Sponsors, customers, delivery teams and performing organisations can all have legitimate but different interests.
The executive task is not to eliminate those differences. It is to make them visible before approval so that trade-offs are deliberate rather than discovered under pressure.
Test the organisational context
Internal conditions can be more decisive than technical merit. A project may depend on specialist capability that is already committed elsewhere. A new technology may require data, infrastructure or skills the organisation does not possess. A transformation may need executive sponsorship that exists in title but not in practice.
These are not delivery details. They are investment conditions.
Identify the decision assumptions
Every project approval rests on assumptions about demand, cost, timing, capability, regulatory conditions, stakeholder behaviour or expected benefits.
The stronger the uncertainty, the more important it is to distinguish facts from assumptions. Assumptions should not be hidden in background calculations. They should be visible because they define the conditions under which the project remains sensible.
Preserve strategic traceability
The study material links project selection to corporate goals and to the strategic environment. This relationship should remain traceable after approval.
When strategy changes, a project that once made sense may no longer deserve the same priority. Continuing purely because money has already been spent confuses sunk cost with strategic relevance.
Related article: Project Selection Is Capital Allocation: Why Good Projects Must Sometimes Be Rejected
Decision Framework
Before authorising a project, an executive team can apply a six-question initiation test.
| Test | Executive question | Evidence expected |
|---|---|---|
| Need | What problem, opportunity or obligation is driving action? | Clear trigger and problem statement |
| Alignment | Which strategic objective does this support? | Explicit connection to strategy |
| Alternatives | What credible options were considered, including non-project options? | Comparative option logic |
| Feasibility | Can the organisation realistically execute the preferred option? | Capability, risk and constraint evidence |
| Value | What benefits justify the costs and disruption? | Business case or equivalent rationale |
| Ownership | Who owns delivery, transition and benefits? | Named sponsor, decision rights and operational owner |
A weak answer to any one of these does not automatically kill the proposal. It does identify where uncertainty remains and what must be resolved before commitment increases.
From Strategy to Execution
Immediate action: require every proposed initiative to identify the trigger, strategic objective, stakeholders, alternatives and core assumptions before it enters formal approval.
Medium-term capability: standardise the decision path from idea to proposal, feasibility, business case and charter. The aim is not bureaucracy. It is to make different decisions visible and to prevent one document from being used as a substitute for all of them.
Long-term positioning: connect project initiation to portfolio governance. New initiatives should compete transparently for capacity rather than entering the organisation through whichever sponsor has the strongest voice.
This changes the culture of initiation. The organisation stops asking only whether a project can be delivered and starts asking whether it deserves to exist.
Signals to Monitor
Leaders should be alert when:
- project objectives cannot be traced to a current strategic need;
- the preferred solution appears before the problem is clearly defined;
- stakeholders first become visible after approval;
- schedules or budgets are announced before feasibility is understood;
- the project manager cannot explain why this option was selected;
- assumptions are treated as facts;
- a project remains protected even after its original strategic rationale has weakened.
These are signs that decision risk has been transferred into delivery.
Questions for the Leadership Team
- What event or need actually triggered this initiative?
- Are we solving the underlying problem or merely implementing the first proposed solution?
- What alternatives were rejected, and on what evidence?
- Which assumptions would make us reconsider approval if they proved false?
- What scarce organisational capacity will this initiative consume?
- Who will own the benefits after the project finishes?
- If this proposal arrived today with no prior political support, would we still approve it?
Closing Perspective
A charter is an important governance threshold, but it is not the true beginning of a project.
The project begins as an organisational choice about where to direct attention, capital and capability. By formal authorisation, the quality of that choice may already be largely determined.
Executives therefore create better delivery outcomes not only by demanding stronger project management, but by improving the decisions that happen before project management formally starts.