Every organisation runs a taxonomy of the work it does. Nobody in the executive team wrote it, most of it is inherited, and it silently determines what gets a budget line, a leader and a seat.
Somewhere in your enterprise there is a list of the domains the organisation recognises. It may be a functional structure, a capability model, a set of policy areas, or the tabs on a governance pack. It has perhaps ten to twenty entries. Each one has an owner, a budget, and a person who can be summoned to explain it.
Everything else is a sub-process. Sub-processes live inside domains, are performed by people whose job title names something else, and are reported as part of a larger heading. They have no owner in the sense that matters, and they compete for attention with whatever they were filed under.
The distinction is administrative in appearance and consequential in effect. And it changes rarely enough that when a change happens, it is worth studying.
The Strategic Context
A teaching source for a project management unit was revised between 2012 and 2013, and the revision is unusually legible because both versions survive.
In the earlier version, the discipline is described as having nine knowledge areas — integration, scope, time, cost, quality, human resources, communications, risk and procurement. Stakeholders appear once in the entire deck, as a single process called Manage Stakeholders, sitting inside the monitoring and controlling group. One activity, in one place, at the back end.
In the later version there are ten. The tenth is stakeholder management, and it is not merely added to a list. Identify Stakeholders moves into the initiating group — among the first two processes a project performs, alongside the charter itself. A stakeholder planning process enters planning. An engagement process enters executing. The elements diagram, which had shown nine, gains a tenth.
A domain that had been one control activity at the end became a management area with standing equal to cost, time and scope, and its identification moved to the first thing you do.
What this evidence is, stated precisely. No edition of the underlying guidance is in the supplied material. What is documented is that a teaching source's account of that guidance changed in this manner between two dated versions. That the underlying editions changed correspondingly is an inference [FACT CHECK REQUIRED]. Two things support it: the deck's citations move from a 2008 edition to a 2013 one, and a second deck revised in the same window adds six slides of stakeholder material, every one citing a 2013 edition where its predecessor cited nothing. It remains an inference, and the argument below does not depend on it. What matters for an executive is the shape of the move, which is checkable inside any organisation regardless of what a standards body did.
What Leaders Commonly Misread
The first misreading is that classification is descriptive. It is not. A taxonomy allocates three things that are genuinely scarce: an owner, a budget line, and a place on an agenda. Something classified as a domain acquires all three. Something classified as a sub-process acquires none of them and instead borrows attention from whatever it sits under — which means it is funded from a budget defended by someone with different priorities.
The second misreading is that promotion is a matter of importance. Organisations frequently agree that something matters a great deal and continue to file it as a sub-process, perceiving no contradiction. Importance is a judgement; classification is a structure. They can disagree for years, and where they do, the structure wins every allocation decision.
The third misreading is that reclassification is a naming exercise. The revised teaching source is instructive here precisely because it is imperfect. Its slide listing ten knowledge areas is followed by an unrevised slide still referring to "the nine knowledge areas". A stakeholder engagement process appears in two groups at once. One citation slide was updated only partially. [FACT CHECK REQUIRED]
The residue outlives the deck. Two years on, the same institution's website carried two incompatible accounts of the phase this change affected: one page listed the phase's outputs as they stood before the reclassification; another, describing that same phase in detail, had replaced one and did not mention it. Neither was wrong on its own terms. Nobody had gone back for the first.
Those defects are not a reason to dismiss the source. They are the most useful thing in it. A reclassification propagates unevenly, and the residue is exactly what one looks like two years in, in any organisation. The declaration is easy. Completing it takes years and nobody tracks the remainder.
A fourth misreading is that this concerns stakeholders. It does not, and the boundary is worth stating plainly. How to read a stakeholder set — who is exposed rather than merely interested — is a different subject with its own method in [Related article: Your Stakeholder Map Measures Attention, Not Exposure]. Who holds the power to redefine what an initiative is for is another, treated in [Related article: Drivers, Supporters and Observers: Who Is Allowed to Change What Your Programme Is For]. This article proposes no stakeholder instrument, no mapping and no axis. Stakeholders are the worked case; the subject is classification.
Reframing the Issue
The reframing is to treat your organisation's taxonomy as a standing capital allocation, and to review it as you would review any other.
That framing produces an unfamiliar question. Not what should we spend on next year? but what does our current list of recognised domains commit us to spending on, indefinitely, without anyone re-approving it? Every domain has an owner who will defend a budget. Every sub-process has no one.
Three diagnostics follow, and each is answerable in an afternoon.
Where does effort concentrate that classification does not recognise? Look for work absorbing significant senior time under a heading that names something else. Sustained effort against a category that does not exist is the clearest signal a sub-process has outgrown its filing.
What fails repeatedly across unrelated initiatives? A failure mode recurring in programmes with nothing else in common is usually a missing domain. Where it recurs inside one programme, it is a delivery problem; where it recurs across many, it is structural.
What has no owner who can be summoned? For each significant category of work, name the individual who would be asked to explain a failure in it. Where no name exists, the work is being done by whoever notices.
Note what the reframing is not. It is not an argument that a standard method fails to transfer between contexts, which is examined in [Related article: Why "The Principles Apply to Any Project" Is Only Half True], nor that governance instruments encode assumptions about the kind of work they were built for, which is the subject of [Related article: What Kind of Work Were These Instruments Built For?]. Both concern what a framework assumes. This concerns what its internal structure asserts about standing.
Strategic Analysis
Why promotion moved the identification to the front
The most informative detail in the revision is not the tenth area. It is that Identify Stakeholders moved into the initiating group.
A process in monitoring and controlling is performed on something that already exists. A process in initiating is performed before the shape of the thing is settled, which means its output can change what gets built. The move is therefore a statement about when the work has to happen for it to be worth anything — and by implication, an admission that performing it later had not been working.
That is the general pattern worth extracting. When something is promoted from sub-process to domain, look at where in the sequence its first activity lands. If it moves earlier, the reclassification is substantive: the discipline concluded that the work was being done too late to affect anything. If it merely gains a heading in the same position, the promotion is nominal.
The same test applies inside an enterprise. A bank that elevates model risk from an activity inside compliance to a domain of its own has done something real only if model review now happens before a model is built rather than after it is in production. If the review still occurs at the same point and simply reports to a new committee, the organisation has added a governance layer and changed nothing.
The cost of a promotion, which nobody costs
Reclassification is presented as a structural tidy-up and is in fact an expensive act with a long tail.
A new domain requires an owner senior enough to be heard, which usually means taking someone from somewhere else. It requires a budget, which comes from domains that will resist. It requires a place on agendas that are already full, which means something is displaced. And it requires the taxonomy's other entries to be redrawn at their boundaries, because a new domain is carved out of existing ones and the parties losing territory rarely concede it cleanly.
The financial services sector has run this repeatedly over two decades — conduct, operational resilience, model risk, data — and the pattern is consistent. The declaration takes a board meeting; the completion takes three years, and the residue outlasts both.
None of which argues against doing it. It argues for costing it honestly and tracking completion rather than declaration, because a half-promoted domain has cost the disruption and not yet returned the benefit.
What the enterprise should conclude from someone else's reclassification
When a profession or a regulator promotes something, the useful executive response is not to copy the change. It is to ask what evidence produced it.
A discipline that moves an activity from the back to the front of its own process has, in effect, published a finding: that doing this work late produced failures reliably enough to justify restructuring around it. That finding is available to you whether or not you adopt the taxonomy — and it is available years before the same lesson arrives through your own failures.
The question to put to a leadership team is therefore narrower and more useful than "should we restructure?" It is: what are we currently doing at the point in the sequence where this discipline concluded it was too late?
Decision Framework
Five steps, run against the organisation's own taxonomy rather than anyone else's.
1. Write the list. The domains your organisation formally recognises — the ones with an owner, a budget line and a standing agenda item. Ten to twenty entries. Most executive teams have never seen this written down in one place, and the act of writing it produces disagreement about what is on it.
2. Name the owner of each, and the person who would answer for a failure. Where those are different people, or where either is missing, the domain is nominal.
3. Apply the three diagnostics. Where does effort concentrate without recognition; what fails across unrelated initiatives; what has no summonable owner. Each produces candidates for promotion.
4. For each candidate, apply the sequence test. If this were promoted, would its first activity move earlier in the process? If the honest answer is no, the promotion is a reporting change and should be described as one.
5. Cost the promotion before declaring it. Name the owner, the budget source, the agenda slot displaced, and the domains whose boundaries are redrawn. Then set a completion measure — not a declaration date, a measure of when the residue is gone.
A supporting convention: track promotions to completion for three years. The half-finished reclassification is the common outcome, and it is invisible because the declaration was minuted and the residue was not.
From Strategy to Execution
Immediate. Complete steps one and two at the next executive meeting. It requires no preparation, it takes forty minutes, and the disagreement it produces about what is actually on the list is the most useful part.
Medium term. Run the diagnostics against the last two years of programme post-mortems, looking specifically for failure modes that recur across initiatives with nothing in common. This is where missing domains are most visible, and the material already exists.
Long term. Establish that the taxonomy is reviewed deliberately rather than inherited. Once every two or three years is enough. The review's purpose is not to reorganise but to ask which categories have stopped matching the work — and organisations that never ask it end up with a structure calibrated to problems they solved a decade ago, staffed by people defending territory that no longer contains anything.
Two connections are worth naming: whether a promotion is worth making at all is a question best asked before committing, per [Related article: What Is the Risk of Not Doing It?]; and where it concerns commercial exposure rather than delivery practice, the allocation question in [Related article: Risk You Transfer Is Risk You Still Own] applies directly.
Signals to Monitor
- Work performed under a heading that does not name it. Track where senior time actually goes against the categories used to report it. Sustained divergence is the promotion signal.
- The same failure mode across unrelated programmes. Not a delivery problem. A missing category.
- Policies filed under a former parent after a reclassification. The residue measure. Count them annually; the count should fall.
- A process appearing in two frameworks at once. Evidence of an incomplete promotion, and a reliable source of confusion about who owns it.
- New domains without a budget source. A domain funded from goodwill is a sub-process with a better title, and it will revert within two cycles.
- Professional or regulatory reclassification in your sector. Read it as published evidence about what fails when performed late, whether or not you adopt the category.
Questions for the Leadership Team
- Can this team list the domains our organisation formally recognises, and would we agree on the list?
- For each, who would we summon if it failed — and are there categories with no such person?
- What failure mode has appeared in three unrelated programmes in the last two years?
- Of the reclassifications we have declared in the last five years, which are actually complete?
- Where a discipline or regulator in our sector has recently moved something to the front of its process, what are we still doing at the back of ours?
- If we promoted something tomorrow, whose budget would fund it and whose agenda slot would it take — and have we asked them?
Closing Perspective
Taxonomies look like filing and behave like constitutions. They determine who is in the room, what has a defender, and which work is performed by someone whose job it is rather than by whoever notices.
Most organisations inherit theirs and never revisit it, which means their structure encodes a set of conclusions drawn years ago about what mattered — conclusions that were probably right then and have not been tested since. The categories persist; the work moves.
When a discipline restructures itself, it is publishing evidence about what it learned failed. The valuable response is not to adopt the new list. It is to look at your own, ask which entries have stopped matching the work, and notice what your organisation is still performing at the point where somebody else concluded it was already too late.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.