take5IRL Podcast

Everyone can say yes. But who’s allowed to say no?When decision-making authority is unclear, priorities shift, teams wait for approvals, and important choices get made by default. In this episode of Take 5 IRL, agilityIRL partners Mike Studeman and Pat Campbell explore who owns the different kinds of “no”—and how clear decision rights help organizations move forward.They break down three distinct types:• Product: “Not now” or “not this”, deciding priority and scope.• Technical: “Not that way” or “not at that quality level”, protecting the product’s long-term health.• Safety and compliance: “Not safe” or “not compliant”, an explicit veto with a clear purpose.Problems arise when one group borrows another group’s authority, or a senior leader’s “one small request” quietly changes the team’s priorities.In this episode, you’ll learn:• Why reversible decisions should be delegated and made quickly.• Which decisions deserve leadership’s time and attention.• How decision deadlines and explicit defaults can reduce waiting.• Why reopening a decision without new information creates waste.• How to build a one-page decision rights map before conflict happens.• Why clear safety and compliance boundaries matter for medical device and MedTech organizations.“The most expensive decision in any organization is the one that nobody explicitly makes.”Explore agilityIRL’s portfolio prioritization check and learn how we help teams and leaders improve alignment, product development flow, and decision-making:https://www.agilityirl.com/Subscribe to Take 5 IRL for practical conversations about leadership, agility, and delivering better results in complex and regulated environments.Who owns the “no” in your organization? Share your experience in the comments.#Leadership #DecisionMaking #ProductDevelopment #MedTech #Take5IRL

Nobody puts the pre-release scramble in the project plan. So why does it keep happening?In this episode of Take 5 IRL, agilityIRL partners Pat Campbell and Mike Studeman explore why product development teams end up racing to finish documentation, traceability, risk records, and release preparation, and how seemingly reasonable decisions create that last-minute chaos.For medical device and MedTech teams, “code complete” can still be a long way from submission ready. Deferring the remaining work adds costs through lost decision rationale, rework, staff turnover, and burnout.In this conversation:• Why waiting for the design to stabilize makes documentation harder• How deadlines, milestones, and rewards encourage the scramble• Why deferred compliance work behaves like debt with interest• How to measure the gap between code complete and submission ready• Practical ways to capture decisions, rehearse releases, and celebrate readinessYour Take 5 Challenge:Review the final six weeks of your most recent release. For each task, identify the earliest point it could have been completed. How many could have happened two or three months earlier? Share that number with your team and start the conversation.Don’t plan the scramble. Plan the release.Explore how agilityIRL helps teams improve product development flow, quality, and delivery in regulated environments:https://www.agilityirl.com/Subscribe for more practical conversations about Agile, leadership, and medical device product development. What always ends up in your team’s release scramble? Tell us in the comments.#MedicalDeviceDevelopment #Agile #MedTech #ProductDevelopment #Take5IRL

In this episode of Take 5 IRL, Jeff Lee and Pat Campbell explore what great organizations do differently, and how leaders build momentum through better decisions, stronger systems, and a culture of continuous learning.Using the analogy of a heavy flywheel, they explain how small, consistent improvements begin reinforcing one another and turn into lasting organizational change.In this episode, we discuss:• Systems thinking: improving the conditions behind problems instead of blaming people • Finishing meaningful work and celebrating customer outcomes • Building quality into product development rather than testing it at the end • Why AI amplifies an organization’s existing strengths and weaknesses • Turning retrospectives into learning that changes how teams work • Leadership’s role in removing friction and improving delivery Whether you’re navigating AI adoption, Agile delivery, medical device development, or organizational change, these habits help teams consistently deliver value.🎯 *The Take 5 Challenge:* Ask your leadership team: “What result do we want to achieve over the next 90 days that would improve the entire system?” Then commit to measuring progress, learning along the way, and adjusting your approach.Organizational maturity isn’t a destination. It’s a habit you develop as you go.Subscribe to Take 5 IRL for practical conversations about leadership, Agile, AI, and better business outcomes. Explore the other episodes in this series for more ways to improve how your organization works.Learn more about agilityIRL: https://www.agilityirl.com/#Leadership #SystemsThinking #ContinuousImprovement #Agile #Take5IRL

