Kurt Lewin's Force Field Analysis: A Practical Guide for Change Leaders
Learn what force field analysis is, how Kurt Lewin's model works, and see real examples with a step-by-step guide to driving and restraining forces.
Guide users inside their tools
Measure real usage
Keep the app portfolio under control
Learn what a RASCI matrix is, how each of its five roles works in practice, how it compares to RACI, and how to build one step by step with a real example.
The RASCI matrix is a responsibility assignment framework that maps five roles (Responsible, Accountable, Supportive, Consulted, and Informed) to every task in a project, so every stakeholder knows exactly what is expected of them. It is a direct extension of the widely used RACI responsibility matrix, adding a dedicated Support role for teams that need an active collaboration layer between the task owner and subject-matter advisors.
The RASCI matrix is a project management tool that visually maps stakeholder roles to each task or deliverable in a project. Its purpose is to eliminate ambiguity, prevent duplicated effort, and ensure that no task is left without a clear owner. Each cell in the grid receives one of five role designations, giving every participant a precise reference point throughout the project lifecycle.
The framework belongs to the broader family of RAM (Responsibility Assignment Matrix) tools. These matrices are standard instruments in project management for linking project roles to deliverables and work packages, making them especially useful during project planning, kick-off, and scope changes.
The RASCI model is also closely related to Lean Six Sigma practice, where defining process ownership is a prerequisite for identifying and eliminating waste. The RASCI chart format, whether built in a spreadsheet or a dedicated project tool, follows the same logic: tasks on one axis, stakeholders on the other, and a single letter in each cell.
Each letter in RASCI describes a distinct level of involvement. Assigning the right role to the right person is the core skill in building a useful matrix. The five RASCI definitions below are the standard interpretations used across project management and Lean Six Sigma contexts.
The Responsible party is the individual or group that performs the work. Multiple people can share this designation for a single task, but over-assigning it dilutes accountability. In practice, keep the number of Responsible parties as small as the task genuinely requires.
The Accountable person holds final decision-making authority and ownership of the outcome. Only one person should be Accountable per task. This is the individual who answers if something goes wrong and who signs off on completion. When this role is missing or duplicated, decisions stall.
The Supportive role is what distinguishes RASCI from RACI. Supportive team members actively assist the Responsible party by providing resources, doing preparatory work, or stepping in to unblock progress. They are more hands-on than a Consulted party but do not own the task outcome. This role is particularly valuable in cross-functional projects.
Consulted individuals are subject-matter experts whose input is sought before or during task execution. Communication with them is two-way: the task owner asks questions, and the Consulted party provides guidance. They advise on the work rather than performing it.
Informed stakeholders receive updates on progress and outcomes. Communication with them is one-way. They need awareness of the project status because of their position, but they do not contribute to execution decisions.
| Role | Level of Involvement | Can There Be Multiple? | Communication Direction |
|---|---|---|---|
| Responsible | Executes the work | Yes, but keep it lean | Two-way with Accountable |
| Accountable | Final authority and ownership | No - exactly one per task | Two-way with Responsible |
| Supportive | Actively assists Responsible | Yes | Two-way with Responsible |
| Consulted | Provides expert advice | Yes | Two-way with Responsible |
| Informed | Receives status updates | Yes | One-way (receives only) |
The RASCI and RACI frameworks serve the same core purpose, but they are not identical. The critical structural difference is the addition of the Support (S) role in RASCI. Understanding the RACI vs. RASCI distinction helps teams choose the right tool before they begin building their matrix.
In a standard RACI framework, a stakeholder either owns the work, advises on it, or is kept in the loop. There is no formal designation for someone who rolls up their sleeves to help the Responsible party without owning the outcome. RASCI fills that gap. The Support role is especially useful in cross-functional projects where specialists from other departments contribute effort without taking ownership of the deliverable.
Both the RACI matrix and the RASCI matrix also serve as diagnostic tools. Working through the grid helps project managers spot:
The choice between RACI and RASCI is not about which is better in absolute terms. For a straightforward project with a small, co-located team, RACI is usually sufficient. For a large, multi-department initiative where active support relationships need to be formalized, RASCI is the stronger model. For a detailed side-by-side breakdown of these two frameworks, see the guide to RASCI vs. RACI key differences.
The primary advantage of RASCI is role clarity at scale. When teams grow beyond a handful of people, informal role expectations break down. A completed RASCI matrix gives every participant a single reference document that answers the question "what is my job here?" for each task.
Additional benefits include:
These benefits directly support broader organizational goals. For teams implementing new systems or processes, pairing a RASCI matrix with a structured change management approach helps ensure that role assignments are understood and acted on, not just documented.
Building a RASCI matrix requires five sequential steps. Work through them in order to avoid backtracking once the grid is populated.
Before creating the matrix, agree on what the project covers. List all major deliverables and break them into discrete tasks or sub-tasks. The left column of the matrix will hold these tasks, so they need to be specific enough to assign a meaningful role to each stakeholder.
List every person or role involved in the project across the top row of the matrix. Use role titles rather than personal names where possible. This makes the RASCI chart reusable if personnel change during the project.
Work through each task row and assign R, A, S, C, or I to each stakeholder column. Apply these rules as you go:
Share the draft matrix with all stakeholders and invite corrections. This step often surfaces disagreements about ownership that are better resolved on paper than mid-project. Color-coding each letter (for example, yellow for A, blue for R) makes the grid easier to scan during review sessions.
Once finalized, make the matrix accessible to everyone on the project. Store it in a shared location and assign someone to update it when scope, personnel, or responsibilities change. A RASCI matrix that is not maintained becomes a source of confusion rather than clarity.
Like any project management tool, the RASCI matrix has limitations. Recognizing them in advance makes it easier to manage them before they affect delivery.
A matrix for a project with dozens of tasks and many stakeholders can become difficult to read and maintain. Work at the right level of granularity: use high-level task groupings in the main matrix and create separate sub-matrices for particularly complex workstreams.
Some team members may be unfamiliar with the RASCI framework or skeptical of its value. Address this by involving key stakeholders in the creation process rather than presenting a completed matrix for sign-off. Participation increases understanding and buy-in.
When responsibilities genuinely overlap between two people, the matrix can expose tensions rather than resolve them. Use the review step as a structured conversation to clarify boundaries before they become conflicts. If two people both believe they are Accountable for the same task, that is a project governance issue that needs resolving at the leadership level.
In agile or rapidly changing projects, the matrix can become outdated quickly. Build a review cadence into the project schedule, for example a brief matrix audit at each sprint retrospective or milestone review, to keep it current without creating excessive overhead.
It is tempting to mark senior stakeholders as Informed on every task. This creates communication overload and signals that the matrix has not been thought through carefully. Only assign I where an individual genuinely needs the information to fulfill their role.
The following example shows how RASCI designations might be applied across a simplified software rollout project. Stakeholder titles are illustrative and represent typical roles rather than named individuals.
| Task | Project Manager | IT Lead | HR Manager | Department Head | Executive Sponsor |
|---|---|---|---|---|---|
| Define project scope | A | R | C | C | I |
| Configure software environment | I | A/R | I | I | I |
| Develop training materials | C | S | A/R | C | I |
| Deliver end-user training | I | S | A | R | I |
| Post-launch review | A | R | R | C | I |
Notice that in "Deliver end-user training," the IT Lead carries an S designation. They are not running the sessions (that is the Department Head's Responsible role), nor do they own the outcome (the HR Manager is Accountable), but they actively support delivery by providing technical assistance. This is the Supportive role doing exactly what it is designed to do, and it is the clearest illustration of where RASCI adds value over a standard RACI chart.
For guidance on building the visual representation of this grid, the RACI diagram guide covers diagramming principles that apply equally to RASCI charts.
Click the image to receive your template

Lemon Learning helps organizations put role clarity into practice. When teams understand their responsibilities, adopting new tools and processes becomes significantly more straightforward. Explore how the Lemon Learning change management solution supports project teams through structured onboarding and in-app guidance that reinforces who does what at every stage of a rollout.
RASCI stands for Responsible, Accountable, Supportive, Consulted, and Informed. Each letter represents a distinct role assigned to stakeholders for every task or deliverable in a project, so everyone knows exactly what is expected of them.
The core difference is a single added role. RACI covers Responsible, Accountable, Consulted, and Informed. RASCI adds a Supportive role for team members who actively assist the Responsible party without owning the outcome. RASCI is better suited to larger, cross-functional projects; RACI is simpler and works well for smaller teams or straightforward projects.
No. RASCI remains a widely used project management and responsibility assignment tool. Critics of responsibility matrices in general point to rigidity in fast-moving environments, but most practitioners address that by scheduling regular matrix reviews rather than abandoning the framework. It continues to be recommended in project management and Lean Six Sigma contexts.
RASCI is typically pronounced 'razz-ee,' treating the acronym as a single spoken word. Some practitioners say each letter individually, but the single-word pronunciation is the most common convention in English-speaking project management communities.
Learn what force field analysis is, how Kurt Lewin's model works, and see real examples with a step-by-step guide to driving and restraining forces.
Learn how to choose an HRIS with a step-by-step selection process, key criteria, vendor considerations, and a practical checklist for HR teams in...
Learn how to measure and optimize ROI when digitizing your Purchasing function. Discover the right KPIs, a 3-step framework, and how to drive lasting