Portrait of Asbjorn Bjaanes
Asbjorn Bjaanes

Articles ·

Agile Coaching Starts Where Teams Rediscover Ownership

Agile Coaching Starts Where Teams Rediscover Ownership

They told me their Agile setup was working well.

A product company of around 150 people, with 25 in development. Delivery was steady. Stand-ups held. Ceremonies in place.

“We’re doing Agile pretty well,” they said.

But something didn’t sit right.

When I listened deeper, I heard it in the language.

  • Teams were “following process,” not shaping it.
  • Retrospectives were routine, not reflective.
  • Prioritization flowed top-down, despite “collaboration.”

Agile was present, but not really alive.

They weren’t doing anything wrong. But they weren’t becoming anything new, either.

They were performing Agile. Not owning it.

From Paddling to Steering

I’ve seen this pattern over and over again in teams and orgs of all sizes. In 2007, I was leading distributed teams across Europe and Asia, managing delivery across cultures, time zones, and stakeholder landscapes.

Scrum helped. We got faster. Clearer. More connected. But as soon as our team’s progress met the wider organization, it stalled.

The environment couldn’t support the agility we were trying to build. Priorities shifted. Dependencies tangled. Leadership still asked for roadmaps, not outcomes.

That’s when I realized:

You can’t transform a system by optimizing a team.

I began working with Lean, not just to improve processes, but to see the system, flow, constraints, value, and waste.

And still, I asked:

Why does this work for some teams, but not others?

The Learning: Performance ≠ Ownership

The missing piece is often invisible: belief.

  • Do teams believe they can shape how they work?
  • Are they invited into ownership, or just executing a template?
  • Is Agile something done to them, or something they build into the way they deliver?

This is the friction I meet. Not always dramatic, but quiet, persistent resistance under the surface. Teams who do the right things, but still don’t move.

I’m not looking for gaps in practice. I’m listening for people’s beliefs and Mindset.

If Culture eat Strategy for lunch… Then Mindset eat Culture for supper — unknown source

That’s what was happening in this conpany with about 150 employees.

They were planning to hire more developers to increase throughput. But based on what I saw, they didn’t need more people, they needed to turn the boat and leverage the stream.

Coaching Creates Leverage in the Gaps

Agile coaching brings value not because we introduce a new process. But because we work in the in-between:

  • Between structure and flow
  • Between what teams say and what they actually feel
  • Between how work is designed and how it’s experienced

In this case, I could see the system was misaligned:

  • Priorities weren’t shaped by the teams closest to the customer
  • The product strategy wasn’t being broken down in ways that empowered developers
  • There was no sense of co-ownership of outcomes
I’m confident they could achieve a 25–30% increase in throughput within 6–12 months Not by working harder, but by unblocking potential that was already present.

That’s what coaching enables.

We don’t just offer ceremonies. We help teams:

  • See the system they’re in
  • Name the constraints they’ve normalized
  • Reclaim agency they didn’t know they had lost

And we do that by building:

  • Trust
  • Safety
  • Clarity
  • And alignment at the team and leadership level

A Metaphor: The Rowboat and the Current

Imagine a team in a rowboat.

The current is strong, but the boat moves slowly. Everyone is paddling, rhythmically, even efficiently. They’re following all the right routines.

But the boat doesn’t glide, it grinds.

That’s what happens when Agile is implemented without systemic alignment. The team works harder, not smarter. They measure progress, but don’t feel momentum.

The problem isn’t the paddling, it’s that they’re rowing against the current.

And what’s worse: most teams assume this is normal.

Coaching helps them see that it’s not. That they have the ability, and the permission, to turn the boat.

What Coaching in an Agile organization Really Brings to the Table

Let’s be honest, “Agile coaching” is often misunderstood. It gets mistaken for facilitation, process cleanup, or framework enforcement.

But good coaching doesn’t push people through a method.

It helps them remember how to move forward with purpose.

When I coach, I’m not just listening for blockers in Jira, I’m listening for where ownership has broken down.

When I coach, I bring a systems lens, but also a deep focus on the human layer, rooted in experience with NLP, neuroscience, and even hypnotherapy.

Not to diagnose. But to understand:

  • Why people resist what they want
  • How psychological safety really forms
  • What helps ownership emerge, not be assigned

Because real agility doesn’t come from compliance. It comes from belief.

And belief doesn’t scale through mandates. It grows through invitation.

Final Reflection: Turn the Boat

If you’re in a team or organization that’s “doing Agile,” ask yourself:

  • Are we shaping how we work, or inheriting it?
  • Do our teams own outcomes, or execute against them?
  • Are we paddling harder, or actually steering?

A coach don’t bring a better paddle, A coach help teams find the rudder they forgot they had and to leverage their potentials.

And when they do?

They don’t just deliver more, They transform…


Written by Asbjorn Bjaanes. Also published on Substack.

Reach out