Tailoring in Project Management: What It Means and Why It Matters
Tailor to context is the least controversial sentence in project management and among the hardest to act on, because on most projects nobody is confident they are allowed to. The framework came from the PMO, the template has thirty fields, the gate review asks for eleven documents, and a project manager who leaves three of them out has made a decision they may have to defend with nothing in writing to defend it with.
That is what the emphasis is about. Tailoring is a deliberate, reasoned and recorded decision about how much of a practice this project needs, taken by somebody with the standing to take it. Every word there is working. Deliberate rules out drift. Reasoned rules out preference. Recorded is what makes it defensible in six months. And somebody with the standing to take it is the part organisations most often leave out, which is why a great deal of tailoring happens quietly and gets called something else.
What is actually being decided
A practice exists to produce something: a decision, a piece of evidence, a shared understanding, a control over a risk. Tailoring asks what this particular project needs from that practice and sets the amount accordingly. The answer runs in both directions, and the two failure modes look nothing like each other.
Over-application is the familiar one. A framework built for an organisation's largest and riskiest work, applied to a six-week internal change, produces effort that changes no decision: a risk register with four entries nobody opens, a design authority review for a design nobody disputes, a benefits plan for a saving somebody already signed off. The cost is not only the hours. A team spending a third of its time on artefacts that inform nothing learns that the framework is theatre, and that lesson travels with them to the project where the framework mattered.
Under-application is rarer and worse. A safety-critical or contractually exposed project run with the controls of an internal tool build reaches the point where somebody asks how a decision was reached, and the answer is that a conversation happened in March. Tailoring carries no licence to reduce, and where the consequence is high the honest tailoring decision sometimes increases what the standard framework asks for.
Why the Eighth Edition leans on it
Section 3.2 of the PMBOK® Guide Eighth Edition puts the case for tailoring directly, and three features of the edition make that emphasis necessary rather than decorative.
The first is that the processes came back. Forty named processes in a book invite a reading the book itself rules out, which is that a well-run project performs all of them. Tailoring is the counterweight, and it has to be loud enough to be heard over a process list.
The second is where the tailoring material sits. It is inside each performance domain, next to the practice being described, instead of in a chapter of its own that a reader reaches long after deciding what to do. Putting the scaling guidance beside the full description makes the cutting-down decision an ordinary part of reading about the practice.
The third is that the work in scope has become much more varied. One organisation now runs regulated hardware, a software product on a two-week release cadence, an office move and a data migration, and a single framework fitting all four is either unusable for the first or negligent for it. Refusing to tailor does not leave you with one clean standard process. It leaves you with four frameworks and a standing argument about which one applies.
The rig and the flight hardware
An aerospace company was building a ground test rig to qualify a new actuator assembly. The rig was steel, stood on the floor of the assembly hall, and would never fly. The organisation had one project framework, written for flight hardware, requiring full configuration control, three formal design reviews and qualification evidence for every component.
Applied unaltered, that framework added an estimated four months to a nine-month build, and the first schedule said so plainly. The tailoring conversation took an afternoon and put one question to every control: is this here because of airworthiness certification, or because it is good practice on a large project?
Most of the controls were the second kind, and those were scaled. The three formal design reviews for the rig's own structure became one, held early enough that the design could still move. Component-level qualification evidence was dropped for the rig frame and kept for anything in the load path. Configuration control, the expensive one, stayed in full force for the single interface where the rig met flight hardware, and that interface also gained a review the standard framework had never asked for, because a rig that loads a flight component wrongly ruins a part worth more than the rig.
The build took ten months. The written tailoring decision ran to two pages and went into the project record, and when an auditor asked about the missing design reviews eighteen months later, answering took four minutes.
For a PMP® candidate, what helps is seeing that tailoring turns up in situations as a question about proportion, and the answer is almost never at either extreme. A small project carrying a heavy governance requirement is not posing the question of whether governance is good. It is asking which parts of it serve a decision on this project, and who can authorise the rest to be scaled. Look for the consequence sitting behind a control before deciding how much of it to keep. Working through that across projects of quite different sizes and risk levels is how a structured PMP exam preparation course handles tailoring.
Put one question to the three most expensive things the framework demands: what decision does this change? A control that changes no decision here is a candidate for scaling, and the answer gets written down with a name against it, because tailoring that nobody recorded is indistinguishable, six months later, from tailoring that nobody did.
Interested in going further?
The hard part of tailoring is showing why, to somebody who was not in the room when the decision was taken. Omega's PMP® Exam Preparation works through decisions where the proportionate answer has to be justified as well as chosen.
The case for tailoring, and the scaling material inside each domain, are both in the PMBOK® Guide Eighth Edition.
Ad · Amazon affiliate link.
References
A079: What Should You Tailor on a Project?
A080: Tailoring the Life Cycle and Development Approach
A083: The Four-Step Tailoring Process Explained
A087: Tailoring Never Stops: Ongoing Improvement in Delivery
A089: Project Diagnostics: When Your Delivery Approach Is Not Working
PMP and PMBOK are registered marks of the Project Management Institute, Inc.
