Scrum Master Toolbox Podcast: Agile storytelling from the trenches

BONUS: Your Developers Got 20x Faster — Now Watch Your Product Managers' Heads Explode
Clarke Ching is "The Bottleneck Guy" — and he just spotted the bottleneck that AI is about to create in every software organization. It's not in the code. It's inside the heads of the people who decide what gets built. In this conversation, Vasco and Clarke unpack why speeding up developers with AI tools pushes the real constraint upstream — onto product managers, designers, and leaders — and what to do before cognitive overload crushes the people your organization depends on most.
Every Business Has a Bottleneck — Most Are in the Wrong Place
"Every single client I have is a detective puzzle. We're looking for this quiet killer sitting inside their business, siphoning off money. And if you look at them without the idea of going 'where's the bottleneck?' — you mistake the busyness for productivity."
 
Clarke approaches Theory of Constraints like a detective story, not a physics lecture. Every business has a bottleneck — the narrowest point that chokes throughput. The question isn't whether you have one, it's whether it's in the right place. In software development, Clarke argues, the bottleneck should almost always be the developers. Not because they're slow, but because they're the pacing resource — like the aircraft carrier in a naval fleet that sets the speed for everything else. When developers are the bottleneck, the people upstream (product managers, designers, architects) have time to curate high-quality, high-value inputs. The people downstream (testers, ops) can deliver fast feedback. Everything flows. But when the bottleneck drifts somewhere else — and nobody notices — everyone gets busy, nothing flows, and the organization mistakes that busyness for productivity. Clarke's latest book, The Speed Book, lays out how to find where your bottleneck actually is and move it to where it belongs.
AI Just Moved the Bottleneck — And Nobody's Talking About It
"Just imagine one person trying to feed 100 developers. It's ridiculous. Everyone goes, 'oh, that's just crazy.' But that's kind of going to be what it's like."
 
Here's the problem: AI coding tools — Claude Code, Cursor, Copilot — are making developers dramatically faster. If a team of 5 developers becomes 20x more productive, that's the equivalent of 100 developers. But you still have one product manager feeding them. The bottleneck hasn't disappeared — it's moved upstream. And when a bottleneck moves to the people who make product decisions, three things happen: they cut corners on requirements (shipping half-baked ideas because the team can turn them around fast), they feed developers busy work just to keep them occupied, and — worst of all — they lose the time needed to push through complexity to find elegance. Clarke references Steve Jobs's insight: Apple kept working past "peak complexity" until they reached "peak simplicity." That's where great products come from. But a product manager juggling work for 100 developers has no time for that journey. Elegance goes out the window.
Why Giving AI to Product People Almost Makes Things Worse
"If you want to wear your dog out so she sleeps, don't take her for long walks. Make the dog think. Brain games exhaust the dog faster than running."
 
The obvious fix — give product people AI tools too — sounds right but misses the point. AI can handle the easy parts of product work: drafting user stories, generating specs, compiling research. That's the equivalent of taking the dog for a run. But the hard parts — the deep thinking about what to build, why it matters, how features interact — that's brain work. And brain work is exhausting in a way that volume work is not. Clarke works with senior leaders whose biggest challenge is pacing themselves. Heavy cognitive lifting burns through energy fast — your brain consumes 30-40% of your body's glucose when you're thinking hard. When AI handles the easy work, the proportion of your day spent on exhausting brain work jumps from maybe 15-20% to 50% or more. It's like lifting weights for six hours straight. You don't get stronger — you break down. On top of that, product people go from coordinating one stream of work to juggling many simultaneous initiatives. Clarke calls these "idea grenades" — and when you're juggling chainsaws with grenades attached, you start dropping things.
The Real Danger: Going in the Wrong Direction, 100x Faster
"If you change the relative capacities and make some of them much, much faster, the bottleneck's gonna move. My next book, jokingly, is gonna be called 'Who Moved My Bottleneck?'"
 
