RACI and the Rescuer
When a leader keeps taking over other people's tasks, the problem is rarely kindness or workload alone. It is usually a role map that was never agreed. RACI names who does the work, who answers for the result, who must be asked, and who must be told — and it shows where rescuing has quietly replaced that agreement.
A scene from project life
A technical lead is preparing a release with a small team. Two junior colleagues own parts of the work, at least on paper. In practice, every difficult piece returns to the lead. A task looks risky, so the lead rewrites it at night. A question from the sponsor looks urgent, so the lead answers for everyone. A deadline moves closer, so the lead stops reviewing and starts doing.
From the outside, this looks like commitment. Inside the project, three things happen at once. The juniors stop treating their tasks as fully theirs, because experience teaches them that the lead will step in. The lead runs out of time for planning, checking, and the decisions that only the lead can make. And the release still slips, because the whole project now depends on one overloaded person.
Nobody in this scene is lazy, and nobody is acting in bad faith. The lead is helping. The team is accepting help that arrives before it is even requested. Yet the result is familiar: postponed delivery, growing resentment, and a quiet shared conclusion that the team cannot manage without rescue. That conclusion, not the original task, is the real problem.
The method, in substance
Transactional Analysis describes this pattern with the Drama Triangle: three roles — Rescuer, Victim, and Persecutor — that people move between in the same piece of work. The Rescuer helps without a clear request or agreement, and takes more responsibility than belongs to the role. The other side then settles into Victim: waiting, deferring, and handing decisions upward. Later the same Rescuer often switches to Persecutor, with a justified complaint: after everything taken on for the team, the team still did not deliver.
The roles rotate, so arguing about character misses the point. The useful question is structural: which responsibility was never contracted clearly enough for people to stay in their own roles? In project work, that question has a standard instrument — RACI.
RACI divides four kinds of involvement in every task or decision. Responsible does the work. Accountable answers for the result and makes the final call; there should be exactly one Accountable for each item. Consulted must be asked before the work or decision is completed, and their input must genuinely be considered. Informed must be told after the fact, in time to act on the information.
A role map adds what the four letters alone do not show: for each role, its responsibility, its authority, its resources, and its escalation path — where the role holder goes when the task exceeds their authority. A project works as a container when those things are explicit: what is mine, what is not mine, when a decision counts as made, and by what signs the work counts as done.
Rescuing breaks this map in a predictable way. The leader absorbs both Responsible and Accountable for tasks that belong to others. Consulted becomes a formality, because the decision has already been made by doing the work. Informed becomes a surprise, because the team learns about changes from the result. The matrix may still exist in a file, but the lived agreement is different: one person carries, the rest wait.
How to use it in a team
Start with the work as it actually runs, not as the organisation chart says it should. Take one project, or one release, and list its recurring tasks and decisions: preparing the release, answering the sponsor, approving a change, checking finished work, closing an incident. For each line, write who currently does it, who answers for it, who is asked, and who is told. Then mark the gaps honestly: lines with two people answering, lines with nobody answering, and lines where the leader does work assigned to someone else.
Next, read the same map as a games map. Where does the leader regularly step in without being asked? Where does a team member regularly wait instead of deciding inside agreed authority? Where does blame appear after a rescue that nobody contracted? These marks usually cluster on a few lines, and those lines are the place to begin.
Then recontract those lines, out loud and in writing. A recontract states three things: what I do, what I do not do, and how help is requested. For a delegated task it also states the limit of authority and the check-in point: the owner does the work and decides inside the limit, the leader is consulted at the check-in or when the limit is reached, and the sponsor is informed at the agreed moment. Help remains available — but as a consulted contribution, not as a takeover.
Hold the new map for one full work cycle before judging it. The first week will feel slower, because questions that rescue used to hide now become visible. That visibility is the point: a question asked early is planning material, while the same question hidden until the deadline becomes a crisis.
Where the method stops
RACI does not create people, time, or skill. If a task has no one able to do it, if authority is formally given to a role that is never allowed to use it, or if the sponsor keeps changing the scope while the dates stay fixed, no matrix will repair that. Those are resourcing and governance decisions, and they belong to the sponsor and the leader together, named as such.
A matrix without a contract also stops quickly. If the team agrees the letters on Monday and the leader takes a task back on Tuesday without renegotiating, the old agreement — rescue and waiting — is the one being taught. The instrument works only when a change to the map is itself agreed, recorded, and explained to everyone the change affects.
Finally, RACI describes tasks and decisions, not the whole relationship. Recognition, trust, and honest feedback still need their own agreements. The matrix clears the ground for them by removing the most common source of confusion: two different maps of the same work, one written and one lived.
One step this week
Choose one recurring task that you, as leader, regularly take over. Write its RACI line as it should run: one Responsible, one Accountable, who is Consulted, who is Informed. Read that line to the task owner and agree it together, including the limit of authority and the check-in point. Then let one full cycle run under the new line — and review the result, not the effort, at the end of the week.