“Teams rarely change because of a new framework. They change when the way they carry work shifts — one conversation, one interaction, one small step at a time.”

Everyone says they want feedback — until they get it.

There’s a famous story about Sony’s yellow Walkman: everyone in the focus group said they loved it. Then, when offered one to take home, every single person chose the black version.

That’s the trouble with feedback. It sounds useful, feels helpful, but it isn’t always true.

In delivery, chasing every opinion can drain momentum faster than any blocker. Real agility isn’t about reacting to everything — it’s about knowing which feedback feeds flow, and which just adds noise.

We froze all new work and focused entirely on what would get value moving again. Two weeks later, we had a working regression pack. One month later, releases that had been stuck for 18 months started going out the door.

The team didn’t need more motivation. They needed permission to stop.
Because sometimes the bravest thing you can do in delivery isn’t to start something new — it’s to stop pretending you’re busy.

Rework isn’t just about fixing bugs — it’s the cost of unclear intent. Every time a team builds the wrong thing or has to redo what’s “done,” delivery slows and trust erodes. The fix isn’t speed; it’s clarity. A short, deliberate conversation before work starts can save weeks later. Here’s how one team turned their rework problem into steady, confident delivery.

I use a rule I call The Power of Two.

If you’ve got three things to do, pick two.

If you’ve got ten, pick two.

Even if you’ve got a hundred, yes, still pick two.

The truth is, the team usually does know. They’re the experts. They understand the problems, the blockers, and the opportunities better than anyone. But they’re waiting for permission that never comes.

I’ve seen one clear, confident decision unlock more progress than six months of discussion. It doesn’t even have to be the perfect decision. It just has to move the team forward. Once you’re in motion, you can adapt, adjust, and refine. But you can’t steer a ship that’s standing still.

So what shapes culture?
It’s learned behaviour.
We learn it from our parents, our friends, our community — and at work, we learn it from our leaders.

Look at your to-do list and decide which are the two most important.
You might not even consciously know why, but I bet you make a good decision.
Even if it’s not the best one, at least you’re doing — and that’s better than just thinking about doing.

Most of us work in wetware — the messy, brilliant, human kind of work.
Hardware follows rules.
Software follows logic.
Wetware? It follows mood, energy, distraction, and sometimes bad coffee.

Real change starts with the few who care enough to make a difference.
Back them. Remove the noise around them. Give them the confidence and skills to deliver.

Most teams don’t struggle to start work — they struggle to finish it.
You can see it on every board: work in progress everywhere, but not much moving to done.

The middle is where work goes to die. It’s where effort builds up, visibility fades, and nobody’s quite sure what’s next.

Agile isn’t a badge. It’s just a set of habits that help work flow better (what some might call Kanban thinking):
• Make the work visible.
• Talk to each other regularly.
• Stop starting everything at once.
• Finish what’s started.

When I’m brought in through Agile Second Opinion, I’m not there to audit or judge — I’m there to spot the patterns that hold delivery back. Sometimes it’s obvious, sometimes it just feels off until I spend more time with the team. Once you see it, you can start to fix it. I call it positive negativity — finding what’s not working, so you can focus on what will.

I’m dyslexic, which means I think fast and talk even faster. When I’m speaking, that’s a strength. I can go off script, make it relevant, sense the room and adapt. But when I write, those same tangents make things messy. What sounds natural when I say it can look chaotic when I read it back.

After 36 years in delivery, working with over 70 teams across countless organisations, I’ve come to a simple conclusion: the success of any change or transformation is less about the method and more about the mindset and that mindset is shaped by culture.

The real outcome? That’s customer impact. Making a tangible difference. Creating something useful

For years I’ve said: “Don’t do Agile, be Agile.” But I think I’ve moved on.

Not because it’s wrong, there’s truth in it, but because it still centres the method, not the mission.

Agile is not the outcome. Agile is a means to an end.