There's an amplification effect that makes this worse than a simple throughput problem. An error in a line of code affects one line. An error in a design document ripples into hundreds of lines. An error at the strategic level — building the wrong features entirely — can be a disaster for the company. Now add AI speed to that equation. Overwhelmed product people making rushed decisions don't just slow things down — they point the entire organization in the wrong direction, and AI-powered developers execute that wrong direction at 20x speed. As Clarke puts it: you crash into the mountain, faster. The fundamental Theory of Constraints insight applies: if you speed up a non-bottleneck resource, you don't speed up the system. You just create more work-in-progress, more chaos, and more cognitive load for whoever the real bottleneck is.
Four Experiments to Try Before Cognitive Crush Hits Your Team
"Quality will come from actually slowing down. Money, profits will come from slowing down, building very good products, focusing on why we're building these products, not just how do we keep the AIs working."
 
Clarke offers four practical experiments for teams navigating this shift:
 
Get product people working with AI — as a thought partner, not a turbo boost. Teach them to delegate the routine work to AI so they can protect their cognitive energy for the decisions that actually matter. Think of AI as a delegation tool, not a productivity multiplier.

Help product people find their sustainable pace. Like Clarke's gym trainer who said "don't come five days a week or you'll never come back" — the people doing heavy cognitive lifting need to pace themselves. Old-school agile called this sustainable pace. It's never been more relevant.

Don't try to keep developers (or AI) busy all the time. The instinct to maximize utilization is the instinct that creates the problem. With AI, you're renting capacity by the minute, not paying salaries. Use it at the pace of good product thinking, not at maximum throughput. Turn the tap on and off as needed.

Measure what matters: value delivered, not stories completed. If 60-70% of features rarely get used today, imagine what happens when you 20x the feature output without improving the decision quality upstream. More features, more waste — at scale.

About Clarke Ching
Clarke Ching is "The Bottleneck Guy" — a Theory of Constraints and lean expert who wrote Rolling Rocks Downhill, the agile+lean business novel that never mentions agile, and The Bottleneck Rules. Born in New Zealand, he spent 20 years abroad (15 of them in Scotland) before returning home. He's spent decades helping teams find and manage the one constraint that controls everything else. LinkedIn
 
You can link with Clarke Ching on LinkedIn.

Mukhtar Kadiri: The Three Qualities That Separate Great Product Owners From Those Who Just Drop Tickets
The Great Product Owner: Decisive, Versatile, and Credible at Every Level
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"This person could hold his own at any level of the organization — with executives, with engineering leadership, and with the team." - Mukhtar Kadiri
 
Mukhtar describes the best product owner he ever worked with through three distinct qualities. First, this person could operate at any level — equally comfortable in a strategic conversation with executives and in a tactical session with the engineering team. Second, they had vast cross-functional knowledge. They weren't a specialist in any one domain, but they could hold intelligent, credible conversations with marketing, go-to-market, customer success, and engineering alike. And third — perhaps most critically — they were decisive. In ambiguous environments where nobody has done this before, teams need someone who will pick a direction and say "let's find out," even if the decision might be wrong. That decisiveness, combined with the ability to course-correct early, is what separates great product owners from those who leave teams waiting for direction that never comes.
 
Self-reflection Question: Which of these three qualities — operating at any level, cross-functional credibility, or decisiveness — is strongest in your product owner, and which one needs the most development?
The Bad Product Owner: Not Owning the Backlog
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"If you don't have a strong product person, engineering just takes over the backlog. And that is dangerous, because it's product that is the representative of the customers." - Mukhtar Kadiri
 
Mukhtar has seen it happen repeatedly: when a product owner doesn't truly own the backlog, a strong engineering lead steps in and takes over prioritization by default. Things still get built — often beautiful, technically elegant solutions — but they don't produce business value because engineering lacks the customer intimacy that product should bring. The fix isn't simple, but Mukhtar identifies three levers. First, mentorship — pairing a junior product person with a more senior one to build confidence and skills. Second, building technical literacy — a product owner who can't meet engineering halfway will always be seen as an outsider dropping tickets. And third, closing the relationship gap between product and engineering. As Mukhtar points out, a product owner is technically a part of the team, but if the team doesn't feel like they're a part of the team, that gap becomes a chasm. There needs to be real overlap between engineering and product — not just shared meetings, but shared understanding.
 
