Asher's Blog

One of the biggest tests of a founder is whether the company can operate without every important question returning to the founder’s desk.

In the beginning, this dependence may seem natural. The founder has the most context, understands the customer, knows why earlier decisions were made and often has the strongest emotional connection to the outcome. Team members therefore come back for approval, clarification and rescue. The founder answers quickly, the immediate problem disappears, and everybody feels productive.

Over time, however, the habit becomes dangerous. People stop developing judgment because asking the founder is safer than deciding. Leaders become coordinators who collect information and transmit it upward. The founder works harder, but the organisation does not become stronger. Eventually the company reaches the limit of one person’s attention.

My biggest lesson about hiring and building an independent team begins with clarity. Before you recruit anybody, you need to know the kind of person you are looking for, the skills and character they must bring, the outcomes they must own and the decisions they should be able to make without returning to you.

Without that clarity, founders often hire impressive people into vague jobs, then micromanage them because nobody agreed on what real ownership meant.

Hiring begins before the interview

The quality of a hire is influenced long before the candidate enters the room. It begins when the founder defines the problem the person is being hired to solve.

Many job descriptions are lists of activities: manage the team, attend meetings, prepare reports, coordinate stakeholders, support growth and perform other duties as required. The language may sound professional, but it does not tell the candidate or company what success looks like.

A better hiring brief begins with a mission for the role, followed by measurable outcomes and the capabilities required to produce them. The book Who by Geoff Smart and Randy Street popularised the use of a hiring scorecard organised around a role’s mission, outcomes and competencies. The framework is useful because it forces a founder to move beyond “I need a strong person” and define what strength must accomplish in this specific company.

For a sales leader, the mission is not simply to manage sales. It may be to build a repeatable enterprise revenue engine, hire and develop a particular team, shorten the sales cycle and deliver a defined level of profitable revenue without creating promises operations cannot fulfil.

For a product leader, the mission is not merely to manage a roadmap. It may be to improve activation and retention for a defined customer segment, build an effective discovery process, reduce time from insight to release and develop product managers who can make sound decisions.

For a finance leader, the mission may include producing timely accounts, creating cash visibility, improving collections, establishing controls and helping the company allocate capital intelligently.

Once the outcome is clear, it becomes easier to identify evidence from the candidate’s past. What comparable outcome have they produced? Under what conditions? What resources did they have? Which part did they personally own? What became stronger after they left?

Clarity protects the company from being seduced by titles, confidence or a prestigious employer that may have supplied the systems the candidate now appears to possess personally.

Hire for the stage you are entering

The right person for one stage can be the wrong person for another. A talented early employee may thrive in ambiguity and personally perform many tasks, but struggle when the role requires building managers and systems. A senior executive from a large corporation may understand scale, yet find it difficult to operate without a large budget, established brand and specialist support functions.

The founder must therefore understand the next chapter of the company. Are you looking for someone to discover the model, build it or optimise it? Do you need a leader who can recruit a department from zero, or one who can improve an existing team? Is the principal challenge technical depth, commercial discipline, operational control, culture or international expansion?

“Best of the best” does not mean the most famous person you can afford. It means the strongest match between the person, the problem, the stage and the organisation you are trying to become.

The candidate should also want the actual job, not merely the title. A role may sound like “Chief Operating Officer,” while the immediate reality involves repairing processes, confronting underperformance and working through incomplete data. If the person expects only strategy and executive visibility, disappointment will begin quickly.

Be honest about the work. Great people are not frightened by difficult problems, but they need to know which problem they are agreeing to own.

Sometimes it takes hiring and rehiring

Even with a disciplined process, hiring will not be perfect. Interviews are compressed simulations, references can be incomplete and some strengths become visible only under real pressure. Sometimes the founder discovers that the role itself was poorly designed. Sometimes the company’s needs change faster than expected. Sometimes the person simply cannot produce the required outcome.

It may therefore take hiring and rehiring to get a critical position right. The important thing is to learn quickly and decide on time.

Founders often retain the wrong person because replacement feels disruptive, the employee is well liked or the founder is embarrassed to admit that the hire was a mistake. Meanwhile, stronger employees compensate for the gap, decisions remain unresolved and the founder quietly takes the function back. The cost is larger than the salary. It includes delayed execution, lost confidence, reduced standards and the message that accountability is optional.

This does not justify impulsive firing. The founder should first examine whether expectations were clear, resources were available, feedback was direct and the person had a reasonable opportunity to improve. A leader should not be punished for failing an outcome they were never empowered to own.

Once the pattern is clear, however, delay does not become kindness. It transfers the cost of indecision to the rest of the team.

Do not hire leaders and then treat them like assistants

If you hire a leader, you should not micromanage that person. A leader who must seek approval for every material action is not leading; they are administering the founder’s preferences.

Micromanagement often begins with good intentions. The founder cares deeply, sees risks others miss and may genuinely be better at performing some parts of the work. Yet constant intervention changes behaviour. The leader stops deciding and starts predicting what the founder wants. Information becomes filtered to avoid criticism. Strong people either become passive or leave, while dependent people remain because the system rewards dependence.

