A method that can be applied to every project is not the same as a method that should be applied to every project in the same way — and enterprises routinely lose money in the gap between those two statements.
The most widely repeated claim in project management is also the least examined: that the discipline is generic. That its principles hold whether you are organising a small domestic undertaking or building a submarine. That the fundamental processes apply across profit and not-for-profit, across service delivery and manufacturing, across every scale and sector.
The claim is stated plainly and deliberately in serious teaching material, and it is not a careless one. It is defensible, it is useful, and it is the basis on which project management became a transferable profession rather than a set of trade-specific customs.
It is also the intellectual foundation of one of the more expensive mistakes large enterprises make: the belief that because a method applies everywhere, it should be applied everywhere in the same form, at the same intensity, with the same artefacts and the same gates.
The universality claim is true. The operational conclusion most organisations draw from it is not.
The Strategic Context
Consider how the claim is usually taught. Project management is presented as generic, and then — often in the same document — a taxonomy of fundamentally different project types is introduced to give the generic content something to attach to. One such taxonomy divides projects along two axes: whether the organisation is profit-driven or not-for-profit, and whether the work produces a service or a manufactured output. Four quadrants: not-for-profit service, not-for-profit manufacturing, profit-driven service, profit-driven manufacturing.
The teaching position is that the fundamental processes apply to all four. That position is coherent. Each quadrant requires the work to be defined, sequenced, resourced, risk-assessed and closed out. The vocabulary genuinely transfers.
But notice what the taxonomy does, whatever the reason for including it. It supplies the context without which generic content is hard to reason about at all — because no one can think clearly about scope, benefit or stakeholder without knowing what kind of enterprise they are standing in. So the material holds two propositions together: context shapes how the content is understood, and process applies regardless of context.
Both can be true, and the source treats them as compatible. The interesting question for an executive is which of the two matters more when designing how an enterprise runs its portfolio — and the answer, consistently, is the one that gets less attention.
What Leaders Commonly Misread
That transferability implies uniformity. A method being applicable across contexts says something about the method's abstraction level. It says nothing about the correct intensity, sequence, artefact set or decision cadence in any specific context. Those are calibration questions, and calibration is where nearly all the value and nearly all the waste sit.
That standardisation reduces risk. It reduces variance, which is not the same thing. Applying a heavyweight governance model to small, reversible, fast-cycle work does not make that work safer; it makes it slower and more expensive while adding no protection, because the protection was designed for a failure mode the work does not have. Applying a lightweight model to large, irreversible, capital-intensive work is the mirror error and considerably more dangerous.
That a single method is what enables comparison across a portfolio. Portfolios need comparable information — expected value, capital required, capability drawn, reversibility, timing. They do not need identical processes to produce it. Conflating the two is how organisations end up imposing a common delivery method for the sake of a common reporting line.
That the debate is about which method is right. Enterprises spend substantial energy on whether to adopt one body of knowledge or another, or whether a structured method suits them better than an adaptive one. [FACT CHECK REQUIRED: the major reference frameworks have all been revised substantially in the past decade; the PMBOK® Guide in particular has moved from a process-and-knowledge-area structure towards a principles-based one, and ISO 21500 has been revised with a broadened scope. Confirm current editions and structures before publication.] If those revisions are as described, the direction of travel would itself be instructive — away from prescribed process and towards principles requiring judgement, which would amount to a tacit concession that calibration was always the harder problem. [FACT CHECK REQUIRED: confirm the direction and substance of these revisions before publishing this characterisation.]
Reframing the Issue
The reframe: method is generic; governance is contextual; and enterprises confuse the two because both are administered by the same function.
Separate them and the picture clarifies.
Method is the vocabulary and the toolkit — the work breakdown, the schedule, the risk assessment, the benefits map. These genuinely do transfer. A capable delivery professional can move between sectors and remain capable, which is the strongest available evidence for the universality claim.
Governance is the decision architecture wrapped around the method — how much evidence is required before commitment, how often position is reviewed, who may approve what, how much is spent on assurance, what triggers escalation. None of this transfers, because all of it is a function of properties that vary enormously between contexts: how reversible the commitment is, how long until consequences appear, how severe failure would be, and who bears it.
The universality claim is a statement about method. Most organisations act on it as though it were a statement about governance.
The Same Principle in Two Industries
Two hypothetical cases make the point. A professional services firm delivering client engagements operates in a context where most commitments are short, consequences appear within weeks, failure is recoverable through the relationship, and the binding constraint is skilled people's time. Governance calibrated to this context should be light, fast, and concentrated at the point of taking work on — because that is where the irreversible decision sits. Once an engagement is accepted, most subsequent decisions are adjustable. Heavy in-flight governance in this setting consumes the very resource that is scarce and protects against a failure mode that is largely absent.
A manufacturer commissioning a new production facility operates in an inverted context. The commitment is long, consequences appear over years, failure is expensive and partly irreversible, and the binding constraints are capital and physical sequence. Here, front-end governance must be heavy — because once foundations are poured and long-lead equipment is ordered, the option set has genuinely closed. In-flight governance must also be substantial, because the interval between a decision and its visible consequence is long enough for several more decisions to be built on top of a wrong one.
The method is the same in both. A work breakdown is a work breakdown. But an enterprise operating in both modes — and many do, particularly manufacturers with substantial service arms — that imposes one governance standard across both will systematically over-govern one and under-govern the other. It will usually over-govern the fast work, because governance frameworks tend to be designed by the people responsible for the large capital decisions, and generalised from there.
The cost is asymmetric and mostly invisible. Over-governed fast work shows up as delay and frustration, which are attributed to bureaucracy in general. Under-governed slow work shows up as a large write-down several years later, attributed to the specific circumstances of that initiative.
Decision Framework
Calibration should follow the properties of the work, not the preferences of the function that owns the framework. Four dimensions determine governance weight.
| Dimension | The question | Implication |
|---|---|---|
| Reversibility | If wrong, can we undo it, and at what cost? | Irreversible commitments justify heavy front-end evidence |
| Consequence latency | How long until we would know? | Long latency requires deliberate detection design |
| Failure severity | Who is harmed, and how badly? | Safety, sovereign and regulatory exposure raise the floor |
| Capability draw | Does this consume scarce enterprise capability? | High draw needs portfolio-level, not project-level, control |
A practical rule follows: govern in proportion to irreversibility, not in proportion to budget. Most enterprises calibrate on spend, which is a poor proxy. A modest investment that commits the organisation to a technology architecture for a decade deserves more scrutiny than a larger one that is fully reversible within a year.
This produces a small number of governance tiers — typically three — rather than a single standard or a proliferation of exceptions. Tiers are defined by the four dimensions above, and work is assigned to a tier at initiation, with reassignment at each boundary if its properties change.
From Strategy to Execution
Immediate. Take the current portfolio and score every initiative on reversibility and consequence latency. Then compare that to the governance each currently receives. The mismatches will be immediately visible, and they will not be random — there will be a systematic bias in one direction that reveals how the framework was designed.
Medium term. Replace the single standard with a small number of tiers, and be explicit that lighter governance is a deliberate calibration rather than an exemption. The language matters: an exemption implies the standard was right and this case is special, which invites erosion. A tier implies the standard was always contextual.
Long term. Build the capability that tiered governance actually depends on, which is the judgement to place work in the right tier. This is the point most standardisation programs miss. A single method survives because it requires no judgement to apply. Tiered governance requires people who can assess reversibility and consequence latency accurately — and building that judgement is a capability investment, not a process change. [Related article: Accountability Without Authority: How Organisations Design Delivery Leadership to Fail]
Signals to Monitor
- Exception volume. A framework generating constant exceptions is miscalibrated, and the exceptions are the organisation telling you where.
- Governance cost as a proportion of initiative cost. If small initiatives carry proportionally more overhead than large ones, the calibration is inverted.
- Delivery teams maintaining shadow processes. A reliable indication that the mandated method does not fit the work, and that people are complying and working around simultaneously.
- Large write-downs on initiatives that passed every gate. Suggests under-calibration on irreversibility rather than a failure of the gates themselves.
- Method debates displacing calibration debates. When the discussion is about which framework to adopt, the harder question is being avoided.
Questions for the Leadership Team
- Do we apply one governance standard across work with fundamentally different reversibility profiles — and if so, which direction is the bias?
- What proportion of our governance effort is spent on decisions that are cheaply reversible?
- Which of our initiatives commit the enterprise irreversibly, and do they receive proportionally more scrutiny than their budget alone would suggest?
- When teams work around our mandated method, what are they telling us?
- Do we have people capable of judging which governance tier a piece of work belongs in — and would we trust their judgement?
Closing Perspective
The generic nature of project management is a genuine achievement. It made delivery capability portable, gave the field a shared language, and allowed hard-won lessons to move between industries that would otherwise have had to learn them separately.
But portability of method was never a licence for uniformity of governance, and the enterprises that read it that way pay twice — once in the friction imposed on work that never needed the protection, and again in the exposure carried by work that needed considerably more.
Related article: What Must Be True: The Assumptions Register as a Strategy Instrument
Related article: What a Stage Gate Is Actually For
Related article: Accountability Without Authority: How Organisations Design Delivery Leadership to Fail
About the author
Kevin Jogin is Founder & Principal Advisor at EraNorth. Meet the Founder.