Seven habits for leading a small team without burning out

Executive overview

Working weekends and feeling like a human shock absorber are symptoms of missing team systems, not missing people. The fix is a set of repeatable habits that shift responsibility to the team and replace reactive firefighting with structured learning.

The core insight: founders burn out by absorbing their team's problems — the solution is building systems that make those problems stay with the person responsible.

Ritualize successful behaviors

• Identify the recurring small actions that produce a desired outcome, then schedule them.
• Ask: "What do I need to do, and at what frequency, to be successful in this area?"
• Example: SOPs get reviewed because a recurring task prompts it every 30 days — not because people remember.
• Treat any business goal as a set of compounding habits, not a one-time effort.

Make mistakes public

• Create a shared error log — a running record of what went wrong and what was learned.
• Adults, unlike toddlers, can learn from others' experiences to avoid repeating them.
• Start by logging your own mistakes first; leadership modelling removes the punitive feel.
• Ask in 1-on-1s: "Can you help me understand what led to this? I'm not looking to assign blame."

Require preventative actions, not apologies

• When something goes wrong, "sorry" and "it won't happen again" are not acceptable outputs.
• The only acceptable response: a concrete step that makes the mistake structurally harder to repeat.
• Example: a typo in a newsletter → a pre-send checklist. A missed call → always two people assigned.
• Responsibility for the fix belongs to the person who owns the area, not the manager.
• Manager's role: oversee that the preventative action actually gets implemented.

Infuse learning into culture

• Add a "what did we learn this week?" section to team meeting agendas.
• Include a student-mentality assessment in performance reviews.
• Celebrate when a mistake leads to a new process — share the template, not just the incident.
• When prompting reflection, ask "what did we learn from this?" with a constructive tone, then stay quiet.
• Prompt compliance directly: "You said you'd update those emails — can you tag me in the task?"

Incentivize the right things

• Measure what actually generates value, not just task completion.
• Penalizing overdue tasks incentivizes team members to take on as little as possible.
• Flip to positive metrics: tasks completed, support tickets resolved, value delivered.
• When mistakes happen, a positive metric lets you celebrate the fix rather than punish the delay.
• Ask direct reports "why is this your top priority?" — the answers reveal where incentives are misaligned.

Don't borrow emergencies

• When someone fails to follow a process and a problem results, do not absorb the problem yourself.
• Return the incomplete work to the person responsible with a clear comment and a deadline.
• Make it their late night, their stress, their overdue — not yours.
• This is the hardest habit and the most impactful: when team members know you won't rescue them, SOPs get read.
• Accepting the short-term pain of slower resolution builds the long-term accountability culture.