Self-reflection Question: Is your product owner truly a member of the team — or are they just someone who shows up to drop tickets and disappear until the next sprint planning?
 
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
 
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
 
Buy Now on Amazon
 
[The Scrum Master Toolbox Podcast Recommends]
 
About Mukhtar Kadiri
 
Mukhtar Kadiri is a PM career coach with 15+ years in project management. He specializes in helping project and program managers land $100–300K roles. He's been named the #1 PM in Canada. He also has a LinkedIn following of 67K+ professionals. He shares practical insights for FREE on LinkedIn, where he talks about job search, career growth, and thriving as a PM.
 
You can link with Mukhtar Kadiri on LinkedIn.

Mukhtar Kadiri: Why Success Means Nothing If the Project Doesn't Move the Business Forward — And How Public Commitments Keep You Honest
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"If you're not careful with success, you can deliver a project, but the project will really not do much for the business." - Mukhtar Kadiri
 
For Mukhtar, success is personal — he's the kind of project leader who gets emotionally invested, who thinks about the project after hours, who needs recovery time between engagements. And that emotional investment shapes how he defines success: not as hitting deadlines or completing tasks, but as delivering real business value. He breaks success metrics into three buckets using his signature rule of three: business and product metrics (NPS, revenue, market penetration), project management metrics (velocity, burn-down, risk scores), and software and system metrics (availability, transactions per second, platform health). But the real insight is in how he holds himself accountable. Mukhtar makes public commitments at the start of every project — "Expect status updates from me every week" — because he knows that the discipline of narrating the project's story every week forces him to truly understand what's happening. A status report isn't bureaucratic busywork when you approach it as storytelling: you have to make sense of the data, surface what's relevant, and articulate where the project actually stands. If you can't tell the story, something's missing from your understanding. That weekly narrative becomes both an accountability mechanism and an early warning system.
 
Self-reflection Question: Can you tell the story of your project right now — not just the tasks completed, but the narrative of where it stands, why, and what that means for the business?
Featured Retrospective Format for the Week: What Worked / What Didn't Work / Next Steps
Mukhtar is a firm believer in simplicity, and his favorite retrospective format reflects that — the classic "What worked, what didn't work, and next steps." He applies his rule of three here as well: three categories are easy for humans to hold in their heads, removing cognitive overhead so the team can focus on the conversation itself. But Mukhtar is quick to point out that a simple structure can still produce terrible retrospectives. What matters more is the facilitation: making sure people feel safe at the very start, level-setting so participants can "land" into the retrospective after jumping from another meeting, giving everyone a moment of quiet introspection to write things down before discussion begins — ensuring both quiet and loud voices are heard. He prepares for every retrospective because, as he puts it, "if you run a bad retro, you could do damage to your team morale and your project." Active facilitation — watching for who isn't speaking, encouraging quieter voices, managing tone — is what transforms a simple format into a powerful conversation.
 
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
 
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
 
Buy Now on Amazon
 
[The Scrum Master Toolbox Podcast Recommends]
 
About Mukhtar Kadiri
 
Mukhtar Kadiri is a PM career coach with 15+ years in project management. He specializes in helping project and program managers land $100–300K roles. He's been named the #1 PM in Canada. He also has a LinkedIn following of 67K+ professionals. He shares practical insights for FREE on LinkedIn, where he talks about job search, career growth, and thriving as a PM.
 
You can link with Mukhtar Kadiri on LinkedIn.

Mukhtar Kadiri: Merging Three Companies Into One Platform — When Founders Can't Let Go and Leaders Won't Decide
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"A lot of times, conflict arises because people don't understand each other. The first thing you need to do is make sure they understand each other." - Mukhtar Kadiri
 
