Fractional Executive Bench, Advisory & LeadershipPlaybook3 min readUpdated September 2026

Building a Delegation Matrix After Series A

Most founders don't delegate too little because they enjoy control. They delegate too little because nobody ever asked them to sort decisions into categories, so everything defaults to the founder deciding. A delegation matrix fixes that by forcing every recurring decision into one of four buckets, based on how reversible it is and how much context it needs.

This walkthrough shows how to build the matrix yourself in about an hour, using decisions from your own last two weeks rather than a generic template.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Start by listing every decision you made in the last two weeks

Go through your calendar, Slack, and email from the last ten working days and write down every decision that wasn't purely product or strategy: who to hire, which vendor to pick, how to respond to a customer complaint, whether to approve an expense, how to handle a scheduling conflict. Most founders are surprised by the volume; twenty to thirty small decisions in two weeks is common even at a small team.

How do you sort decisions by reversibility and context?

For each decision, ask two questions: how expensive is it to reverse if someone gets it wrong, and how much company-specific context does it need that isn't written down anywhere? A vendor choice under a modest monthly commitment is cheap to reverse and needs little context: it belongs in someone else's hands. A pricing change for your top customer segment is expensive to reverse and needs deep context: it stays with you, at least for now.

How do you build a four-column delegation matrix?

Set up four columns: Keep, for decisions that are costly to reverse and need your context; Coach, where someone else decides but checks with you first for a defined period; Delegate, where someone else decides and tells you after, for visibility; and Remove, for decisions that no longer need a person at all because they should be a standing rule instead. Place every decision from step one into exactly one column. Most founders find that far more decisions belong in Coach and Delegate than they'd assumed, and a surprising number belong in Remove entirely.

Each column answers a different question about who decides:

  • Keep: decisions that are costly to reverse and depend on company context that only you hold.
  • Coach: someone else decides, but checks with you first for a defined period.
  • Delegate: someone else decides and tells you afterward, so you keep visibility.
  • Remove: decisions that should become a standing rule so no person has to make them.

A short worked example from a real week

Take four decisions from a typical week and sort them to see the pattern. Approving a new vendor for office snacks: cheap to reverse, no real context needed, so it goes in Remove as a standing rule with a spending limit. Choosing which candidate to extend an offer to for a support role: reversible but time-consuming to redo, moderate context needed, so it goes in Coach with your head of support deciding and checking with you first for the next two hires. Responding to an angry churn-risk customer from your largest account: expensive to get wrong and full of context only you have, so it stays in Keep for now. Picking a new project management tool for the team: cheap to reverse if it doesn't work out, low context needed beyond team preference, so it goes in Delegate with whoever leads that team deciding and telling you afterward. Running this exercise on even four real decisions usually makes the pattern obvious enough to sort the rest quickly.

Assign an owner and a review date to each Delegate and Coach item

A decision without a named owner just moves back to you by default within a month. For each Coach or Delegate item, write the specific person's name, not a role or team. Set a review date 30 to 60 days out to check whether the decision is landing well in their hands. If it isn't, that's information about the person or the process, not a reason to pull the decision back to yourself permanently.

Keep the matrix somewhere everyone can see it

A delegation matrix that lives in your head or a private note doesn't change anyone's behavior. Document it somewhere your team can reference, ideally in the same tool where the actual work happens; Trainual works well for capturing the reasoning behind each Coach and Delegate assignment, while ClickUp works well if you'd rather track it as living tasks with owners and due dates tied directly to the work itself. Revisit the whole matrix every quarter, since what needed your context at ten people rarely still does at thirty.

Executive Capability Standard

What Good Looks Like

Good practice is a written matrix, reviewed quarterly, where every recurring decision has a named owner and an explicit column, not an informal sense of who usually handles what.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Read through your last two weeks of decisions and sort a handful into Keep, Coach, Delegate, or Remove as a test before building the full matrix.
2. Do Manually:Build the complete four-column matrix yourself for every recurring decision type in the business, with a named owner for each Coach or Delegate item.
3. Delegate:Ask each named owner to review their own section of the matrix and flag anything where they don't yet feel confident deciding without you.
4. Automate:Track Delegate and Coach items as recurring tasks in ClickUp with owners and review dates, so nothing silently drifts back to you by default.
5. Buy:Bring in a fractional COO or chief of staff to run the full delegation exercise across the company if doing it yourself keeps getting deprioritized.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Frequently Asked Questions

How often should a delegation matrix be updated?

Quarterly is a reasonable default for an early-stage company, and immediately after any major milestone like a funding round, a new executive hire, or a big jump in headcount. Decisions that genuinely needed the founder's context at ten employees often don't at thirty, and the matrix should move with the company.

What if an employee I delegate to keeps making the wrong call?

First check whether they actually had the context they needed, since a wrong call is often a documentation gap rather than a judgment gap. If they had the context and still got it wrong repeatedly, move that specific decision back to Coach rather than Remove entirely, so you're reviewing it before it's final while they build the judgment.

Should every founder build this, or only after Series A?

The exercise helps at any stage, but it becomes necessary once decisions genuinely compete for your attention, usually around Series A or a headcount near fifteen to twenty. Before that point, a lighter version still works: list your recent decisions and mark the ones someone else could own. Waiting until the volume feels unmanageable usually means the founder is already the bottleneck.

About the numbers

This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.

Related Guides