M2: Managing Managers

If your team keeps filling your inbox with questions, updates, and requests for decisions, the problem may start before anyone writes an email.Jim worked with an executive who was spending much of her day responding to her team. She wanted to be available and helpful, but her own work kept getting pushed aside. When they reviewed her inbox together, they found capable people asking for things they needed to move forward: a decision, a priority, more context, or help with a blocker.In this episode, Jim and Thomas discuss the practice they put in place and why the executive reported a 40% reduction in internal email afterward.In this episode:Why being highly responsive can generate even more emailWhat to look for when you review the messages your team sends youTwo rules that make weekly one-on-ones a dependable place to get clarityHow giving direct reports the first part of the agenda builds ownershipWhy clearer decision rights can reduce unnecessary questions and updatesTry this: Look at the emails you’ve sent over the past few days. How many answered a question that could have been handled in a weekly conversation? How many involved a decision someone else could make if they knew they had the authority?Chapters00:00 — The inbox problem03:53 — What the team’s emails had in common06:41 — Where the requests were coming from07:33 — The weekly one-on-one practice11:41 — Why a dependable meeting time matters14:30 — Why the direct report leads the agenda19:34 — What Jim would change about his own one-on-ones as CEO22:01 — Clarifying who makes which decisions27:34 — A three-week experiment

You manage managers. Almost nothing you're accountable for gets done by your own hands -- it gets done because you asked someone, and they agreed.And yet the meeting ends with everyone nodding, and a week later the work hasn't moved. It's as if the meeting never happened.In this episode of M2: Managing Managers, Thomas Cox and Jim Prinzing name that pattern -- meeting amnesia -- and then show you the structure hiding underneath it. The manager who says yes and doesn't deliver looks like they have a character problem. The team that agrees in the room and stalls outside it looks like a culture problem. Both are the same structural failure, and it starts upstream from when you noticed it.What you'll get:The four phases of the Accountability Protocol -- Initiate, Negotiate, Perform, Accept -- and how to tell which one brokeWhere the damage gets done: you catch accountability problems at delivery, but we say more than 70% of those problems were created in the first two phasesThe weak Yes -- why "sure, I'll take care of it" from a direct report can be a red flag, and what to ask insteadEffort promises vs. outcome promises -- why demanding a deadline for a problem nobody has solved yet sets everyone up to failPerformance isn't finished until it's reported -- the handoff gap that burns days of your team's time before anyone noticesIf you want fewer surprises at the deadline, less rework, and direct reports who renegotiate proactively (instead of apologizing after they fail), this episode gives you a four-part structure you can teach your team -- and use yourself -- immediately.

You manage managers. That means more than half your business lives or dies on the quality of frontline supervision.And yet teams still spend enormous energy solving problems without ever confirming the outcome they’re solving for.In this episode of M2: Managing Managers, Jim and Thomas tackle one of the most common and expensive leadership blind spots: losing the “why” while obsessing over the “how.” Strong executors rise into leadership because they get things done. But that same wiring can pull teams deep into tactics, details, and forward motion—without shared clarity about what must be true at the end.What you’ll get:How to recognize when your team is optimizing activity instead of outcomesThe friction signal: Why hidden misalignment shows up as subtle conflict and reworkThe Outcome Question: “What do we want to be true?” and why it changes everythingVisceral clarity vs. intellectual clarity — and why metrics alone aren’t enoughA simple way to surface alignment in any meeting without creating status tensionIf you want faster decisions, less rework, and teams that move in the same direction instead of talking past each other, this episode gives you a practical clarity tool you can use immediately.

Scale your team’s speed and ownership without losing control.You want a team that spots problems, fixes them, and innovates without waiting for your permission. But how do you give that kind of autonomy without inviting chaos? In this episode of M2: Managing Managers, Jim and Thomas break down the "Operating Envelope"—the structural secret to building teams that run fast, own their work, and need less supervision.What you’ll get:The "Operating Envelope" Framework: How to define clear, firm boundaries (budget, safety, brand) so your team has total freedom to sprint inside them.The "Context over Control" Shift: Why giving your team more information (even financial realities) creates better decisions than giving them orders ever could.The Google "Error Budget": How to mathematically calculate how much failure is acceptable, so your team stops playing it safe and starts playing to win.The Hero Trap: Why "saving the day" when things go wrong actually destroys ownership and trains your staff to be helpless.Engineering Pride: How to use the envelope to trigger the deep psychological pride that drives "first-time quality" and high retention.Case Studies in Speed: Lessons from Google, Toyota’s production line, and Dutch nursing teams on how high-autonomy structures outperform hierarchies.If you are tired of being the bottleneck and want to build your team into a self-correcting, high-performance machine, this episode gives you the blueprint to step back so they can step up.

High-performing teams operate in a zone of "safe discomfort."In this episode of M2: Managing Managers, Jim and Thomas dismantle the false choice between being a supportive "servant leader" and a demanding driver of results. We break down the science and give you the scripts for upholding high standards without destroying morale.What you’ll get:The "Nice Guy" Trap: Why Jim’s early attempt to protect his team’s feelings actually capped their potential—and how to avoid the "performance ceiling" caused by high loyalty/low accountability.The Relating vs. Requiring Matrix: Why these aren’t opposites on a continuum. Learn how to move from the "Country Club" or "Sweatshop" quadrants into the "Best Boss" zone by both Relating and Requiring simultaneously.The "Micro-Hack" for Tough Feedback: A specific, 20-second opening script that lowers defenses and proves you care before you deliver hard news.The "Early and Often" Protocol: How to use tiny course corrections to prevent the dreaded "heavy conversation" conversation later on.Stress Titration: How to dial pressure up (or down) to keep different personality types in their specific Zone of Optimal Performance (Eustress).Permission to Push: Why your high performers actually want you to challenge them, and why "rescuing" them is a sign of distrust.If you manage managers who are reluctant to give honest feedback, this episode provides the mental models and language to help you show them how lead with backbone and heart.