Every Step in this Process Was Added for a Good Reason. That’s the Problem.
Over-design is the most defensible form of HR Complexity, because every layer of it was rational at the moment it was added. Understanding why it accumulates, and what it costs, is the work that precedes any meaningful simplification.
Ask an HR team to walk you through a complex process. A merit cycle, a job requisition approval, or a performance improvement plan. Something interesting happens. For every step that looks bureaucratic from the outside, there is a story. That third approval was added after an incident where a manager made an offer that created a equity compression problem. That documentation checklist was introduced after a wrongful termination claim that we almost lost. That two-week cooling off period is there because as executive once acted impulsively and there were consequences.
Every step has a reason. Every layer has a history. The result is a system that has become its own problem. The solution is more complex to navigate than the situations it was designed to govern, and more expensive to run that the risks it was designed to prevent.
This is over-design. And it is the most difficult structural driver of the HR Complexity Tax to address. Not because the solutions are technically complicated, but because the legitimacy of each individual addition makes the system as a whole almost impossible to challenge from the inside.
When someone proposes removing a step from a process that exists because of a real incident, the response is predictable: “We added that for a reason. Do you want that situation to happen again?” The question is rhetorically powerful and analytically weak. The real question of whether the step is still doing proportionate work relative to its cost never gets asked. And so the process grows, one defensible addition at a time, until the cost of running it has quietly exceeded the cost of the problem it was designed to prevent.
What Over-Design Actually Is, and Isn’t
Over-design is not bad design. That distinction matters. A badly designed process is one that fails to accomplish its purpose. It has the wrong steps, in the wrong sequence. owned by the wrong people. Over-design is something more specific and more insidious. It is a process that is working as designed, for a purpose that has either changed or need superseded, at a cost that was never made visible because the cost was never measured against the original risk that justified the design.
The clearest signal of over-design is what happens when you ask people to explain the purpose of specific steps in a process. There are three characteristic responses. The first is a clear, current, proportionate answer: “This step exists to catch equity anomalies before they become compensation commitments.” The second is an historical answer: “That was added after the Williams situation in 2019.” The third, and this is the over-design signal, is a deferred answer: “I think legal required it, but you'd have to check with them.” When a significant proportion of process steps produce the second or third response, the process is over-designed.
It is also important to distinguish over-design from appropriate rigor. Some HR processes should be demanding. Performance improvement processes that have legal implications require documentation and structured timelines. Compensation decisions at senior levels require multiple review points. Hiring decisions for roles with regulatory requirements need specific verification steps. Rigor in these contexts is not over-design. It is the right design for the risk profile.
Over-design begins when the rigor applied to high-stakes decisions migrates to low-stakes ones. When the approval chain designed for an executive compensation decision becomes the template for a mid-level merit adjustment. When the documentation standard developed for a PIP becomes the default for a routine performance conversation. When the verification process built for a regulated role gets applied universally because no one ever designed a lighter-weight alternative for roles that don't need it.
The HR Complexity Tax Assessment treats over-design as a structural driver precisely because this migration is structural. It is not a mistake that any individual made. It is what happens when an organization has a mechanism for adding process rigor and no corresponding mechanism for calibrating it to the actual risk level of the decision being made.
It Always Starts with an Incident
The accumulation of over-design follows a pattern that is almost universal across organizations. Understanding the pattern is prerequisite to diagnosing where an organization currently sits within it.
It begins with an incident. Something goes wrong — a compliance failure, a manager decision that produces an employee relations claim, a compensation commitment that violates policy, a hiring decision that turns out to have been made without adequate documentation. The incident is real, the consequence is significant, and the organizational response is rational: add a control that prevents this specific failure from recurring.
The control is added. It works, in the narrow sense that the specific incident is not repeated. The process is now slightly more complex, but the complexity is justified by the risk it mitigates. No one measures the cost of the new step relative to the probability of the incident recurring. The incident happened once; the control runs every time the process runs, for everyone who uses it, for every subsequent year, regardless of whether the risk profile that produced the incident still exists.
The Accumulation Asymmetry
Most HR functions have a clear mechanism for adding process steps. An incident occurs, a risk is identified, a control is designed and implemented. Very few have an equally formal mechanism for removing steps when the risk has been mitigated, the context has changed, or the cost has grown so disproportionate to the benefit. This asymmetry, easy to add but impossible to remove, is the structural engine of over-design.
The second accumulation vector is compliance. Regulatory requirements generate process additions that are, by definition, non-negotiable at the moment of introduction. But compliance landscapes change. Requirements are updated, superseded, or reinterpreted. The process additions that were mandatory in one regulatory environment are sometimes retained long after the requirement has evolved, because the compliance team that added them has moved on, the institutional memory of why they were added is diffuse, and the default organizational position on anything that might have a compliance dimension is to leave it in place.
The third vector is best practice adoption. This is a particularly interesting source of over-design because it feels like improvement. An HR leader attends a conference, sees how a high-performing organization structures its talent review process, and brings the design home. The design is sound. It was built for an organization with a different scale, a different manager population, a different cultural context, and a different strategic moment. Applied wholesale to a different organization, the process is often over-engineered for the actual decision quality it needs to produce. But because it came from a respected source and was implemented with good intentions, it is rarely challenged.
Each of these vectors operates independently. An organization can be accumulating over-design through incident response, compliance additions, and best practice imports simultaneously, with no single view of what the combined process looks like or what it is collectively costing.
The Business Cost: What Over-Design Is Actually Charging
The cost of over-design is paid in three currencies, and most organizations are only aware of the first.
The first is time. Over-designed processes take longer than they need to, for the people running them, for the managers navigating them, and for the HR teams administering them. This cost is visible in the abstract but rarely measured with any precision. The number of hours a manager population spends navigating a merit cycle, a headcount approval process, or a performance documentation requirement is almost never calculated. If it were, the figure would be prominent in most organizations and the comparison of that figure against the actual risk being mitigated would be more prominent still.
The second cost is decision quality. This is counterintuitive, because the logic of adding process rigor is that it produces better decisions. And in some cases, it actually does. But over-designed processes can actively degrade decision quality in ways that the process architecture does not make visible.
When approval chains are long, the people at the end of them are often too far removed from the decision context to add meaningful judgment. They approve because they are required to approve, because refusing requires an explanation, and because the substantive decision has already been made by someone who knew far more about the situation. The approval step looks like governance. It functions as rubber-stamping with additional delay.
When documentation requirements are extensive, the energy that managers invest goes into documentation compliance rather than decision quality. The form is completed correctly. The thinking behind the decision may be no more rigorous than it would have been without the form, and sometimes less, because the form has provided a structure that substitutes for genuine reflection.
The third cost, organizational will, is the one that matters most for HR transformation and is almost never measured. Every time a manager navigates an over-designed process and experiences it as disproportionate to the decision being made, a small withdrawal is made from the account of goodwill that HR needs to execute change. The manager's tolerance for HR complexity is finite. Over-designed processes spend it faster than strategic HR programs can replenish it.
When HR leaders wonder why adoption of new initiatives is slow, why engagement with HR programs is reluctant, why managers describe HR as 'bureaucratic' even when significant investment has been made in strategic capability, the answer is often located in the accumulated experience of navigating over-designed processes. The strategic HR work is real. But it is experienced through the same system that required four approvals for a training budget decision and six weeks to process a lateral transfer.
Load-Bearing Complexity vs Dead Weight
The most important diagnostic distinction in assessing over-design is between complexity that is load-bearing and complexity that is dead weight. This distinction is harder to make than it sounds, and getting it wrong in either direction has significant consequences.
Load-bearing complexity is process rigor that is doing genuine work. It is the approval step that actually catches errors, the documentation requirement that genuinely protects the organization, the review gate that produces decisions of meaningfully higher quality than would have been made without it. Removing load-bearing complexity and the risk doesn’t disappear. The risk just relocated into the organization where it will surface on its own timeline, in its own form, without the controls that were containing it.
Dead-weight complexity is process rigor that was once load-bearing and no longer is. This might be because the risk has been mitigated, the context has changed, the organization has developed the capability to make the decision well without the control, or the step was never truly load-bearing but was added in a moment of organizational anxiety and never examined thereafter.
The Load-Bearing Test
For any process step under diagnostic review, ask three questions: 1- What specific failure does this step prevent? 2- How frequently does that failure occur without this step, and has that frequency been measured? 3- If this step were removed, who would need to absorb the work it currently does, and what would that cost relative to the cost of running the step? Steps that cannot produce clear answers to all three questions are candidates for removal or redesign.
The diagnostic challenge is that load-bearing and dead-weight complexity often look identical from the outside. Both are process steps with documented purposes. Both have advocates who can articulate why they exist. Both have survived previous simplification efforts, often because the previous efforts didn't distinguish between them. Therefore they either removed things that mattered or left everything in place to avoid the risk of removing something that did.
The HR Complexity Tax Assessment addresses this through a structured diagnostic that tests each process element against three criteria: proportionality (is the rigor appropriate to the actual risk level?), currency (does the risk that justified this step still exist at the level that justified the design?), and utility (is the step producing the quality improvement it was designed to produce, or has it become procedural theater?). Steps that fail on any of these dimensions are over-design candidates. Steps that fail on all three are priorities for immediate removal.
This matters because the distinction between load-bearing and dead-weight complexity determines the sequencing of any simplification effort. Organizations that remove dead weight first free up organizational capacity and credibility to address the harder work of redesigning load-bearing complexity to accomplish its purpose at lower cost. Organizations that don't make the distinction either remove too much and create gaps, or remove too little and produce the version of simplification that everyone recognizes: new language for the same process, slightly rearranged.
Five Lenses. One Question: Is This Step Still Earning Its Place?
The over-design component of the HR Complexity Tax Assessment works through five diagnostic lenses, each targeting a different dimension of the problem. Together they produce a picture of where the process architecture is working proportionately and where it has grown beyond what the organization's actual risk profile requires.
Step Origin Audit reviews when and why each process step was introduced. Steps with historical origins, diffuse ownership, or undocumented current purpose are immediate over-design candidates. The goal is not to justify the removal but to require justification for retention.
Risk Proportionality Mapping examines whether the rigor applied to each decision type is calibrated to the actual risk level of that decision. Over-design is almost always visible here in executive level controls being applied to routine decisions, or documentation standards built for high-stakes situations running on low-stakes ones.
Approval Chain Analysis evaluates the number of approval levels for standard process categories, and whether each level is producing genuine decision value or functioning as procedural confirmation. Approval chains longer than three levels for non-executive decisions are a near-universal over-design signal.
Process Compliance Patterns investigates how people actually navigate the process relative to how it was designed to be navigated. Workarounds, informal shortcuts, and “known exceptions” are the clearest evidence that a process has been over-designed for the reality its meant to govern.
Removal Governance Audit determines whether the organization has any formal mechanism for removing process steps when the risks they were designed to mitigate have been addressed. The absence of a removal mechanism is itself a structural driver of over-design, and one that will regenerate complexity after any simplification effort that doesn’t address it.
The output of the over-design diagnostic is a process map that distinguishes load-bearing from dead-weight complexity across the HR function. This map feeds directly into Pillar 2: Operational Clarity and Decision Design, where the governance architecture for both the simplification and its sustainability is established.
The Governance Problem That Sits Behind All of It
Every discussion of over-design eventually arrives at the same underlying problem: the absence of a removal discipline. Organizations have well-developed mechanisms for adding process rigor: incident response protocols, compliance teams, best practice benchmarking, risk management frameworks. The addition of a new process step triggers review, approval, and documentation. The removal of an existing step, in most organizations, triggers nothing. It simply doesn't happen, because there is no mechanism that requires it to happen.
This is the governance problem that the over-design diagnostic is designed to surface, and the reason that simplification efforts without a governance component reliably produce temporary results. The effort removes dead weight. Six months later, a new incident occurs. A new step is added. A new compliance requirement arrives. A new best practice is imported. The process is complex again, and no one can quite explain how it happened.
"Simplification without a removal governance mechanism is not simplification. It is a one-time clearing of accumulated complexity, without any design for preventing that complexity from accumulating again. The clearing takes months. The re-accumulation takes less."
The removal discipline that addresses this is not bureaucratic. It does not require a formal committee to approve the removal of every process step. It requires a principle, embedded in HR operating governance, that every addition triggers a review of what the addition displaces, and that every process at a defined review interval is evaluated against the same proportionality, currency, and utility criteria applied in the initial diagnostic.
This is what Pillar 2 — Operational Clarity and Decision Design — is designed to establish. Not a simpler process, but a governance architecture that prevents the next simplification effort from being necessary. The over-design diagnostic tells you what needs to be removed and redesigned today. Pillar 2 tells you how to ensure that the problem you are solving today doesn't reassemble itself in the same form by the time the current transformation is complete.
The Compliance Theater Problem
There is one specific manifestation of over-design that deserves its own treatment because it is both extremely common and extremely difficult to challenge. Compliance theater.
Compliance theater is process rigor that exists to demonstrate compliance rather than to achieve it. The distinction is important. Genuine compliance process is designed to produce a specific behavioral or documentation outcome that actually reduces legal, regulatory, or ethical risk. Compliance theater is designed to produce evidence that the organization takes compliance seriously; evidence that would be presented in a legal proceeding or audit, regardless of whether the process is actually producing the risk reduction it appears to.
The test for compliance theater is simple in theory and politically difficult in practice: does this process actually change the decisions being made, or does it change the documentation of decisions that would have been made the same way regardless? If a manager who would have terminated an employee for documented performance reasons goes through a twelve-step performance management process and terminates the employee for documented performance reasons, the process has produced documentation. Whether it has produced a better decision — a more considered, more defensible, more equitable decision — is a question most organizations have never formally evaluated.
The Compliance Theater Test
For any process that exists primarily for compliance purposes, ask: if this process where removed and replaced with a clear decision standard and a documentation requirements, would the decisions made be materially different? If the honest answer is no, that the decisions would be the same, the outcomes would be similar, and the risk profile would be comparable, then the process is compliance theater. It is producing documentation of a decision, not improvement of it.
Calling this out in an organization is not a recommendation to abandon compliance. It is a recommendation to distinguish between compliance processes that are doing genuine risk mitigation work and compliance processes that are doing documentation work that could be accomplished with significantly less organizational friction.
The distinction matters for the over-design diagnostic because compliance theater is the most protected category of dead-weight complexity. It has legal cover, historical precedent, and institutional advocates. It is the last thing to be examined in a simplification effort and the first to be reinstated when the effort faces pushback. Getting the diagnostic right on compliance theater requires involving legal and risk leadership in the assessment; not as gatekeepers of simplification, but as co-owners of the question of whether the current process is actually producing the risk reduction it costs.
What to Do Before You Simplify Anything
The counsel for HR leaders looking at their own over-design situation mirrors the advice given for fragmentation: resist the instinct to move directly to intervention. The temptation is to convene a working group, map the processes, identify the redundant steps, and remove them. The instinct is correct in direction. The problem is sequencing.
Simplification without a prior diagnostic produces two characteristic failure modes. The first is under-simplification: the working group identifies obvious dead weight but leaves load-bearing complexity in place because the load-bearing work is not visible to a process map review. The result is a process that is shorter but still over-designed for most of the decisions it governs.
The second failure mode is over-simplification: the working group, motivated by the clear mandate to simplify and the organizational frustration with complexity, removes steps that were doing genuine work. The consequence surfaces six to eighteen months later, in the form of an incident that the removed step was designed to prevent. At this point the step is reinstated, typically with additional controls, and the process ends up more complex than it started.
The right sequence begins with the diagnostic lenses described above. Map the origin of each process step. Test proportionality against the actual risk level. Audit approval chains for genuine decision value. Look for the workarounds that reveal where the process has been over-designed for the reality it governs. And audit the governance mechanism, or its absence, that will determine whether the simplification produces a durable result or a temporary one.
Then, and only then, design the simpler process. Not a process that has fewer steps, but a process that has the right steps, calibrated to the actual risk, owned by people who are genuinely adding decision value, and supported by a governance architecture that will prevent the next layer of dead weight from accumulating unnoticed.
That is what the over-design diagnostic is designed to produce. Not a cleaner process diagram. A process that is proportionate, current, and governed in a way that keeps it that way.