Curtis Stoaks The Durable Performance System™
Get the Drift Diagnostic

Tag: Accountability

Posts about ownership, standards, follow-through, responsibility, and the difference between real accountability and accountability theater.

  • The Leadership Obligation

    The Leadership Obligation

    Edition 24 | September 2, 2026

    Publish: Wednesday, September 2, 2026 — 7:00 AM Mountain Time

    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

    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

    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

    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

    Edition 20 | August 5, 2026

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

    Who missed the deadline?

    Who failed to communicate?

    Who made the weak decision?

    Who did not escalate soon enough?

    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.

    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.

    Expectations are clarified.

    A manager is coached.

    A warning is issued.

    A role is reduced.

    Someone is replaced.

    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.

    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 commitments are made 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

    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.

    Systems are harder to confront.

    Systems are made of accumulated decisions:

    • who can decide
    • who can quietly reopen the decision
    • what behavior receives protection
    • what information gets filtered
    • what capacity limits remain unacknowledged
    • which exceptions have become normal
    • whether accountability is matched by 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.

    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 is rewarded or protected 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?

    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

    Explore the books →

    Continue Through The Durable Performance System™

  • Why Strong Leaders Restore Decision Rights Deliberately

    Why Strong Leaders Restore Decision Rights Deliberately

    Edition 18 | July 22, 2026

    Weak organizations do not always lose decision quality first.

    They lose decision location.

    The call still gets made. Sometimes it is even the right call. But it no longer gets made where it should.

    A decision that once belonged to a manager begins requiring director input. A routine customer exception moves upward “for visibility.” A cross-functional disagreement becomes an executive issue. A team that was told to take ownership starts scheduling pre-alignment meetings before acting.

    No one formally announces that authority has changed.

    It migrates.

    And once authority moves upward, it rarely moves back down without deliberate leadership action.

    The Core Thesis

    Temporary centralization easily becomes permanent operating design.

    Pressure rises. A visible mistake occurs. Confidence in local judgment drops. Senior leaders step closer to stabilize the situation.

    That intervention may be justified.

    The problem begins when the conditions that caused the intervention pass, but the authority remains at the center.

    Managers remember being reversed.

    Teams remember that acting independently created exposure.

    Functions remember that broad alignment felt safer than ownership.

    Leaders remember the cost of the original mistake and remain reluctant to return discretion.

    The organization now has structural memory.

    Centralization teaches caution. Caution increases escalation. Escalation creates dependency. Dependency then becomes evidence that continued centralization is necessary.

    The system has built a loop that will not correct itself.

    Strong leaders understand that restoring decision rights requires more than telling people to “take ownership.” It requires moving legitimate authority back to the proper level and changing the behaviors that made local ownership feel unsafe in the first place.

    What This Looks Like in the Wild

    Formal authority and actual authority begin separating.

    The role description says the manager decides.

    The manager still seeks approval.

    The operating model says the team owns customer exceptions.

    Senior leaders still expect a preview.

    The organization says decisions should remain close to the work.

    Executives routinely reopen decisions after they are made.

    This creates ceremonial ownership.

    People are allowed to research, package, recommend, and present. But the system still teaches them that the real decision belongs elsewhere.

    That is not delegated authority.

    It is delegated preparation.

    The difference becomes visible in behavior:

    • Routine decisions are escalated for protection rather than risk.
    • Meetings labeled “alignment” function as unofficial approvals.
    • Leaders complain about excessive escalation while continuing to accept it.
    • Teams prepare executive-facing narratives before acting.
    • Managers ask permission where they should be exercising judgment.
    • People closest to the work hesitate because their authority does not feel durable.

    Eventually, the organization stops asking, “Who should decide this?”

    It starts asking, “Who must be involved so no one gets exposed?”

    That is decision architecture turning into political self-protection.

    Why Leaders Misread It

    Because many leaders believe they have returned authority when they have only changed their language.

    They say:

    “You own this.”

    But they still expect to be consulted before anything significant happens.

    They still ask enough questions to signal that the decision remains provisional.

    They still intervene when the local choice differs from what they would have chosen.

    They still reverse legitimate decisions because senior discomfort rises after the fact.

    The organization notices.

    A decision right is not real merely because a leader assigned it in a meeting. It becomes real when the decision survives reasonable disagreement, executive interest, and imperfect outcomes.

    This is the difficult part of restoration.

    Leaders must accept that local decisions will sometimes differ from their preferences. Some will be imperfect. A senior leader may have made a marginally better call.

    But a slightly imperfect decision made at the correct level can create more long-term organizational strength than a perfectly optimized decision repeatedly pulled back to the center.

    Strong leaders coach judgment without absorbing ownership.

    They examine reasoning, clarify risk, challenge assumptions, and sharpen tradeoffs. But they resist becoming the decision-maker simply because they could improve the decision.

    One Practical Diagnostic

    Choose the five recurring decisions that generate the most escalation in your organization.

    For each one, ask:

    Who formally owns this decision?

    Then ask the more important question:

    Who can actually make it without seeking informal permission?

    Look for the gap.

    Then examine:

    • Who decides?
    • Who approves?
    • Who must be consulted?
    • Who only needs to be informed?
    • What specific risk threshold requires escalation?
    • Is the decision reversible?
    • Does the person accountable for the outcome control the main variables that shape it?
    • What happens when a legitimate local decision makes a senior leader uncomfortable?

    If the formal owner cannot make the call without previewing, socializing, or protecting themselves politically, the authority is not truly local.

    If a decision repeatedly escalates without new risk, authority has drifted upward. It should either be returned or explicitly redesigned.

    If You Change One Thing This Week

    Return one class of reversible decisions to the proper level.

    Do not issue a broad statement about empowerment.

    Choose a real decision category.

    Pricing exceptions below a defined amount.

    Routine staffing adjustments within budget.

    Customer remedies inside an established range.

    Project sequencing within an approved priority set.

    Then define four things clearly:

    The owner
    Name the role that makes the final call.

    The boundary
    Clarify what sits inside that person’s authority.

    The escalation threshold
    Specify the risk, cost, legal exposure, customer impact, or cross-functional condition that changes the decision level.

    The protection
    Commit that senior leaders will not casually reopen a legitimate decision that remained within the boundary.

    This last element is essential.

    Authority cannot be restored if it disappears the moment someone more senior becomes interested.

    Restoration becomes credible through repeated lived moments: someone makes a legitimate decision, the decision remains local, and leadership protects the boundary even when it would have chosen differently.

    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 how capable leaders unintentionally centralize authority, create escalation dependence, and weaken ownership beneath them—and how deliberate decision-right restoration reverses that pattern.

    Closing Thought

    Authority rarely returns simply because the crisis has passed.

    Someone has to put it back.

    That requires leaders to do more than ask for ownership.

    They must define it.

    Transfer it.

    Bound it.

    And protect it after the decision is made.

    Because an organization does not become stronger when more people prepare recommendations for the center.

    It becomes stronger when legitimate decisions can be made—and allowed to stand—at the right level.

    Question for readers: What decision still rises to senior leadership even though the information, capability, and accountability already live somewhere below?

    Next Wednesday: Why healthy organizations audit during strength.

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

    Explore the books →

    Continue Through The Durable Performance System™

  • Why Smart Leaders Stop Confusing Patience With Discipline

    Why Smart Leaders Stop Confusing Patience With Discipline

    Some leaders are not too reactive.

    They are too slow to act in the name of looking mature.

    That is the trap.

    Delay can sound disciplined. It comes wrapped in good language: measured judgment, executive restraint, timing, fairness, perspective, one more cycle, one more chance. Sometimes that language is exactly right. Sometimes it is avoidance wearing a disciplined face. That is what makes this pattern hard to see. Impulsive leadership is easy to criticize. Slow leadership often sounds intelligent.

    The Core Thesis

    Patience is not the same thing as drift with better language.

    Real patience has a reason, a boundary, and a clock.

    It gives time to clarify a pattern, stabilize facts, create a fairer sequence, or allow a person to respond meaningfully. It uses time deliberately. Distortive patience does something else. It uses time to postpone discomfort, preserve optionality, and delay the moment when judgment must become action.

    That difference matters because time is never neutral inside a system.

    While leaders wait, the organization keeps learning.

    Managers keep covering for weakening standards. Teams keep adapting to unresolved inconsistency. High performers keep compensating. People start noticing which issues are always “still being watched” and which ones actually trigger action. What looks like thoughtful delay at the center often feels like unprotected drift everywhere else.

    This is why patience must be governed.

    Not atmospheric.

    Not emotional.

    Not indefinite.

    Once time stops clarifying and starts merely prolonging, patience is no longer serving discipline. It is weakening it.

    What This Looks Like in the Wild

    A weakening manager gets “another cycle.”

    A team norm that is clearly degrading keeps being described as something leadership wants to observe a little longer.

    A known issue keeps borrowing from the future because acting now still feels severe.

    A leader says they do not want to move too quickly, but the same pattern has already become familiar to everyone close to the work.

    None of this looks reckless.

    That is why it survives.

    The leader sounds balanced, fair, and non-reactive. The system experiences something different. Managers start reading patience as reluctance. They become less direct, more interpretive, and more likely to keep problems quiet until they become undeniable. Once that happens, the management layer has started adapting to leadership delay instead of relying on leadership clarity. That is a major systems loss.

    This is also where “one more chance” becomes expensive.

    Not because second chances are wrong.

    Because unbounded chances teach the organization that goodwill is replacing judgment. Hope may still be emotionally appealing, but the system is already paying for it in credibility, consistency, and delayed correction.

    Why Leaders Misread It

    Because delayed leadership can feel morally superior to decisive leadership.

    It feels calmer. Fairer. More evolved. Leaders do not want to over-index on one moment, move too fast, or act before they are certain. Those instincts can be healthy. But the cumulative use of that language around the same person, same pattern, or same weakening standard is a warning sign, not a virtue.

    Leaders also confuse stability with health.

    Nothing has collapsed. The metrics are still defensible. Attrition is manageable. Customers are not leaving in waves. From a distance, things look steady. Inside the system, managers are smoothing more, standards are being applied unevenly, and disciplined people are compensating for what enforcement no longer holds cleanly. Stability in that condition is a poor signal. It often means the system is being kept afloat by people carrying costs leadership has delayed naming or correcting.

    That is where patience becomes dangerous.

    Not when it slows one decision.

    When it trains the system to believe that recognizable drift can remain unresolved as long as the language around it stays sophisticated enough.

    One Practical Diagnostic

    Ask this in your next leadership meeting:

    What are we still calling patience that has stopped creating clarity?

    Then press harder:

    • What is time actually doing for us here?
    • Is it clarifying, or merely prolonging?
    • What issue has already become familiar enough that waiting no longer makes the eventual decision fairer?
    • Where are managers carrying questions leadership should have settled by now?
    • What cost is the system already paying for our delay?

    Those questions matter because the right use of time produces cleaner judgment.

    The wrong use of time produces more expensive correction later.

    If You Change One Thing This Week

    Take one issue you are “watching.”

    Force precision.

    Write down:

    • what you are actually waiting to learn
    • what evidence would change the call
    • how long the runway truly is
    • what threshold triggers action
    • what cost is already being paid during the wait

    If you cannot answer those clearly, you are probably not practicing discipline.

    You are extending uncertainty.

    Strong leaders do not become impulsive. They become exact about timing. They know when observation has done its job, when one more cycle is no longer wisdom, and when the system has already paid enough.

    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 the leadership behaviors that look prudent, fair, and mature in the moment, but quietly prolong drift when timing is left atmospheric instead of governed.

    Closing Thought

    The goal is not fast leadership.

    It is timely leadership.

    Leadership that knows when observation has done its job.

    When the pattern is clear enough.

    When one more cycle is no longer wisdom.

    Because once patience becomes the language leaders use to justify avoidable delay, the organization does not experience maturity.

    It experiences unprotected drift.

    Question for readers: Where in your organization is “patience” still being used to protect a delay that is already costing more than action would?

    Next Wednesday: Why strong leaders restore decision rights deliberately.

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

    Explore the books →

    Continue Through The Durable Performance System™

  • Why Smart Leaders Stop Waiting Too Long to Name What Everyone Can See

    Why Smart Leaders Stop Waiting Too Long to Name What Everyone Can See

    Edition 16 | July 8, 2026

    A lot of leaders mistake delayed naming for maturity.

    They think they are being measured.
    Fair.
    Responsible.
    Disciplined.

    Sometimes they are.

    Sometimes they are simply postponing the moment when truth has to become operational. That is the danger. A leader can privately see the pattern, discuss it indirectly, and keep asking for a little more time, a little more evidence, or a slightly cleaner moment. Meanwhile, the system keeps adapting around what remains officially unsaid.

    The Core Thesis

    Seeing clearly is not the same thing as leading clearly.

    A leader may already know a manager has lost standing, a team norm has become corrosive, an initiative is failing, a role fit has deteriorated, or a high performer is operating outside the standard. But if none of that is named clearly enough for the organization to reorient around it, the system is still living in drift. Private recognition matters. It just does not change the operating reality on its own.

    That is the structural break.

    Because once the truth is obvious to enough people but still left unofficial, the organization does not wait patiently. It builds parallel language. Side conversations. Private acknowledgments. Quiet warnings. Coded phrases. Informal workarounds. People start learning what can be said openly and what must be handled through implication. When that line forms, politics deepens, and trust in formal communication starts thinning.

    This is why delayed naming is expensive.

    The leader experiences caution.

    The organization experiences hesitation.

    Managers keep coaching around what they cannot fully say. Peers keep protecting themselves from what leadership has not made real. Disciplined people keep carrying the burden of pretending that an obvious reality is still somehow tentative. What looks like prudence at the center often becomes an interpretive burden everywhere else.

    What This Looks Like in the Wild

    An issue is discussed thematically but never plainly.

    A pattern is “being watched closely” long after everyone already knows what it is.

    A leader keeps speaking in atmospheres instead of facts because naming the truth would force a boundary, a correction, a consequence, or a decision.

    A manager keeps losing credibility while leadership continues treating the situation as though it is still too early to say clearly.

    Nothing about this usually looks reckless.

    That is why it survives.

    The leader appears calm. Thoughtful. Unreactive. Measured. They are praised for not making the moment bigger than it needs to be. But while leadership is being congratulated for composure, the system is quietly paying for the delay. The issue keeps operating. The standard keeps weakening. The person involved keeps learning that visible drift can survive without direct naming. Observers keep concluding that truth belongs in side channels before it belongs in authority.

    Managers feel this earliest and most sharply.

    They have to carry operational consequences before leadership has made the truth usable. They coach around it, compensate for it, and attempt to enforce inside a reality the formal system still refuses to settle. Over time, they stop trusting that the truth will be named while there is still enough credibility and energy left to do something clean with it. That is a major systems cost.

    Why Leaders Misread It

    Because delayed naming often sounds like restraint.

    Leaders tell themselves they are avoiding overreaction, protecting dignity, staying composed, and resisting premature judgment. Those instincts can be healthy. The problem begins when evidentiary language survives past the point where the issue is no longer unclear. At that point, the delay is often no longer about fairness. It is about the reluctance to trigger what naming will require.

    That requirement is what leaders often avoid.

    Once the real thing is said plainly, ambiguity narrows. The social room tightens. A correction, a boundary, a consequence, or a decision now has to happen. Continued observation is easier. Continued watching is easier. Continued thematic language is easier. The system still pays.

    This is also why leaders confuse internal clarity with actual leadership.

    They know what is happening, so they assume the organization is effectively governed. It is not. Systems are not changed by what leaders silently understand. They are changed by what leaders are willing to make real enough that the rest of the organization can organize around it.

    One Practical Diagnostic

    Ask this in your next leadership meeting:

    What in our system is already obvious to too many people for us to keep treating it as tentative?

    Then press harder:

    • What issue are managers already working around because leadership has delayed making it official?
    • Where are we still asking for more evidence when what we really need is more courage?
    • What conversations have become overly thematic because no one wants to say the real thing plainly?
    • Who is currently trapped inside an unspoken truth?
    • What cost is the organization already paying for our restraint?

    Those questions matter because leaders do not only teach through action.

    They also teach through the timing and clarity of what they are willing to name.

    If You Change One Thing This Week

    Pick one issue that has already become too visible to remain unofficial.

    Then say the real thing clearly enough that the system can reorient.

    Do not aim for drama.

    Aim for usability.

    That may mean naming a credibility problem, clarifying that a norm is no longer acceptable, saying that a role fit has changed, declaring that an initiative is failing, or admitting that a relationship is structurally broken and will not improve through more implication. The point is not harshness. The point is to make reality usable while there is still enough trust, energy, and authority left to correct it cleanly.

    Strong leaders do not name early for theater.

    They name on time for credibility.

    Because once people stop expecting leadership to say the real thing, before the environment becomes obviously distorted, rebuilding trust takes a long time.

    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 how leaders weaken systems not only through what they do, but through what they delay saying plainly. When obvious reality remains unofficial too long, managers weaken, teams adapt around silence, and side-channel truth starts replacing formal clarity.

    Closing Thought

    Leadership is not only the work of seeing clearly.

    It is the work of making reality usable.

    Because once leaders wait too long to name what everyone can already see, the organization stops looking to authority for clarity.

    It starts looking everywhere else.

    Question for readers: Where in your organization is an obvious truth still being managed as an atmosphere instead of being named clearly enough to act on?

    Next Wednesday: Why smart leaders stop confusing patience with discipline.

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

    Explore the books →

    Continue Through The Durable Performance System™

  • Why Smart Leaders Stop Absorbing Pressure Instead of Redistributing It

    Why Smart Leaders Stop Absorbing Pressure Instead of Redistributing It

    Edition 15 | July 1, 2026

    A lot of leaders become indispensable for the wrong reason.

    They absorb too much.

    That pattern is easy to praise. The leader takes the difficult call, carries the political strain, smooths the cross-functional conflict, calms the customer issue, translates the ambiguity, and keeps the system moving. In the short term, this can look like strength. It often is a strength. The problem begins when personal endurance becomes the operating design. Then, pressure stops teaching the system how to grow and starts teaching it where to send everything hard.

    The Core Thesis

    Pressure cannot always be eliminated.

    But it can be distributed differently.

    That is the real leadership question. Not: How much pressure can I personally carry? But: What should this pressure teach the system to become? When leaders absorb too much strain themselves, they create temporary relief without building future strength. When they redistribute pressure well, they use the moment to create clearer decision rights, sharper escalation boundaries, stronger managers, better local judgment, and more durable ownership beneath them.

    That difference matters because teams are adaptive.

    If the leader repeatedly becomes the closer, the shock absorber, the conflict carrier, the escalation endpoint, and the interpreter of every serious problem, the organization learns quickly. Managers stop holding tension for as long. Teams escalate before fully working the issue. Cross-functional friction rises faster. Ambiguity gets routed upward instead of being resolved near the work. Serious pressure starts to feel like something that belongs above.

    That is the trap.

    A leader can become so good at carrying pressure that they stop noticing the system is failing to grow pressure-bearing capacity beneath them. Now, strength is being used in a way that quietly suppresses development. What looks like support can become underinvestment in capability.

    What This Looks Like in the Wild

    A team faces a visible customer issue. The leader handles it directly because the stakes feel too high to leave in weaker hands.

    A manager struggles with cross-functional conflict. The leader keeps stepping in because the relationship is fragile and the manager is not fully ready.

    A politically difficult message needs to be delivered. The leader takes it personally to keep the team from being crushed.

    Each move can be reasonable.

    The problem is that the return path is rarely defined. The leader knows how to step in. They do not define how the system steps back out. So the intervention stays. The leader remains the translator, the tie-breaker, the emotional buffer, the one who can “just handle it.” Architecture starts forming around a person instead of growing through the layer below.

    Managers feel this cost first.

    They still carry the title. They still appear to own the work. But when the pressure becomes serious enough, real leadership arrives from above. Over time, they learn a damaging lesson: my role is to manage operations until the issue becomes consequential, then the center takes over. That does not build conflict capacity, judgment under pressure, or truth-telling when the stakes rise. It teaches borrowed authority.

    Why Leaders Misread It

    Because over-absorption often feels humane.

    Leaders do not want people crushed by a political fight they are not ready for. They do not want a developing manager damaged by a visible miss. They do not want the team carrying more strain than it can bear. Some of that is real care. But leaders have to ask a harder question: Am I protecting this person from destructive pressure, or from developmental pressure? Those are not the same thing. Destructive pressure overwhelms without building. Developmental pressure stretches capability when it is bounded, supported, and real.

    Leaders also misread overload once the pattern is mature.

    At some point, everything important seems to touch them. Too many conflicts need intervention. Too many escalations need interpretation. Too many decisions rise. The leader often explains this in one of two ways: the team is not strong enough, or the season is just hard. Both may be partly true. But sometimes the leader is experiencing the downstream effect of having taught the organization to route serious pressure toward the center by default.

    This is why heroic leadership is not the same thing as durable leadership.

    Heroics can rescue a launch, save an account, fix a relationship, or repair a miss. But repeated heroics are often evidence of weak design being offset by strong individuals. A system dependent on rescue is not resilient. It is underbuilt.

    One Practical Diagnostic

    Ask this in your next leadership meeting:

    Where in our system has serious pressure started belonging to the center by habit?

    Then press harder:

    • What recurring tensions still flow upward that should increasingly be handled below?
    • What manager still has partial ownership because real authority arrives only when the situation becomes consequential?
    • What pressure have we stabilized without defining how the capability returns below?
    • Are people in this system learning from pressure, or mainly learning to transfer it?
    • If a leader disappeared for two weeks, what conflicts, decisions, or escalations would stall simply because that leader has become the system’s shock absorber?

    Those questions matter because pressure is always instructional. The only question is what the system is being taught.

    If You Change One Thing This Week

    Pick one class of pressure you keep absorbing personally.

    Then define the return path.

    That means naming:

    • Who should own the first pass next time
    • What authority do they need to carry it
    • What escalation threshold actually justifies senior involvement
    • What coaching or backing will they receive when they hold the weight properly

    Do not just step back rhetorically.

    Redistribute structurally.

    Strong leaders do not stop carrying pressure. They stop carrying all of it themselves. They resist the urge to rescue too soon so the right layer can feel enough real weight to become stronger, not just safer.

    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 how capable leaders can become the default absorber of conflict, ambiguity, and escalation, and how that pattern quietly weakens managers, teaches dependence, and concentrates pressure where it should no longer live.

    Closing Thought

    The goal is not to prove how much weight you can personally carry.

    The goal is to build a system that can carry more of the right weight at the right level without needing your rescue every time.

    Because once serious pressure belongs to the center by habit, the organization stops growing its capabilities.

    It starts growing dependence.

    Question for readers: Where in your organization is leadership still carrying pressure that should already be building strength below?

    Next Wednesday: Why smart leaders stop waiting too long to name what everyone can see.

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

    Explore the books →

    Continue Through The Durable Performance System™

  • Why Smart Leaders Stop Trying to Be Universally Liked

    Why Smart Leaders Stop Trying to Be Universally Liked

    Why Smart Leaders Stop Trying to Be Universally Liked

    Edition 14 | June 24, 2026

    A surprising amount of weak leadership comes from a decent instinct.

    The desire to keep relationships smooth.

    That sounds harmless. Mature, even. But when leaders start using approval as a compass, the system changes in predictable ways. Boundaries soften. Standards become more negotiable. Clear no’s turn into extended maybes. Managers stop trusting that enforcement will hold when the case becomes inconvenient. What looks like kindness at the center often becomes ambiguity everywhere else.

    The Core Thesis

    Trust and approval are not the same thing.

    Approval is about how people feel about you.

    Trust is about whether people believe the line around you is real.

    That distinction matters because many leaders quietly optimize for the wrong one. They want to be seen as fair, humane, collaborative, and open. None of those are bad aims. The problem begins when the leader starts treating immediate emotional smoothness as evidence of healthy leadership. Then the organization pays for the leader’s relational comfort with slower, lower-grade pain spread across the system.

    This is where trying to be liked becomes structural.

    A leader avoids disappointing one person.

    Now the team absorbs the extra ambiguity.

    A leader avoids a hard conversation.

    Now a manager keeps carrying a burden that should have been resolved earlier.

    A leader avoids tension.

    Now disciplined people lose trust because the standard is being talked around instead of held.

    That is not kindness.

    It is redistributed discomfort.

    The leader spares themselves one concentrated moment of relational pain by spreading lower-grade confusion, delay, and resentment across far more people for far longer. That trade rarely looks expensive at first. It becomes expensive because the system starts adapting to it.

    What This Looks Like in the Wild

    A clear no gets turned into a prolonged maybe.

    A manager needs backing, but leadership keeps trying to preserve everyone’s feelings, leaving the manager exposed.

    A standard is violated, but the conversation gets reframed around mutual understanding until the line itself becomes blurry.

    A decision needs closure, but more input keeps getting invited because the leader is still searching for a version no one will dislike.

    None of this usually looks dramatic.

    It looks like smoothing.

    That is why it survives.

    The leader sounds reasonable. Open. Patient. Considerate. The room may even feel calmer in the moment. But underneath that calm, the operating environment gets weaker. The system becomes more interpretive, more cautious, more uneven, and more political because emotional exposure that should have been absorbed as part of the role is being pushed outward into everyone else’s work.

    Managers feel this first.

    They live close to the cost. They are covering for inconsistencies, carrying team questions, and trying to enforce standards leadership seems hesitant to formalize. Over time, they stop reading patience as strategy. They start reading it as reluctance. Then their own behavior shifts. They become more interpretive, less direct, and more likely to contain problems quietly rather than confront them early. That is a major system loss.

    Why Leaders Misread It

    Because being appreciated can feel like evidence of effectiveness.

    It is not necessarily.

    People may like a leader because expectations are soft, access is easy, boundaries remain negotiable, and discomfort rarely lands sharply enough to create resentment. In that case, likability is not proof of strength. It may be proof of avoidance.

    Leaders also misread the role itself.

    They start carrying mood, perception, approval, and narrative as though those are core obligations of leadership. They are not. Leadership is custodial before it is expressive. The job is to protect clarity, decision rights, standards, trust, and the structural conditions under which others can do serious work without constantly decoding the environment.

    That often requires disappointing people cleanly.

    Not disrespecting them.

    Not humiliating them.

    Not becoming cold.

    But being willing to hold a line without needing everyone to feel good about it immediately. Strong leaders stop asking, How do I do this without anyone feeling bad about me? They start asking, What does the system need from me, and how do I deliver it with as much dignity and clarity as possible?

    One Practical Diagnostic

    Ask this in your next leadership meeting:

    Where are we preserving approval at the expense of trust?

    Then press harder:

    • Where has a clear no become an extended maybe?
    • Which boundaries keep inviting more interpretation because leadership wants everyone to feel heard?
    • Do managers trust they will be backed when enforcement becomes inconvenient?
    • What discomfort is leadership avoiding that the rest of the system is now carrying?
    • Are people trusting the line more, or studying personalities to guess whether the line still applies?

    Those questions matter because organizations weaken when leaders start treating emotional smoothness as proof of health. Sometimes smoothness is simply what drift feels like before the cost arrives.

    If You Change One Thing This Week

    Pick one place where you have been unconsciously optimizing for approval.

    Then replace softness with clean clarity.

    That may mean:

    • saying no without extended rescue language
    • backing a manager publicly enough that the line becomes real
    • closing a decision instead of reopening it for more relational comfort
    • giving honest feedback without cushioning it until the message disappears

    The standard is simple:

    Do not aim to be liked in every moment.

    Aim to be clear, respectful, and trustworthy.

    People can tolerate disappointment far better than they can tolerate a system that keeps becoming less legible because leadership is trying to stay emotionally well-positioned with everyone all the time.

    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 explores the leadership behaviors that feel humane and relationally intelligent in the moment, but quietly weaken standards, blur boundaries, and make the system harder to trust over time.

    Closing Thought

    A leader can be liked and still not trusted.

    A leader can also be trusted without being universally liked.

    That is one of the hardest emotional transitions in leadership.

    Because the job is not to maximize approval.

    It is to build a system people can rely on when approval becomes inconvenient.

    Question for readers: Where in your organization has the desire to keep everyone comfortable started making the operating environment less clear?

    Next Wednesday: Why smart leaders stop absorbing pressure instead of redistributing it.

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

    Explore the books →

    Continue Through The Durable Performance System™