🧭 Dojo Compass
Module: Leadership, People and Organizational Excellence
Focus Area: Organizational Design and Governance
Key Article Point
Teamwork is one of the most powerful force multipliers available to a business.
When people work effectively together, the combined result can be substantially greater than the contribution of the individuals involved. Ideas move faster, problems are solved more effectively, resources are deployed more intelligently and organizational momentum increases.
The opposite is also true.
Poor collaboration creates friction, duplication, delays, misunderstandings and missed opportunities. The resulting loss of value can be considerably greater than the weakness of any individual employee.
Yet despite its importance, teamwork is surprisingly difficult to create and sustain.
Organizations frequently approach teamwork as a cultural aspiration:
“We need to work together.”
“We are one team.”
“Communication is important.”
These statements may be true, but they rarely create sustained teamwork.
The deeper insight is that teamwork is not primarily a slogan, a personality trait or even a state of mind. It is an organizational system.
Modern organizations are not composed of one permanent team. They are better understood as fluid ecosystems of teams that form, interact, compete, collaborate and dissolve according to the work that needs to be done.
The challenge for leadership is therefore not simply to make everyone “work together.”
It is to design and manage the conditions under which the right people collaborate effectively around the right objectives at the right time.
🎯 Key Challenge
The traditional organizational model tends to view the company as a collection of departments and individuals.
Marketing has its team.
Finance has its team.
Operations has its team.
Legal has its team.
Technology has its team.
But much of the work that actually creates value does not fit neatly into those structures.
Imagine a company launching a major new product.
The work may require:
- product development;
- engineering;
- marketing;
- sales;
- finance;
- legal;
- customer support;
- external partners.
There may be no single department responsible for the entire outcome.
Instead, a temporary collaborative unit must form around the objective.
And this is where many organizations struggle.
They try to force fluid work into static organizational structures.
The result is often a series of handoffs:
“That is Marketing’s responsibility.”
“Finance needs to approve it.”
“Legal has not reviewed it.”
“Technology is still working on its part.”
Each department may perform its individual responsibilities correctly while the overall initiative performs poorly.
The problem is not necessarily a lack of capable people.
It is the absence of an effective team system.
🥋 Dojo Solution
Replace the Concept of “The Team” with a Team Ecosystem
A more useful organizational model is to think of the company as having a team ecosystem.
Different teams exist for different purposes.
Some are permanent.
Some are temporary.
Some are functional.
Some are cross-functional.
Some may last for years.
Others may exist for only several weeks.
Some may collaborate closely.
Others may have partially competing objectives and need a structured mechanism for resolving their differences.
This is not organizational disorder.
It is organizational flexibility.
The objective is to create a system capable of assembling the appropriate collaborative capability around the work that matters.
A strong teamwork system therefore has several components.
1. Strong Leadership
Teamwork requires leadership because collaboration naturally deteriorates without active management.
Priorities change.
People become busy.
Conflicts emerge.
Responsibilities become unclear.
Teams can gradually drift away from their original objectives.
The deterioration may be so gradual that nobody notices until significant value has already been lost.
Leadership therefore has an important role in maintaining the conditions for effective collaboration.
This does not mean that every team needs a senior executive.
It means every meaningful team needs someone accountable for its effectiveness.
2. Design Teams Around Work, Not Organizational Charts
One of the most important questions management can ask is:
“What team does this work actually require?”
Suppose the company needs to develop a new product.
Rather than assigning the project to one department, management should identify the capabilities required to complete it.
Perhaps the team requires:
- one product specialist;
- two engineers;
- one salesperson;
- one marketing specialist;
- one finance representative;
- one legal adviser.
The resulting team may cut across five organizational departments.
That is not a problem.
It may be exactly what the work requires.
The organizational chart should support the work rather than dictate how the work must be performed.
3. Build Multiple Teams, Not One Giant Team
A common misconception is that teamwork means getting everyone together.
Often this makes teamwork worse.
Large groups can become slow, unfocused and difficult to manage.
Instead, an important initiative may require several smaller teams operating simultaneously.
For example:
Team A: Product design
Team B: Customer research
Team C: Commercial strategy
Team D: Technical implementation
These teams may periodically exchange information or converge around specific decisions.
The organization therefore becomes a network of interconnected teams rather than one giant collaborative group.
The objective is coordination without unnecessary complexity.
4. Allow Teams to Form and Dissolve
A highly effective organization should be capable of rapidly creating teams around important problems.
When the problem is solved, the team should be capable of dissolving.
This is particularly important for SMEs, where resources are limited.
Imagine a company suddenly discovering a major problem with one of its products.
The organization might temporarily bring together people from:
- engineering;
- customer service;
- operations;
- sales;
- finance.
They form a problem-solving team.
Once the issue is resolved, those people return to their ordinary responsibilities or join other teams.
This is essentially an organizational version of resource reallocation.
People should be deployed according to where they can create the greatest value.
5. Give Every Team a Clear Objective
Fluidity does not mean ambiguity.
Every team should understand:
What are we trying to accomplish?
Why does it matter?
What is the deadline?
What does success look like?
What authority do we have?
Without these parameters, teams can easily drift.
A team may continue discussing a problem long after the important decision has become clear.
Or different team members may pursue different interpretations of the objective.
Clear objectives create a common operating point.
6. Give Teams Leaders
Every meaningful team needs ownership.
The team leader does not necessarily need to be the most senior person.
The leader’s responsibility is to:
- maintain focus;
- coordinate activities;
- resolve issues;
- facilitate decisions;
- escalate matters when necessary;
- monitor progress;
- and ensure accountability.
A team without clear leadership can become a committee.
A committee discusses.
A team executes.
7. Establish Decision-Making Frameworks
Disagreement is not necessarily bad teamwork.
In fact, disagreement can improve decisions.
The problem occurs when disagreement produces paralysis.
Teams should therefore know:
- who makes the final decision;
- which decisions require consensus;
- which decisions can be delegated;
- when escalation is necessary;
- and how quickly decisions should be made.
Different teams may require different decision-making speeds.
A crisis-response team may need decisions within minutes.
A product strategy team may have weeks.
The decision framework should therefore match the team’s objective.
8. Create Team Identity
Even temporary teams benefit from identity.
Give the team:
- a name;
- a clear mission;
- a defined objective;
- visible milestones.
Recognize accomplishments.
Celebrate important victories.
Acknowledge exceptional contributions.
This does not require elaborate corporate exercises.
A simple message from leadership recognizing that a team solved an important problem can reinforce the idea that collaborative work matters.
Team identity creates psychological ownership.
People begin to think:
“This is our problem to solve.”
rather than:
“This is another task management assigned to me.”
9. Measure and Learn
Every team creates information about how the organization works.
Management should capture it.
Ask:
- Did the team have the right people?
- Was its objective clear?
- Were decisions made quickly enough?
- Were responsibilities clear?
- Where did communication break down?
- What caused delays?
- Which skills were missing?
- What should be done differently next time?
This creates an organizational learning loop:
Team → Performance → Data → Learning → Better Team Design
Over time, the company becomes better at assembling teams.
That itself becomes a competitive capability.
🏗️ Putting It into Practice
Step 1. Identify the Work That Matters
List the company’s most important current initiatives.
Do not begin with departments.
Begin with outcomes.
For example:
- launch Product X;
- acquire 20 new enterprise customers;
- reduce customer response time;
- enter Market Y;
- solve a major operational bottleneck.
Step 2. Define the Required Capabilities
For each objective, identify the capabilities required.
Ask:
Who needs to know something?
Who needs to do something?
Who needs to make decisions?
Who needs to approve something?
This produces the initial team architecture.
Step 3. Form the Team
Select the smallest group capable of accomplishing the objective.
Avoid adding people simply because they are interested or because their department normally participates.
The right team is not necessarily the largest team.
Step 4. Establish the Operating Framework
Define:
- objective;
- deadline;
- roles;
- leader;
- decision rights;
- meeting cadence;
- escalation process;
- success metrics.
Step 5. Monitor Team Health
During execution, watch for:
- unclear ownership;
- slow decisions;
- recurring conflict;
- duplicated work;
- communication gaps;
- loss of focus.
Address these issues early.
Step 6. Conduct a Team After-Action Review
When the objective is achieved, ask what worked and what did not.
Capture the lessons.
Then decide whether the team should:
- continue;
- change composition;
- split into smaller teams;
- merge with another team;
- or dissolve.
This keeps the organizational system fluid.
📌 Key Takeaways
- Teamwork is not created by slogans.
- Sustained teamwork requires a system.
- Organizations should be viewed as ecosystems of teams rather than a single permanent team.
- Teams should be built around work and outcomes, not merely departments.
- Cross-functional teams are often essential for complex initiatives.
- Teams can be temporary and should be capable of forming and dissolving quickly.
- Every team needs a clear objective, leader and decision-making framework.
- Disagreement can be productive when the decision process is clear.
- Team identity can strengthen ownership even in temporary teams.
- Team performance should generate organizational learning.
- Strong teamwork requires continual adjustment as priorities and circumstances change.
- The goal is not to make everyone collaborate with everyone.
- The goal is to create the right collaboration around the right work at the right time.
🌿 Reflection
Perhaps the most important shift is to stop thinking about teamwork as a permanent condition.
Organizations are often described as if they were machines.
Departments are the components.
Employees are the parts.
Processes connect everything together.
But real organizations are much more dynamic.
People move between projects.
Priorities change.
New problems emerge.
Customers create unexpected demands.
Technology changes how work is performed.
A small group may suddenly become critically important to the organization, while another group that was previously central becomes less important.
The organization is therefore constantly reconfiguring itself around work.
The best organizations recognize this.
They do not attempt to eliminate the fluidity.
They build systems that allow them to manage it.
This also changes the meaning of teamwork.
Teamwork does not mean that everyone gets along all the time.
It does not mean that everyone agrees.
It does not mean that every decision is made collectively.
And it certainly does not mean repeating the phrase “we are one team.”
Real teamwork means that the right people can combine their capabilities effectively to accomplish something that would be harder or impossible to accomplish individually.
Sometimes that requires cooperation.
Sometimes it requires constructive disagreement.
Sometimes it requires one team to challenge another.
Sometimes it requires a team to dissolve so its members can be redeployed elsewhere.
The objective is not harmony for its own sake.
The objective is collective performance.
That is why teamwork should be treated as an organizational design problem.
If the company repeatedly struggles to collaborate, management should not simply tell people to communicate better.
It should ask:
“What is it about our system that makes effective collaboration difficult?”
That question moves the organization from aspiration to action.
⚔️ Dojo Mission
Map Your Team Ecosystem
Choose one major initiative currently underway in your business.
Ignore the organizational chart for a moment.
Instead, identify the actual team required to accomplish the objective.
Write down:
- The objective.
- The deadline.
- The people who actually need to participate.
- The leader.
- Each person’s responsibility.
- Who has decision-making authority.
- How disagreements will be resolved.
- How success will be measured.
- When the team should dissolve or be reconfigured.
Then ask one final question:
“If we designed this team from scratch based solely on the work that needs to be done, would it look different from the team we currently have?”
If the answer is yes, you have probably identified an opportunity to improve not only teamwork, but the organization’s overall capacity to execute.
Leave a Reply