『Definitely, Maybe Agile』のカバーアート

Definitely, Maybe Agile

Definitely, Maybe Agile

著者: Peter Maddison and Dave Sharrock
無料で聴く

概要

Adopting new ways of working like Agile and DevOps often falters further up the organization. Even in smaller organizations, it can be hard to get right. In this podcast, we are discussing the art and science of definitely, maybe achieving business agility in your organization.© 2026 Definitely, Maybe Agile マネジメント マネジメント・リーダーシップ 経済学
エピソード
  • Two Speeds, One Organization
    2026/03/05

    Something is shifting inside organizations right now, and it's creating a split that's hard to ignore. AI is compressing the time it takes to generate, validate, and prototype ideas. Some people inside your org are moving at a completely different speed than the systems built to support them. Peter and Dave are calling it the great decoupling, and it's already happening whether you've noticed it or not.

    In this episode, they dig into why acceleration in one part of a system creates pressure everywhere else. When you map the end-to-end journey from idea to live product, you often find 30 to 40 distinct steps. AI is handling a handful of them. The rest? Still waiting on decisions, reviews, and handoffs that haven't changed in years. Development isn't the main blocker anymore. Decision latency is.

    They talk through what it looks like when product managers are running parallel experiments and validating ideas in hours, then slamming into unchanged processes for security sign-off, change control, and release management. And why the smartest people on your team are quietly finding workarounds rather than waiting in line, which creates more risk, not less.

    This isn't a conversation about AI hype. It's about the real organizational friction that shows up when the pace of work outgrows the systems designed to manage it. And what you can actually do about it.

    If your team is moving faster but waiting longer, this one's worth your time.

    This Week's Takeaways:

    1. Acceleration in one part of the system creates stress everywhere else
    2. Map the end-to-end flow before you optimize any single part
    3. If it's happening inside your organization, you need to deal with it internally

    If this episode resonated, follow Definitely Maybe Agile wherever you listen to podcasts so you never miss a conversation. And if you know someone sitting at one of those 40 steps wondering why everything feels stuck, send this one their way. There are plenty more episodes worth your time at definitelymaybeagile.com.

    続きを読む 一部表示
    19 分
  • AI and Automation with David Kilzer
    2026/02/26

    A few times in tech, two streams collide, and everything changes. David Kilzer has spent 50 years putting automation to work in manufacturing and distribution around the world, and he thinks we're at one of those moments right now. The convergence of AI and humanoid robotics, in his view, is the biggest shift humankind has faced since fire.

    In this episode, David joins Peter and Dave to unpack where automation ends, and AI begins, why confusing the two creates brittle systems, and what organizations should actually be thinking about when making investment decisions right now. The short version: don't slap AI on everything.

    This week's takeaways:

    • Stay optimistic, stay connected, and participate in the change. Don't be overrun by it.
    • Automation works brilliantly within its designed boundaries. But unprecedented events expose its fragility in ways we don't always anticipate.
    • The shift toward flexible, adaptable robots means the environment no longer has to be built around the machine. The machine adjusts to the environment instead.
    続きを読む 一部表示
    37 分
  • Flow Over Efficiency with Steve Pereira
    2026/02/19

    Peter Maddison and Dave Sharrock sit down with Steve Pereira, founder of Visible Flow Consulting, to talk about something most organizations get backwards: the obsession with efficiency at the expense of actual flow.

    Steve works with large companies to improve operational performance through value stream mapping and continuous delivery. But the conversations he keeps having aren't about cutting costs. They're about untethering capable people from the systems that are quietly holding them back.

    In this episode, the three dig into why high utilization is often the enemy of good work, how lean thinking applies to knowledge work without losing what makes knowledge work different, and why adding AI on top of a broken system just makes things break faster.

    If your organization feels like it should be doing more than it is, this one's worth your time. And if you want all 4 takeaways, don't miss the last few minutes of the episode.

    This week´s takeaways:

    1. Step back from the work to look at how the work works. Whether it's a value stream mapping session or a quiet moment of reflection, intentional distance helps you see not just whether the saw is dull, but whether you're sawing the right tree.
    2. High utilization is not efficiency. Running people and teams at full capacity removes the slack needed to respond, adapt, and make good decisions. Optimal is closer to 80 percent. The rest needs to be budgeted, not eliminated.
    3. Understand your system before adding new tools. Whether it's AI, automation, or the latest framework, bolting new capabilities onto a system you don't fully understand tends to make existing problems worse, not better. Map first. Then act.

    Extra Resources:

    📖 Tools of Flow by Tody Goldratt: https://www.goodreads.com/es/book/show/75304520-goldratt-s-rules-of-flow

    続きを読む 一部表示
    39 分
まだレビューはありません