Create an account to save sources and durable progress.
Helping founders design the right roles, build trust and create a team that increases the company’s capability.
Leadership is not about doing more yourself. It is about increasing the capability of everyone around you.
Start here
In the early days of a company, the founder often carries everything.
They sell, make product decisions, solve customer problems, approve spending, recruit people, review work and step into every issue that appears. This level of involvement may be necessary at the beginning.
It does not scale.
As the company grows, the founder’s role must change. The challenge is no longer simply to produce more personal output. It is to increase the capability of the people around them.
That is the role of leadership.
A strong team requires more than talented individuals. It needs the right roles, clear ownership, trusted relationships, useful measures, honest feedback and enough authority for people to act.
When these foundations are weak, the founder becomes the centre of every decision. Work slows down, responsibilities overlap, capable people wait for approval and important issues remain unresolved.
The company may have more employees but less clarity.
Apollo believes team performance depends on two connected dimensions:
Apollo uses two established models to understand these dimensions:
Together, they help the founder answer:
The founder’s job is not to control every action or rescue every problem.
It is to build a team that can think, decide and perform together.
Key takeaways
By the end of this guide, you’ll understand how to:
Design roles around the company’s current stage and required outcomes.
Separate a role-design problem from an individual performance problem.
Use forming, storming, norming and performing as a practical team diagnostic.
Build the trust required for productive conflict and honest communication.
Turn debate into commitment, accountability and collective results.
Clarify ownership, responsibilities and decision rights.
Core question
How can a founder build a trusted, accountable team that performs well without depending on constant founder intervention?
Mike’s story
The Apollo Perspective on Team Performance
Apollo believes a high-performing team requires both the right design and the right behaviours.
A company may employ capable individuals but still perform poorly because important roles are missing, responsibilities overlap or people are working in positions that no longer match what the business needs.
Likewise, a well-designed organisation can underperform when trust is weak, disagreement is avoided or accountability depends entirely on the founder.
Talent alone is not enough.
High performance requires:
Team Development Is a Practical Role Question
Tuckman’s model is often described as:
Forming → Storming → Norming → Performing
For a founder, this is not merely a description of how people feel over time.
It is a practical way to evaluate:
Every time the strategy changes, the company grows or a significant person joins or leaves, the team may move through these stages again.
During forming, the founder is defining the team required for the company’s current stage.
The Path to High Performance Starts With Trust
Tuckman helps diagnose the development and design of the team.
Lencioni provides the behavioural path towards high performance.
Apollo expresses that progression as:
Trust → Productive conflict → Commitment → Accountability → Collective results
Each level depends on the one below it.
Without trust, people protect themselves.
When people protect themselves, honest conflict disappears.
Without honest conflict, decisions lack genuine commitment.
Without commitment, accountability feels unfair or personal.
Without accountability, individual interests begin to outrank collective results.
The Apollo Team Performance Model
Apollo combines both models into one practical diagnostic.
Forming → Storming → Norming → Performing
Ask:
Trust → Productive conflict → Commitment → Accountability → Collective results
Ask:
The Foundations of a Team That Multiplies
Apollo believes teams multiply capability through seven connected foundations.
| Foundation | Leadership question |
|---|---|
| Trust | Can people speak honestly about mistakes, risks and uncertainty? |
| Role clarity |
The Founder-as-Saviour Trap
In the early stages of a company, the founder often becomes the person who saves everything.
A customer is unhappy, so the founder steps in.
A deadline is at risk, so the founder finishes the work.
A team member is uncertain, so the founder makes the decision.
Sales are slow, so the founder closes the deal.
The product has a problem, so the founder directs the fix.
At first, this behaviour can help the company survive. The founder holds the context, feels the urgency and is often capable of solving the problem faster than anyone else.
The danger is that rescue becomes the operating model.
The founder becomes the saviour.
Then the saviour becomes the bottleneck.
The team learns that difficult problems will eventually return to the founder. People wait for approval, escalate routine decisions and become hesitant to act without reassurance.
Common People Traps
People problems are often described as personality problems.
Sometimes they are. More often, the deeper issue is unclear roles, weak trust, avoided conflict, poor delegation or expectations that were never made explicit.
Apollo recommends diagnosing the system before blaming the individual.
| People trap | What it looks like | Better alternative |
|---|---|---|
| The title-first trap |
A Practical People Process
A strong team does not emerge from good intentions alone.
It develops when the founder repeatedly clarifies what the company needs, matches people to meaningful roles, builds trust and gives others enough authority to perform.
Apollo recommends a practical eight-step process.
The team structure should reflect the company you are building now—not the company you hope to become several years from now.
Begin by clarifying:
The Founder Dependency Test
Ask:
If the founder stepped away for four weeks, what would stop?
The answers may reveal:
A company is too dependent on the founder when:
The One-Page Team System
A founder should be able to describe the current team system on one page.
Include:
Key Takeaways
Next Step
Create the first version of your One-Page Team System.
Start with five decisions:
Then choose one meaningful leadership action.
It may be:
The objective is not to remove the founder from everything.
It is to stop making the founder the answer to everything.
Think • Reflect • Act
A high-performing team needs the right roles, the right people and the trust required to work through difficult problems together.
Team performance has two dimensions.
Clear roles do not guarantee performance when people cannot speak honestly.
Trust alone does not compensate for missing capability or unclear ownership.
Questions
A founder can rescue a company through a difficult moment.
But a company cannot scale when rescue becomes its normal way of working.
The strongest leaders tell the truth, clarify what matters, put the right people in the right roles and steadily transfer the context and authority others need to succeed.
Continue learning
You have explored how to design the roles a company needs, strengthen the behaviours that create high performance and reduce unhealthy dependence on the founder.
As the team grows, another challenge becomes increasingly important.
Every new role, salary, tool and operating commitment affects the company’s financial position. Founders need to understand whether the company is creating and capturing enough value to support its ambition.
Define roles, clarify accountability, support hiring and build a practical people operating system.
© Apollo Advisors° ABN 34 346 108 139
Delegate meaningful outcomes rather than isolated tasks.
Give timely feedback and address difficult performance issues.
Recognise when the founder has become the company’s bottleneck.
Move from founder-as-saviour to multiplying leader.
I did not pretend to have all the answers.
I told the team:
I’m worried too. I don’t know exactly how this will unfold, but here is the plan. Share your ideas, help one another and let’s do our best work together.
That honesty changed the atmosphere.
People understood the reality of the situation rather than filling the gaps with rumours. They could see how their work connected to the company’s survival. They contributed ideas, supported colleagues and focused on winning the new business required to protect the team.
We mostly avoided the anticipated cuts.
We won new clients.
But the most important result was not simply commercial.
The culture became much stronger.
Trust increased because people saw that leadership was willing to tell the truth, including when the truth was uncomfortable. The team understood that vulnerability did not mean avoiding responsibility. I could admit uncertainty while still providing direction, making decisions and asking everyone to contribute.
That experience changed how I think about leadership.
People do not expect leaders to predict the future perfectly. They do need leaders who are honest about reality, clear about the plan and willing to face uncertainty alongside them.
Transparency alone is not enough. A leader must also provide a path forward.
The combination matters:
Radical transparency did not remove the fear.
It turned private fear into a shared challenge the team could address together.
High performance requires both the right roles and the right relationships.
The key questions are:
The mistake is beginning with titles or copying the structure of a larger company.
A startup should design roles around the work and outcomes that matter now.
For example, the company may not need a broad Head of Marketing. It may need someone specifically accountable for generating qualified demand from one defined customer segment.
Storming is where reality tests the original team design.
Differences and tensions become visible:
Storming should not automatically be treated as interpersonal dysfunction.
It may be evidence that the roles, people or operating model need to change.
The founder should ask:
Avoiding these questions allows confusion and resentment to grow.
Norming occurs when the company turns lessons from the storming stage into a clearer operating model.
The team establishes:
The practical test is whether every important outcome has one clear owner.
Team members should understand:
Norming reduces dependence on the founder because the team no longer needs constant interpretation of responsibilities.
A performing team has the roles, capabilities and behaviours required to deliver together.
People:
Performance does not mean that the original roles remain fixed forever.
As the business evolves, the founder must continue asking:
Are these still the roles we need, and are these individuals successfully doing what those roles now require?
A person who was an excellent fit at one stage may need coaching, additional support, a redesigned role or a different position as the company grows.
The team cannot skip directly to performance metrics.
It must begin with trust.
Trust allows people to be honest about:
At Tribal DDB during the global financial crisis, radical transparency helped create this foundation. The situation was frightening, but acknowledging reality made it possible for the team to face the challenge together.
Trust does not mean avoiding standards or difficult decisions.
It means people do not need to hide the truth to protect themselves.
Trust makes honest disagreement possible.
People can challenge:
The purpose is not to win an argument.
It is to reach a stronger decision.
Teams that avoid conflict may appear harmonious while important doubts, risks and resentment move into private conversations.
After the team has debated the issue, it must make a clear decision.
Commitment requires clarity about:
People do not need to receive their preferred outcome.
They need the opportunity to contribute and confidence that the decision is clear.
Debate openly. Decide clearly. Commit together.
Commitment creates the basis for accountability.
The team can now address:
Accountability should not be the founder’s responsibility alone.
High-performing teams hold one another to the standards and commitments they have agreed.
The final test is whether people prioritise the team’s shared outcomes above:
A high-performing team understands that individual success matters most when it contributes to the company’s shared result.
A team may have strong trust but unclear roles.
It may have clear roles but avoid conflict.
It may contain talented people who are no longer matched to what their roles require.
The leadership task is to identify the weakest point and address it directly.
| Alignment | Are people working towards the same priorities and outcomes? |
| Decision rights | Is it clear who decides, who contributes and who executes? |
| Accountability | Are commitments visible and performance issues addressed? |
| Feedback and learning | Can the team improve without blame or defensiveness? |
| Leadership multiplication | Are leaders increasing the capability of others? |
These foundations reinforce one another.
Trust without clarity can produce warmth but little progress. Clarity without trust can create compliance rather than commitment. Accountability without clear ownership feels unfair. Delegation without decision rights creates confusion.
A multiplying team needs all seven.
Trust begins when people believe that reality can be discussed openly.
That includes:
The Tribal DDB experience taught me that people can handle difficult information better than leaders often assume.
What damages trust is not always the bad news itself. It is the feeling that important information is being hidden or softened until it is too late.
Transparency does not mean sharing every private detail or speaking without judgement. It means giving people the information they genuinely need to understand the situation and contribute responsibly.
A leader can say:
I do not have every answer yet. Here is what we know, what remains uncertain and what we are doing next.
That is more useful than false certainty.
As startups grow, responsibilities often develop informally.
Someone begins helping with sales. Another person takes ownership of operations. A founder continues making product decisions because they have always done so.
Over time, several people may believe they own the same outcome—or nobody does.
Role clarity should answer:
A job title is not enough.
A strong role definition focuses on responsibility rather than a long list of tasks.
For example:
Own the system that generates qualified demand from large Australian gaming venues and moves those opportunities into the sales pipeline.
That is clearer than:
Manage marketing.
People can work hard while moving in different directions.
Sales may prioritise short-term revenue. Product may prioritise platform quality. Marketing may prioritise reach. Operations may prioritise efficiency.
Each objective may be sensible in isolation while creating conflict across the company.
Alignment means agreeing on the small number of outcomes that matter most now.
A useful alignment rhythm clarifies:
The team should be able to answer:
What are we trying to achieve together, and how does my work contribute?
Founders often delegate work without delegating decisions.
A team member may be responsible for an outcome but still need approval for every important choice. This creates the appearance of ownership without the authority required to deliver.
Decision clarity should distinguish between:
Not every decision needs a committee.
| Decision type | Likely owner |
|---|---|
| Company strategy | Founder and leadership team |
| Product priorities within an agreed strategy | Product owner |
| Customer issue within defined limits | Customer-success owner |
| Hiring within an approved role and budget | Functional leader |
| Day-to-day execution | Person closest to the work |
| Material legal, financial or reputational risk | Appropriate executive or board authority |
Accountability often becomes emotional because it is introduced only after something has gone wrong.
A healthier approach makes commitments visible from the beginning.
Every meaningful commitment should clarify:
When a commitment is missed, the first goal is to understand why.
Possible causes include:
Accountability should identify the real issue rather than immediately assigning blame.
But empathy must not become avoidance.
Feedback should help people improve the work and their judgement.
It should not be limited to annual performance reviews or moments of frustration.
Useful feedback is:
A simple feedback structure is:
For example:
In yesterday’s client meeting, you answered the implementation question before checking with the delivery team. That created an expectation we may not be able to meet. Next time, confirm the commitment before giving the customer a deadline.
This is more useful than:
You need to communicate better.
Feedback should also move upwards.
Founders need people who can say:
The final stage is not simply building a team that follows the founder well.
It is developing people who can create clarity, make decisions and improve the capability of others.
A multiplying leader:
Doing the work personally may be faster today.
Teaching someone else to own it creates more capacity tomorrow.
The founder should regularly ask:
Am I solving this problem because only I can—or because I have not yet helped someone else become capable of solving it?
The founder remains involved in everything because everything appears to require the founder.
This creates a cycle:
The founder rescues the team → the team develops less capability → more problems require the founder → the founder becomes increasingly overloaded.
The company may continue growing in headcount while remaining dependent on one person.
That is not scalable.
Common signs include:
The founder may believe they are protecting quality.
In reality, they may be preventing the team from developing judgement, confidence and ownership.
The pattern usually comes from positive intentions:
And it often is faster—today.
But repeatedly solving the problem personally makes the company slower tomorrow.
Every rescue should raise a second question:
What capability, role, decision right or process is missing that caused this problem to depend on me?
The goal is not for the founder to stop helping.
The goal is to stop being the only person capable of helping.
A multiplying leader responds differently.
Instead of immediately taking over, they ask:
The founder may still intervene during a genuine crisis.
But intervention should be followed by learning:
The objective is to leave the company more capable after every problem.
| Design each role around the outcomes the company needs now. |
| The wrong-stage trap | A person who succeeded earlier is expected to fit every future stage automatically. | Reassess whether the role and individual still match the company’s needs. |
| The role-confusion trap | Several people share responsibility, but nobody clearly owns the outcome. | Give every important outcome one accountable owner. |
| The founder-as-saviour trap | Problems, approvals and decisions continually return to the founder. | Transfer context, authority and capability deliberately. |
| The artificial-harmony trap | The team avoids disagreement to protect relationships. | Build enough trust for productive conflict. |
| The false-consensus trap | Silence is interpreted as commitment. | Invite challenge, decide clearly and confirm ownership. |
| The accountability-avoidance trap | Missed commitments and poor behaviour remain unaddressed. | Make expectations visible and discuss gaps early. |
| The activity trap | Performance is judged by busyness rather than outcomes. | Define the result each role exists to produce. |
| The delayed-feedback trap | Concerns accumulate until they become formal performance problems. | Give specific, timely feedback while improvement is possible. |
Early-stage companies often copy job titles and structures from much larger organisations.
A title may sound appropriate while concealing a poorly designed role.
Start with the work.
Ask:
Startups change quickly.
A role that was appropriate at ten people may look very different at thirty or one hundred. The person who succeeded while improvising may struggle when the company requires planning, delegation and repeatable systems.
This does not automatically mean the person has failed.
It may mean:
Ask:
If we were designing this role today, would we define it the same way—and would we still choose the same person for it?
Shared responsibility often sounds collaborative.
In practice, it can mean that nobody feels fully accountable.
For every important outcome, define:
Some teams appear calm because nobody challenges one another.
Meetings remain polite. Decisions receive little resistance. Difficult topics are postponed or discussed privately afterwards.
This is not necessarily alignment.
It may be artificial harmony.
Leaders can encourage healthy conflict by asking:
A team may have a thoughtful discussion and still leave with different interpretations of the decision.
At the end of an important discussion, confirm:
Founders often delay difficult conversations because they want to preserve trust or morale.
But unaddressed performance issues usually damage both.
Begin by clarifying whether the issue is:
Accountability should be direct and fair.
It should include support, clear improvement expectations and an honest timeframe.
Teams can become extremely busy without producing the outcomes the company needs.
Each role should have a small number of clear outcomes.
Activities matter only when they contribute to the result.
Feedback loses value when it arrives too late.
A concern that could have been corrected through one early conversation may become months of frustration, lost trust and formal performance management.
Do not store feedback for an annual review.
Annual reviews should summarise and develop—not surprise.
Design the team around the company’s next stage—not its distant ambition.
For each role, clarify:
Why does the role exist?
Which meaningful results must it produce?
What ongoing work belongs to the role?
Which decisions can the person make?
What knowledge, judgement and behaviour are required?
Which people and teams must the role work with?
How will the company recognise strong performance?
Only then assess whether the current individual matches what the role requires.
This separates two questions:
Evaluate each person against the role as it exists now.
Consider:
Ask:
Possible actions include:
Share enough context for people to exercise judgement.
This may include:
The Tribal DDB town halls worked because transparency was paired with a plan.
The message was not:
Everything will be fine.
It was:
Here is what is happening. Here is what is at risk. Here is what we can do. Let us face it together.
Every important outcome should have one clear owner.
For each priority, define:
Use a delegation progression:
| Level | Decision approach |
|---|---|
| 1. I decide | The founder decides and explains the reasoning. |
| 2. We decide | The founder and team member decide together. |
| 3. Recommend | The team member recommends; the founder confirms. |
| 4. Decide and inform | The team member decides and keeps the founder informed. |
| 5. Own the outcome | The team member owns the decisions, result and improvement of the system. |
When roles, priorities or decisions change, disagreement is normal.
Invite people to challenge:
Then close the discussion clearly.
Confirm:
Choose the measures that show whether the team is producing the intended result.
Review outcomes through a regular rhythm.
When a problem reaches the founder, pause before taking it over.
Ask:
When intervention is necessary, improve the system afterwards.
A company cannot scale beyond the founder while the founder remains the answer to every important problem.
The purpose is not to create a static organisation chart.
It is to make the current team design, behaviour and leadership constraint visible.
Transfer one meaningful outcome before the founder’s rescue becomes part of the culture.
The founder must diagnose both.
Where is your team underperforming because of the individual—and where might the real problem be the role, expectations or operating system around them?
Ask:
Consider your current team.
Then answer the harder question:
Am I still solving these problems because only I can—or because I have not yet transferred enough context, authority and capability to someone else?
Create a one-page assessment of your current team.
Complete:
Over the next 12 months, the company must:
List the three to five outcomes that matter most.
The capabilities required are:
Identify what the team must be able to do well.
| Outcome | Required role | Current owner | Fit |
|---|---|---|---|
| Strong / Developing / Misaligned / Unfilled |
For each role, clarify:
For each current owner, ask:
Choose:
Complete:
The evidence for this stage is:
The team needs from leadership now:
The role or operating issue that must be resolved is:
Score each foundation from 1 to 5.
| Foundation | Score | Evidence | Next action |
|---|---|---|---|
| Trust | |||
Ask:
If I stepped away for four weeks, what would stop?
For each answer, identify the underlying cause:
Choose one dependency to reduce.
Clarify:
Do not delegate only the tasks while retaining every meaningful decision.
Choose one action:
Use this structure:
Here is what we know. Here is what remains uncertain. Here is the plan. Here is how you can contribute.
Identify one role, performance, behaviour or accountability issue that has been delayed.
Prepare:
Have the conversation early, directly and respectfully.
Keep commitments, responsibilities, client work and important relationships visible as the team grows.
Reflect on leadership decisions, prepare for difficult conversations and recognise recurring founder patterns.
Understand whether hiring plans, compensation and organisational growth are financially sustainable.
Related content
Your reading position stays on this device. Create an account when you want durable guide, reflection, note, and saved-item milestones.
Create an account for durable progress| Productive conflict |
| Commitment |
| Accountability |
| Collective results |
Start with the weakest foundation closest to the base.