Curtis Stoaks The Durable Performance System™
Get the Drift Diagnostic
Menu

Tag: Leadership

Posts about how leaders shape system behavior through what they correct, tolerate, reward, centralize, clarify, or leave unresolved.

  • The Slow Erosion of Judgment

    The Slow Erosion of Judgment

    The Durable Performance Brief · Edition 30 · October 14, 2026

    Most organizations do not lose judgment because their people suddenly become less capable.

    They lose it because the system gradually makes independent judgment less useful, less welcome, or more personally expensive.

    A manager encounters an unfamiliar situation. The policy provides general direction, but the circumstances require interpretation. The manager has the authority to decide and enough experience to make a reasonable call.

    Still, the decision is escalated.

    Not because the risk exceeds the manager’s authority. Not because additional expertise is necessary. But because involving someone higher in the organization feels safer than carrying the decision independently.

    Leadership may interpret that behavior as caution or collaboration.

    It may be something more consequential.

    The organization may be losing its capacity for judgment while preserving the appearance of control.

    Judgment Can Erode Without Authority Changing

    Formal authority and exercised judgment are not the same thing.

    A manager can retain responsibility for an outcome while becoming increasingly reluctant to make the decisions required to produce it.

    That reluctance often develops through experience.

    A reasonable decision is questioned after the fact. A senior leader reopens a call that was within the manager’s authority. An unusual outcome receives more scrutiny than the reasoning behind it. A manager who escalated a similar situation avoids criticism, while someone who decided independently must defend the result.

    No formal delegation changes.

    But the organization has communicated something important about the personal cost of judgment.

    People begin adjusting.

    They consult more frequently. They document more extensively. They seek informal approval before exercising formal authority. They become increasingly careful about making decisions that might later require explanation.

    This is why authority design cannot be evaluated only by organizational charts and delegation documents.

    The real question is whether people can exercise the authority they have been given without unreasonable exposure when their decisions produce imperfect outcomes.

    When Process Becomes a Substitute for Thinking

    Process is necessary.

    Organizations need standards, repeatability, controls, and clear boundaries. Good processes reduce unnecessary variation and prevent people from repeatedly solving problems that should already have reliable answers.

    But process becomes destructive when it replaces the judgment it was supposed to support.

    Consider a customer situation that falls outside normal operating conditions.

    The employee understands the customer’s needs, the available resources, and the likely consequences of several possible responses. A reasonable decision is possible within established business boundaries.

    Instead, the employee searches for a procedure that provides an exact answer.

    When none exists, the issue is escalated.

    The organization may interpret this as a documentation problem and respond by adding another rule.

    The next unusual situation produces another gap.

    Another rule follows.

    Over time, the system becomes more comprehensive on paper while its people become less practiced at evaluating circumstances that do not fit neatly inside it.

    The organization is no longer using process to support judgment.

    It is using process to avoid the need for judgment.

    That distinction matters because operating conditions will never be perfectly predictable. Customers behave differently. Priorities collide. Information remains incomplete. Tradeoffs emerge that no procedure can fully anticipate.

    A system that depends on having an approved answer for every situation will eventually become dependent on the people authorized to interpret the rules.

    That creates execution drag even when everyone is following the process correctly.

    The Capability the Organization Stops Developing

    Judgment is not merely a personal trait.

    It is a capability strengthened through repeated use, feedback, and responsibility.

    People develop judgment by evaluating incomplete information, weighing consequences, making decisions within reasonable boundaries, and learning from the results.

    When organizations repeatedly remove those opportunities, they also weaken the conditions under which judgment develops.

    The immediate effect may be difficult to see.

    Decisions still get made. Senior leaders provide answers. Policies become more detailed. Managers remain busy and engaged.

    But the distribution of capability begins changing.

    Experienced leaders become the default source of interpretation. Middle managers become increasingly skilled at presenting issues rather than resolving them. Employees learn which questions should be elevated before anyone can criticize their handling of them.

    The organization becomes more dependent on the center.

    Eventually, leadership may conclude that people below them lack sufficient judgment.

    Sometimes that assessment is accurate.

    But leadership should also ask whether the system has been allowing those people to develop and demonstrate judgment in the first place.

    This is an important distinction within leadership systems: leadership behavior does not merely influence individual decisions. Repeated behavior shapes the capabilities an organization develops, preserves, or allows to weaken.

    Why More Training May Not Solve It

    When managers appear hesitant or overly dependent, organizations frequently respond with training.

    They invest in decision-making workshops, leadership development, communication programs, and additional coaching.

    Those investments can be valuable when capability is genuinely missing.

    But training cannot fully compensate for an operating environment that discourages people from using what they have learned.

    A manager can understand sound decision-making principles and still avoid making decisions if the organization repeatedly punishes reasonable mistakes, reopens legitimate calls, or rewards precautionary escalation.

    The problem is not necessarily knowledge.

    It may be the relationship between authority, accountability, and consequence.

    If people are expected to exercise judgment, the system must distinguish between poor judgment and an unfavorable outcome.

    A decision can be reasonable when made and still produce a disappointing result.

    A decision can also produce a favorable result despite weak reasoning.

    Organizations that evaluate judgment only through outcomes risk teaching people to protect themselves from uncertainty rather than manage it intelligently.

    That weakens accountability design because responsibility becomes disconnected from the authority and discretion required to act.

    One Practical Diagnostic

    Examine a decision category that regularly moves upward through your organization.

    Ask:

    What would happen if the person closest to the work made this decision independently and the outcome was imperfect?

    Do not settle for the formal answer.

    The policy may say the person has authority. The delegation document may confirm it. Leadership may insist that employees are empowered.

    Instead, examine what has happened in practice.

    When was the last imperfect local decision reviewed without automatically removing authority?

    Was the reasoning evaluated, or only the result?

    Did leadership coach the decision, or replace it?

    Did the person retain the authority to make the next comparable call?

    Would another employee observing the situation conclude that exercising judgment was encouraged or that escalation would have been safer?

    Those answers reveal more about the organization’s judgment capacity than its formal delegation structure.

    If You Change One Thing This Week

    Choose one recurring category of decisions that employees or managers are authorized to make but frequently escalate anyway.

    Restore the expectation of local judgment.

    Define the boundaries clearly: what the decision owner can decide, what conditions require consultation, and what material risks genuinely justify escalation.

    Then establish how imperfect outcomes will be reviewed.

    Evaluate the information available when the decision was made, the reasoning used, the alternatives considered, and whether the decision remained inside its authorized boundaries.

    Correct weak reasoning when necessary. Strengthen the guardrails when evidence shows they are inadequate. Escalate genuinely material risks.

    But do not automatically reclaim authority because a reasonable decision produced an undesirable result.

    That is how organizations begin rebuilding judgment as an operating capability rather than treating it as a quality employees either possess or lack.

    Go Deeper

    Why Organizations Drift examines how judgment weakens as organizations become increasingly dependent on process, approval, and precautionary escalation.

    The broader lesson is that organizational capability depends not only on having competent people, but also on maintaining conditions in which their competence can be exercised.

    Closing Thought

    A capable organization is not one in which every difficult decision eventually reaches someone senior enough to provide the answer.

    It is one in which sound judgment can be exercised throughout the system, within clear boundaries, with appropriate accountability.

    That capability cannot be preserved through training alone.

    It must be practiced.

    It must be protected.

    And it must remain legitimate even when reasonable decisions produce imperfect results.

    Otherwise, the organization may preserve its policies, its hierarchy, and its formal authority while quietly losing something far more valuable.

    Its ability to think and act without constant permission.

    Question for readers: Where in your organization do people still have formal authority but no longer feel safe exercising independent judgment?

    Next Wednesday: When process replaces accountability.

    Part of The Durable Performance System™
    Books, field guides, and frameworks on power, incentives, authority, accountability, and execution.
    Published every Wednesday morning.
    Curtisstoaks.com – YouTube – @curtisstoaksauthor

  • When Exceptions Become Policy

    When Exceptions Become Policy

    The Durable Performance Brief · Edition 29 · October 7, 2026

    Most organizations have two sets of policies.

    The first is written down.

    The second is learned through experience.

    The written policy may say that approvals belong at a certain level, deadlines have a defined meaning, performance standards apply consistently, or a particular process must be followed.

    Then something unusual happens.

    A customer situation requires flexibility. A valuable employee needs latitude. A deadline forces compromise. A leader makes a reasonable judgment call and grants an exception.

    Nothing about that is necessarily a problem.

    The problem begins when the exception survives the circumstances that justified it.

    Someone remembers it.

    Someone references it.

    A similar case appears.

    And eventually the organization stops asking whether the exception should exist.

    It starts asking who qualifies for it.

    That is the moment an exception begins becoming policy.

    Policy Can Change Without Being Rewritten

    Organizations often think of policy change as a formal event.

    Someone proposes a revision. Leaders discuss it. Legal or HR reviews it. Documentation changes. The new standard is communicated.

    But operating policy can change without any of that happening.

    Behavior only needs a precedent strong enough to compete with the written rule.

    Consider a manager who is allowed to bypass a normal approval because an important customer is at risk.

    The decision may be correct.

    Three months later, another manager faces a similar situation and points to the earlier exception. Denying the second request now requires leadership to explain why the cases are different.

    So the second exception is granted.

    Then a third.

    Eventually, the conversation changes.

    The organization is no longer debating the original standard. It is managing the boundaries of an alternative operating rule.

    The formal policy still exists.

    The precedent governs behavior.

    That is a classic mechanism of organizational drift. Structure changes through repeated operating decisions long before anyone announces that the structure has changed.

    Precedent Creates Its Own Logic

    Once an exception exists, it becomes a comparison point.

    That creates pressure for consistency.

    If one person received flexibility, why should another similar case not receive it?

    If one team was allowed to bypass the process, why should another team bear the full burden?

    If one high performer was protected from a consequence, what distinguishes the next high performer?

    This is where an isolated judgment decision starts becoming structural.

    Leadership may still believe it is evaluating every situation independently. The people inside the system are doing something different: they are mapping the precedents.

    They are learning where the boundaries actually sit.

    Over time, people become skilled at framing their circumstances so they resemble previously approved exceptions.

    The question is no longer:

    What does the standard require?

    It becomes:

    How do we qualify for the exception?

    Once that happens, the exception is influencing behavior more strongly than the rule.

    The Hidden Shift in Accountability

    This creates a particularly difficult problem for accountability design.

    Accountability depends on people being able to predict the relationship among standards, ownership, correction, and consequence.

    Exception-driven systems make that relationship increasingly conditional.

    A manager enforcing the written standard can suddenly look unreasonable because another manager received flexibility.

    An employee being corrected can point to someone who was not.

    A leader trying to restore discipline can appear inconsistent because the organization has already adapted to the exception.

    The irony is important.

    The original exception may have been granted in the name of fairness.

    Repeated exceptions eventually make fairness harder to establish.

    Now every decision requires context.

    Every standard needs interpretation.

    Every correction invites comparison.

    The organization becomes increasingly dependent on explanation because the operating rule is no longer obvious.

    Why Leaders Add Process

    At this point, organizations often try to solve the problem by formalizing the exceptions.

    They add approval criteria.

    They create review committees.

    They define special circumstances.

    They add documentation requirements so managers can distinguish legitimate exceptions from illegitimate ones.

    That can feel like discipline.

    But sometimes the organization is simply building bureaucracy around a standard it no longer consistently enforces.

    The original rule remains.

    The exceptions remain.

    Now there is also a process for deciding who gets to bypass the rule.

    This is how organizational entropy accumulates through reasonable additions.

    Nothing is necessarily removed.

    The organization keeps the standard, keeps the exception, and adds machinery to manage the tension between them.

    What began as flexibility becomes structural load.

    The Difference Between an Exception and a Policy

    The distinction is not whether something is written down.

    It is whether the organization expects it to happen again.

    A real exception is bounded.

    It has a reason.

    It has an owner.

    It has conditions.

    Most importantly, it has an end.

    An informal policy is different.

    People expect it.

    They reference precedent.

    Managers know how to request it.

    Similar situations receive similar treatment.

    Removing it would now feel like changing the rules.

    That final condition is particularly revealing.

    If ending an “exception” would require a change-management effort, it probably stopped being an exception some time ago.

    One Practical Diagnostic

    List the significant exceptions your organization has granted during the last six months.

    Then ask one question about each:

    If we denied this same exception tomorrow, would people believe we had changed the rules?

    If the answer is yes, investigate further:

    • Has the exception occurred more than once?
    • Do employees or managers reference earlier cases when requesting it?
    • Is there now an informal process for obtaining it?
    • Does leadership spend time deciding who qualifies?
    • Would removing it create accusations of inconsistency or unfairness?
    • Does the original standard still describe how work actually happens?

    Those are signs that precedent may already have become operating policy.

    If You Change One Thing This Week

    Create an exception register.

    Do not make it elaborate.

    For every material exception, record:

    The standard being suspended
    Why the exception is necessary
    Who owns the exception
    Who or what it applies to
    The expiration or review date

    Then add one more question:

    Does this exception reveal that the underlying standard itself should change?

    That matters.

    Not every exception is evidence of weak discipline. Sometimes repeated exceptions reveal a badly designed rule.

    A disciplined organization should be willing to change a standard deliberately when reality shows that the standard no longer serves its purpose.

    What it should avoid is allowing the standard to change accidentally through accumulated precedent.

    That is the role of leadership systems: making sure temporary accommodations expire, structural decisions remain deliberate, and operating reality does not quietly outrun formal expectations.

    Go Deeper

    Why Organizations Drift examines how reasonable exceptions become precedent, why precedent becomes increasingly difficult to reverse, and how organizations gradually replace clear standards with context-dependent operating rules.

    The issue is not whether leaders should ever make exceptions.

    They should.

    The issue is whether the organization can distinguish a deliberate exception from an accidental redesign.

    Closing Thought

    Organizations rarely announce that a standard no longer applies.

    They simply behave around it long enough that enforcing it begins to feel unusual.

    That is how an exception becomes policy.

    Not through a vote.

    Not through a memo.

    Not through a deliberate redesign.

    Through precedent.

    The policy on paper survives.

    The operating policy moves somewhere else.

    Question for readers: Which “temporary” exception in your organization would now feel like a policy change if you removed it?

    Next Wednesday: The slow erosion of judgment.

    Part of The Durable Performance System™
    Books, field guides, and frameworks on power, incentives, authority, accountability, and execution.
    Published every Wednesday morning.
    Curtisstoaks.com – YouTube – @curtisstoaksauthor

  • When Drift Looks Like Stability

    When Drift Looks Like Stability

    The Durable Performance Brief · Edition 26 · September 16, 2026

    Organizations rarely worry when the numbers still look acceptable.

    Revenue is holding.

    Customers are staying.

    Attrition is manageable.

    Projects are getting finished.

    The team is still delivering.

    Nothing appears broken enough to demand a major correction.

    That is precisely what makes some forms of organizational drift difficult to see.

    A system can remain stable because it is healthy.

    It can also remain stable because capable people are quietly compensating for everything that is not.

    The outcomes can look remarkably similar.

    The structural conditions underneath them are not.

    The Core Thesis

    Stability is an outcome. It is not a diagnosis.

    When leaders see acceptable results, they naturally infer that the operating system producing those results is working reasonably well.

    Sometimes that conclusion is correct.

    Sometimes the organization is spending hidden capacity to preserve visible performance.

    Managers resolve the same recurring conflicts.

    High performers absorb extra work.

    Experienced employees know which processes to bypass.

    Teams compensate for unclear ownership through relationships.

    Leaders personally intervene when important work starts to wobble.

    Customers encounter friction, but strong employees recover the experience before it becomes a visible loss.

    The organization still performs.

    But it is performing partly through compensation rather than design.

    That distinction matters because compensation can preserve results while concealing deterioration.

    See more on Organizational Drift for how weakening standards, authority, accountability, and execution discipline can progress before failure becomes obvious.

    The Hidden Labor of Stability

    Imagine a team that consistently meets its commitments.

    From the dashboard, the team looks healthy.

    Now look closer.

    One senior employee knows which approvals can be accelerated through personal relationships.

    A manager spends several hours each week resolving ownership questions that should already be clear.

    Two high performers routinely pick up work when handoffs fail.

    A project lead schedules informal pre-meetings because the formal meeting cannot reliably produce a decision.

    Everyone knows which executive needs to be consulted before certain decisions, even though no policy requires it.

    None of those behaviors necessarily appears in a performance report.

    Together, they may be the reason the performance report still looks good.

    That is hidden structural labor.

    The organization is consuming judgment, relationships, managerial attention, discretionary effort, and personal endurance to compensate for conditions the formal system has stopped handling well.

    This is where Organizational Effectiveness becomes a more useful lens than results alone.

    The question is not simply:

    What did we produce?

    It is also:

    What did the organization have to consume to produce it?

    High Performers Can Hide Weak Systems

    Strong people are one of the greatest assets an organization can have.

    They are also remarkably effective at hiding structural weakness.

    When a process breaks, they improvise.

    When ownership is unclear, they figure it out.

    When priorities collide, they absorb more.

    When a customer is frustrated, they repair the relationship.

    When another team misses a handoff, they compensate.

    That is valuable.

    It can also delay correction.

    Leadership sees acceptable output and concludes that the underlying arrangement is working.

    The high performer experiences something different: more friction, more invisible work, and more responsibility for keeping weaknesses from becoming visible.

    Over time, the organization begins depending on compensation it never deliberately designed.

    That is fragile stability.

    The danger becomes obvious only when the person stops compensating.

    They leave.

    They burn out.

    They move roles.

    Demand increases beyond what they can absorb.

    Or they simply stop spending discretionary effort repairing problems the organization refuses to remove.

    Then what looks like sudden deterioration may actually be the disappearance of a subsidy that had been hiding the problem for years.

    Managers Can Hide It Too

    Managers often become structural shock absorbers.

    They translate ambiguous priorities.

    Negotiate around unclear authority.

    Resolve conflicts privately.

    Chase decisions.

    Reconcile contradictory expectations.

    Protect teams from organizational noise.

    Good managers should do some of this.

    The problem is recurrence.

    If the same managerial intervention is required week after week, the manager may no longer be handling exceptions.

    They may be compensating for architecture.

    That distinction is important.

    A strong manager can make a weak system look functional for a surprisingly long time.

    Leadership may even praise them for being indispensable.

    But if the organization needs that manager’s constant translation and intervention simply to maintain normal operation, indispensability is not necessarily evidence of organizational strength.

    It may be evidence that the structure has outsourced its weaknesses to a person.

    Why Dashboards Miss This

    Most organizational measures focus on visible outputs.

    Revenue.

    Margin.

    Delivery.

    Retention.

    Customer satisfaction.

    Productivity.

    Those measures matter.

    But they usually do not show how much hidden effort was required to produce them.

    A project delivered on time looks successful whether it moved cleanly through the system or required three senior people to rescue it.

    A customer retained looks successful whether the experience worked as designed or an exceptional employee repaired it manually.

    A target achieved looks successful whether priorities were clear or the team worked nights to absorb conflicting demands.

    The output is identical.

    The durability is not.

    This is why Execution Drag deserves attention even while performance remains acceptable. Friction, overload, handoffs, ambiguity, and coordination burden can rise long before the final output reveals the cost.

    The Compensation Test

    A useful way to distinguish healthy stability from fragile stability is to remove the compensation mentally.

    Ask:

    What would happen if our strongest people stopped compensating for the system?

    Not if they stopped caring.

    Not if they performed poorly.

    If they simply stopped doing work the structure should already handle.

    What happens if managers stop chasing routine decisions?

    If high performers stop absorbing overflow?

    If employees stop using personal relationships to navigate unclear processes?

    If senior leaders stop rescuing ordinary execution problems?

    If teams stop holding pre-meetings before the real meeting?

    Would performance remain roughly intact?

    If yes, the system may be healthier than it feels.

    If performance deteriorates quickly, you have identified something important:

    The stability was being subsidized.

    One Practical Diagnostic

    In your next leadership meeting, choose one area that appears to be performing well.

    Then ask:

    What invisible work is keeping this stable?

    Look specifically for:

    • recurring managerial intervention
    • high performers carrying work outside their role
    • manual workarounds
    • unofficial approval paths
    • relationship-dependent coordination
    • repeated rescue
    • extra hours that have become normal
    • meetings required mainly to compensate for unclear ownership
    • experienced employees translating rules everyone else struggles to navigate

    Then ask one more question:

    If we removed the compensation but changed nothing else, what would break?

    Do not blame the people doing the compensating.

    Their behavior may be exactly what has kept the organization functioning.

    Treat their effort as diagnostic evidence.

    They are showing you where the structure is asking people to do work the structure should be doing itself.

    If You Change One Thing This Week

    Find one recurring act of compensation.

    Not the biggest problem in the company.

    One repeated workaround that everyone has learned to accept.

    Then trace backward.

    Why is the workaround necessary?

    What ambiguity, approval, handoff, capacity problem, incentive, or missing decision right created it?

    What would have to change for a capable person to stop compensating without performance getting worse?

    Then fix that condition.

    The goal is not to make strong people contribute less.

    It is to stop spending their strength on preventable friction.

    That is an important distinction.

    High performers should create leverage.

    They should not be used as structural adhesive.

    For the broader mechanism, explore Organizational Entropy—the accumulation of complexity, exceptions, weakened standards, and structural misalignment that can continue beneath visible strength.

    Go Deeper

    This issue builds on ideas from Why Organizations Drift, part of The Durable Performance System™ series.

    Related read:
    Why Organizations Drift examines why deterioration can remain hidden inside organizations that still appear functional. Reasonable accommodations accumulate, enforcement weakens, strong people compensate, and visible stability can persist long after the underlying system has started changing.

    Closing Thought

    Some organizations are stable because their systems are strong.

    Others are stable because their people are.

    For a while, both can look successful.

    The difference appears under pressure.

    A durable system does not require extraordinary people to continually rescue ordinary work.

    It allows strong people to spend their judgment on creating value rather than compensating for preventable weakness.

    So when everything still looks fine, do not ask only:

    Are we performing?

    Ask:

    What is making that performance possible?

    The answer will tell you whether you are looking at strength—

    or compensation that has not failed yet.

    Question for readers: What part of your organization looks healthy today mainly because capable people keep absorbing the friction?

    Next Wednesday: When intent stops controlling behavior.

    Part of The Durable Performance System™
    Books, field guides, and frameworks on power, incentives, authority, accountability, and execution.
    Published every Wednesday morning.
    Curtisstoaks.com – YouTube – @curtisstoaksauthor

  • The System Effect of Leadership

    The System Effect of Leadership

    The Durable Performance Brief · Edition 25 · September 9, 2026

    Most leaders judge themselves using evidence that is too close to them.

    They worked hard. They stayed involved. They supported the team. They made themselves available. They tried to be fair. They protected people. They solved difficult problems. They carried a lot.

    All of that may be true.

    None of it tells you whether their leadership made the organization stronger.

    That requires a different question:

    What became more true because you were there?

    That is the system effect of leadership.

    The Core Thesis

    Leadership should ultimately be judged by structural effect, not self-perception.

    Intent matters. Character matters. Effort matters. Results matter.

    But none of them is wide enough by itself.

    A decent, hardworking, deeply committed leader can still create an organization that becomes slower, more cautious, more politically dependent, less truthful, more centralized, and increasingly reliant on that leader’s personal intervention.

    The motive may be admirable.

    The effect can still weaken the system.

    This is why Leadership Systems matters. Repeated leadership behavior becomes operating structure. Over time, the organization learns where authority really lives, how truth should travel, what standards actually hold, which behavior receives protection, and how much independent judgment is genuinely safe.

    The system keeps the record.

    What Strong System Effect Looks Like

    Strong leadership leaves fingerprints.

    Truth gets cleaner—not because difficult information disappears, but because people do not need to package it as carefully before sending it upward.

    Authority gets clearer—not because every decision becomes simple, but because people know what they legitimately own and when escalation is actually required.

    Standards become more predictable—not because leadership becomes harsh, but because the line survives status, performance, and inconvenience.

    Managers become stronger—not because they receive more motivational language, but because they carry real authority, real consequence, and visible backing.

    Escalation becomes more disciplined.

    Complexity falls.

    Dependence on the center decreases.

    The leader remains important. They simply become less structurally necessary in places where capability should already exist below them.

    This is also an Organizational Effectiveness question. A healthy organization should not be judged only by what it produces, but by what it must consume to produce it.

    How much executive attention is required?

    How much managerial rework?

    How much coordination?

    How much heroics?

    How much political interpretation?

    How much repeated rescue?

    Strong results can coexist with weak architecture for a long time. The cost usually appears in what the organization must keep spending to hold those results together.

    What Weak System Effect Looks Like

    Weak system effect is harder to see because the leader often looks impressive.

    Busy. Responsive. Engaged. Highly informed. Needed everywhere.

    The calendar is full because important issues require the leader’s attention. The leader may even be producing excellent personal work.

    Meanwhile, bad news gets polished. Routine decisions move upward. Managers hesitate. Teams ask for more interpretation. Reporting grows. High performers receive more protection. Serious movement increasingly waits for the center.

    The leader becomes more important while the system becomes less capable.

    That is the trap.

    Personal contribution can rise at the same time structural strength falls.

    This is why indispensability is such an unreliable leadership metric.

    Sometimes indispensability reflects extraordinary value.

    Sometimes it reflects an organization that has learned not to operate without you.

    The Delay Makes This Hard to See

    Leadership behavior and system effect rarely arrive at the same time.

    Centralize a decision today and the decision may improve immediately.

    Ask for more reporting and visibility may improve immediately.

    Protect a strong performer and short-term stability may improve.

    Absorb pressure and the team may experience real relief.

    Step into a difficult problem and it may get solved faster.

    The structural bill arrives later.

    People begin waiting.

    Truth gets packaged.

    Standards become conditional.

    Managers build less pressure-bearing capacity.

    The center gets crowded.

    What felt helpful at the point of intervention eventually becomes normal operating behavior.

    That delay is why leadership cannot be judged only by whether an intervention worked.

    It has to be judged by what repeated intervention taught.

    Why the System Is the Better Witness

    People can be influenced by personality.

    Meetings can be managed.

    Narratives can be polished.

    Leadership explanations can be sophisticated and sincere.

    The system is harder to persuade.

    It records what actually happened to authority, truth, standards, decision speed, managerial courage, local judgment, reporting burden, and dependence.

    It does not care whether centralization was described as diligence. It records whether decisions moved upward.

    It does not care whether more reporting was called visibility. It records whether truth became more curated.

    It does not care whether selective tolerance was described as nuance. It records whether standards became less predictable.

    The system records consequence.

    That makes it the most honest witness to leadership effect.

    One Practical Diagnostic

    Ask this:

    What is my leadership making more normal?

    Then examine the last six to twelve months.

    Are people telling hard truths earlier or later?

    Are managers bringing finished judgment or half-formed problems?

    Are decisions sitting lower and cleaner, or moving upward more often?

    Has escalation become more selective or more routine?

    Are standards more predictable or more interpreted?

    Has reporting become lighter and more useful, or heavier and more reassuring?

    Are strong people learning judgment and ownership, or learning proximity and narrative management?

    What stops working when you are unavailable?

    Then add one harder question:

    What part of my leadership feels most valuable to me but may be teaching the system the wrong lesson?

    That is often where the useful diagnosis begins.

    If You Change One Thing This Week

    Choose one behavior you personally repeat as a leader.

    Not something your team does.

    Something you do.

    Perhaps you reopen decisions.

    Ask for routine visibility.

    Join meetings after your involvement is no longer necessary.

    Resolve cross-functional tension yourself.

    Allow exceptions for someone difficult to replace.

    Answer before a manager has finished reasoning.

    Now stop asking whether the behavior feels helpful.

    Measure its system effect.

    Does it create cleaner truth or more packaging?

    Clearer authority or more escalation?

    Stronger managers or more dependence?

    Less complexity or another recurring layer?

    Better ownership or better preparation for you?

    If the effect contradicts the intention, change the behavior.

    For deeper context, see more on Authority Design when the pattern involves decision ownership and escalation, and explore Signal Integrity when leadership behavior is changing how truth travels.

    Go Deeper

    This issue builds on ideas from What Smart Leaders Stop Doing, part of The Durable Performance System™ series.

    The book examines leadership not as a matter of style, but as system effect: whether authority becomes clearer or more centralized, truth cleaner or more curated, standards more predictable or more selective, and capability stronger or dependence deeper.

    Closing Thought

    One of the strongest defenses a leader can offer is:

    I was trying to help.

    That may be completely true.

    It is still not the final question.

    The final question is:

    What did your help teach the system to become?

    Leadership is not ultimately what the leader intended.

    It is not what the leader carried.

    It is not even what the leader accomplished personally.

    Leadership is what becomes structurally more true because that leader was there.

    Let the system judge.

    Question for readers: If you judged your leadership only by structural effect—not effort or intent—what would you have to admit?

    Next Wednesday: When drift looks like stability.

    Part of The Durable Performance System™
    Books, field guides, and frameworks on power, incentives, authority, accountability, and execution.
    Published every Wednesday morning.
    Curtisstoaks.com – YouTube – @curtisstoaksauthor

  • The Leadership Obligation

    The Leadership Obligation

    The Durable Performance Brief · Edition 24 · September 2, 2026

    Leadership is often described in the language of opportunity.

    More influence.

    More scope.

    More visibility.

    More authority.

    A larger voice in what happens next.

    Those things may come with the role.

    They are not the center of it.

    The center is obligation.

    The obligation to govern conditions other people cannot fully govern for themselves. The obligation to act when structural drift is visible even when failure has not yet created enough pain to make action popular. The obligation to protect truth, standards, legitimate authority, and future capability when doing so makes the present moment harder.

    The Core Thesis

    Leadership is not a privilege arranged around authority.

    It is an obligation arranged around consequence.

    The more authority a leader holds, the more their choices shape the operating environment other people have to inhabit.

    A delayed correction teaches.

    An exemption teaches.

    An executive intervention teaches.

    A truth that cannot be spoken directly teaches.

    A manager who is asked to hold a standard but is abandoned when enforcement becomes politically difficult learns something.

    So does everyone watching.

    This is why leadership has to be understood as custodial before it is expressive.

    The role is not primarily a platform for demonstrating style, confidence, vision, charisma, or decisiveness.

    It is stewardship of the structural conditions under which other people must work.

    See how Leadership Systems turn repeated leader behavior into operating structure.

    Obligation Begins Before Failure

    One of the easiest ways to avoid leadership responsibility is to wait until the evidence becomes undeniable.

    Once the customer is lost, the manager resigns, the project fails, the numbers collapse, or the corrosive behavior becomes publicly impossible to defend, action becomes easier.

    Now there is permission.

    The danger is obvious.

    People expect intervention.

    The political cost of doing nothing becomes higher than the cost of acting.

    But durable leadership often has to move earlier.

    When the pattern is clear enough to know where the system is heading, even though the organization can still tolerate it.

    That is a different standard.

    Reaction waits for pain.

    Obligation acts when responsibility becomes sufficiently clear.

    This is particularly important with Organizational Drift. Drift rarely arrives as a single undeniable event. It advances through individually defensible accommodations that become precedent through repetition.

    The Obligation to Restrain Yourself

    Not every leadership obligation requires action.

    Some require restraint.

    That may be harder.

    A senior leader can enter a decision because they know the answer.

    They can ask for another update because uncertainty is uncomfortable.

    They can rescue a manager because watching someone struggle feels inefficient.

    They can soften a consequence because the person involved is valuable.

    They can keep a decision centralized because distributed judgment creates variance.

    Every one of those moves can feel responsible.

    Every one can also make the system more dependent on the leader.

    This is why power creates an obligation to understand your own capacity to distort.

    Sometimes leadership means acting.

    Sometimes it means refusing to recenter what should remain local.

    Refusing to rescue too soon.

    Refusing to ask for reassurance disguised as visibility.

    Refusing to convert every uncomfortable situation into executive involvement.

    Refusing to let your own need for certainty redesign the operating system around you.

    That is not passivity.

    It is disciplined authority.

    The Obligation to Protect Truth

    Truth inside organizations is fragile.

    It gets packaged.

    Sequenced.

    Softened.

    Contextualized.

    Delayed.

    Sometimes because people are dishonest.

    More often because they are rational.

    They learn how leadership responds.

    If early bad news creates blame, people wait.

    If disagreement creates political cost, people soften.

    If executive confidence matters more than operating reality, people learn to protect confidence.

    Soon leadership receives more information and less truth.

    That makes Signal Integrity a leadership obligation, not merely a communication issue.

    The leader is responsible for whether operating reality can arrive early enough, clearly enough, and safely enough to be useful.

    You cannot demand candor while punishing the conditions that produce it.

    The Obligation to the People Closest to the Work

    Leadership also owes something downward.

    Not comfort.

    Not protection from the normal difficulty of serious work.

    Something more operational.

    People closest to the work should not have to carry unnecessary distortion created above them.

    They should not be given responsibility without usable authority.

    They should not have to disguise truth to make it survivable.

    Managers should not be expected to enforce standards senior leaders will abandon when someone powerful resists.

    Disciplined people should not be required to compensate indefinitely for tolerated dysfunction.

    Local judgment should not have to survive inside permanent ambiguity.

    This is not sentimental leadership.

    It is what the book describes as operational justice: the recognition that people below cannot fully redesign the architecture above them, while leadership can.

    That asymmetry creates obligation.

    The Obligation to Future Conditions

    Weak leadership often optimizes for the current room.

    How do we keep this calm?

    How do we avoid unnecessary disruption?

    How do we protect the quarter?

    How do we preserve confidence?

    The stronger question is:

    What does this become if we repeat it?

    What precedent does this exception establish?

    What behavior does this protection finance?

    What becomes harder to correct six months from now?

    What future system are we creating by choosing present comfort?

    That is the time horizon leadership has to hold when others cannot.

    Because one of the most dangerous organizational trades is exchanging future integrity for present smoothness while calling the trade maturity.

    This is where Accountability Design becomes important. A standard is only credible when authority, evidence, correction, and consequence remain coherent when applying them becomes expensive.

    One Practical Diagnostic

    Ask this in your next leadership meeting:

    What structural duty do we already know is ours but keep postponing because acting now is expensive?

    Then ask:

    • What truth has become clear enough to act on?
    • What standard is louder in language than in consequence?
    • What authority remains centralized mainly because returning it feels risky?
    • What are people below us compensating for that they cannot redesign themselves?
    • What present accommodation is creating tomorrow’s precedent?
    • Where are we waiting for failure to create permission we already have?

    Those questions separate difficulty from obligation.

    Some difficult things are not yours to carry.

    Some obligations cannot responsibly be transferred to anyone else.

    If You Change One Thing This Week

    Identify one decision you already know leadership has an obligation to make.

    Not an idea to study.

    Not an issue to keep watching.

    Something whose structural direction is already clear.

    Then define:

    What must be named?

    What must change?

    Who must own the correction?

    What consequence or boundary makes the correction real?

    By when?

    Do not make it dramatic.

    Make it explicit.

    Leadership obligation is not measured by how severe the action appears.

    It is measured by whether the system receives the correction before drift makes that correction harder, more political, and more expensive than it needed to be.

    Go Deeper

    This issue builds on ideas from What Smart Leaders Stop Doing, part of The Durable Performance System™ series.

    Related read:
    What Smart Leaders Stop Doing examines leadership as structural responsibility rather than personal expression. Its final leadership standard moves from what leaders are responsible for, to the obligation those responsibilities create, and ultimately to the system effect by which leadership should be judged.

    Closing Thought

    Leadership is not made serious by the title.

    It becomes serious when duty becomes clearer than self-interest.

    When truth matters more than reassurance.

    When future integrity matters more than present calm.

    When the standard matters even when enforcement costs something.

    When the leader knows when to act—and when to restrain themselves.

    Authority gives leaders options.

    Obligation tells them which options they can no longer responsibly avoid.

    Question for readers: What leadership obligation in your organization is already clear but still waiting for failure to make action easier?

    Next Wednesday: The system effect of leadership.

    Part of The Durable Performance System™
    Books, field guides, and frameworks on power, incentives, authority, accountability, and execution.
    Published every Wednesday morning.
    Curtisstoaks.com – YouTube – @curtisstoaksauthor

  • What Leaders Are Actually Responsible For

    What Leaders Are Actually Responsible For

    The Durable Performance Brief · Edition 23 · August 26, 2026

    Most leaders carry too much.

    Not necessarily too much work.

    Too much responsibility for things that were never truly theirs to govern.

    The mood in the room.

    Whether everyone approves.

    Whether every difficult decision feels comfortable.

    Whether uncertainty is visible.

    Whether people think leadership has everything under control.

    Whether every important problem eventually finds its way to them.

    Those burdens feel like leadership because they are heavy.

    But weight is not the same thing as responsibility.

    And when leaders spend too much energy carrying what is emotionally near, they often neglect what is structurally theirs.

    The Core Thesis

    Leadership responsibility is architectural.

    Leaders are responsible for the conditions under which other people must operate.

    That means asking whether:

    truth can travel,

    authority sits where it should,

    incentives reinforce the right behavior,

    standards remain credible,

    and the system stays simple enough for people to think and act clearly.

    The leader’s personality matters.

    Intent matters.

    Communication matters.

    But none of them is the final test.

    The system is.

    A leader can be charismatic while authority centralizes around them.

    Supportive while accountability becomes less credible.

    Decisive while capability beneath them contracts.

    Calm while inconvenient information gets increasingly packaged before it reaches the center.

    Leadership has to be evaluated by what becomes structurally more true because that leader is there.

    See more on Leadership Systems for how repeated leadership behavior becomes operating structure rather than remaining a matter of style or personality.

    Responsibility #1: Protect the Signal

    Leaders cannot govern a system they cannot see.

    That does not mean they need every detail.

    It means important reality must be able to reach the people capable of acting on it without becoming distorted by fear, optics, hierarchy, or narrative management.

    Leaders are responsible for asking:

    Can someone tell us something we do not want to hear?

    Does bad news move quickly enough to matter?

    Are managers explaining reality—or packaging it?

    Have our reactions trained people to protect us from uncomfortable information?

    This is why Signal Integrity is a leadership responsibility.

    If truth becomes harder to transmit as it moves upward, leadership cannot blame the system alone.

    Leadership helped create the conditions under which that signal travels.

    Responsibility #2: Put Authority Where the Work Requires It

    Leaders are responsible for deciding where legitimate decision authority belongs.

    Not where it feels safest.

    Not where the smartest person sits.

    Not where political exposure can be minimized.

    Where the work requires it.

    That means clear owners.

    Real decision boundaries.

    Defined escalation thresholds.

    And enough restraint from senior leaders that local authority remains real after it has been delegated.

    If every consequential call eventually rises to the center, the leader may feel responsible.

    The organization experiences dependence.

    Explore Authority Design for the structural relationship among ownership, boundaries, consultation, approval, and escalation.

    Responsibility #3: Govern What the System Rewards

    Organizations do not behave according to what leadership prefers.

    They adapt to what actually pays.

    Who gets promoted?

    What receives praise?

    What behavior receives protection?

    What gets ignored because the person producing results is valuable?

    What does the organization fund with attention, opportunity, status, compensation, and tolerance?

    A leader who says one thing while structurally rewarding another has not merely communicated poorly.

    They have governed poorly.

    This is why leadership responsibility extends beyond stated expectations into the reinforcement system itself.

    Responsibility #4: Make the Standard Real

    A standard is not a sentence in a policy.

    It is a predictable relationship between behavior and outcome.

    Leaders are responsible for whether that relationship remains credible.

    That does not mean identical treatment in every circumstance.

    Context matters.

    Judgment matters.

    But the underlying principle must remain recognizable when enforcement becomes inconvenient.

    Does high performance purchase exemption?

    Does hierarchy purchase reinterpretation?

    Does political value buy more time?

    Does leadership enforce the line differently when the cost rises?

    This is where Accountability Design matters. Accountability works when ownership, authority, standards, evidence, correction, and consequence reinforce one another instead of separating under pressure.

    Responsibility #5: Keep the System Usable

    Weak systems accumulate.

    Another review.

    Another dashboard.

    Another approval.

    Another recurring meeting.

    Another workaround.

    Another temporary control that becomes permanent.

    Each addition may be reasonable.

    Collectively, they create weight.

    Leaders are responsible for whether complexity is removed as aggressively as it is added.

    The goal is not minimalism.

    It is usability.

    Can people still understand what matters?

    Can they make decisions without unnecessary coordination?

    Can the system absorb pressure without adding another permanent layer every time something goes wrong?

    Structural simplicity is not administrative housekeeping.

    It is part of leadership stewardship.

    What Leaders Are Not Responsible For

    This boundary matters just as much.

    Leaders are not responsible for:

    making everyone comfortable with every standard,

    keeping every relationship warm,

    personally absorbing every source of pressure,

    eliminating uncertainty,

    preserving every contributor regardless of cost,

    or maintaining a reassuring narrative after reality has contradicted it.

    Trying to own those things often distorts the responsibilities that matter more.

    Truth gets softened to preserve confidence.

    Consequence gets delayed to preserve relationships.

    Authority gets centralized to reduce uncertainty.

    Pressure gets absorbed rather than redistributed.

    Complexity gets added because carrying more feels safer than removing something.

    The result is a leader who carries more while governing less.

    That is misplaced responsibility.

    One Practical Diagnostic

    Ask yourself:

    What am I currently carrying that feels like leadership but may actually be distracting me from leadership?

    Then ask five structural questions:

    Is truth getting through?

    Does authority sit where it should?

    Are we reinforcing the behavior we actually want?

    Are standards predictable enough to trust?

    Is the system becoming simpler and stronger—or heavier and more dependent?

    Those questions are useful because they move leadership away from self-perception.

    Not:

    Do people think I am supportive enough?

    But:

    What conditions am I preserving?

    Not:

    Am I involved enough?

    But:

    Is my involvement making the system more capable?

    Not:

    How do I carry this better?

    But:

    Should this still be carried here at all?

    If You Change One Thing This Week

    Take one recurring leadership burden that consumes significant energy.

    An escalation.

    A review.

    A relationship you constantly stabilize.

    A decision category.

    A recurring conflict.

    A reporting loop.

    Then ask:

    What would have to be structurally true for this to stop requiring me?

    Perhaps authority needs to move.

    A standard needs to become explicit.

    A consequence needs to become credible.

    A manager needs legitimate backing.

    A reporting artifact needs to disappear.

    A difficult truth needs to be named.

    Do not solve for how to carry the burden more efficiently.

    Solve for why the system keeps routing it to you.

    That is the difference between performing responsibility and governing structure.

    Go Deeper

    This issue builds on ideas from What Smart Leaders Stop Doing, part of The Durable Performance System™ series.

    Related read: What Smart Leaders Stop Doing examines leadership as system effect rather than personal performance. It asks leaders to judge themselves by whether authority becomes clearer, signal becomes cleaner, standards become more predictable, ownership grows stronger, and capability expands beneath the center.

    Closing Thought

    Leadership is not proved by how much you carry.

    It is proved by what becomes stronger because you governed it well.

    Clearer authority.

    Cleaner truth.

    Better reinforcement.

    More credible standards.

    Less unnecessary complexity.

    Stronger capability below the center.

    That is the work.

    Because the organization does not ultimately experience your intent.

    It experiences the system your leadership leaves behind.

    Question for readers: What are you carrying today that feels like leadership responsibility but may actually be evidence that the system needs redesign?

    Next Wednesday: The leadership obligation.

    Part of The Durable Performance System™
    Books, field guides, and frameworks on power, incentives, authority, accountability, and execution.
    Published every Wednesday morning.
    Curtisstoaks.com – YouTube – @curtisstoaksauthor

  • What Predictable Standards Make Possible

    What Predictable Standards Make Possible

    The Durable Performance Brief · Edition 22 · August 19, 2026

    Most organizations can tell you what their standards are.

    Respect matters.

    Ownership matters.

    Deadlines matter.

    Truth matters.

    Follow-through matters.

    The problem is rarely whether those standards have been stated.

    The problem is whether people can predict what happens when they are violated.

    That is where standards become structural—or become little more than organizational language.

    A standard is not strong because leadership talks about it forcefully.

    It is strong when people trust that the line will still hold when holding it becomes inconvenient.

    The Core Thesis

    Predictability creates operating trust.

    When people understand the standard and can reasonably predict how leadership will respond when it is crossed, several things become possible at once.

    Managers become more confident.

    Employees spend less energy reading personalities.

    Political calculation declines.

    Correction becomes less surprising.

    High performers understand that results do not purchase exemption.

    People can focus more on the work because they do not have to continuously interpret whether the rules will change depending on who is involved.

    This is why standards are not merely cultural statements.

    They are part of Accountability Design.

    Accountability becomes credible when ownership, standards, evidence, correction, and consequence are aligned rather than applied selectively from case to case.

    The goal is not sameness.

    Different situations can require different responses.

    Context matters.

    Intent matters.

    Severity matters.

    History matters.

    But context should shape the response without erasing the principle.

    That is the distinction.

    Predictability does not mean every case gets the same consequence.

    It means people can still see the same standard operating underneath the consequence.

    What This Looks Like in the Wild

    Imagine an organization that says respect is non-negotiable.

    A new manager behaves dismissively in a meeting and is corrected quickly.

    A high-performing sales leader behaves similarly but receives a softer response because the quarter is important.

    A technically brilliant director repeatedly undercuts colleagues but is described as difficult and valuable.

    Leadership still believes it has a respect standard.

    The organization sees something else.

    It sees a hierarchy of consequence.

    It learns that the line depends on status, value, timing, and political inconvenience.

    Now people no longer have to ask:

    What is the standard?

    They ask:

    Who is involved this time?

    That question changes the entire operating environment.

    Once employees have to interpret the person before they can interpret the standard, politics has entered the gap.

    See more on Organizational Drift because this is exactly how reasonable exceptions and selective enforcement gradually become operating precedent.

    The standard rarely disappears formally.

    It becomes conditional.

    And conditional standards force people to study the system socially rather than trust it structurally.

    What Predictability Gives Managers

    Managers often sit closest to the cost of inconsistent standards.

    They are told to hold the line.

    Then they watch senior leadership reinterpret the line when the case gets uncomfortable.

    That teaches them quickly.

    The next time a difficult issue appears, they hesitate.

    They escalate earlier.

    They soften the conversation.

    They wait for senior sponsorship before enforcing what they were supposedly already responsible for enforcing.

    Eventually, leadership complains that managers lack courage.

    The deeper question is whether managers have learned that enforcement is safe only when senior leaders agree with the specific case.

    Predictability changes that.

    Managers know the standard.

    They understand their authority.

    They know when escalation is appropriate.

    And most importantly, they believe leadership will still back legitimate enforcement when the person involved is valuable, influential, senior, or politically inconvenient.

    That is when Leadership Systems become trustworthy rather than personality-dependent.

    Predictability Is Not Harshness

    This distinction matters.

    Strong standards are sometimes confused with hard leadership.

    That is the wrong frame.

    The goal is not more punishment.

    It is not public correction theater.

    It is not severity.

    It is not making examples of people.

    The goal is a stable operating environment.

    People know where the line is.

    Managers know who owns it.

    Exceptions are genuinely exceptional and understandable.

    Leadership emotion does not determine whether enforcement occurs.

    And correction arrives early enough that small drift does not have to become a crisis before anyone acts.

    Predictability actually reduces the need for dramatic enforcement.

    When people trust the standard, fewer situations need to become symbolic tests of leadership credibility.

    The line does more work because the line is believed.

    One Practical Diagnostic

    Ask this in your next leadership meeting:

    Can people predict what will happen when one of our important standards is violated?

    Then test the answer:

    • Which standards are enforced consistently across levels?
    • Who receives more interpretation when the line is crossed?
    • Which manager would hesitate to enforce a standard without senior approval?
    • Where do results, hierarchy, relationships, or timing change the response?
    • What exception would be difficult to explain publicly without making the underlying standard look negotiable?
    • What is the most expensive standard leadership may soon have to prove is real?

    That final question matters.

    Predictability is easy when enforcement costs little.

    It becomes credible when leadership holds the line despite cost.

    If You Change One Thing This Week

    Choose one important organizational standard.

    Not ten.

    One.

    Then define what predictable enforcement actually means.

    Clarify:

    The line
    What behavior is inside or outside the standard?

    The owner
    Who is responsible for addressing it first?

    The response
    What normally happens when the standard is crossed?

    The escalation threshold
    What genuinely changes the level of response?

    The exception rule
    Under what unusual circumstances could the response differ, and how would the principle remain clear?

    Then look backward.

    Review the last three times that standard was tested.

    Did the principle survive the people involved?

    If not, the next leadership action is not another statement about expectations.

    It is restoring credibility.

    Explore Incentive Architecture because people adapt not only to what receives formal reward, but also to what receives protection, tolerance, and exemption.

    Go Deeper

    This issue builds on ideas from What Smart Leaders Stop Doing, part of The Durable Performance System™ series.

    Related read:
    What Smart Leaders Stop Doing examines why standards become real only when enforcement is predictable enough that people trust the principle more than they trust case-by-case interpretation. That requires consistency, managerial backing, legible consequences, and the willingness to hold the line when doing so costs something.

    Closing Thought

    The strongest standards are not the ones leaders defend most loudly.

    They are the ones people do not have to wonder about.

    The line is known.

    The response is credible.

    The manager is backed.

    Status does not purchase immunity.

    Context can shape judgment without erasing principle.

    That is what predictable standards make possible:

    less politics,

    less interpretation,

    stronger managers,

    cleaner accountability,

    and greater trust in the system itself.

    Question for readers: Which standard in your organization sounds clearer than it actually behaves?

    Next Wednesday: What leaders are actually responsible for.

    Part of The Durable Performance System™
    Books, field guides, and frameworks on power, incentives, authority, accountability, and execution.
    Published every Wednesday morning.
    Curtisstoaks.com – YouTube – @curtisstoaksauthor

  • Build Leaders Beneath You or Build Dependency Around You

    Build Leaders Beneath You or Build Dependency Around You

    The Durable Performance Brief · Edition 21 · August 12, 2026

    A leader can look exceptionally strong while building an exceptionally fragile organization.

    They know the details.

    They are pulled into important meetings.

    People ask for their judgment before difficult decisions.

    Escalations find them quickly.

    Problems move faster when they enter the room.

    From the outside, this can look like leadership at its highest level.

    But there is another possibility.

    The organization may not be becoming stronger.

    It may simply be becoming better at depending on one person.

    That distinction matters because leadership is not multiplied by how much the leader personally carries. It is multiplied by how much legitimate judgment, ownership, and pressure-bearing capacity grows beneath them.

    The Core Thesis

    Strong leaders expand capability.

    Weak leadership systems accumulate dependence.

    That does not mean the leader is weak in skill, intelligence, commitment, or judgment. In fact, the problem often becomes most pronounced around highly capable leaders.

    They can solve quickly.

    They see around corners.

    They know the political terrain.

    They can rescue an uncertain manager, reframe a difficult decision, calm a tense meeting, and improve a weak plan in minutes.

    That capability is valuable.

    It becomes structurally expensive when the organization learns that consequential leadership happens only when that person enters.

    Then the leader is no longer simply supporting the system.

    They are becoming part of its required operating infrastructure.

    See more on Leadership Systems, where repeated leadership behavior is treated as operating structure rather than merely style or intent.

    What This Looks Like in the Wild

    A vice president has a talented director.

    The director is respected, experienced, and increasingly capable.

    Leadership says they want the director to step up.

    But whenever an important cross-functional conflict appears, the vice president joins the meeting.

    When a difficult decision has political consequences, the vice president reframes it.

    When feedback becomes uncomfortable, the vice president softens the message.

    When the director makes a reasonable call that differs from the vice president’s preference, the decision gets reopened.

    Nothing about this looks obviously dysfunctional.

    The vice president may believe they are coaching.

    The director may feel supported.

    The organization may even get a slightly better decision in the moment.

    But the system is teaching something very specific:

    You lead until the situation becomes consequential. Then real authority returns upward.

    That is not leadership development.

    It is conditional ownership.

    And conditional ownership creates leaders who become better at anticipating the person above them rather than better at carrying the system beneath them.

    This is why Authority Design matters. Real development requires more than responsibility. It requires legitimate decision rights, clear boundaries, escalation thresholds, and visible backing when those rights are exercised.

    Support Is Not the Same as Substitution

    This is where good leaders often get trapped.

    They answer questions.

    Share context.

    Give advice.

    Stay accessible.

    Join difficult meetings.

    Model good judgment.

    Protect people from unnecessary political noise.

    All of those things can help.

    None of them guarantees that capability is actually expanding.

    People become stronger leaders by doing harder things themselves:

    making meaningful decisions,

    holding standards when doing so creates friction,

    absorbing bounded pressure,

    dealing with consequence,

    telling difficult truths,

    and learning from legitimate mistakes without having the work pulled away from them.

    That requires support.

    It also requires room.

    Without real room, mentoring can become a sophisticated form of dependence. The subordinate becomes extremely good at consulting the leader, preparing for the leader, and predicting the leader—without becoming substantially more capable of operating without the leader.

    Why Leaders Misread This

    Dependence is flattering.

    It creates daily evidence that the leader matters.

    People need your judgment.

    They seek your input.

    They bring you important issues.

    They want you in the room.

    Your calendar is full because your involvement appears consequential.

    It is easy to interpret that as proof that leadership is working.

    Sometimes it is.

    But strong leaders eventually change the scorecard.

    They stop asking:

    How well does this team respond to me?

    They start asking:

    How much legitimate leadership can this team carry without me?

    That is a very different standard.

    A reduction in escalations can become evidence of strength rather than lost relevance.

    A leader below you resolving a conflict differently than you would can become evidence of growth rather than loss of control.

    A difficult meeting that succeeds without you can become a leadership win instead of a reason to wonder why you were not included.

    That emotional transition matters.

    Leaders who need continuous proof of their indispensability will keep organizing the system around themselves—even while talking about empowerment.

    One Practical Diagnostic

    Ask yourself:

    If I disappeared for two weeks, what would stop working because the organization genuinely needs my authority—and what would stop merely because people have learned to wait for me?

    That distinction is revealing.

    Look at the leaders directly beneath you.

    Can they make consequential decisions without pre-clearing them?

    Can they handle cross-functional conflict without importing your authority into the room?

    Can they hold a standard when the person resisting it has influence?

    Can they deliver difficult feedback without expecting you to soften it afterward?

    Can they make a reasonable decision differently than you would—and still trust that you will protect their legitimate authority?

    Would the people below them describe their leadership as real?

    These are not abstract development questions.

    They are structural ones.

    See how Accountability Design supports real ownership by aligning responsibility, standards, decision rights, correction, and consequence instead of separating them.

    If You Change One Thing This Week

    Choose one leader beneath you who is ready to carry more.

    Then transfer one piece of real leadership, not just more work.

    Give them a decision that matters.

    Define the boundary.

    Clarify what would actually justify escalation.

    Coach before the moment rather than taking over inside it.

    Back them publicly once the boundary is set.

    Correct privately if needed afterward.

    And allow enough bounded difference that they can develop judgment rather than simply imitate yours.

    Do not hand off the easy part and retain every consequential part.

    That teaches administration.

    Not leadership.

    The goal is not to disappear.

    The goal is to become less structurally necessary in places where capability should already be growing beneath you.

    When leaders do this consistently, dependence begins to fall.

    Authority becomes more legitimate.

    Judgment deepens.

    Escalation becomes more selective.

    And capability starts expanding instead of accumulating at the center.

    Go Deeper

    This issue builds on ideas from What Smart Leaders Stop Doing, part of The Durable Performance System™ series.

    Related read:
    What Smart Leaders Stop Doing examines why strong leadership is not proven by how indispensable a leader becomes, but by whether judgment, ownership, standards, truth, and pressure-bearing capability deepen below the center.

    For the broader structural mechanism, see more on Organizational Drift. Temporary centralization can become permanent, local capability can narrow, and the organization can adapt to dependence long before anyone formally redesigns the structure.

    Closing Thought

    A leader should become more valuable as the organization becomes less dependent on their constant intervention.

    That is not a contradiction.

    It is multiplication.

    The strongest leader in the system should not remain the only place consequential judgment lives.

    Because leadership is not proven by how many people need you.

    It is proven by what becomes strong enough not to.

    Question for readers: Where are you still calling it leadership development when the person beneath you is actually being trained to depend on your involvement?

    Next Wednesday: What predictable standards make possible.

    Part of The Durable Performance System™
    Books, field guides, and frameworks on power, incentives, authority, accountability, and execution.
    Published every Wednesday morning.
    Curtisstoaks.com – YouTube – @curtisstoaksauthor

  • Correct the System, Not Just the Symptom

    Correct the System, Not Just the Symptom

    The Durable Performance Brief · Edition 20 · August 5, 2026

    When something goes wrong, leaders usually look for a person.

    Who missed the deadline?

    Where did communication fail?

    Which decision was too weak?

    Why did escalation come too late?

    Who failed to take ownership?

    Sometimes that is the correct place to look. People can be careless, unprepared, avoidant, poorly matched to a role, or unwilling to meet a clear standard.

    However, the mistake is not correcting people.

    The mistake is believing the diagnosis is complete because the person closest to the failure has been identified.

    The Core Thesis

    A people correction can be necessary and still be insufficient.

    A performance conversation happens.

    Leaders clarify expectations.

    They coach a manager.

    A warning follows.

    They reduce a role.

    Leadership replaces someone.

    As a result, the organization feels as though it acted decisively. Yet several months later, the same category of problem returns through someone else.

    That recurrence is structural data.

    It suggests the visible person may have expressed the problem without being the only condition producing it. The underlying arrangement—authority, incentives, reporting lines, capacity, role clarity, information flow, accountability, or consequence—may still be intact.

    Still, this does not remove individual responsibility.

    It makes leadership responsible for examining both levels.

    The person may need correction.

    The system may need redesign.

    Durable leadership knows how to do both without using either one to excuse the other.

    What This Looks Like in the Wild

    A company repeatedly misses project-delivery commitments.

    Leadership identifies the program lead as the problem.

    The person receives stronger expectations, closer oversight, and more frequent reviews. Eventually, the role is changed or the person is replaced.

    For a while, performance improves.

    Then the same pattern returns.

    Dates move.

    Tradeoffs surface late.

    Cross-functional conflict remains unresolved.

    Leaders again complain about weak ownership.

    A deeper inspection reveals something different:

    • decision rights across functions remain vague
    • commercial teams make commitments before operational review
    • status meetings reward confidence more than clean risk signals
    • escalation thresholds are unclear
    • multiple leaders can reopen scope without owning the downstream cost

    Even so, the program lead may still have underperformed.

    But replacing that person without changing the operating field gives the next person the same structural problem with a new title attached to it.

    That is how organizations begin changing people while preserving the conditions that keep reproducing the same failure.

    Why Leaders Prefer People Problems

    People are visible.

    They have names, roles, behaviors, records, strengths, and weaknesses.

    By contrast, systems are harder to confront.

    Systems are made of accumulated decisions:

    • who can decide
    • who can quietly reopen the decision
    • what behavior leaders protect
    • who filters information
    • what capacity limits remain unacknowledged
    • which exceptions have become normal
    • whether leaders match accountability with authority

    A person can be coached by Friday.

    A system may require leaders to reconsider decisions they made, controls they added, incentives they approved, or ambiguity they allowed to survive.

    That is the hidden appeal of a people-only diagnosis.

    It preserves the current architecture.

    The manager was weak.

    The employee lacked urgency.

    The function failed to execute.

    The team did not communicate.

    Those explanations may contain truth. They may also protect leadership from asking whether the environment made the failure more likely.

    System correction becomes personal when leaders realize some part of the design belongs to them.

    Perhaps they kept a temporary control too long.

    Rewarded the behavior they now want stopped.

    Asked for accountability without transferring authority.

    Reacted to bad news in ways that taught people to package the truth.

    Allowed a role to become incoherent.

    Accepted recurring workarounds instead of redesigning the structure.

    In other words, recognizing that is not self-condemnation.

    It is leadership.

    One Practical Diagnostic

    Ask this in your next leadership meeting:

    If we replaced the person at the center of this problem but changed nothing else, what would likely happen?

    Then examine:

    • Has this pattern appeared across more than one person?
    • Where is accountability heavier than authority?
    • What behavior do leaders reward or protect in ways that make the problem rational?
    • What burden are managers carrying that the organizational chart does not acknowledge?
    • What disciplined people are quietly compensating for the weakness?
    • What role ambiguity keeps being solved socially rather than structurally?
    • Where does leadership’s own behavior reinforce the condition?

    The Field Guide’s central discipline is useful here: persistent outcomes should be treated as evidence of what the structure permits. Diagnosis should identify the operating condition beneath the visible symptom and end with enforceable correction, not discussion alone.

    If You Change One Thing This Week

    Choose one recurring performance problem that has already survived coaching, additional oversight, or personnel change.

    Run a two-level correction.

    At the person level, ask:

    What expectation, capability, judgment, behavior, or role-fit issue must be addressed directly?

    At the system level, ask:

    What authority, incentive, signal, capacity, role, process, or consequence condition keeps making this category of failure more likely?

    Then make one correction at each level.

    Coach the person and clarify the decision right.

    Address the performance gap and remove the conflicting incentive.

    Reset the role and eliminate the approval pattern that weakened ownership.

    Apply consequence and correct the selective tolerance that made the standard uncertain.

    This is harder than blame.

    It is also more durable.

    Personnel-only correction often feels faster and then repeats.

    System correction feels slower initially and then compounds through fewer repeated failures, clearer accountability, stronger trust, and less dependence on heroic intervention.

    Go Deeper

    This issue builds on ideas from What Smart Leaders Stop Doing and The Durable Performance Field Guide, part of The Durable Performance System™ series.

    Related reading:
    What Smart Leaders Stop Doing examines how recurring human struggle can reveal distorted authority, incentives, signal, accountability, and consequence. The Durable Performance Field Guide turns that diagnosis into scoring, applied exercises, reset actions, and visible follow-through.

    Closing Thought

    The person closest to the failure may be responsible.

    They may require coaching, consequence, reduced scope, or removal.

    But they may not be the whole explanation.

    When the same problem survives multiple people, the system is no longer offering a personnel story.

    It is revealing its design.

    Strong leaders do not stop correcting people.

    They stop changing people while preserving the architecture that trained the problem to return.

    Question for readers: What recurring problem in your organization is still being treated primarily as a people issue when the pattern is already pointing to the system?


    Curtisstoaks.com – YouTube – @curtisstoaksauthor

    Next Wednesday: Build leaders beneath you—or build dependency around you.

    Part of The Durable Performance System™
    Books, field guides, and frameworks on power, incentives, authority, accountability, and execution.
    Published every Wednesday morning.
    Curtisstoaks.com – YouTube – @curtisstoaksauthor

  • Why Healthy Organizations Audit During Strength

    Why Healthy Organizations Audit During Strength

    The Durable Performance Brief · Edition 19 · July 29, 2026

    Most organizations inspect themselves when something hurts.

    A number drops.

    A customer escalates.

    Turnover rises.

    A launch fails.

    A control breaks.

    A visible miss creates enough urgency—and enough political permission—to ask structural questions that should have been asked much earlier.

    Then come the reviews, postmortems, diagnostics, process changes, and operating resets.

    That response may be necessary.

    It is also late.

    By the time failure makes structural weakness visible, the organization has usually been paying for it quietly for months or years.

    The Core Thesis

    Healthy organizations do not wait for pain to make inspection legitimate.

    They audit during strength.

    They examine authority, incentives, information flow, accountability, consequence, complexity, and capability while performance is still defensible and the system still has room to correct without panic.

    This requires discipline because success creates reassurance.

    The quarter closes.

    Customers remain stable.

    Growth continues.

    The dashboard is mostly green.

    The organization appears capable.

    Leaders naturally interpret those outcomes as evidence that the system underneath them is healthy.

    But visible performance does not reveal what is producing it.

    Strong results may come from sound structure.

    They may also come from market tailwinds, extraordinary effort, temporary workarounds, accumulated goodwill, hidden coordination labor, or a small number of capable people compensating for weaknesses no one has examined.

    Success confirms the outcome.

    It does not automatically validate the arrangement that produced it.

    That is why auditing during strength matters.

    It separates performance that is structurally durable from performance that is quietly borrowing against people, trust, speed, or future capacity.

    What This Looks Like in the Wild

    A business unit is meeting its targets.

    Nothing appears seriously broken.

    But a closer inspection reveals that more routine decisions are reaching senior leaders than they did six months ago.

    Status reporting has expanded.

    Two strong managers are carrying coordination loads that are mostly invisible.

    Bad news is being packaged carefully before it reaches executives.

    A high-output employee is receiving behavioral flexibility that others have noticed.

    None of these conditions has produced visible failure yet.

    That is precisely why this is the best time to act.

    The organization still has room to restore decision rights without crisis.

    It can reduce unnecessary reporting without appearing to abandon control.

    It can redistribute managerial load before exhaustion becomes attrition.

    It can improve signal quality before executive surprise triggers overcorrection.

    It can correct selective standards before resentment hardens into cultural truth.

    When leaders wait for visible damage, the same corrections become harder.

    Trust has weakened.

    Political positions have formed.

    Dependencies have deepened.

    People have adapted around the distortion.

    The eventual response must now overcome not only the original problem, but also the system’s accumulated accommodation to it.

    Maintenance is quieter than repair.

    It is also cheaper.

    Why Leaders Avoid It

    Auditing what appears to be working can feel unnecessary.

    It interrupts momentum.

    It may be interpreted as distrust.

    It can seem unfair to question a team producing acceptable results.

    It may also expose leadership choices that are difficult to confront.

    If authority has drifted upward, leaders may have to acknowledge that their own intervention habits helped centralize it.

    If information is overly curated, they may have to examine whether their reactions made unfiltered truth unsafe.

    If incentives are distorted, they may have to confront whom they have been rewarding.

    If standards have softened, they may have to face what they repeatedly tolerated.

    If heroics are holding the system together, they may have to admit that visible success has been borrowing from human endurance.

    This is why superficial audits are so common.

    Leadership asks questions, gathers feedback, and produces recommendations—but avoids findings that would require real redistribution, subtraction, correction, or consequence.

    The process becomes reassurance infrastructure.

    A real structural audit does not exist to confirm that the organization is generally fine.

    It exists to reveal what is becoming fragile while the organization still has enough strength to correct it cleanly.

    One Practical Diagnostic

    Ask this in your next leadership meeting:

    What are we currently trusting because it still works?

    Then inspect the arrangement beneath the result:

    Authority

    • Where are decisions actually being made compared with six months ago?
    • What now requires senior involvement that should not?

    Signal

    • What do people closest to the work know that leadership receives only after filtering?
    • Where is bad news being softened or delayed?

    Incentives

    • What behavior is currently paying off?
    • What short-term results are being purchased with long-term distortion?

    Accountability

    • Who is responsible for outcomes without controlling the main variables?
    • Where does ownership exist on paper but not in practice?

    Consequence

    • Where are standards applied differently because of hierarchy, performance, influence, or convenience?

    Capability

    • What team appears strong only because someone else keeps compensating for it?

    These questions do not measure whether results are good.

    They examine whether those results are clean enough to trust.

    If You Change One Thing This Week

    Choose one operating area that currently appears healthy.

    Do not begin with its outcomes.

    Inspect how those outcomes are being produced.

    Compare the current arrangement with six months ago:

    • escalation volume
    • approval requirements
    • reporting burden
    • decision location
    • exception patterns
    • managerial load
    • information quality
    • dependence on key individuals

    Then identify one structural change that has occurred without an explicit decision.

    Perhaps a temporary review became permanent.

    A senior leader became the default tie-breaker.

    A manager started carrying work outside the role.

    A report expanded but never contracted.

    An exception became routine.

    Correct one of those shifts while the system is still strong enough to absorb the correction without fear.

    Do not make the audit theatrical.

    Do not frame it as a search for failure.

    Frame it as maintenance: responsible inspection of the system before visible performance becomes the most expensive possible warning signal.

    Go Deeper

    This issue builds on ideas from What Smart Leaders Stop Doing and The Architecture of Durable Performance, part of The Durable Performance System™ series.

    Related reading:
    These books examine why structural decline often begins beneath acceptable results—and how disciplined review of authority, incentives, signal, accountability, and consequence can surface weakening conditions before volatility forces a more disruptive correction.

    Closing Thought

    Failure is an effective detector.

    It is also an expensive one.

    Strong leaders do not wait for pain to make structural inspection feel justified.

    They examine what looks healthy.

    They question what still works.

    They inspect strength for hidden dependence, quiet distortion, and accumulated fragility.

    Not because they distrust success.

    Because they want to know whether the system can continue producing it without borrowing against the future.

    Question for readers: What part of your organization appears healthy today but has not been structurally examined in the past year?

    YouTube – @curtisstoaksauthor

    Next Wednesday: Correct the system, not just the symptom.

    Part of The Durable Performance System™
    Books, field guides, and frameworks on power, incentives, authority, accountability, and execution.
    Published every Wednesday morning.
    Curtisstoaks.com – YouTube – @curtisstoaksauthor