Your bathroom scale gives you a number, But does it tell you how healthy you are? Your business dashboard might have the same problem.Tickets closed. Hours worked. Features delivered. Those numbers show activity, but are they telling you whether you’re creating value?In our newest Take 5 IRL episode, Jeff Lee and Pat Campbell explore why the measures you choose shape the behavior you get, and how to connect those measures to outcomes that matter.

What does servant leadership look like when you’re responsible for more than one team?In this episode of Take Five IRL, Jeff Lee and Mike Studeman explore why servant leadership becomes even more important at the senior director level. The job isn’t to attend every meeting or solve every problem yourself. It’s to address the conflicting priorities, delayed decisions, outdated policies, and cross-functional bottlenecks that make good work harder than it needs to be.They discuss how leaders can create clarity, hold people accountable without creating a culture of blame, and build an organization that doesn’t depend on a hero to keep things moving.Subscribe for more practical conversations about leadership, agility, and improving how work gets done.Learn more about agilityIRL: https://agilityirl.com#ServantLeadership #Leadership #AgileLeadership #TakeFiveIRL

When your team says a feature is “done,” what still has to happen before it can actually be released?

Documentation?
Testing?
Traceability updates?
Quality review?
Risk assessment?

Every “yes” represents unfinished work—and unfinished work is inventory that slows flow, extends cycle times, and creates the end-of-release scramble regulated teams know too well.

In the newest episode of Take Five IRL, Pat Campbell and Mike Studeman explain why a Definition of Done is more than a checklist. It’s a promise of quality, transparency, and release readiness.

Because “done” shouldn’t mean finishing your part. It should mean finishing the work.

If you like what you hear, download our free "Definition of Done" checklist here: https://lnkd.in/gUuPbydj

Listen to the latest episode and take this week’s five-minute challenge: review your Definition of Done and identify everything your team is still leaving until later.

#MedicalDevices #MedTech #RegulatedProductDevelopment #Agile #QualityManagement #ProductDevelopment #DefinitionOfDone

AI isn’t going to fix your organization’s problems. In fact, it might help you create them faster.In this episode of Take Five IRL, Mike Studeman and Pat Campbell explore why true AI readiness doesn’t start with choosing the right technology, it starts with leadership.AI is a multiplier. Strong priorities, effective decision-making, and healthy product development systems can become even better with AI. But unclear priorities, overloaded teams, and broken processes? AI can accelerate those too.Mike and Pat discuss why leaders need to define the business outcomes they actually want AI to improve, establish clear governance and guardrails, and determine where human judgment still matters. They also explain why the question shouldn’t be “Which AI tools should we buy?” but rather “What business problem are we trying to solve?”And this episode’s Take Five Challenge gives leadership teams a simple exercise: identify the three biggest challenges you want AI to help solve, then ask whether you’ve actually addressed the underlying processes first.In this episode:Why AI readiness begins in the executive suiteHow AI can amplify both good and broken systemsWhy business outcomes should come before technologyThe role of leadership in AI governanceWhy competitive advantage comes from your ability to learn and adapt, not simply the AI tools you purchaseHow to avoid automating chaosLearn more about how agilityIRL helps organizations improve product development and prepare for AI at agilityirl.com.👍 Like the episode and subscribe for more practical conversations about leadership, product development, AI, and ways of working that actually work in real life.#AI #ArtificialIntelligence #AIReadiness #Leadership #AIGovernance #ProductDevelopment #BusinessTransformation #Agile #TakeFiveIRL #agilityIRL

