A team cannot be coached into high performance if the organisation has not first created the conditions in which high performance is possible.
A senior leader can recruit capable people, appoint an experienced manager and still create a weak team. The failure is often misdiagnosed as a motivation problem, a personality clash or a lack of accountability. Sometimes those explanations are correct. But often the deeper problem is structural: the people have not been given a sufficiently clear shared task, stable boundaries, useful roles, decision rights, time to develop trust, or an organisational environment that supports the work.
This distinction matters because organisations frequently spend money trying to repair behaviour that was produced by poor design. More team-building sessions will not resolve conflicting reporting lines. More inspirational communication will not correct an impossible workload. More pressure for collaboration will not compensate for unclear ownership. Leadership matters, but it operates inside a system.
The Strategic Context
Project and transformation teams are assembled because ordinary functional structures are not enough to deliver a temporary, cross-boundary outcome. That gives them an advantage: they can combine expertise that normally sits in different parts of the organisation. It also creates fragility. Members may have different priorities, managers, professional languages and career incentives. Some may join late or leave early. Others may only contribute part of their time.
The supplied project-leadership material uses two useful lenses. Tuckman's group-development model describes the evolution from forming through storming, norming and performing, with adjourning added for team dissolution. Hackman's team-effectiveness work focuses less on a universal sequence and more on the conditions surrounding a team: whether it is a real team, has compelling direction, an enabling structure, a supportive context and access to appropriate coaching.
The strategic insight is not that one model is "right". It is that development and design are different problems. A team can be mature in its relationships yet structurally constrained. It can also have excellent structure and still need time to establish trust, shared expectations and workable norms.
What Leaders Commonly Misread
The first mistake is treating staffing as team formation. A collection of specialists is not automatically a team. People become interdependent when the work requires them to coordinate decisions, exchange information and accept mutual consequences. If the task can be completed independently, forcing "teamwork" may simply add meetings.
The second mistake is believing conflict proves the team is failing. Early disagreement can reveal hidden assumptions, unclear authority, incompatible priorities or competing interpretations of the task. The question is whether the conflict is being converted into clearer decisions and stronger working norms or allowed to become personal and destructive.
The third mistake is expecting the leader to compensate indefinitely for system weakness. A skilled leader may bridge gaps through extraordinary effort, personal relationships and constant intervention. That can create the appearance of a successful team while hiding an unsustainable operating model. When that leader leaves, performance collapses because capability was never institutionalised.
Reframing the Issue
Team performance should be treated as an organisational capability problem. The executive question is not merely, "Do we have good people?" It is, "Have we designed a system in which these people can combine their capabilities effectively?"
That requires leaders to consider at least five conditions.
First, the team needs a genuine shared outcome. A broad slogan is not enough. Members should understand what result they are jointly responsible for and which trade-offs they are authorised to make.
Second, team boundaries should be clear enough that people know who is inside the decision system, who is consulted and who remains an external stakeholder. Constantly changing membership can be unavoidable, but it carries a coordination cost that should be recognised rather than ignored.
Third, the work structure must support the outcome. Roles, interfaces, information flows and decision rights should reduce ambiguity rather than simply document it.
Fourth, the wider organisation must provide resources, information, tools, political support and realistic priorities. A team cannot outperform the constraints imposed by its environment forever.
Fifth, coaching and leadership should be matched to the team's maturity and task. New teams may require more clarity and active guidance. Mature teams often benefit from greater delegation and less intrusive control.
Team Development Is Not a Straight Line
Development models are useful because they remind leaders that teams change over time. They become dangerous when treated as a timetable. Real project teams can move backwards. A major scope change can return a performing team to conflict. A new specialist can unsettle established norms. A crisis can temporarily centralise decision-making. A merger of two workstreams can create a new "forming" phase even when every individual is experienced.
The practical implication is that leaders should monitor the team's operating state rather than assume maturity because the team has existed for a long time. Useful signals include whether members raise problems early, whether decisions are understood consistently, whether people ask for help without political fear, and whether conflict improves or degrades the quality of work.
A high-performing team is therefore not a final destination. It is a condition that must be maintained while the task, membership and environment continue to change.
Decision Framework
A leadership team considering a new project or a struggling existing team can use five tests.
1. Outcome test. Is there one consequential result that requires collective performance, or are we grouping largely independent work under one label?
2. Boundary test. Is it clear who has standing to make, challenge and implement decisions? Are key contributors actually available when needed?
3. Structure test. Do roles, interfaces, meeting rhythms and information flows help the work move, or do they create additional friction?
4. Context test. Does the organisation supply the resources, sponsorship and political support necessary for the team to succeed?
5. Development test. What does the team currently need from leadership: direction, conflict resolution, norm-setting, coaching, delegation or renewal?
Failure on one test does not automatically mean the team should be redesigned. It does mean leaders should stop assuming the problem can be solved by motivation alone.
From Strategy to Execution
Immediate action: clarify the team's shared outcome, critical interfaces and decision rights. Identify where members receive incompatible priorities from other parts of the organisation. Remove avoidable ambiguity before introducing new behavioural interventions.
Medium-term capability: build explicit team routines for planning, challenge, conflict resolution, information sharing and after-action learning. Integrate newcomers deliberately rather than assuming they will absorb unwritten norms. Track whether the team is becoming more capable of solving its own problems.
Long-term strategic positioning: design project and cross-functional team practices as an organisational capability. Reuse effective patterns for team charters, mobilisation, role design, sponsor support, coaching and knowledge transfer. The objective is not to standardise every team, but to stop relearning the same lessons from scratch.
Related article: Cross-Functional Teams Create Value at the Interfaces
Related article: When Strong Teams Make Bad Decisions
Signals to Monitor
Watch for repeated escalation of decisions that should be made inside the team, growing dependence on one individual, persistent role ambiguity, increasing meeting time without faster decisions, silent disagreement, high turnover at key interfaces, and a widening gap between formal responsibility and actual authority.
Positive signals include earlier identification of problems, fewer avoidable hand-off failures, stronger peer-to-peer problem solving, clearer ownership and an increasing ability to absorb change without losing coherence.
Questions for the Leadership Team
- Is this genuinely a team, or simply a reporting label placed over separate contributors?
- Which current performance problems are behavioural, and which are consequences of our organisational design?
- What decisions should the team be able to make without escalation?
- Where are members receiving conflicting incentives or priorities?
- If the current team leader disappeared tomorrow, which capabilities would remain and which would collapse?
- Are we measuring only delivery, or also whether the team is becoming more capable of future performance?
Closing Perspective
The quality of a team is never only the quality of its people. Performance emerges from the interaction between people, task, structure, context and leadership. Executives who understand that distinction stop asking leaders to heroically compensate for poor design. They create teams that can become effective, remain effective and transfer capability beyond the life of a single project.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.