Process Improvement

How Agile Coaches Can Use AI to Prepare Better for Every Conversation

How Agile Coaches Can Use AI to Prepare Better for Every Conversation

Most coaches who use AI use it for content. Writing summaries, drafting emails, generating workshop descriptions. That’s fine. But it’s the smallest thing AI can do for a coaching practice.

The bigger opportunity is in preparation — the work that happens before you open your mouth. The thinking before the session. The context before the standup. The framing before the difficult conversation.

Here are five ways AI can become part of how you prepare for the work that actually matters.

Stress-Test Your Framing Before a Difficult Conversation

Coaching involves conversations most people avoid. A manager who bypasses the team’s process by assigning work directly to individuals. A product owner who accepts every stakeholder request without pushing back. A leader who treats delivery commitments as flexible.

These conversations carry real stakes. The relationship matters. The political dynamics matter. One poorly framed sentence can close a door that took months to open.

AI can help you prepare. Describe the situation in full — who’s involved, what the power dynamics look like, what outcome you need. Ask for the opening line that frames it around outcomes rather than behavior. Ask for the most likely objections and how to respond to each one.

The judgment stays with you. The preparation gets sharper.

Keep Context Across Multiple Teams

Coaches who work across several teams face a constant challenge: holding context. What did this team decide last sprint? What action items came out of their retro? What did you commit to following up on?

When you’re working with three, five, or seven teams, that context doesn’t stay fresh on its own. And walking into a session without it means spending the first ten minutes catching up instead of coaching.

A simple habit solves this. After every team interaction, record a short voice note or write a quick summary — two minutes, unstructured, just what happened and what matters. Before the next session with that team, ask AI to pull out the open threads: action items, recurring themes, commitments you made.

You walk in with full context on your first question. The team feels it immediately.

Design Retrospectives That Target the Real Issue

There’s a pattern most coaches recognize. A team runs retrospectives every sprint. Action items get captured. Few get completed. The same themes keep surfacing. The format hasn’t changed in months.

The problem is rarely the format itself. It’s that the format isn’t designed to surface what the team actually needs to talk about. A team that overcommits every sprint needs a different retro than a team struggling with cross-functional collaboration.

Give AI the specifics — how mature the team is, what tension sits underneath the surface, what the last three retros produced. Ask it to design a session that draws out the real pattern without you having to call it out directly.

What you get back is a facilitation plan built for this team’s specific dynamic. You’ll adjust it in the moment — that’s the coaching skill. But the starting design is already pointed at the right issue.

Get the Full Assessment Before Your First Meeting

This is what we built Nave’s AI Insights for.

When you connect your team’s data, the AI traces what’s happening across the workflow — which stages are accumulating work, what’s behind the accumulation, which items have aged past their percentile thresholds, and how these signals connect to each other. A full causal chain, with specific item IDs and numbers, ready before you’ve opened a single chart.

For coaches, this changes the shape of an engagement. The data investigation that used to take the first few weeks is already done. The first conversation can start with what to do about what the data shows — instead of spending weeks building the picture.

You can try it out at getnave.com.

Build Scenarios That Help Leadership Make Hard Decisions

One of the most common coaching challenges is the initiative overload conversation. An organization is running more work than its teams can deliver. Everyone can feel it. Delivery dates are slipping. People are stretched across too many things. But nobody wants to be the one to say which initiatives should stop.

Coaches can use AI to build the conversation leadership actually needs. Take the current portfolio — how many active initiatives, what the teams’ throughput looks like, what the delivery timelines are. Ask AI to build two scenarios side by side: continue at the current load, or focus on a smaller set.

Frame the difference in language leadership already uses — delivery dates, revenue impact, customer commitments at risk. When the trade-off is concrete and visible, the conversation shifts from opinion to evidence. Leadership can look at two futures and make a choice.

The Coaching Skill Stays the Same

Reading the dynamics of a difficult conversation. Sitting with discomfort when a leader hears something they’d rather not. Deciding which recommendation to push for now and which one needs a different approach.

None of that changes. That’s the craft.

What changes is how prepared you are when those moments arrive. And that preparation is now faster and more thorough than it’s ever been.

Pick one of these five and try it this week. The difference shows up the moment the conversation starts.

Sonya

Do you find this article valuable?
Rating: 5 stars (3 readers voted)

Leave a Comment