What if the way your organization funds work is actually slowing delivery down?In this episode of Take Five IRL, Mike Studeman and Pat Campbell tackle a potentially controversial idea: Stop funding projects. Start funding flow.They’re not arguing that projects should disappear. Instead, they explore what happens when organizations continually launch and fund new projects without increasing capacity. More work enters the system, WIP increases, teams context-switch, dependencies grow—and delivery gets slower.Mike and Pat discuss why leaders should shift the conversation from “Who can we put on this project?” to “What’s the most valuable thing this team should deliver next?” They also explore the value of long-lived, stable teams with deep customer knowledge and why leadership—not individual Agile teams—ultimately owns the funding model and the flow of work through the organization.In this episode, you’ll learn about project funding vs. flow, the impact of too much work in progress, why being busy doesn’t necessarily mean delivering value, how stable teams can improve customer outcomes, and the flow metrics leaders should pay attention to—including cycle time and throughput.The Take Five Challenge: At your next leadership meeting, list every project currently underway and ask: Which are continuously delivering value? Which are consuming capacity? And if you paused one tomorrow, would something else get delivered faster?Because sometimes the bottleneck isn’t your people. It’s your portfolio.Learn more about agilityIRL at agilityirl.com.#Agile #ProductDevelopment #Leadership #ProductManagement #PortfolioManagement #Flow #AgileLeadership #BusinessAgility #TakeFiveIRL

Does compliance really slow down innovation in medical device product development?It can certainly feel that way. But the real problem often isn't compliance itself—it's when and how quality and regulatory work gets done.In this episode of Take 5 IRL, agilityIRL partners Pat Campbell and Mike Studeman challenge the common belief that regulated product development forces organizations to choose between speed and compliance.When documentation, traceability, verification, risk controls, Quality, and Regulatory are pushed toward the end of development, teams can find themselves caught in the dreaded pre-release scramble—reconstructing decisions, finding evidence, repeating tests, completing documentation, and discovering gaps just when everyone thought the product was ready.Pat and Mike discuss a different approach: build quality and compliance into product development from the beginning.In this episode, you'll learn:Why late compliance work creates delays and unnecessary reworkHow to make Quality and Regulatory part of iterative product developmentWhy your Definition of Done should include technical, quality, documentation, and regulatory expectationsHow outdated Quality Management Systems (QMS) can unintentionally create bottlenecksWhy Engineering, Quality, Regulatory, Product, and leadership need shared accountabilityHow moving compliance activities earlier can make delivery more predictableA simple Take 5 Challenge your team can try immediatelyPat and Mike also share a real-world example in which a company's submission-documentation effort dropped from 27 weeks to just 8 weeks after changes were made to its process and workflow—a 19-week improvement with implications not just for the business, but for how quickly therapies can reach patients.The takeaway?Compliance doesn't have to slow innovation. Late and disconnected compliance does.When quality and regulatory expectations are built into the delivery system, teams can reduce rework, eliminate surprises, improve visibility, and create a smoother path to release.If your organization is trying to make Agile work in a regulated medical device environment, agilityIRL helps teams align iterative product development with quality systems and regulatory expectations.Learn more at agilityIRL.com👍 Like this episode if you found it helpful🔔 Subscribe for more practical conversations about leadership, product development, Agile, AI, and regulated medical device development💬 Tell us in the comments: At what point in your development process do Quality and Regulatory get involved?#MedicalDevice #MedTech #FDACompliance #Agile #ProductDevelopment #QualityManagement #RegulatoryAffairs #QMS #AgileMedicalDevice #Take5IRL

Sometimes the best thing a leader can say is: “No, not right now.”

It sounds simple. In practice, not so much.

Leaders want to support their teams, satisfy stakeholders, and deliver more value. So when someone asks, “Can we just squeeze this one thing in?”, the instinct is often to say yes.

Every additional priority has a cost.

More work in progress can mean:

→ Work piles up

→ Deadlines slip

→ Teams slow down

→ Morale suffers

→ Your highest-priority work takes even longer to finish.

In the newest episode of Take Five IRL, Mike Studeman and Jeff Lee talk about one of the most overlooked leadership skills: knowing when to say “no, not right now.”

They dig into WIP limits, prioritization, Little's Law, and why keeping everyone at maximum capacity can actually make the entire system slower.

The big takeaway? Organizations don't get better by starting more work. They get better by finishing the work that matters most.

🎧 Watch the newest episode of Take Five IRL and ask yourself: What could your organization finish faster if you were willing to put something else on pause?#Leadership #Agile #ProductDevelopment #Prioritization #WorkInProgress #TakeFiveIRL