Mukhtar brings us a challenge from a merger and acquisition program where a dominant software company acquired two competitors simultaneously — both solving the same market gap, each with their own platform, their own founders still in place, and their own fierce loyalties. The mission: merge three platforms into one. But the technical challenge was the easy part. The real complexity was human — founders who'd built their companies from scratch watching their babies potentially get retired, teams losing people to low morale and uncertainty, and leadership paralyzed by the knowledge that every decision would make somebody unhappy. Together, Mukhtar and Vasco explore a four-step approach to navigating these high-stakes disagreements: first, create a feeling of time abundance — never rush a decision that requires buy-in. Second, get each side to present their perspective with only clarifying questions, no judgment. Third, name the disagreement explicitly — turn emotions into concrete, debatable statements. And fourth, co-create an alternative solution that doesn't come from either original position, because co-creation builds commitment. Mukhtar adds a critical fifth element: steel-manning — having each side articulate the other's argument as if defending it. When people feel genuinely understood, even "disagree and commit" becomes possible.
 
In this episode, we refer to steel-manning and the concept of disagree and commit.
 
Self-reflection Question: When you're facilitating a disagreement between two strong positions, do you rush toward a decision — or do you invest the time to make sure both sides can articulate each other's argument before you even think about next steps?
 
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
 
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
 
Buy Now on Amazon
 
[The Scrum Master Toolbox Podcast Recommends]
 
About Mukhtar Kadiri
 
Mukhtar Kadiri is a PM career coach with 15+ years in project management. He specializes in helping project and program managers land $100–300K roles. He's been named the #1 PM in Canada. He also has a LinkedIn following of 67K+ professionals. He shares practical insights for FREE on LinkedIn, where he talks about job search, career growth, and thriving as a PM.
 
You can link with Mukhtar Kadiri on LinkedIn.

Mukhtar Kadiri: When the Smartest Person on the Team Becomes the Biggest Bottleneck — And Explodes in a Meeting
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"A lot of times, the problem is not necessarily technical. It's a human problem. Just figuring out the human dynamics removes the obstacles and makes the project flow." - Mukhtar Kadiri
 
Mukhtar was brought into a healthcare software project where the team couldn't hit any of their milestones. The product manager, engineering team, and head of engineering were supposed to be self-sustaining, but chaos reigned. What Mukhtar found through his one-on-ones was a pattern of finger-pointing — product blaming engineering, engineering blaming product. Then, in one meeting, the head of engineering exploded. He burst out yelling in front of the entire team. In a private conversation afterward, Mukhtar discovered the root cause: this brilliant architect was a bottleneck. Everyone depended on him, he was stretched across multiple projects, and the frustration had been building with no outlet. Mukhtar's approach was direct — "Your name is on this project. Yelling is not going to help." But the real insight came from what happened next. Once the head of engineering started controlling his outbursts, team morale improved almost immediately. Combined with basic structure — regular meetings, low-hanging-fruit milestones — the team built momentum and eventually became self-sufficient. The lesson? No matter how technical the challenge looks, it's always a people problem. And one-on-ones aren't just status updates — they're pressure valves that prevent public explosions that can cause irreparable damage to team morale.
 
Self-reflection Question: Is there someone on your team who's carrying too much load in silence — and what would it take for you to create a safe space where they can express that frustration before it boils over?
Featured Book of the Week: HBR Project Management Handbook by Antonio Nieto-Rodriguez
Mukhtar recommends the HBR Project Management Handbook because, as he puts it, "A lot of project management books, I can read them and it's almost like I'm not really learning anything new. But this one had substance." After stumbling into project management and leading projects for seven years before even pursuing his PMP, Mukhtar found that most PM books simply codified what he already knew from experience. The HBR handbook was different — it offered breadth, depth, and fresh approaches to common project management challenges. He also recommends the Rita Mulcahy PMP Exam Prep for those preparing for PMP certification, noting that studying for the exam crystallized frameworks around things he had been doing instinctively.
 
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
 
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
 
Buy Now on Amazon
 
[The Scrum Master Toolbox Podcast Recommends]
 
About Mukhtar Kadiri
 
Mukhtar Kadiri is a PM career coach with 15+ years in project management. He specializes in helping project and program managers land $100–300K roles. He's been named the #1 PM in Canada. He also has a LinkedIn following of 67K+ professionals. He shares practical insights for FREE on LinkedIn, where he talks about job search, career growth, and thriving as a PM.
 
You can link with Mukhtar Kadiri on LinkedIn.