What if your daily stand-up stopped being a status report and actually became a moment where the team steered the ship?

Picture this: it’s 9:30 AM. The daily starts. Someone starts reading Jira tickets. Another person says, “Same as yesterday.” And someone mentions a blocker that has already been there for three days.

Fifteen minutes later, everyone knows what happened in the team, but no one is sure what changed. You talked, but you did not get any closer to the sprint goal.

That is the trap. Too many dailies are still rituals for reporting activity. They are not about moving forward. They are just about looking busy.

And here is the thing: now that we have AI, we have a huge opportunity, but also a huge risk.

AI can make dailies faster. It can summarize tickets, spot patterns, and show you what changed since yesterday. But if you only use AI to make the same old boring daily faster, you have not improved anything. You have just automated the waste.

Hi, I’m Josep, and this is The AI Agile Facilitator. Today I want to show you how AI and the SEA framework — Strategy, Empathy, and Adaptability — can turn your daily from a reporting ritual into a moment of real alignment.

The classic daily trap

We all know the three classic questions:

• What did I do yesterday?
• What will I do today?
• Do I have any blockers?

There is nothing wrong with those questions, but they are inherently individual. One person speaks, then the next, then the next. In the end, you have collected a bunch of updates, but you have not made a single team decision.

Some teams try to improve this by asking how confident they are about the goal. That is better, because it focuses on the outcome. But visibility without action is still just reporting.

I have seen teams that stay confident for ten days in a row and then, a couple of days before the end of the sprint, start lowering their confidence when there is nothing the team can actually do about it.

The real question is not, “How do we feel?” or “How confident are we?”

The real question is: based on what we have learned, what do we need to change today?

AI as the warm-up, not the meeting

This is where AI becomes useful.

AI should not run the meeting, and it definitely should not become a surveillance tool. We are not here to monitor people. We are here to get a clear view of the system.

Think of AI as a warm-up before the meeting. It can:

• highlight work that has moved
• flag tickets that are getting old
• detect hidden dependencies
• suggest the top three things that actually need your attention today

In other words: AI gives you the signal, so you do not have to start from scratch.

Apply SEA to the daily

Once AI has done the warm-up, the team can use SEA.

Strategy

Strategy is about direction.

Instead of everyone repeating status, look at the signal and ask:

One of our key stories is sleeping. What deserves our focus today to protect the sprint goal?

Maybe you stop starting new work. Maybe you swarm. Maybe you change the order of the day.

That is strategy in action.

Empathy

AI can show you a ticket that is stuck, but it cannot tell you why.

Maybe someone is overloaded. Maybe they are blocked but do not want to admit it. Maybe they need help, not pressure.

This is where the human conversation matters.

Do not ask, “Why is this not done?”

Ask, “How can we support you here?”

Adaptability

If the same blocker shows up three days in a row, do not just report it again.

Change something.

Maybe reviews are taking too long. Maybe the team needs to pair for an hour. Maybe the WIP limit is too high. Maybe the scope needs to be renegotiated.

AI helps you see the pattern. The team decides the fix.

A concrete example

Imagine you walk into the daily and the AI summary says:

• one user story is stuck
• one pull request has not been reviewed by anyone
• there is a dependency risk with the DevOps team

Now you do not start with what you did yesterday.

You start with:

Here is the signal. How do we protect our goal today?

The AI has pointed to three problems. Now the team decides three actions:

• review the pull request right after the daily
• pair up to unblock the stuck user story
• Eva calls DevOps to resolve the dependency risk

That is a better daily. Not because it is high-tech, but because it focuses on action.

The takeaway

The daily was never supposed to be a status report.

It is an inspection and adaptation ceremony.

AI cleans up the noise so you can have the right conversations. AI brings the signal. Strategy focuses the goal. Empathy supports the people. Adaptability adjusts the plan.

So the goal is not a faster bad daily. The goal is a better daily.

Stop using AI to make bad dailies faster. Use it to make your team better.

If you want to apply these ideas to your own team, I have prepared a worksheet to help you reflect on your daily using Strategy, Empathy, and Adaptability. You will find the link in the description below.

I’m Josep, and I’ll see you in the next AI Agile Facilitator video. Thanks for watching, and now go and have a daily that actually matters.