Running a Lean Team: Delegation, Incentives & Staying Close to the Work
Building a company young teaches you things in the wrong order. You learn the lesson, then you understand why it mattered, usually after it's already cost you.…
Building a company young teaches you things in the wrong order. You learn the lesson, then you understand why it mattered, usually after it's already cost you. Two of those lessons — about delegation and about incentives — changed how I run a small team.
Delegation was the best and worst decision I made
When you start a company before you know what you're doing, you figure things out by making mistakes, and you take on far too much until you burn out. That was me. The fix seemed obvious and worked beautifully: hire subject-matter experts and hand each domain off to them. Fewer mistakes. A genuine eureka moment.
Then it came crumbling back down.
Because delegation has two hidden costs nobody warns you about:
1. You become the integrator. The moment you delegate, it's your job to bring everyone together toward a common mission. There's no way around this — coordination becomes your real work. 2. You lose first-degree knowledge. You're no longer in direct contact with what's actually happening in that domain. You get the perceived reality filtered through the person you delegated to — which isn't necessarily true. That gap quietly produces miscalculated decisions, bad assumptions, and, occasionally, people who realise they can manage your perception instead of the work.
I think this is exactly why some of the most successful founders still periodically do the lowest-level job in their own company — the founder of a giant delivery company still occasionally working as a delivery rider isn't a PR stunt; it's how he keeps first-degree contact with the truth.
So here's where I landed: delegate responsibility, but every once in a while, step back in and do the work at ground level. Be an intern at your own company. Step into each person's shoes occasionally so you keep your roots. I won't pretend I'm certain this is the perfect answer — but losing touch with the ground is a worse failure than getting your hands dirty.
Incentives are a design problem, not a willpower problem
The second lesson is about consistency. On a small team with a tight budget, the constraint is never ambition — everyone's willing. The constraint is consistency: showing up, every day, long enough for compounding to kick in. Time (effort) and money are the two levers, and when you're reinvesting everything you make back into the business, you need the effort lever to be reliable.
I learned not to moralise about this but to design for it. The system I built had exactly one purpose: incentivise consistency, with clear, symmetric rules — reward the people who show up, gently penalise the people who repeatedly vanish. The specifics matter less than the principles behind them:
- Make the expectation explicit and measurable. "Be reliable" is a wish. "Tell us at least two hours before if you can't make a check-in; you have a budget of N informed absences a month" is a system.
- Reward and penalty should be symmetric and real. A small bonus for high consistency, a small deduction for repeated unreliability — visible enough to matter, small enough to feel fair.
- **Distinguish informed from uninformed.** Missing with notice is a scheduling fact; vanishing without notice is a trust problem. Treat them differently.
- Allow a humane buffer. People have lives. A few free passes a month keeps the system from feeling punitive and keeps it focused on patterns, not one-off bad days.
- Tie it to the shared "why." People accept incentives when they understand the stakes — that consistency now is what lets a small, broke team become something bigger.
The deeper insight: on a small team, culture is mostly the incentives you actually enforce, not the values you put on a wall. If you want consistency, build a small, fair machine that rewards it — don't hope for it.
The throughline
Delegate, but never go blind — step back onto the ground floor regularly so you're deciding from first-degree reality, not second-hand summaries. And when you need a behaviour from a team, design an incentive for it instead of relying on goodwill. Both lessons rhyme: stay close enough to the truth to lead from it, and make the right thing the easy, rewarded thing.