There is a familiar tension in almost every busy leadership team. The calendar is full, priorities are competing, operational issues need attention and there is always something that feels more urgent than spending time working on the team itself. When a team development session, offsite or coaching conversation appears in the diary, it can be tempting to look at everything else demanding attention and wonder whether this is really the best use of everyone’s time.

At our recent High Performing Teams event, Claire Spencer described exactly this experience. Her executive team deliberately sets aside time each quarter to work on themselves as a team, yet as each session approaches, the reaction is remarkably human:

“Oh my god, do we have to do this? We’re so busy.”

And yet, afterwards, the response is very different:

“Oh my god, that was so energising, that was so brilliant.”

That tension captures something important about high performing teams. The work that helps a team perform better can feel difficult to prioritise precisely because the team is already so busy performing. The danger is that when teams continually defer development in favour of delivery, they can become very efficient at maintaining ways of working that no longer serve them.

Being Busy Together Is Not the Same as Performing Well Together

Most teams spend a significant amount of time together. They attend meetings, make decisions, solve problems, manage stakeholders and deliver work. Senior teams may spend hours every week discussing organisational priorities and responding to emerging challenges. But spending time together does not automatically mean a team is developing.

Teams can work alongside one another for years without deliberately examining how effectively they are operating as a collective. Patterns become established, responsibilities evolve, communication habits form and particular people gradually take on informal roles within the group. Some of those patterns support performance. Others quietly constrain it.

A team might become dependent on one leader for decisions. Difficult issues might repeatedly be deferred. Meetings might become dominated by operational updates. Certain voices may carry more influence than others. Team members may become highly effective within their own portfolios while collective accountability gradually weakens.

None of these patterns necessarily indicates a dysfunctional team. They are often simply the result of people adapting to the demands around them.

The challenge is that without deliberately creating space to examine those patterns, the team may have very little opportunity to recognise them.

High Performance Is a Practice, Not a Destination

There can be a tendency to think about team development as something required when a team is new or when something has gone wrong. A new executive team might undertake an offsite. A team experiencing conflict might bring in a facilitator. An organisation undergoing restructure might invest in rebuilding relationships and clarifying roles. All of these can be valuable interventions. But sustainable high performance requires a different mindset.

Teams are dynamic systems. People join and leave. Strategies change. Workloads shift. New stakeholders emerge. Organisational structures evolve and external pressures alter what the team needs to deliver. A team that was highly effective twelve months ago cannot assume that the same behaviours, structures and ways of working will continue to produce the same result. This is why ongoing team development matters.

Steople’s High Performance Teams model identifies seven conditions that contribute to sustained team performance: Direction, Clarity, Interdependency,

 Communication, Balance, Commitment and Trust.

Those conditions are not established once and then permanently secured. They need attention as the team and its environment change.

Working on the Team Creates Space to See the Team

One of the most valuable things deliberate team development provides is perspective. When people are immersed in delivery, their attention is naturally drawn towards the work in front of them. They are thinking about the next decision, deadline, stakeholder or problem. Stepping outside that operating rhythm creates an opportunity to examine the system itself.

How are decisions actually being made? Where does work become stuck? Are responsibilities still clear? Is information moving effectively across the team? Are people challenging one another constructively? Is workload distributed sustainably? Has the team become overly reliant on particular individuals?

These conversations can be difficult to have while simultaneously trying to progress the agenda. They also benefit from evidence.

Our approach to high performing teams deliberately combines assessment data with stakeholder perspectives, behavioural evidence and observation of the team’s real work. This allows teams to look beyond perceptions and explore the organisational conditions shaping how they operate. The objective isn’t reflection for reflection’s sake. It is to identify the few changes that will make it easier for the team to perform.

The Return on Investment Often Appears Back in the Work

The most common objection to ongoing team development is understandable: time.

For senior teams in particular, taking several people away from operational priorities represents a genuine investment.

Claire reflected on this directly:

“It feels like a big investment of time and energy, but the return on that investment is significant.”

The return she described was not abstract.

Without that investment, she believed the team would still be caught in what she called “the washing machine.” Their development work had created greater clarity and direction, while also giving leaders space to reflect on their roles, relationships and how they supported one another.

