Why You Keep Breaking Your Own Focus Block

And how Extreme Ownership sharpens Attention Management in return.

Attention management means deciding in advance which blocks of time go to which kind of work, then defending that block against interruption, rather than reactively responding to whatever shows up — an email, a notification, a request — as it happens. Extreme Ownership, a leadership idea from former Navy SEAL officers Jocko Willink and Leif Babin, means that when something goes wrong on a team, the leader's first move is to look at their own decisions, training, or communication as the cause, rather than blaming the team member whose action was the immediate, visible trigger. The two meet at a specific, everyday failure point: a protected work block gets broken — you pick up the phone, answer the message — and the automatic response is to blame the interruption itself, the busy season, or the person who pinged you. Extreme Ownership's core discipline, applied to your own attention practice instead of a team, means treating a broken block as your own setup failure — you didn't physically remove the phone, you didn't tell people you'd be unreachable — which produces an actual fix rather than a vague resolve to try harder next time.

What each one is actually for

Attention Management

Attention management starts from a specific claim: switching between tasks carries a real cognitive cost, called context switching, where your mind needs time to reload the details of a task each time you return to it, so frequent interruption doesn't just take the time the interruption itself lasts — it degrades the quality of the work around it too. The practice is to decide, before the day starts, which specific block of time is protected for your highest-value work, and to physically remove the conditions that make interruption easy during that block: phone in another room rather than face-down on the desk, notifications off rather than silenced, a closed door rather than an open one with headphones on. The block is decided calmly, in advance, precisely so that in the reactive moment — a notification lighting up, a colleague at the door — there's already a standing decision in place that doesn't require fresh willpower to hold.

Extreme Ownership

Extreme Ownership asks a leader, when something on their team goes wrong — a missed deadline, a subordinate's error — to look first at their own decisions and actions as the actual cause, even when someone else's specific choice was the immediate, visible trigger. This isn't about denying that the team member did something that led to the failure; it's about the leader refusing the reflex to stop the analysis there. The practiced question becomes: what did I fail to communicate clearly enough, train thoroughly enough, or set up well enough that let this happen — because that question, unlike blaming the team member, actually produces something you can go change. In practice, this looks like a leader responding to a missed deadline not with 'why didn't you finish this' but with 'what did I not make clear about the priority or the resources you needed,' out loud, in front of the team, as a standing habit rather than a one-time gesture.

What you get out of pairing them

Attention management gives you a genuine defense against a real, measurable cost — task-switching that degrades the quality of your best work — but it doesn't have much to say about what happens the moment you break your own rule, which happens to almost everyone eventually. Extreme Ownership's discipline, aimed at your own broken attention block instead of a team's failure, gives you a specific next move for that exact moment: instead of blaming the notification, the busy week, or your own weak willpower in a way that produces nothing but guilt, you ask what you actually failed to set up — did you leave the phone in reach, did you not tell your team you were unreachable — and fix that specific gap. That turns a repeated failure into a repeated source of real, structural improvement instead of a repeated source of vague self-criticism that changes nothing about tomorrow's block.

What Attention Management rests on

  • Implementation intention closes intention action gap randomised trials
    Pre-committing to a specific situational cue paired with a specific response lets the behavior fire automatically when the cue occurs, without depending on in-the-moment willpower.
  • Attention is trainable randomised trials
    Repeatedly practicing directing and redirecting attention strengthens the ability to control where it goes, making that control more available over time.
  • Context switching degrades performance randomised trials
    Frequent switching between tasks imposes a cognitive cost that reduces the effective output of the time spent.

What Extreme Ownership rests on

  • Internal attribution increases agency observational studies
    Attributing outcomes including others' failures to one's own controllable actions increases perceived agency and drives problem-solving instead of blame-seeking.
  • Leader modeling shapes team norms practitioner report
    A leader who visibly takes ownership of team failures models a norm that subordinates then adopt and this shifts team-wide behavior over time.
  • Removing blame target redirects energy to solutions practitioner report
    When blame-shifting is not available as an option the energy that would go into assigning fault gets redirected toward identifying and fixing the actual problem.

Where they actually meet

Both practices refuse a default, reactive response and replace it with a stance chosen in advance of the moment it's needed. Attention management refuses the default of letting whatever's loudest — a notification, a request — decide where your attention goes, replacing it with a block decided calmly beforehand. Extreme Ownership refuses the default of blaming whoever's action was closest to a failure, replacing it with a standing habit of asking what the leader themselves failed to set up. Neither one is a reaction invented fresh in the moment; both are standing postures, decided once, then applied automatically whenever the triggering moment arrives — a notification, a missed deadline, a broken rule.

The principle underneath both

A limited resource — your attention, or a team's problem-solving energy — left to distribute itself automatically tends to flow toward whatever is loudest or easiest in the moment, the newest notification, the most convenient person to blame, rather than toward what actually produces results. Deciding in advance, in a calm moment, where that resource goes removes the decision from the influence of whatever's loudest when the moment actually arrives, whether the moment is a notification or a failure that needs a real cause identified.

