Most teams don’t have a process problem. They have a conversation problem.
I’ve been thinking about this for a while, and the more I look at Agile teams, the more it feels like we’re solving the wrong problems. We spend a lot of time fixing process refining backlogs, improving estimation, adjusting ceremonies. But when things actually go wrong, it rarely comes back to those. It comes back to something much simpler. And honestly, more uncomfortable.
People knew something earlier. They just didn’t say it.
I remember sitting in a planning discussion not too long ago.
Everything was moving quickly. Dependencies were being called out, teams were aligning, timelines were getting locked in. It felt efficient the kind of session you walk out of thinking, that went well.
At one point, someone raised a concern. Not strongly more like testing the waters.
Something along the lines of, “This might be tight if X slips.”
There was a brief pause. Someone responded with a workaround. It sounded reasonable. The conversation moved on almost immediately. No one pushed further. Not even the person who raised it. At the time, it didn’t feel like anything important. Looking back, that was probably the most important moment in the entire session.
A couple of weeks later, the same thing came back.
The dependency slipped. The workaround didn’t really hold. Now it was urgent. More people got involved. Conversations got longer, more tense and suddenly it became a “delivery issue.”
But it wasn’t. The issue had already shown up. It just wasn’t fully dealt with when it was still easy.
I keep seeing versions of this.
Not dramatic failures. Just small moments that get skipped.
A hesitation.
A softened concern.
A “let’s move on for now.”
And it adds up.
That’s the part Agile doesn’t really solve. We’ve built really good systems to track work. Boards, metrics, cadences all of that helps.
But none of it guarantees that people will actually say what they’re thinking when it matters. And if that doesn’t happen, the rest doesn’t help as much as we think.
I don’t think most teams lack awareness.
People usually see the problems early. They notice when something feels off. They can tell when a plan is a bit too optimistic.
They just hesitate.
Sometimes it’s because they don’t want to slow things down. Sometimes they’re not completely sure. Sometimes, if we’re being honest they’ve learned that pushing too hard isn’t always welcomed.
So they adjust. They say a softer version. Or nothing at all.
And from that point on, the team is no longer working with the full picture.
The difference in stronger teams isn’t that this never happens.
It’s that someone eventually doesn’t let it go.
They’ll say, “I’m not convinced this will work,” even if it makes the room slightly uncomfortable.
Or they’ll go back to a point everyone already moved past and say, “Can we pause on this for a second?”
It slows things down in the moment.
But it saves a lot later.
People call this psychological safety. That’s fine, but I think we make it sound simpler than it is. It’s not about being comfortable. It’s about not second-guessing whether speaking up will cost you something.
And that calculation is always happening in the background.
People notice reactions. They remember what gets dismissed, what gets explored, what gets ignored.
And over time, they adapt.
Leadership shows up here in ways that don’t look like leadership.
A quick interruption.
A slightly impatient response.
Moving past a concern because time is tight.
None of these feel significant, but they send a message. And once that message lands a few times, people start filtering what they say. Not consciously. Just enough to avoid friction.
From the outside, everything still looks fine.
The ceremonies are happening. Work is moving. Updates are being shared.
But underneath, something is missing.
Not effort. Not structure.
Just honesty at the point where it actually matters.
I’ve started to think that this is where most teams struggle.
Not because they don’t know what to do.
But because they don’t fully say what they know at least not when it would make a difference. Plans being wrong isn’t the problem. That’s expected. The real problem is when something is known early, but only becomes visible when it’s already a problem.
And that’s where emotional intelligence actually matters. Not as a concept. Not as a leadership trait.
Just as the ability to sit in that slightly uncomfortable moment—and not look away from it.
To say the thing.
To ask the question.
To not let it slide.
That’s the difference.
Not between teams that follow Agile and teams that don’t.
But between teams that look like they’re working…
and teams that actually are.
Leave a Reply