When Methods and Frameworks Fail—the Challenge of Cognitive Overload

Your team doesn't need another framework. They need three questions: Why should I care? What's in it for me? How do I proceed?

I Bounced Between Five Contexts Today. Not Once Did I Reach for a Framework.

Forget about SAFe, LeSS, Holacracy, Team Topologies, Design Thinking, and the Business Model Canvas. AI Leadership Answers These Questions: Why Should They Care? What's In It for Them? How Do They Proceed?

Today, I bounced between at least five different contexts, and guess what? At no point did I pause dramatically, stroke my chin, and muse, “Hmm, I wonder which theoretical model or fashionable method applies here?” No, I never asked myself how one of the five hundred goal-setting frameworks might make me more productive or whether there’s a perfect two-by-two matrix that can magically streamline my day. I'm busy enough juggling life without adding abstract puzzles to my mental load. Instead, the only three questions I actually cared about today were:

• Why should I care? (Purpose)

• What's in it for me? (Benefit)

• How do I proceed? (Action)

The Problem: Too Many Models, Not Enough Clarity

Let’s face it: we leaders, coaches, consultants, and other self-styled change agents drown ourselves in a deluge of models. We seem to enjoy generating our own cognitive overload!

Scrum, SAFe, LeSS, Holacracy, Team Topologies, SWOT Analysis, Design Thinking, Theory of Constraints, Business Model Canvas, Balanced Scorecard, Eisenhower Matrix, Belbin Team Roles, Cynefin, Lean Startup, Wardley Maps, RACI Matrix, Porter’s Five Forces, Open Space Technology—seriously, the list never ends. There’s a new model every day!

In this age of relentless distraction, our brains feel more like ping-pong balls ricocheting through a pinball machine. Context-switching fries our mental circuits, and juggling multiple projects—usually an efficiency killer—becomes a necessary evil. Whether we do it well or poorly, cognitive overload is inevitable.

Context-Switching Makes Frameworks Useless

In a world where context-switching is as routine as breathing, the last thing people want is to memorize intricate distinctions between trendy workplace models. Is a Scrum team different from a Stream-Aligned Team? Can LeSS and SAFe coexist peacefully? How do Wardley Maps intersect with the Business Model Canvas? If you're pondering these questions with glee, congratulations: you're officially a model nerd (like me)!

However, let me be blunt. Among the real heroes—those actually doing the frontline work we're trying so desperately to improve—nobody cares.

Consider this:

1. Yesterday, I upgraded my customer management tool (action) because I want a more efficient way to handle relationships (purpose) for the sake of growing my business (benefit).

2. I dove into various Substack publications (action) because I'm intent on expanding my network (purpose) and drawing inspiration from smarter people (benefit).

3. My sister wanted me to contribute to a happy family brunch (purpose), so I scoured several recipes online (action) and selfishly picked something I love (benefit).

4. I drafted this article (action) guided by a monster Substack checklist because I aspire to influence other people’s thinking (purpose) and maybe, just maybe, earn a few paid subscribers (benefit).

5. I also obsessively researched a new venture in algorithmic management (action) because I want to make a difference (purpose) and I’m still after that elusive sustainable income (benefit).

And that was just five different contexts yesterday.

People tell me I’m admirably disciplined and focused, yet even I’m bouncing between contexts like a caffeinated squirrel. Imagine how chaotic the day is for everyone else!

---

I’m a founder, intrapreneur, and former CIO rethinking governance for the one-person business, navigating sole accountability in the age of intelligent machines—informed by plenty of scar tissue. All posts are free, always. Paying supporters keep it that way (and get a full-color PDF of my book Human Robot Agent plus other monthly extras as a thank-you)—for just one café latte per month.

---

Three Questions That Replace Every Framework

Throughout today’s circus, did I once think about Scrum, OKRs, Porter’s Five Forces, or any of those countless other useful models? Absolutely not. It was only these three questions that were continuously lurking in the back of my mind:

• Why should I care? (Purpose)

• What's in it for me? (Benefit)

• How do I proceed? (Action)

Please don’t misunderstand me; models are fantastic—for those of us obsessed with such toys. I've personally created plenty: Moving Motivators, Ten Lifecycle Stages, Behavioral Values, Seven Delegation Levels, Innovation Vortex, up to and including the pretty Wicked Framework that I offer in my new book. Models genuinely help me think.

But there’s a crucial thing to remember. Abstract models are tools for leaders, coaches, and consultants—not practical guidance for the average worker drowning in a tsunami of tasks, chats, and alerts. They don’t need another infographic diagram explaining the nuanced differences between a Product Owner and Product Manager. All they care about is clarity:

• Why should I care? (Purpose)

• What's in it for me? (Benefit)

• How do I proceed? (Action)

This isn’t groundbreaking. You’ll see this echoed in classic change management models like ADKAR, Kurt Lewin’s 3-Stage Model, and Kotter’s 8-Step Process for Leading Change. But, crucially, these models are designed for leaders and change agents—not the overwhelmed individuals we hope to influence. We don’t initiate organizational change by inviting workers to a two-day course on ADKAR, Kurt Lewin’s 3-Stage Model, or Kotter’s 8-Step Process for Leading Change.

For example, don't bother your team with yet another meta-level discussion about objectives versus outcomes versus initiatives versus impact versus whatever. Instead, get them to care about something that you deem important (purpose), explain why this matters to them personally (benefit), and show them the next steps to take (action). Save the meta-discussion for the nerds, like me.

Your Models Aren't Their Problem—Translate, Don't Teach

In our distraction-heavy world—filled with endless notifications, overflowing inboxes, and back-to-back virtual meetings—the average worker doesn’t have the mental bandwidth for a fifty-minute lecture on Holacracy versus Team Topologies.

Our job as leaders, coaches, and consultants is simple yet challenging: we should use our beloved models privately, interpret their wisdom, and translate our insights into straightforward answers everyone else actually needs.

Your team doesn’t need yet another method or framework—they need answers:

• Why should I care? (Purpose)

• What's in it for me? (Benefit)

• How do I proceed? (Action)

If you can’t answer these questions, you're just adding more noise.

Everyone already has plenty of that.

Would you ask another question?

Jurgen, Solo Chief

👇🏻 p.s. For my awesome supporters, I include Gemini’s Deep Research report on how these three questions compare with change management models such as ADKAR, Kurt Lewin’s 3-Stage Model, and Kotter’s 8-Step Process. 👇🏻