What Is the BART Framework?
BART stands for Boundary, Authority, Role, and Task. Green and Molenkamp (2005) present it in the group relations tradition, which includes Tavistock-style conferences. Their work draws on a psychodynamic view of how groups function. At work, you can use the four dimensions to examine a specific episode and check your interpretation with the people involved.
Boundaries define the group’s scope, deadlines, and points of contact with other teams. Authority concerns who has the right to act and how people exercise that right. A role includes the responsibilities someone is assigned and the work they actually take on. The task is what the group is there to accomplish and what it does to get there. Green and Molenkamp also distinguish a group’s primary task from the work it does to manage how its members work together.
What Does a RACI Matrix Tell You About Responsibilities?
The Project Management Institute (2004) presents RACI as a type of responsibility assignment matrix. Each row describes an activity, deliverable, or decision. The columns show what each person or team does in relation to that item.
- R · Responsible is the person or team that does the work.
- A · Accountable is the person or group that ultimately answers for the outcome.
- C · Consulted identifies the people whose input is sought before action is taken or a decision is made.
- I · Informed identifies the people who receive updates at the agreed time.
Giving each row one clear A shows where final accountability sits. The same person or team can be both R and A. If a committee makes the decision, the matrix can name it and the committee’s charter can explain how it decides.
Why Examine Authority When an “A” Is Already Assigned?
The A in RACI tells you who answers for the work. In BART, examining authority also means looking at what authority was delegated, what resources support it, and how the person exercises it. Someone may have the authority to coordinate a task and still depend on another manager to commit the resources. When one line obscures those two decisions, the team may ask the project manager to settle a question that leadership or IT still has to decide.
Looking at the work also brings informal roles into view. A business lead may get decisions made because they have good relationships with both departments. That person’s mediation helps the project move forward. If decisions routinely have to go through them, the team comes to rely on their availability. BART helps the team decide whether to recognize the role, set a clear path for escalating decisions, or delegate authority differently.
How Do You Apply the Four BART Dimensions to a Project?
Take the software rollout. The team picks a configuration request that was put on hold. It traces where the request went, whose input was sought, and who made the last decision. The project manager, IT, and the business team may each see the episode differently. The BART worksheet gives them specific questions to reconstruct what happened.
If meetings revolve around out-of-scope requests, the team has less time to prepare for testing. If the business team is assigned to test the tool, its manager needs to be able to set aside time for that work. Those findings help identify what belongs in the matrix and which decisions need clear authorization.
How Do You Build a RACI Matrix and Check It with BART?
- Examine the work with BART. Clarify the scope, the team’s primary task, and the decisions it has the authority to make. If a RACI matrix already exists, start there. Look at specific episodes to see how the assignments work in practice.
- Record the responsibilities in RACI. Use one activity or decision per row. Agree on who does the work, who answers for the outcome, and who should be consulted or informed.
- Check that people can carry out their assignments. For each row that has caused a problem, ask who can act, what resources they can use, and where their authority ends. If the team needs a decision from someone outside the project, specify who gets the request and when.
In the example below, the project manager is accountable for configuration, and IT does the work. The business team runs user testing. Its charter specifies who signs off on the results. Leadership approves the budget and authorizes go-live.
If configuration stalls because IT staff are unavailable, the project needs a separate decision about how to allocate technical resources. Leadership can delegate that decision to IT within agreed limits. The project manager is accountable for delivering the agreed configuration. The team can spell out the escalation path in its charter and add a row to the RACI if the decision comes up regularly. At the next review, it can check whether requests are being decided by the people with the agreed authority.
Where Do BART and RACI Fit in the MEET© Protocol?
In the MEET© protocol, BART is an optional tool for investigating questions about authority, scope, or roles during Model. When teams depend on each other to move the work forward, behavioral systems mapping can help clarify how their actions fit together.
In Engineer, a RACI matrix can turn decisions from that investigation into explicit assignments and consultation rules. The approach proposed here uses a BART worksheet for diagnosis and a separate RACI matrix tied to the project charter. In Experiment, the team checks who actually makes decisions and whether issues are escalated to the people authorized to resolve them.
Frequently Asked Questions
Who invented the RACI matrix?
The origin of the acronym is uncertain. In a retrospective published by PMI, Webster (1999) notes that Cleland and Munsey described a Linear Responsibility Chart in 1967. The third edition of the PMBOK Guide (2004) includes an explicit example of a RACI matrix. These sources document the spread of the method and show that responsibility matrices had been in use earlier.
Can you use BART if you already have a RACI matrix?
Yes. Pick a recent decision that stalled or was handed off to someone else. Compare the assignments on the matrix with the path the decision actually took. That helps you see whether the row needs clarification or whether the team needs different decision rights, resources, or escalation rules.
What if two people think they have the final say?
Start by spelling out the decision each person thinks they own. They may have authority over two related decisions, such as confirming technical readiness and authorizing go-live. If their authority extends to the same decision, the sponsor needs to clarify who makes the call and how the other person contributes.
References
Green, Z. G., and Molenkamp, R. J. (2005). The BART System of Group and Organizational Analysis: Boundary, Authority, Role and Task. Working paper, University of San Diego, Digital USD. Repository record and text
Project Management Institute (2004). A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 3rd ed., p. 206, fig. 9-5. 2004 edition
Webster, F. M. (1999). They wrote the book: The early literature of modern project management. PM Network, 13(8), 59-62. Retrospective published by PMI
About the Author
Maxime Rabéchault is the founder and president of UNREST, a change enablement consultancy. He applies behavioral science to organizational transformation and leadership development.
.webp)
