Most organizations think they have a capacity problem. They usually don't.

What they have is a work-in-progress problem. And those two things call for very different solutions.

In this episode, Peter Maddison and Dave Sharrock dig into one of the most persistent headaches in organizational management: capacity tracking. Why does the instinct to measure utilization backfire? Why does loading people up to 100% actually slow things down? And what should leaders be asking instead?

The conversation covers the real cost of context switching, why that "nearly done" project is probably further away than it looks, and how AI is making all of this more urgent, not easier.

Three things to take away from this episode:

1. 100% utilization is not a goal. It's a warning sign.
2. The right question isn't "how much capacity do we have?" It's "how much work in progress can we actually sustain?
3. AI accelerates your breaking points.

If this conversation resonated, there's more where it came from. Peter Maddison and Dave Sharrock explore these kinds of organizational challenges every week on Definitely Maybe Agile - the podcast that gets into the real complexity of modern ways of working, without the buzzwords.

Listen wherever you get your podcasts, or visit definitelymaybeagile.com to catch up on past episodes and reach out with your own questions.

AI is changing how products get built. That part isn't news. But it's also changing who needs to do what - and that's a conversation most organizations haven't had yet.

In this episode, Peter and Dave dig into one of the more interesting tensions emerging in 2026: as coding agents take on more of the actual development work, the thing that drives quality output isn't just better tooling. It's better context. Clear, structured, well-owned context that tells agents what you're actually trying to build, who it's for, and what can't be compromised.

Which raises a real question. Who owns that? Where does it live? And what happens when it's missing - which, let's be honest, it usually is?

They get into the rise of "context engineering" as a role, why the name creates its own problems, and what this shift means for product owners, product managers, and the long-standing gap between business and technology teams.

Key takeaways from this episode:

• Most organizations have never truly written down their product intent in a structured, usable way. AI is making that gap impossible to ignore.
• Good context drives better outcomes from agents - and the work of capturing, structuring, and maintaining that context needs a clear owner.
• Start asking: what context exists to guide your products? Where is it stored? Who creates it? Who picks it up and moves it through the system?
• The business and technology divide matters more now, not less. You can't afford to throw things over the wall anymore. The two groups need to work closely together, not in parallel.
• What's new here isn't the idea. It's the urgency. These are transformations organizations have been attempting for years. AI is just forcing the issue.

Want to continue the conversation?

If this episode brought up questions about how your teams are navigating the shift to agentic development - or where context ownership actually sits in your organization - reach out at feedback@definitelymaybeagile.com. We'd love to hear what you're seeing.

A lot of organizations are betting that AI will make their teams faster. Some of them are right. Most are solving the wrong problem.

AJ Bubb, founder of MxP Studio and host of Facing Disruption, joins Peter and Dave to talk about what actually happens when AI lands in a development team without fixing the system around it. If engineers can't get approvals, can't get access, and spend half their day in meetings, AI just means they produce more output the organization still can't handle. That's not a tooling problem. It's a structural one.

They also get into velocity without direction, what ownership really looks like when a ticket gets blocked, and why synthetic user testing might be the most polite way to avoid talking to actual customers.

This Week's Takeaways

• Own the problem from the customer all the way down. When something is blocked, it's still yours until it moves.
• When an outcome surprises you in either direction, ask whether your model was wrong. Most teams take the win and move on. The ones that improve don't.
• Before reaching for a technical solution, ask why five times. The problem someone walks in with is usually the invitation to a conversation, not the actual problem.

If this episode got you thinking, we'd love to hear from you. Drop us a note at feedback@definitelymaybeagile.com or leave a review on your podcast app. And if you know someone navigating AI adoption right now, send this one their way.