Episodios

  • Using AI to Go From User Insight to Better Backlogs - Mike Cohn
    Jan 28 2026

    Using AI to Go From User Insight to Better Backlogs - Mike Cohn

    AI is rapidly changing how product teams work—but the biggest opportunity isn’t replacing product thinking. It’s reducing the friction between understanding users and turning those insights into high-quality backlog items.
    To make the ideas concrete, I use a consistent example throughout: a team building software for valet-attended parking garages, initially selling to independent operations like boutique hotels. Each step builds on the previous one, showing how AI outputs can feed naturally into your existing agile practices.
    With a straightforward prompt, AI can help you build a detailed persona—including hopes, concerns, emotional triggers, and decision criteria. In my example, the persona that emerged was a garage owner/operator with high staff turnover, contract-renewal anxiety, and a strong desire for predictable labor costs. Several of these insights are things I might have missed or deprioritized on my own.
    Understanding a persona’s aspirations—not just their functional needs—turns out to be especially valuable.

    Once a persona exists, you can ask AI to role-play that person and let you interview them. This is not a replacement for real user interviews, but it’s a great way to explore assumptions, test questions, and uncover gaps in your thinking.
    AI is also excellent at preparing interview guides for real users who match a persona. With the right prompt, it can generate a structured guide that covers:

    • Opening context (confidentiality, purpose, time commitment)
    • Current workflows and pain points
    • Desired future state and success criteria
    • Constraints (including regulatory or operational)
    • Thoughtful wrap-up questions


    Looking at the results, I was struck by how much better prepared I could have been for many interviews over the years if I’d had this kind of support.

    Once you’re ready to move into backlog work, AI can help generate user stories and job stories that follow well-established agile guidance.
    By being explicit in the prompt—format, INVEST criteria, and output rules—you can get clean, ready-to-use stories that are easy to import into a backlog tool. AI can also correctly choose between user stories and job stories depending on whether the situation or the role is more important.
    In the valet parking example, this resulted in stories about vehicle handoff tracking, damage-claim protection, wait-time monitoring, staff accountability, and remote visibility into operations.

    I prefer to add acceptance criteria as a separate step, and AI handles this easily. You can ask for:

    • A simple bullet list (great for user reviews), or
    • Gherkin (given-when-then) format for more formal specification

    You can even convert between formats later. Either way, this step quickly raises clarity and testability.

    AI isn’t just for generating content—it’s also useful for critique.
    With a structured prompt, AI can evaluate user and job stories against the INVEST criteria, identify only what’s missing, explain why, and suggest a focused improvement. This works whether the stories were written by AI or by you.
    Over time, you can even build a library of good and bad examples to further improve the quality of feedback you get.

    AI won’t replace talking to users, making judgment calls, or exercising product sense. What it can do is help teams move faster from vague ideas to concrete artifacts, surface blind spots, and raise the baseline quality of their work—especially when time or experience is limited.
    Used well, AI becomes a tireless collaborator: one that remembers persona details, never gets impatient with rewrites, and can move effortlessly from big-picture thinking to precise backlog items.
    The key mindset shift is this: don’t ask whether AI can replace parts of product discovery or backlog refinement. Ask how it can help you arrive better prepared for the conversations that still matter most.

    Más Menos
    9 m
  • Story Point Estimations are failing your Team! - Here We Go Again...
    Jan 27 2026

    Story Point Estimations are failing your Team! - Here We Go Again...

    Story Pointing wasn’t a completely novel idea. It evolved out of the Delphi method — a research technique that helped drive consensus and forecasting built on collective wisdom. In 1950s, RAND Corporation began using it as a way to forecast the effect of technology on warfare.

    So, it wasn’t just an idea dreamed up by someone in the Agile community randomly — no. It’s actually based on a scientific approach. Something that’s been applied and true in other disciplines for many, many years.

    And, when Scrum needed a prescriptive technique to help the Teams estimate and measure the amount of work the Team could consistently deliver Sprint after Sprint, this became a recommended approach.

    How to connect with AgileDad:

    - [website] ⁠https://www.agiledad.com/⁠

    - [instagram] ⁠https://www.instagram.com/agile_coach/⁠

    - [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠

    - [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

    Más Menos
    12 m
  • What Makes a Great Scrum Master?
    Jan 26 2026

    What Makes a Great Scrum Master?

    When people ask me, “What does it take to be a great Scrum Master?” my first response is always — In what kind of organization?

    It’s not a dodge. It’s the most honest answer I can give.

    We talk about Scrum Masters as if the role is universal — a fixed job description that applies equally everywhere. But the reality?
    The Scrum Master navigating a twenty — person startup looks completely different from one guiding a 200-person enterprise team.

    And both are doing the job right.

    How to connect with AgileDad:

    - [website] ⁠https://www.agiledad.com/⁠

    - [instagram] ⁠https://www.instagram.com/agile_coach/⁠

    - [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠

    - [Linkedin] ⁠https://www.linkedin.com/in/leehenson/


    Más Menos
    11 m
  • The 7 Two-Minute Habits That Make People Actually Want to Follow You
    Jan 23 2026

    The 7 Two-Minute Habits That Make People Actually Want to Follow You

    1) Active Listen Burst

    Here’s the move: give someone 60 seconds of your full attention, then paraphrase what they said and ask one clarifying question. The moment someone starts speaking, resist the urge to formulate your response. Instead, just listen. Then say: “So what I’m hearing is ____. Did I miss anything?” This works because people trust leaders who make them feel truly seen — and it clears up confusion before solutions start flying around the room. Just watch out for one thing: don’t hijack the moment with your own story. Paraphrase first, then ask your question.

    2) Values Compass

    Before or after making a key decision, take a moment to name the value guiding your choice. It’s simple: “I’m choosing X because it best serves [fairness / ownership / customer care].” This habit works because when values are explicit, your team immediately understands the trade-offs you’re making. They might not always agree with the decision, but they’ll understand the why behind it. Pro tip: keep your organization’s core values in your notes and use the same vocabulary consistently so your team recognizes the pattern.

    3) Openness Nudge

    In the final two minutes of every meeting, create space for dissent and missing perspectives. Simply ask: “What haven’t I heard yet — especially if you disagree with me?” This is how you build psychological safety — it doesn’t happen by accident. You have to actively pull the truth out of the room. If everyone stays quiet, try a 30-second silent vote: “Type your concerns in the chat now.” This removes the social pressure and gives people a safer way to speak up. The uncomfortable truths you uncover here will save you from bigger problems later.

    4) No-Blame Language

    During reviews or post-mortems, shift the conversation from “who’s at fault” to “what system failed.” Ask: “What part of the system or process produced this outcome?” This reframing is powerful because shame kills learning, while systems thinking scales it. When people aren’t afraid of being blamed, they’ll be honest about what actually happened — and that’s where real improvement begins. Make sure to close the loop by assigning one owner and setting a deadline for fixing the system issue you’ve identified.

    5) Compass Check (Fair? Clear? Kind?)

    Before you hit send on any tough message, run it through three quick filters: Is it fair? Is it clear? Is it kind? If you can’t say yes to all three, go back and fix one line. This is emotional quality control that takes less than a minute but saves hours of cleanup later. It reduces drama, increases alignment, and helps you communicate difficult things in ways that maintain trust. The discipline of pausing before sending is what separates reactive leaders from respected ones.

    6) One-Line Intent

    At the start of every meeting, state your goal in one clear sentence: “Goal: decide/align on ____.” That’s it. This simple habit works because people relax when they know what “done” looks like. It eliminates the wandering discussions where everyone leaves confused about what actually happened. Put this goal at the top of your agenda and read it out loud in the first 30 seconds. It sets the tone and gives everyone permission to redirect the conversation if things go off track.

    7) Decision Note (What/Who/When)

    Right after any decision, log it in one sentence: “Decision: ____. Owner: ____. By: ____.” This creates transparency and accountability while saving everyone from those frustrating moments three weeks later when no one remembers what was actually decided. Future-you won’t have to dig through five different chat threads trying to reconstruct the conversation. \

    How to connect with AgileDad:

    - [website] ⁠https://www.agiledad.com/⁠

    - [instagram] ⁠https://www.instagram.com/agile_coach/⁠

    - [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠

    - [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

    Más Menos
    6 m
  • Why Most Agile Teams Build Features Instead of Value and How To Flip the Script
    Jan 22 2026

    Why Most Agile Teams Build Features Instead of Value and How To Flip the Script

    For a long time, I believed that the number of features we shipped was a sign of a healthy product team. New capabilities meant progress. More releases meant momentum. A packed roadmap meant ambition. And during sprint reviews, when we showcased everything we had delivered, I felt proud as if quantity itself was proof of impact.

    But something always nagged me. After each launch, I would look at the data or talk to users and feel this uncomfortable tension between what we had built and what had actually changed. The features were there, polished, documented, deployed but the world around them stayed strangely still. The metric didn’t move. The user behavior didn’t shift. We were launching features into the void, and the void was yawning back.

    How to connect with AgileDad:

    - [website] ⁠https://www.agiledad.com/⁠

    - [instagram] ⁠https://www.instagram.com/agile_coach/⁠

    - [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠

    - [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

    Más Menos
    8 m
  • Start The Year With a Clean Backlog - Mike Cohn
    Jan 21 2026

    Start The Year With a Clean Backlog - Mike Cohn

    Think outside the box.
    Do you hate that phrase as much as I do?
    It’s become another overused business cliché, and it bothers me for another reason: Creativity often comes from thinking inside the box.
    This is especially true in agile story-writing workshops.

    The difference between a successful story-writing workshop and one that fails to deliver often comes down to a single factor:
    Whether or not the product owner defines a clear, significant objective: a “box” within which the team can think.
    Workshops without boundaries often roam across the entire product. Teams may generate a long list of user stories but those stories lack cohesion or purpose. They’re hard to prioritize, and even harder to act on.


    The most productive workshops start with a simple framing statement from the product owner, like:

    “We’re here to think about this specific subset of the product.”
    That’s it. One well-chosen boundary and suddenly the team is aligned, focused, and generating better, more valuable ideas.
    Early in the product’s life, that boundary might be about identifying what’s needed to deliver an MVP.
    Later on, it might center around a Minimum Marketable Feature (MMF), something small enough to ship but valuable enough to matter.

    When workshops are focused around a meaningful objective, you don’t need to hold them every sprint. I typically run them about once a quarter because one well-run session generates a steady flow of high-value stories.
    As this year closes and a new one begins, it’s a great time to schedule a story-writing session. You might even want to bring our trainers in for a Story-Writing Workshop, where we’ll work with you to:

    • Set powerful, objective-based boundaries
    • Write stories that are right-sized and ready to build
    • Build a focused backlog that everyone can align around


    Discover how to kick off the new year with a backlog that’s ready to go.
    Whether you hold your own story-writing workshop or bring us in to help, remember that thinking inside the box is a powerful way to take teams from good to great,

    How to connect with AgileDad:

    - [website] ⁠https://www.agiledad.com/⁠

    - [instagram] ⁠https://www.instagram.com/agile_coach/⁠

    - [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠

    - [Linkedin] ⁠https://www.linkedin.com/in/leehenson/


    Más Menos
    4 m
  • The OKR Illusion, Why Structure Without Direction Is Just Noise
    Jan 20 2026

    The OKR Illusion, Why Structure Without Direction Is Just Noise

    OKRs (Objectives and Key Results) have gained significant traction over the past decade, especially after being widely adopted and championed by companies like Google. Originally developed at Intel, OKRs are a simple yet powerful framework for setting and tracking goals. At their core, OKRs are about defining what you want to achieve (Objectives) and how you’ll measure progress (Key Results). While the concept is simple, the impact lies in how OKRs align teams, create focus, and connect everyday work to meaningful, measurable outcomes.

    How to connect with AgileDad:

    - [website] ⁠https://www.agiledad.com/⁠

    - [instagram] ⁠https://www.instagram.com/agile_coach/⁠

    - [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠

    - [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

    Más Menos
    10 m
  • Celebrating Dr Martin Luther King Jr
    Jan 19 2026

    Celebrating Dr Martin Luther King Jr

    Understanding Civil Rights Day and what we can do today to make a difference.

    How to connect with AgileDad:

    - [website] ⁠https://www.agiledad.com/⁠

    - [instagram] ⁠https://www.instagram.com/agile_coach/⁠

    - [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠

    - [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

    Más Menos
    6 m