If your team feels scattered right now—half-starting things, forgetting details, dropping balls—it’s tempting to label it as a motivation problem.

It usually isn’t.

More often, it’s a cognitive load problem.

When leaders stack priorities without closing loops, the brain stays in a constant background hum of “don’t forget this.” That hum steals focus, drains energy, and makes even simple work feel heavy.

This Mindset Monday is about the real productivity killer: open loops—and how to reduce them fast.

The real productivity killer: open loops

An open loop is anything that’s been started, implied, requested, or discussed… but not clearly finished, scheduled, or contained.

Open loops look like:

• “We should revisit that next week.”
• “Can you take a first pass?” (no deadline, no definition of done)
• “Let’s keep this moving.” (moving toward what?)
• A project that’s 70% complete but missing one decision
• A meeting where five actions were named and none were owned

Open loops don’t just create messy work.

They create mental noise.

Why unfinished work stays “on” in the brain

Your brain is designed to protect you from forgetting what matters.

When something is incomplete, your attention system keeps it “active” in the background to increase the odds you’ll return to it. That’s helpful when you have one or two things open.

But when you have twenty? Fifty?

You get:

• constant task-switching
• shallow focus
• decision fatigue
• irritability
• the feeling of being busy without making progress

This is why people can work all day and still feel like they didn’t finish anything.

Working memory limits and the illusion of multitasking

Working memory is limited. When you overload it, performance drops.

Multitasking feels productive because you’re moving. But cognitively, you’re paying a switching cost every time you jump between priorities.

The result:

• more errors
• slower completion
• less strategic thinking
• more rework

If your team is “multitasking,” they’re often just context-switching under pressure.

The IronMind M.O.M.E.N.T.U.M. move:

O — Open loops audit

In IronMind, momentum isn’t created by adding more.

It’s created by reducing drag.

That’s why the next M.O.M.E.N.T.U.M. move is:

O — Open loops audit.

The goal is to surface what’s silently consuming attention—and make clean decisions so the brain can release it.

The Open-Loop Inventory (what we’re kind of doing)

Here’s the simplest way to run it:

Ask each person (including you) to list:

• projects in motion
• requests they’ve received
• decisions waiting on someone
• “I’m kind of doing this” work
• follow-ups they’re carrying

If you want a fast prompt, use:

• What are you holding in your head that isn’t on a list?
• What are you waiting on?
• What did we start that we didn’t restart properly?

This isn’t about blame.

It’s about making the invisible visible.

Kill / Commit / Contain: the three decisions that restore focus

Once the open loops are on the table, every item gets one of three decisions:

1) Kill

If it’s not truly important, end it.

• “We’re not doing this.”
• “This is no longer a priority.”
• “We’re stopping work on this effective today.”

Killing work is leadership.

2) Commit

If it matters, commit properly.

Commit means:

• owner
• next step
• deadline
• definition of done

Not “keep going.”

A real commitment.

3) Contain

If it matters but not now, contain it.

Containment is a focus skill.

It sounds like:

• “Not now—we’ll decide on Oct 3 after the client review.”
• “Not now—we’re waiting for budget confirmation. Next check-in is Sept 22.”

Containment reduces threat because it replaces ambiguity with structure.

How to restart projects without restarting chaos

A common fall pattern: leaders “restart” projects by announcing urgency.

But if you restart without clarity, you restart chaos.

Use two tools: Definition of Started and Containment language.

Definition of Started: roles, first deliverable, decision owner

Before a project is considered “started,” confirm:

• Roles: who is doing what?
• First deliverable: what’s the first tangible output?
• Decision owner: who makes the call when trade-offs appear?

If you don’t define these, your team will create their own assumptions—and you’ll pay for it in rework.

Containment language: “Not now” with a date and a reason

Most leaders avoid saying “not now” because they fear it will sound dismissive.

But “not now” without containment is what creates overload.

Try this structure:

• “Not now—because [reason].”
• “We’ll revisit on [date].”
• “If [trigger] happens, we’ll pull it forward.”

That’s respectful, clear, and stabilizing.

Preparing for winter: protect capacity before illness/holidays hit

Winter doesn’t just reduce time.

It reduces capacity.

Illness, holidays, and year-end pressure shrink your available focus. If you don’t reduce open loops in September/October, you’ll hit November with a backlog your nervous system can’t carry.

Build a buffer week and a decision gate

Two practical moves:

• Buffer week: one week per month with fewer launches and more completion
• Decision gate: a rule like “No new projects start without an owner, first deliverable, and decision owner.”

Your team doesn’t need more motivation.

They need fewer open loops.

Try this today

Run a 15-minute Open-Loop Inventory with your team

Set a timer for 15 minutes.

• Everyone lists open loops silently (5 minutes)
• Share and capture them in one place (5 minutes)
• For each item, decide: Kill / Commit / Contain (5 minutes)

If you can’t decide in the moment, contain the decision:

• “We’ll decide by Thursday at 2:00pm.”

That alone reduces cognitive load.

Mindset Monday CTA: If you want a simple, science-backed leadership reset like this in your inbox each week, sign up for Mindset Monday. It’s built for busy leaders who want clarity, focus, and practical tools they can use immediately.

If you want, paste 5–10 of your team’s current open loops here (anonymized) and I’ll help you sort them into Kill / Commit / Contain with clean containment language you can use immediately.