Why Organizations Need Coaches on the Field, Not Just on the Sidelines

What high-performing sports teams understand about coaching that organizations are only beginning to learn

Imagine a professional sports team announcing that it had decided to stop using coaches during the season.

Instead, the players would attend a coaching retreat before the season began. They would spend a day talking about communication, teamwork, strategy and performance. Perhaps they would complete an assessment, establish some team norms and identify a few goals.

Then the coaches would leave.

The players would be expected to take it from there.

They would navigate injuries, new players, losing streaks, changes in strategy, interpersonal tensions, high-pressure games and unexpected competition largely on their own. If things became particularly difficult, perhaps the organization would bring the coaches back for another workshop.

It sounds ridiculous.

Yet in organizations, this is surprisingly close to how we often approach coaching and team development.

We bring a coach into a room for a leadership retreat, a team-building day or a development program. We have good conversations. People leave energized and committed to doing things differently.

And then everyone returns to the system that helped create the existing behaviours in the first place.

Sports Teams Treat Coaching Differently

In sport, coaching isn't considered remedial.

It isn't reserved for athletes who are struggling.

And it certainly isn't something that happens once a year.

Coaching is embedded in the performance environment.

A team may have a head coach, assistant coaches, position coaches, strength and conditioning specialists, performance specialists and others working alongside athletes throughout the season.

These coaches aren't playing the game.

They are helping the people who are.

They observe patterns that can be difficult to see from inside the action. They notice when communication breaks down, when positioning changes, when an athlete starts compensating for someone else, or when a strategy that worked earlier in the season no longer fits the conditions.

Most importantly, they are present while the environment changes.

They watch.

They ask questions.

They offer perspective.

They help people adjust.

Then they watch again.

That continuous cycle of observe, reflect and adjust is very different from the way many organizations approach development.

And it is one of the ideas behind our work in Collaborative Coaching.

Organizations are complex performance environments too.

Consider a major project involving an owner organization, contractors, consultants, engineering firms, suppliers, regulators, community partners and multiple internal departments.

There may be hundreds, sometimes thousands, of people connected to the work.

Everyone can be highly competent.

Every organization can have excellent processes.

Every contract can clearly define responsibilities.

And collaboration can still become difficult.

Why?

Because the project exists not simply within an organizational chart, but within a living system of relationships.

Decisions move across organizational boundaries.

Information moves at different speeds.

Priorities compete.

People interpret risk differently.

Power sits in different places.

Teams develop their own shorthand.

Unspoken assumptions emerge.

Pressure changes behaviour.

What appears to be a communication problem in one meeting may actually be the visible symptom of unclear decision rights somewhere else in the system.

A disagreement between two individuals may actually reflect competing organizational incentives.

A delay may look operational but have its roots in trust, governance or information flow.

Traditional team coaching can help enormously. But sometimes the team isn't the whole system.

That distinction matters.

From Team Coaching to Collaborative Coaching

Collaborative Coaching begins with a slightly different question.

Instead of asking only:

How can we make this team more effective?

we also ask:

What is happening in the system around this team that is influencing its ability to collaborate?

And when we ask about the system, we mean both internally and externally.

That opens up a much broader field of view.

The unit of attention might sometimes be a leadership team.

At another moment, it might be the relationship between two organizations.

Later it might be the interaction between governance and the project team, or between the owner and a contractor, or between technical and operational groups.

This is why we describe Collaborative Coaching as working alongside the system rather than outside it.

The goal is to understand the system well enough to know where coaching attention will have the greatest value. And where that value is will shift and evolve, as every team, every organization, every project, every joint venture (you get the idea) is a evolving system.

Sometimes that means working with the core project leadership team.

Sometimes it means observing an important meeting.

Sometimes it means helping two groups examine a recurring friction point.

Sometimes it means bringing several parts of the system together to clarify expectations.

And sometimes it means stepping out of the way.

Good coaching is not about making the system dependent on the coach.

It is about increasing the system's capacity to notice and respond to what is happening.

Coaching the Space Between Organizations

One of the biggest differences in collaborative work is that performance increasingly happens between organizations, not simply inside them.

Major infrastructure projects are a good example.

The owner may have one culture.

The engineering firm another.

The construction partner another.

A specialist supplier may operate globally.

Each organization brings its own language, expectations, processes, measures of success and experiences from previous projects.

A contract can define the commercial relationship.

It cannot completely define the human one.

And that space between organizations is often where collaboration either strengthens or deteriorates.

Who speaks when there is disagreement?

How quickly are concerns raised?

Are decisions understood or simply communicated?

Do people know when they can challenge something?

How are competing priorities discussed?

Do people understand the pressures being experienced elsewhere in the system?

What happens when something goes wrong?

These aren't soft questions.

