Inside PMBOK® 8: Tailoring. Explore the PMBOK® Guide Eighth Edition… | by William Meller | May, 2026 | MediumSitemapOpen in appSign up<br>Sign in

Medium Logo

Get app<br>Write

Search

Sign up<br>Sign in

Mastodon

Inside PMBOK® 8: Tailoring

William Meller

7 min read·<br>May 12, 2026

Listen

Share

Explore the PMBOK® Guide Eighth Edition through the Inside PMBOK® 8 Series, a practical collection of guides explaining the updated global project management standard.

Before we start, you might think these notes are just tips, but they are parts of a complete delivery system. If you find value here, you are likely missing out on the specialized layers designed to help you navigate complexity:<br>The Standards: Understand the frameworks that govern high-impact delivery at Standards & Frameworks.<br>The Toolkit: Access the Free Resources to audit and upgrade your project documentation.<br>The Accelerator: For those ready to move from coordination to strategy, the VIP Premium Packs provide the systems to scale your impact.<br>The Reality of Project Tailoring<br>Have you ever found yourself strictly following a process that made absolutely no sense for your specific project… but you did it anyway just because someone told you that is how things are done?<br>Most of us have been right there. You spend hours filling out heavy documents that nobody actually reads. You run these complex approval ceremonies designed for a massive team of 50… when your current project has exactly six people.<br>You take a massive risk framework built for heavy commercial construction and try to force it onto a simple three-month software update.<br>Somewhere in the back of your mind, you know this is pure waste. But the process is the process, so you just put your head down and do the work.<br>The PMBOK® Guide Eighth Edition actually has a direct and brutal answer to this exact problem. It is called tailoring. And honestly… it is one of the most practically useful ideas we will ever implement.<br>Why One Size Fits All Is a Lie That Costs Money<br>Think about buying a suit off the rack. A standard suit fits reasonably well, it covers you, and it looks acceptable from a distance.<br>But it was designed for a statistical average. If your shoulders are slightly wider, it pulls awkwardly at the back. If your arms are long, the sleeves look completely wrong. You adjust, you compromise, and you make do.<br>A tailored suit is different. It does not fit the average person at all… it fits you perfectly.<br>Project management works the exact same way. The official guide gives us the raw fabric. Tailoring is the active process of cutting and fitting that fabric to your specific reality.<br>There is no single approach that can be applied to all projects all of the time.

That sentence should honestly be printed in bold text and posted on the wall of every Project Management Office (PMO) on the planet.<br>The reason tailoring matters goes far beyond just making the team comfortable. It has direct, measurable financial consequences.<br>When you use too few processes, you invite chaos and completely ineffective management. But when you use too many processes, you create heavy administrative waste, slow down delivery, and explode your operational costs. We know from basic organizational psychology that unnecessary bureaucratic steps massively increase cognitive load and team burnout.<br>The exact right number of processes, perfectly fitted to your context, is where actual efficiency lives.<br>What Tailoring Actually Means (And What It Is Not)<br>Let me be incredibly clear about something before we go any further.<br>Tailoring is not a free pass to skip the things you just find inconvenient. It is not saying that you hate writing status reports, so you are simply tailoring that out of your workflow. That is just avoidance.<br>Tailoring is the deliberate adaptation of approach, governance, and processes to make them more suitable for the given environment and the work at hand.<br>The word deliberate is doing all the heavy lifting in that sentence. It means you have a solid, defensible reason for your choices. You can clearly explain exactly why you removed something, why you modified a template, or why you added a new step. You can connect that specific decision directly to the unique characteristics of your project.<br>According to the standard, three main things can and should be tailored:<br>Life cycle and development approach: This is your biggest lever. Do you use a predictive approach, an adaptive approach, or a hybrid model? You might predictively manage building a physical data center, while using an adaptive approach for the software running inside it.<br>Processes: Individual processes can be added if you need more rigor. They can be modified if the standard version does not fit. Or they can be completely removed if they just create unnecessary cost.<br>Engagement: This one is constantly forgotten by project managers. How you engage with people is highly tailorable. Who is empowered to make local decisions? How much supervision does...