The alternative is not neglect. Founders should know what is happening in important areas, ask difficult questions and review performance. The issue is whether oversight increases the leader’s capacity or replaces it.

A useful distinction is between controlling the method and holding someone accountable for an outcome. The founder can agree on the objective, constraints, budget, decision rights and review rhythm, then allow the leader to choose the path. If the leader’s approach differs from the founder’s but remains responsible and produces the result, that difference may be evidence that real ownership exists.

High-stakes projects deserve temporary depth

There are moments when the founder should request more detail. A major enterprise implementation, fundraising process, regulatory application, security incident, product launch or transformation programme may be sufficiently important that ordinary reporting is inadequate.

For that period, the founder and leader can design a special operating rhythm: a weekly review, risk register, decision log, milestone dashboard or shorter escalation window. The business may depend on the project, and the founder’s context or authority may help remove obstacles quickly.

This is not automatically micromanagement. It becomes micromanagement when the founder quietly takes control, begins issuing instructions to the leader’s team, changes decisions without context or continues the emergency reporting long after the special need has ended.

The arrangement should be explicit. Why is the additional visibility required? What information will be reviewed? Which decisions remain with the leader? Which events require escalation? When will the intensified cadence end?

Temporary depth should make the project safer while preserving one accountable owner.

Responsibility must be attached to outcomes

One of the most important cultural shifts is moving people from responsibility for activity to responsibility for outcomes.

Attending meetings is an activity. Sending proposals is an activity. Releasing features is an activity. Producing reports is an activity. These things may be necessary, but they do not prove that the organisation achieved anything valuable.

The sales team’s outcome is not the number of calls made; it includes suitable revenue that closes, collects and can be served profitably. The product team’s outcome is not the number of features released; it is the change in customer behaviour or business performance those features were intended to create. Customer success is not measured only by tickets closed, but by customers receiving value, remaining and expanding. Finance is not finished when a spreadsheet is circulated; the numbers must be accurate enough to support decisions and obligations must be met.

When an outcome is missed, the responsible leader should not simply list everything the team did. The discussion should examine why the work failed to produce the result, what assumptions were wrong and what will change.

This does not mean leaders control everything affecting an outcome. Markets change, dependencies fail and other teams contribute. Ownership means the leader identifies those dependencies early, escalates material risks, mobilises help and remains answerable for guiding the outcome rather than retreating into “my team completed its tasks.”

If you cannot afford senior leaders, grow ownership earlier

Young companies may not be able to recruit experienced executives into every function. That does not mean all responsibility must remain with the founder.

Push meaningful ownership to the people you have. Give a promising team member a defined outcome, the context behind it, reasonable authority and a review rhythm. Allow them to prepare the recommendation rather than merely collect data. Ask them to identify risks, propose alternatives and make a decision within agreed boundaries.

Responsibility should expand in stages. Begin with a contained problem where mistakes are recoverable. Review the reasoning, not only the result. As judgment improves, increase the scope, consequences and ambiguity of the decisions entrusted to the person.

This is how leaders are developed. A founder cannot demand mature ownership from people who have spent years being instructed at every step.

The company should also invest in learning. Exposure to strong mentors, consultants, books, courses and experienced advisers can accelerate people who have talent but have not previously seen scale. In Africa, where the supply of experienced startup executives may be limited in some functions, developing internal talent and borrowing expertise can be more practical than waiting indefinitely for a perfect hire.

Still, potential should not be confused with readiness. A person may be capable of growing into a role without being ready to carry an existential responsibility today. The founder must balance development with the risk the company can safely bear.

Decision rights must be visible

Teams often send everything back to the founder because nobody knows who can decide.

A leader is told to “own marketing,” but the founder approves every campaign, finance can stop every expense, product controls the launch date and sales expects to determine the message. When the boundaries are unclear, returning to the founder becomes rational.

For recurring decisions, the company should clarify who recommends, who decides, who must be consulted and who merely needs to be informed. Atlassian’s DACI framework uses the roles Driver, Approver, Contributors and Informed to make this structure explicit. The labels matter less than the clarity: one person should drive the process, and the final decision should not belong to an invisible committee.

Decision rights should also include thresholds. A leader may approve spending up to a defined amount, hire within an agreed plan, resolve standard customer issues and change operational processes within regulatory boundaries. Matters involving extraordinary capital, legal exposure, customer funds or a strategic reversal may require the founder, executive team or board.

When people know the boundary, they can move quickly inside it and escalate responsibly outside it.

Context is what allows people to decide well

Delegation without context is abandonment. If the founder hands over a task without explaining the company’s purpose, constraints, history and current priorities, the employee must either guess or keep returning for answers.

Teams need to understand how the company makes trade-offs. Is this year’s priority growth, margin, reliability or a particular customer segment? Which risks are unacceptable? What has already been tried? Which commitments have been made to customers and investors? What is the cash position? What does “good” look like?

Netflix popularised the phrase “context, not control” in its management culture. Whatever one thinks about every aspect of that model, the underlying insight is valuable: informed people can exercise judgment more effectively than people who receive isolated instructions.

