The reason work keeps landing on you is probably not that your team is lazy. It is that your RACI matrix — the grid of who is Responsible, Accountable, Consulted and Informed for each recurring task — has your name in the Accountable column on nearly every row. When one person is A on everything, every decision queues behind that person's calendar. Fixing it starts as a paperwork problem, and that is the cheapest kind of management problem you will ever solve.
Key takeaways
- A RACI matrix with one person Accountable on almost every row is not documentation of roles; it is a diagram of a bottleneck with your name on it.
- A row with no Responsible owner is the loudest signal that the founder is quietly doing the work, because unowned work always defaults upward.
- Moving Accountable to three different people across the rows spreads decision rights, and a few lines of SOP behind each new owner gives them something concrete to decide against.
- Exporting the before and after matrices as PDF turns a private suspicion into a shared picture the team can actually act on.
The before matrix: ten tasks, nine of them yours
Picture a six-person operations team. Founder, ops manager, logistics lead, support lead, procurement lead, systems lead. Ten recurring tasks make up most of the week: supplier orders, the weekly dispatch schedule, customer escalations, invoice approvals, hiring sign-off, tool and access requests, stock counts, refund exceptions, process changes, and month-end reporting.
Write those ten tasks down, one per row, and fill in the columns honestly. In most small ops teams the founder's initial lands in A on nine of the ten. Sometimes a row carries the founder and the ops manager both, which is worse — two deciders on one row means no decider at all.
Build the grid once and the invisible thing becomes visible. You can draft it in a few minutes with the free RACI matrix generator: list the roles, list the tasks, click a box to cycle through blank, R, A, AR, C and I, and it drafts a first pass of who is Responsible, Accountable, Consulted and Informed.
What the rule-breaking flags actually tell you
A generator that checks RACI rules is useful precisely because it argues with you. These are the flags that matter most in a small ops team, and what each one is pointing at.
| What the flag shows | What it means | First move |
|---|---|---|
| One person holds A on most rows | Every decision waits for one calendar, and that calendar is full | Reassign A on two or three rows this week, not all of them |
| A row has no R at all | Nobody owns the doing, so the task quietly reverts to the founder | Name the R before you name the deadline |
| More than one A on a single row | Two deciders, which resolves to escalation and delay | Keep one A, move the other to C |
| Everyone is C on everything | Consultation becomes a committee and speed collapses | Cut C down to the people whose work actually changes |
| An A with no SOP behind it | The new owner guesses, gets it wrong, and hands it back | Write three lines: trigger, decision, definition of done |
The flag that stings is the empty Responsible cell. A row with no R is not a gap in your documentation; it is a confession that you have been doing that task between meetings and never told anyone it was yours. An unowned task does not wait politely for an owner. It travels to whoever feels most anxious about it, and in most teams that person is the founder.
The after matrix: three people holding A
The corrected version of that six-person grid does not spread accountability evenly, because even distribution is not the goal. The goal is that every row has exactly one A, that A sits with the person closest to the decision, and that no one holds more than a manageable share of the rows.
In the rewritten matrix, the founder keeps A on three rows: supplier contracts, process changes, and hiring sign-off. The ops manager picks up A on the weekly dispatch schedule, month-end reporting, and tool and access requests. The support lead takes A on customer escalations and refund exceptions. The procurement lead takes A on stock counts and invoice approvals. Ten rows, ten single owners, four people deciding instead of one.
The founder still has a vote on the rows that carry real money or real risk. What changes is the default. Escalations no longer travel upward automatically; they travel upward when the assigned A decides the situation is above their authority, and that decision is now a choice rather than a reflex.
Write the SOP behind each task
Handing someone an A without context is how delegation fails twice. The new accountable owner needs to know what triggers the decision, what they are allowed to decide, and what finished looks like. That is three lines, not a policy manual.
Take refund exceptions. Trigger: a refund request outside the standard window, or above the routine approval amount. Decision: the support lead approves, declines, or offers credit, and does not need to ask. Done: the customer is notified, the reason is logged, and the ledger entry is made the same day. That is a standard operating procedure, and it took less time to write than the first argument it prevents.
The generator drafts the SOP from your own notes on each task, so a few lines you already know become a full procedure sitting behind the row it belongs to. The rules are yours; the tool does the tidying.
Export both versions and show the team
Do not skip this step. Export the before matrix as PDF and keep it. Then export the after matrix and put them side by side in your next team meeting. The before page answers a question nobody wanted to ask out loud — why does everything come back to one desk — and the after page answers the follow-up: here is who decides now, and here is the written procedure that says so.
CSV is the right export if you want to sort, filter, or feed the rows into another system. Text is the right export if you are pasting the grid into a document, a ticket, or a message that needs to land without an attachment.
Quick checklist
- List your ten most frequent recurring tasks, one per row.
- List every role that touches them, including yourself, and fill in the grid honestly.
- Find the rows with no R — those are the tasks you have been doing invisibly.
- Find the rows where you hold A and nothing forces you to; pick two or three to hand over this week.
- Write a three-line SOP behind every row you reassign: trigger, decision, definition of done.
- Export the before and after matrices as PDF and walk the team through both.
The bottleneck is almost never a motivation problem, and it is almost never solved by working harder on the same rows. It is a decision-rights problem, and decision rights live in a grid you can draw in an afternoon. Start with the free generator at tools.exiuss.com/raci-matrix, put your own ten tasks in the rows, and let the flags tell you where you are still the only person allowed to say yes.