What that makes the real goal

If a limited resource defaults toward whatever's loudest unless a decision is made in advance, the real goal is to move as much of the actual decision-making as possible into a calm moment before the pressure arrives, and leave the pressured moment itself with as little left to decide as possible — recognize the pull, apply the standing rule, move on. For attention, that means the block and its physical protections are decided the night before, not negotiated fresh each time a notification appears. For ownership, that means the leader's question — what did I fail to set up — is a standing habit applied automatically to any failure, not a judgment call made fresh, and possibly skipped, in the heat of each specific incident.

Other practices that serve the same goal

Implementation intentions, researched extensively by psychologist Peter Gollwitzer, pursue this same objective in general form — a specific 'if this happens, then I will do that' plan, decided in advance, carries strong controlled-trial support across many kinds of behavior, from exercise to conflict de-escalation. Pre-mortems, a project-management technique where a team decides in advance what could go wrong and who's specifically responsible for catching it, serve the accountability half of the same goal before any actual failure occurs. Environmental design — physically removing a phone from a room rather than relying on willpower not to check it, a move drawn from behavioral economics research on defaults — serves the attention half of the same goal by taking the decision out of the moment entirely.

Using Attention Management to enhance Extreme Ownership

An ownership review — the moment after a team failure where a leader asks what they themselves failed to set up — requires real, undistracted thinking to do properly, not a rushed few minutes between meetings and Slack notifications. Done in the margins of a busy day, it tends to produce a shallow version: a quick 'I should communicate better next time' that doesn't trace anything specific. Protect an actual block for it. After a team failure, before responding to anyone or announcing a fix, take twenty to thirty minutes with the phone in another room and no messages open, and use that block specifically to trace what you failed to communicate, train, or check — was the priority actually clear, did the person have what they needed, did you follow up. The ownership stance is only as good as the thinking behind it, and that thinking needs the same protected conditions any other high-value work does.

Using Extreme Ownership to enhance Attention Management

Attention management routinely fails not because the block was never scheduled, but because you break your own rule mid-block — the phone comes off the desk, the notification gets answered — and the usual response is to blame something external: the notification itself, a demanding season, the person who messaged. Extreme Ownership's core discipline, redirected at your own practice instead of a team, means refusing that reflex. When a block breaks, ask what you failed to set up rather than what interrupted you: did you actually leave the phone in another room, or just face-down on the desk where it could still buzz and be seen. Did you tell your team you were unreachable for that window, or leave that unstated and then feel obligated to respond. Treating a broken block as your own planning gap, not a willpower failure or someone else's fault, produces a concrete change to make before tomorrow's block instead of a vague resolution to focus harder.

9:04am, a Slack message about a missed client deadline, and the quarterly plan half-finished

Your calendar says 9:00 to 10:30 is protected for the quarterly plan, the one thing you keep not finishing. At 9:04, a message from a direct report lights up your screen: the Morrison deliverable is late, and the client already noticed. Your hand is already reaching for the laptop trackpad to open Slack and start fixing it. You catch the reach. The old pattern here is either to answer immediately, torching the block, or to ignore it out of pure willpower and feel a low hum of guilt about it for the next ninety minutes either way. Instead, you do two things. First, you send one line — 'saw it, will follow up by 11' — and close the laptop, keeping the block. Second, you make a note to come back at 11 not with 'why did this happen' but with the ownership question: what did I fail to make clear about the Morrison timeline three weeks ago. By 10:30, the plan is actually further along than it's been in a week, and the 11am conversation has an actual question in it instead of just blame.

When this is worth reaching for

Your own after-action reviews happen distracted, squeezed into the margins of a busy day, and produce the same shallow fix twice in a row instead of a real one. Or a block breaks and the explanation is always external — a busy week, an urgent message — never your own setup. Either pattern is the specific gap this pairing closes.

Where this does not apply

If a team's real problem is a leader who's genuinely absent or negligent rather than distracted-but-trying, telling that leader to protect attention and take more ownership doesn't address the actual issue, which is closer to a fit or capacity problem. And Extreme Ownership taken without a genuine next fix attached — self-blame with no concrete change made to what you'll do differently — risks becoming self-flagellation rather than the fix-oriented stance it's meant to be; pairing it with attention management's habit of producing a specific setup change is what keeps it useful.

What the evidence does and does not support

Implementation-intention research, the mechanism underlying both a protected attention block and a pre-decided ownership stance, has strong controlled-trial support across many behaviors. The specific cost of task-switching has real experimental support in cognitive psychology. Extreme Ownership as a leadership philosophy is supported mainly by anecdote and case study from military and business settings rather than controlled research — a compelling, widely applied account rather than a measured one. The specific combination here, using a protected block as the setting for an ownership review, hasn't been tested as such.

Practice this with IX Coach

Try this practice

The two practices on their own

Other pairings with these practices

The principles underneath both