A project method is valuable only while its assumptions about the environment remain useful.
One of the easiest ways to create project bureaucracy is to standardise a method without standardising the conditions in which projects operate. A regulatory infrastructure project, a new digital product, a plant relocation and a monthly software release may all be called projects, but they do not contain the same uncertainty, reversibility, stakeholder exposure or cost of failure.
The supplied MPM416 material makes the point directly: one size does not fit all. It distinguishes plan-driven, change-driven and time-driven approaches and argues that project-management practices should be tailored to project characteristics and external conditions rather than applied uniformly.
The strategic challenge is deciding what to tailor, how far to tailor it and who has authority to make that judgement.
The Strategic Context
Traditional project-management disciplines were strongly shaped by engineering, construction and defence contexts where planning, decomposition, scheduling and control could create substantial value. The supplied study material describes this as a comparatively “hard” view of project management, associated with structured goals, work breakdown, schedule control and techniques such as PERT and CPM.
As project management expanded into organisational change, technology and more socially complex environments, a “soft” perspective became more important. Stakeholder behaviour, communication, ambiguity, change adoption and social interaction cannot be reduced to a network diagram.
The conclusion should not be that hard methods are obsolete. The stronger conclusion is that the management system must fit the uncertainty profile. A technically demanding project may require rigorous planning and still need adaptive stakeholder management. A digital innovation may need iterative requirements while maintaining strict controls around cybersecurity, safety or financial authority.
Tailoring is therefore not permission to abandon discipline. It is the discipline of choosing the right level and form of control.
What Leaders Commonly Misread
The first misread is equating consistency with uniformity. Consistency means comparable decision standards, clear accountability and reliable governance. Uniformity means applying the same artefacts and process intensity regardless of context. The first can strengthen an organisation; the second can create unnecessary work or false confidence.
The second misread is treating uncertainty as poor planning. Some uncertainty comes from inadequate analysis. Other uncertainty is inherent because the future condition cannot yet be known. When customer behaviour, technology, regulation or interfaces are genuinely evolving, demanding a fully fixed plan may force teams to manufacture precision rather than reduce uncertainty.
The third misread is using agility as a synonym for low governance. A change-driven approach can require tighter decision cadence, clearer product ownership, stronger feedback loops and more transparent prioritisation than a conventional plan-driven project. Flexibility without decision discipline becomes churn.
The fourth misread is tailoring only at project start. Environmental dynamism can increase after approval. A project that begins in stable conditions may encounter a regulatory change, supplier collapse, technical discovery or strategic reprioritisation. Tailoring must therefore be reviewable.
Reframing the Issue
The supplied economics and change notes define environmental uncertainty through complexity and dynamism. They also draw on Ansoff's environmental-dependence hypothesis: the challenges presented by the environment should influence the optimal mode of organisational behaviour.
For project leaders, the translation is straightforward:
The delivery approach should be a response to the environment, not an organisational ritual imposed upon it.
Three variables are especially useful.
Predictability: How confidently can requirements, interfaces and outcomes be specified in advance?
Consequence: What happens if the project is wrong, late, unsafe or non-compliant?
Reversibility: How easily can a decision or deliverable be changed once committed?
A project with high predictability, high consequence and low reversibility may justify extensive planning and assurance. A project with low predictability and high reversibility may benefit from rapid experiments and incremental commitment. Low predictability combined with high consequence is the difficult quadrant: experimentation may still be necessary, but it should occur inside tighter technical and governance boundaries.
Strategic Analysis: Tailor the Control System, Not Just the Documents
The source material identifies three broad approaches.
A plan-driven approach is appropriate where significant risk, regulation or consequences justify more extensive planning, monitoring and control. This does not mean change is prohibited. It means deviations require deliberate evaluation because the cost of being wrong is high.
A change-driven approach is appropriate where the project seeks an innovative outcome, requirements are difficult to define in advance and incremental improvements can deliver stakeholder value. The central management task is to learn quickly enough to make better subsequent decisions.
A time-driven approach is appropriate where speed is dominant and the work is sufficiently repeatable that only essential component processes are needed. The danger is assuming that urgency removes the need for governance; in reality it increases the need to identify which controls are essential and which can be simplified.
These are not mutually exclusive enterprise categories. A single program can contain all three. A hypothetical medical-technology program might use a change-driven approach for early product discovery, a plan-driven approach for regulated validation and a time-driven approach for a repeatable market-release process. Tailoring at component level can therefore be more intelligent than forcing the entire program into one label.
Related article: The Strategic Cost of Assuming the Old Normal Will Return
Decision Framework
A practical TAILOR test can guide the level of governance.
| Dimension | Question | Higher score generally implies |
|---|---|---|
| T — Threat of failure | What is the consequence of being wrong? | More assurance and explicit decision rights. |
| A — Ambiguity | How uncertain are requirements, interfaces or solutions? | More experimentation and shorter feedback cycles. |
| I — Irreversibility | How difficult is it to undo major commitments? | Staged investment and stronger gates. |
| L — Legal and regulatory exposure | What compliance constraints cannot be negotiated? | More formal evidence, traceability and verification. |
| O — Organisational novelty | How unfamiliar is the work to the organisation? | More learning, specialist support and review. |
| R — Rate of change | How quickly can the external environment invalidate the plan? | More frequent reassessment and adaptive planning. |
The result should not produce an automatic methodology. It should produce a governance conversation.
The tailoring decision should state what is being increased, reduced or changed: documentation depth, approval levels, planning horizon, iteration length, assurance intensity, change-control threshold, stakeholder cadence, procurement model, risk reviews or technical verification.
Equally important, the decision should define what cannot be tailored away. Safety obligations, ethical requirements, financial delegations and critical regulatory controls may remain mandatory regardless of delivery style.
From Strategy to Execution
Immediate action is to require a short tailoring rationale at project initiation. This should explain the project's uncertainty, consequence and reversibility profile and identify why the proposed management approach fits that profile. The goal is not another document; it is explicit reasoning.
Medium-term capability building requires giving project leaders more than one approved delivery pattern. Organisations can establish a small set of governance archetypes—such as regulated capital delivery, adaptive digital delivery and rapid repeatable delivery—then allow controlled tailoring within them.
Long-term positioning means developing managers who can diagnose context rather than merely follow process. A methodology cannot compensate for weak judgement. Tailoring works only when people understand the purpose of the controls they are changing.
Governance should also include review triggers. If uncertainty, risk exposure, stakeholder conflict or technical novelty increases materially, the project should reconsider its approach. Conversely, a project that has resolved major uncertainties may be able to simplify governance as it enters repeatable execution.
Signals to Monitor
Watch for teams producing documents that nobody uses; repeated approval delays caused by low-value governance steps; unstable requirements being hidden to preserve a baseline; projects choosing “agile” mainly to avoid accountability; safety or regulatory evidence being compressed in the name of speed; and identical governance being imposed on radically different project types.
Another strong signal is when teams can explain what the process requires but cannot explain why the control exists.
Questions for the Leadership Team
- Which project characteristics genuinely justify our current governance intensity?
- Where are teams creating false precision because uncertainty is not yet resolvable?
- Which controls are mandatory because the consequence of failure is unacceptable?
- Do project managers have authority to tailor, and is that authority itself governed?
- How often do we reassess whether the delivery approach still fits the environment?
- Are we confusing agility with speed or with reduced documentation?
Sources and Notes
This article is based on supplied MPM416 study material describing hard and soft project-management perspectives, environmental uncertainty, strategic flexibility and plan-driven, change-driven and time-driven tailoring. The tailoring notes cite Burgan and Burgan (2014), “One size does not fit all: Choosing the right project approach,” presented at the PMI Global Congress 2014—North America.
The study material attributes the environmental-turbulence framework to Ansoff (1984). Exact original publication details should be verified before formal external citation. [SOURCE DETAILS REQUIRED]
Closing Perspective
Good governance does not make every project look the same. It makes the reasoning behind different approaches visible, deliberate and accountable. The more varied the environment, the more important that distinction becomes.