The founder should therefore repeat important context. What feels obvious to the founder may be new to an employee and only partially understood by a leader. Strategy needs to appear in resource decisions, operating reviews and the questions senior people ask, not merely in an annual presentation.

When the context changes, say so. A team cannot be accountable for yesterday’s priority after the founder privately moved to tomorrow’s.

Build systems that answer ordinary questions

Some decisions return to the founder because the company has not converted repeated judgment into systems.

If the same discount request appears every week, define pricing authority and exceptions. If teams repeatedly ask which customer issue is urgent, create severity levels and escalation rules. If hiring approvals remain confusing, establish workforce plans and compensation bands. If product priorities change through private messages, create a visible review and decision process.

A system is not merely software or a policy document. It is a repeatable way to handle a recurring situation. Good systems reduce unnecessary variation while preserving judgment for genuinely unusual cases.

Dashboards are part of this design. When leaders can see the metrics they own, they do not need the founder to tell them that performance has changed. Regular operating reviews allow risks to surface without a constant stream of ad hoc requests. Written decisions preserve reasoning so future employees do not have to rediscover the same context.

The goal is to make ordinary work independent and exceptional work visible.

Leaders must be allowed to hold their own teams accountable

A founder undermines a leader by bypassing them constantly. If employees can appeal every difficult instruction directly to the founder, or if the founder privately assigns work without informing the leader, formal accountability becomes impossible.

This does not mean employees should have no access to the founder or that misconduct must remain inside a reporting line. Healthy organisations need channels for serious concerns and leaders should not control information. The principle is that ordinary management should respect ownership.

When the founder disagrees with a leader, discuss it directly. When the founder needs something from the team, involve the accountable leader. When an employee raises a routine operational complaint, help them resolve it through the proper structure rather than becoming an alternative manager.

The leader must also be capable of giving feedback, addressing underperformance and making difficult people decisions. If every disciplinary matter comes back to the founder, the company has managers in title but not in practice.

Do not rescue people so quickly that they never learn

Founders are often fast problem-solvers. When a leader brings a difficult issue, the founder sees an answer and gives it immediately. That feels efficient, but repeated rescue trains the team to bring problems rather than judgments.

Before answering, ask: What do you think we should do? Which alternatives did you consider? What information is missing? What is the risk of waiting? What decision would you make if I were unavailable?

The founder can then challenge the reasoning, add context and approve or modify the recommendation. Over time, the leader learns how the founder thinks and develops an independent decision-making framework.

There are emergencies in which speed matters more than development, but emergencies should not become the normal management model. If the founder always supplies the answer, the organisation will never learn to think without the founder.

Create accountability without creating fear

Outcome ownership requires consequences, but a culture of fear encourages people to hide bad news. Leaders must be able to say that a target is at risk, an assumption was wrong or a mistake occurred while there is still time to respond.

Accountability asks whether the person acted responsibly with the information and authority available, surfaced risk early, learned quickly and changed the approach. It distinguishes an intelligent experiment that failed from negligence, repeated excuses or concealed underperformance.

Psychological safety does not mean low standards. It means people can tell the truth without being humiliated. High standards and honest communication should strengthen one another.

The founder sets this tone through response. If every piece of bad news produces anger, people will wait until the evidence is undeniable. If failure has no consequence and commitments can be missed indefinitely, ownership disappears. Mature leadership holds both truth and performance together.

Measure whether the team is becoming independent

Founder independence should become observable. The company can ask:

• Are decisions being made at the appropriate level, or does the founder remain the default approver?
• Do leaders bring recommendations and trade-offs, or merely report problems?
• Can teams explain the outcomes they own and the metrics that reveal progress?
• Are risks escalated early, with enough context for a decision?
• Does the founder continue to attend meetings that would function well without them?
• Can the company operate effectively when the founder is unavailable for a week?
• Are high-stakes projects receiving appropriate visibility without destroying the accountable leader’s authority?
• When an employee leaves, does the process continue because knowledge belongs to the organisation?

The answers reveal whether delegation is real or ceremonial.

Build leaders, not messengers

A company that can operate without everything returning to the founder is not a company in which the founder has become irrelevant. It is a company in which the founder has transformed personal judgment into organisational capability.

Begin with clarity. Define the mission, outcomes, competencies and decision rights before hiring. Recruit people whose evidence matches the stage and problem, not merely people with impressive titles. Accept that some critical roles may require rehiring, but diagnose the failure honestly and act before the cost spreads through the company.

Do not micromanage leaders. Give them context, authority, resources and accountability. When a project is unusually important, create temporary visibility with explicit boundaries rather than quietly taking the work back. Hold people responsible for results, not attendance, task lists or activity without consequence.

If you cannot yet afford senior leaders, begin developing ownership in the team you have. Increase responsibility deliberately, provide coaching and allow people to make recoverable decisions. Build systems that handle recurring questions, respect reporting lines and stop rescuing people before they have had the opportunity to think.

The test of leadership is not how many decisions the founder can make correctly. It is how many people the founder can develop to make good decisions, take responsibility for outcomes and strengthen the company without waiting for permission at every turn.

That is how a founder stops being the centre of every operation without abandoning the responsibility to lead.