How to use RACI when setting team goals.
RACI is widely used in project management. It’s used far less consistently when it comes to goals — which is often why team goals stall. Here is how to apply it properly.
The problem
Why team goals need RACI
Individual goals have a natural owner — the individual. Team goals do not. A team goal is shared, which means it is simultaneously owned by everyone and, in practice, owned by no one in particular.
This is the accountability diffusion problem. When five people are responsible for a team goal, each person can reasonably assume that progress is happening because one of the others is pushing it forward. Each person can also reasonably feel that their contribution is marginal — that the goal would succeed or fail regardless of what they specifically do this week.
RACI breaks this pattern by forcing clarity about who does what. It does not eliminate the shared nature of the goal. It structures the sharing so that accountability is assigned rather than assumed.
Application
Mapping RACI to a team goal
Apply RACI at the level of the goal and at the level of the milestones within it. These are different assignments.
At the goal level, every team goal should have: one Accountable — the person who owns the outcome, answers for it at leadership level, and has the authority to make decisions about how it is pursued. In most organisations this is a manager or team lead. At least one Responsible — the people doing the day-to-day work of executing toward the goal. On a team goal this is often the whole team, but each person’s Responsible contribution should be defined specifically, not assumed collectively. Consulted — typically adjacent teams, subject matter experts, or senior stakeholders whose input shapes how the goal is pursued. Informed — leadership or other parts of the business who need to know the goal exists and whether it is on track, but who are not involved in execution.
At the milestone level, individual milestones within a team goal often have different ownership from the goal itself. A milestone that requires IT involvement might have the IT lead as Responsible, with the original goal owner as Accountable. Assigning RACI at milestone level makes execution clearer and makes it easier to identify where blockers are coming from when the goal is not progressing.
Ownership
What does “Accountable” actually mean for a team goal?
This is where RACI gets complicated in a team goal context. For a project task, Accountable is relatively clear — someone signs off. For a team goal that spans months and involves multiple people, the Accountable role is more nuanced.
Accountable for a team goal means three things. The Accountable decides how the goal is pursued when there is disagreement within the team — not by overriding everyone, but by making the call when the team cannot. The Accountable surfaces blockers to leadership before they become critical, not after the goal has already slipped. They are the person leadership goes to for a status update, and that person should always have a real answer. The Accountable does not absorb all of the Responsible work. The most common RACI failure in team goal settings is the Accountable also doing all the execution, which means there is no oversight layer. When the Accountable is also the only Responsible, nobody is watching the goal from the outside.
“One Accountable. That person knows they are Accountable. Leadership knows who to call. The team knows who makes the final call. This is the only form of team goal ownership that actually works.”
Failure modes
Where it breaks down — team goal edition
The goal has three Accountables. Often framed as “shared ownership” or “joint accountability.” In practice, when one Accountable is dissatisfied with progress, they defer to the others. When two Accountables disagree about approach, there is no mechanism for resolution. Joint accountability is deferred accountability.
Everyone is Responsible, nobody has a specific task. A team goal where every team member is listed as Responsible but nobody has a defined contribution is a group intention, not a structured plan. The RACI matrix must be followed by a breakdown of what each Responsible person is actually doing — their milestones, steps, and daily habits — or the R assignment is meaningless.
Consulted becomes a veto. On team goals that cross departmental lines — which most strategic goals do — the Consulted column tends to expand. Adjacent departments ask to be consulted; it feels political to refuse. Over time, the Consulted list becomes a set of informal veto holders who slow execution without formal accountability for the outcome.
RACI is assigned at goal creation and never revisited. Team goals change shape. People leave. Priorities shift. A RACI matrix that was accurate in January may be completely wrong by March — but nobody has updated it because updating it feels like admitting something went wrong. Build RACI review into the milestone check-in process, not just into the goal creation process.
In practice
RACI in Goalite team goals
Goalite’s team goal features are built around the same ownership structure RACI defines. When a team goal is created in Goalite, an Accountable is assigned — the single person who owns the outcome. Contributors are added with defined roles. Manager visibility shows the Accountable in real time whether milestones are progressing and whether daily habits are being tracked.
The difference from a static RACI matrix: ownership is active throughout the goal, not just at the moment of assignment. The Accountable can see at any point whether execution is happening — not because they scheduled a meeting to find out, but because the platform surfaces it.
“RACI tells you who owns the goal. Goalite shows you whether execution is actually happening — and surfaces it to the Accountable before it becomes a problem.”
Running team goals in your organisation?
See how Goalite’s pilot programme works — six months, paid, with defined success criteria and manager visibility built in from day one.