The method should change when the context changes; the obligation to produce decision-grade evidence should not.
Organisations often respond to inconsistent delivery by standardising harder. One methodology, one set of templates, one lifecycle, one reporting cadence and one approval architecture are imposed across every initiative in the hope that consistency will create control.
Consistency can help. But when projects differ materially in novelty, uncertainty, stakeholder complexity and delivery conditions, excessive standardisation can create a false sense of governance. Teams comply with the method while the method stops fitting the work.
The supplied MPM416 teaching material takes a different position: there is no single approach that can be applied to all projects all of the time. Tailoring can include the lifecycle and development approach, processes, engagement, tools, methods and artefacts. The strategic purpose is not methodological freedom for its own sake. It is to make the management system appropriate to the project's operating environment and needs.
The executive challenge is to tailor how work is governed without weakening what accountability must prove.
The Strategic Context
Project-management methods originally developed strongly around settings where decomposition, scheduling and control created major value. Those techniques remain useful. But the supplied course material also describes the expansion of projects into complex social and organisational environments where stakeholder expectations, change and uncertainty play larger roles.
That expansion creates a recurring governance problem. A method designed for one type of work can become ritual when applied indiscriminately to another.
A repeat plant modification, a regulatory remediation program, a software discovery initiative and a major organisational transformation may all be called projects. They should not automatically use identical planning horizons, design gates, contracting approaches, stakeholder practices or evidence requirements.
The contingency perspective described in the Silvius paper reinforces the same principle: projects differ, so project-management processes should adapt to project and organisational characteristics. Sustainability research extends the argument again by showing that even sustainability indicators may need to be configurable to project context rather than imposed as one universal list.
Tailoring is therefore not a niche project-management technique. It is a practical expression of systems thinking.
What Leaders Commonly Misread
The first mistake is to treat tailoring as permission to remove governance. Teams sometimes interpret "fit for purpose" as a reason to avoid documentation, independent review or decision gates. That is not tailoring. It is weakened accountability.
The second mistake is to tailor only templates. Deleting fields from a form does not address a mismatch in lifecycle, commercial model, stakeholder process or decision rights.
The third mistake is to confuse methodological consistency with strategic control. Executives do not need every project to look identical. They need every project to answer the critical questions appropriate to the investment.
Those questions include:
- What outcome is being pursued?
- What value is expected?
- What evidence supports the chosen approach?
- Who can make which decisions?
- What risks and assumptions are material?
- What commitments are reversible?
- How will the organisation know whether the project should continue?
A tailored approach that answers those questions clearly may be better governed than a fully compliant project that produces large volumes of low-value documentation.
Reframing the Issue
The real distinction is between standardising controls and standardising methods.
Controls express what the organisation must know or protect: safety, financial authority, regulatory compliance, investment logic, security, quality, decision rights, benefits ownership and material risk.
Methods describe how a team will create the evidence and perform the work.
The first category should change slowly. The second should be deliberately adaptable.
This distinction allows a mature organisation to be both disciplined and flexible.
Related article: Strategic Flexibility: Match the Management System to Environmental Turbulence
Strategic Analysis: Tailor Around the Sources of Uncertainty
Tailor the lifecycle
When requirements and technology are mature, a more sequential lifecycle may support efficient planning and contracting. When requirements are uncertain or discovery is necessary, staged or iterative work may create better evidence before major commitment.
The question is not which lifecycle is fashionable. It is when the organisation can responsibly freeze decisions.
Tailor engagement
Stakeholder intensity should match consequence and dependency. A technically simple project can still require extensive engagement if communities, employees, regulators or customers can materially affect acceptance and value. Conversely, not every low-risk internal improvement needs an elaborate stakeholder architecture.
Tailor evidence
High-consequence decisions need stronger evidence. A reversible pilot can tolerate more uncertainty than an irreversible capital commitment. The evidence standard should therefore rise with consequence, uncertainty and irreversibility.
Tailor controls to interfaces
Complexity often lives at interfaces: project to operations, customer to supplier, technology to process, program to project, or temporary organisation to permanent organisation. Tailoring should put additional control where failure is likely to cross an interface rather than distributing equal administrative effort everywhere.
Tailor the commercial approach
Although the supplied material does not prescribe contract models, its uncertainty logic has a clear implication: commercial commitment should reflect how well the work can be defined. Leaders should avoid forcing artificial certainty into a project simply because the organisation prefers a familiar procurement process.
That is an ERANORTH inference from the source material's contingency and uncertainty principles, not a claim that one commercial model is universally superior.
Decision Framework
A practical tailoring decision can be built around five dimensions.
| Dimension | Diagnostic question | Tailoring implication |
|---|---|---|
| Novelty | How familiar is the work? | More novelty requires more learning before lock-in |
| Uncertainty | How predictable are requirements and conditions? | Higher uncertainty favours staged commitments |
| Complexity | How many interacting elements and interfaces matter? | Increase integration and interface governance |
| Stakeholder consequence | Whose acceptance or behaviour controls value? | Increase participation and decision transparency |
| Irreversibility | What becomes difficult to change after commitment? | Raise evidence thresholds before crossing the gate |
Then preserve a common accountability spine across all projects:
purpose → business case → authority → risk/assumptions → evidence → decision → transition → benefit ownership.
Everything else should earn its place by helping the team manage the actual work.
From Strategy to Execution
Immediate action: Ask each active project to identify what has been tailored and why. If the answer is simply "because this is our methodology", tailoring has not occurred.
Medium-term capability: Replace methodology compliance audits with governance-effectiveness reviews. Test whether the chosen lifecycle, controls and artefacts produce useful evidence for decisions.
Long-term positioning: Build a small set of approved delivery patterns rather than one mandatory method. For example, organisations may maintain patterns for repeatable delivery, complex capital work, discovery-heavy digital initiatives and enterprise change. Each pattern should connect to the same authority and accountability framework.
Related article: The Iron Triangle Does Not Measure Strategic Success
Signals to Monitor
- teams produce templates that decision-makers do not use;
- approval gates occur after the key commitment has already been made;
- projects with fundamentally different uncertainty profiles follow identical lifecycles;
- "agile" or "tailored" becomes a reason to avoid accountability;
- methods are selected before the problem and context are understood;
- governance effort concentrates on formatting rather than assumptions, interfaces and decisions;
- operational stakeholders first engage seriously at handover.
Questions for the Leadership Team
- Which controls are genuinely non-negotiable across our organisation?
- Which parts of our current methodology exist because they create decision value, and which exist because they have always been there?
- Where are projects being forced to commit before uncertainty has been reduced sufficiently?
- Do we tailor stakeholder engagement according to actual dependency and consequence?
- Are our gates positioned before irreversible decisions or merely before documentation milestones?
- Could a project comply fully with our method and still avoid answering whether it should continue?
Source References
- University of South Australia, MPM416 Week 1 teaching material on tailoring, complex project environments and project context.
- Silvius, G. (2017), Sustainability as a new school of thought in project management, Journal of Cleaner Production, 166, 1479–1493.
Closing Perspective
The strongest project organisations do not choose between discipline and adaptability. They separate them.
They remain uncompromising about accountability, evidence, authority and value. They remain flexible about the methods used to achieve them.
That is the principle behind effective tailoring: change the project-management system until it fits the work, but never lower the standard of evidence required to justify the decision.