Matthew Eames described a different but related shift. Before investing in the team, progressing work required greater direction, tracking and task management. As the team developed, leaders were increasingly able to define the outcome and allow people to bring their own expertise to how it would be achieved. That created more capacity for leaders to focus on business development, strategic oversight and continuous improvement.

This is an important distinction. The return on team development does not only appear in how people feel about the team.

It can appear in how the work gets done.

One-Off Team Building Can Only Take You So Far

There is nothing inherently wrong with a team-building day. A well-designed offsite can create momentum, strengthen relationships and provide valuable space for conversations that do not happen during ordinary working routines. The limitation comes when the event itself is expected to create sustained behavioural change. Teams return to environments full of existing pressures, habits and competing demands. Without reinforcement, even strong intentions can quickly be overtaken by established ways of working.

Jason Smith captured this during the High Performing Teams event:

“There’s actually real work that sits behind it, where you’ve actually got to… put some of the energy into it to actually drive the outcomes.”

This is why we think about team development as a journey rather than an event. Within Steople’s High Performance Teams approach, the initial diagnostic and development work is followed by observation of real team meetings, ongoing group coaching, quarterly development sessions, behaviour-change commitments and reassessment.

That architecture matters because insight alone rarely changes behaviour. Teams need opportunities to practise new ways of working, notice when old patterns reappear, receive feedback and adjust.

The Real Work Happens Between the Sessions

A team may leave an offsite agreeing to communicate more openly, delegate differently or hold one another accountable. The test comes several weeks later when deadlines are tight, a difficult decision needs to be made and everyone defaults to familiar behaviour. This is where development either becomes embedded or gradually disappears.

Small commitments can be particularly powerful because they translate broad intentions into observable behaviour. Rather than committing to “improve communication”, a team might change how decisions are recorded and communicated. Rather than promising “greater accountability”, members might agree how they will challenge missed commitments. Rather than aspiring to “delegate more”, a leader might become explicit about the outcome and boundaries before allowing the team to determine the approach.

Steople’s Habit Builder is incorporated into our High Performance Teams journey for this reason, keeping individual commitments visible through prompts, progress tracking and peer support between formal development sessions. High performance is built through what teams repeatedly do.

Development Is Not Always Comfortable

There is another reason teams sometimes avoid working on themselves. Good team development does not always feel good. It can expose differences in expectations, surface frustrations or require people to examine their own contribution to a difficult dynamic.

Matthew described part of his team’s experience memorably as:

“The train wreck we had to have.”

He explained that bringing people together created friction, but that friction was necessary to build something different. He also reflected that some of the people who enjoyed the process least experienced some of the greatest development.

This connects strongly with psychological safety. A psychologically safe team is not a team that avoids discomfort. It is one where people have enough trust to work through disagreement, challenge assumptions, acknowledge mistakes and have conversations that matter.

The aim of team development therefore isn’t permanent harmony. It is increasing the team’s capability to navigate the inevitable complexity of working together.

Sustainable High Performance Is Designed Deliberately

Teams are often asked to perform in environments characterised by increasing complexity, competing priorities and sustained pressure. Individual capability matters enormously in those environments, but it is not enough.

As Steople’s High Performance Teams approach recognises, sustained performance cannot depend on individual effort alone. Team habits, workload, leadership behaviour and shared norms all influence whether performance and wellbeing can be maintained over time.

That is why deliberate team development should not be seen as time away from performance.

It is part of how sustainable performance is created.

The teams most committed to performance are not necessarily those that spend every available moment delivering. They are also willing to create enough space to examine how they are delivering, what has changed around them and what they need to do differently next. High-performing teams do not reach a point where they no longer need to work on themselves. They develop the discipline to keep doing it.

Build the Team Your Strategy Needs

Steople’s High Performance Teams program combines evidence, organisational psychology, facilitated development, coaching and behaviour change to help teams understand how they are working today and deliberately strengthen the conditions they need for the future.

Whether your team is navigating change, experiencing sustained pressure or already performing strongly and looking to lift its impact, we can help you move beyond a one-off intervention towards an evidence-based approach to sustainable team performance.

Talk to Steople about building the team your strategy needs.