They influence real project outcomes.

Collaboration Isn't Static

Another lesson from sport is that teams change during the season.

A team that is functioning beautifully in October may look completely different in February.

The context changes.

People change.

Pressure changes.

The competition changes.

The same is true of organizational systems.

Collaboration at project initiation is different from collaboration during design.

Design is different from procurement.

Procurement is different from construction.

Construction is different again when schedules tighten, costs increase or unexpected technical issues emerge.

This is why our Collaborative Coaching approach includes tools such as Collaborative Readiness assessments, systems mapping, regular pulse checks, observation and reflective conversations.

The point isn't to give a project a collaboration score and declare the work complete.

The point is to establish a baseline and then keep paying attention.

Where are we strong?

Where is friction increasing?

Where are decisions getting stuck?

What are people experiencing?

What has changed in the system?

And what small adjustments now might prevent much larger problems later?

In this sense, collaboration is less like something you achieve and more like something you continuously maintain and adapt.

The Coach as Observer of the System

One of the most valuable roles a sports coach plays is noticing what players cannot easily see while they are in the game.

Organizational leaders experience the same challenge.

When you're responsible for delivering a complex project, your attention is understandably pulled toward deadlines, budgets, risks, decisions and deliverables.

You are inside the action.

A collaborative coach has the advantage of being close enough to understand the work while maintaining enough distance to notice patterns.

For example:

A coach may notice that decisions repeatedly return to the same meeting even though everyone believes they were resolved.

Or that certain people become increasingly quiet when pressure rises.

Or that project leaders continually solve problems that should be owned elsewhere, gradually creating dependency.

Or that two organizations use the same word — "urgent," "approved," "complete," "risk" — but mean very different things.

None of these observations automatically tells us what to do.

They give us something perhaps even more valuable:

That is where Collaborative Coaching connects strongly with our broader philosophy of Collective Inquiry.

Rather than assuming the coach possesses the answer, we help the system become curious about its own patterns.

What are we noticing?

What might be creating this?

Who else is affected?

What aren't we seeing?

What do we want to experiment with?

Then we observe what happens next.

Moving Beyond the Annual Team-Building Day

There is absolutely a place for workshops, retreats and team-building sessions.

They can create shared language, introduce useful models and give teams the space to have conversations they rarely have during normal operations.

The mistake is expecting the event to carry the entire weight of behavioural change.

Imagine a sports coach saying:

"We covered communication at training camp. I'm not sure why we're talking about it again."

Of course they're talking about it again.

The conditions have changed.

That's the work.

Organizations could benefit from adopting the same mindset.

Instead of viewing coaching as an intervention, we can begin viewing it as part of the performance infrastructure surrounding important work.

Not everywhere.

Not all the time.

But available throughout the lifecycle of the work.

Embedded Doesn't Mean Intrusive

There is an important distinction here.

Embedded coaching does not mean another person sitting in every meeting.

Complex projects already suffer from too many meetings, overlapping governance structures and overloaded leaders.

The goal should be the opposite.

Our approach is to establish a core Collaborative Coaching group and then strategically engage different elements of the system as they become relevant.

The executive or governance level may need attention at one stage.

The project management team may be the focus at another.

A contractor-owner relationship may require attention later.

Internal departments, external partners or specialist teams may be brought into the conversation when the system tells us they matter.

The coaching architecture should flex with the project.

That is how we can remain embedded without becoming another layer of bureaucracy.

From Intervention to Infrastructure

Perhaps the bigger shift is conceptual.

For decades, organizations have tended to treat coaching as something we provide to people.

A leader gets a coach.

A team gets a workshop.

A struggling relationship gets an intervention.

Collaborative Coaching asks us to imagine something different.

What if coaching became part of how complex work gets done?

What if we intentionally created capacity within major initiatives to observe not only technical performance, but relational and systemic performance?

What if we noticed small fractures in collaboration before they became major project problems?

What if reflection happened throughout the work rather than only during a post-project lessons-learned exercise?

Sports teams wouldn't dream of removing coaches from the season and asking athletes to reconnect after the championship was over.

Yet organizations routinely wait until collaboration has deteriorated before bringing someone in to help.

There is another possibility.

Put coaches closer to the field.

Let them understand the system.

Give them enough proximity to see the patterns and enough independence to ask the questions others may not be able to ask.

And then allow the people doing the work to do what great teams have always done:

Because in complex environments, collaboration isn't a one-time event.

It is part of the work itself.

The Collaborative Coaching Group works alongside complex teams, organizations, and major projects to strengthen the relationships, behaviours, and conditions that enable effective collaboration. Our approach goes beyond traditional team coaching by working across the broader system—bringing together internal and external partners, leaders, and stakeholders to improve alignment, decision-making, trust, and collective performance.