Team Roles, Structure and Accountability

Introduction

Effective teams do not succeed merely because talented people are placed together. They succeed when contributions are coordinated, authority is understood, responsibilities are explicit, decisions are made at the appropriate level, and members can be held fairly accountable for agreed results. Team structure provides the formal arrangement of work and reporting relationships; team roles describe the contributions individuals make; accountability connects authority and responsibility to performance and learning.

This chapter introduces practical frameworks for organising team contributions. Particular attention is given to Belbin’s team-role model, the RACI responsibility matrix, delegation, authority, responsibility, decision rights, and accountability mechanisms. These tools are useful in project teams, operational departments, committees, service organisations, and hybrid or virtual workplaces.

The frameworks should not be treated as mechanical substitutes for leadership judgement. A role label does not define a person permanently, and a RACI chart does not resolve every interpersonal or political issue. Their value lies in making assumptions visible, encouraging constructive discussion, and reducing avoidable ambiguity.

Learning Objectives

By the end of this chapter, you should be able to:

1. Explain the relationship between team roles, structure, authority, responsibility, and accountability.
2. Describe Belbin’s nine team roles and apply them appropriately.
3. Design and interpret a RACI matrix.
4. Distinguish delegation from abdication and explain the conditions for effective delegation.
5. Clarify decision rights and escalation arrangements.
6. Select practical accountability mechanisms for different types of work.
7. Evaluate the limitations and ethical risks of role and responsibility frameworks.

1. Team Structure and the Coordination Problem

A team is a group of interdependent people who combine their expertise to achieve a shared purpose. Interdependence means that one person’s work affects the timing, quality, or feasibility of another person’s work. For example, a marketing campaign may depend on accurate information from finance, creative material from communications, legal approval, and technical implementation.

Team structure answers several questions:

• What work must be completed?
• How is work divided and integrated?
• Who reports to whom?
• Who has authority to make particular decisions?
• How are conflicts and exceptions escalated?
• How will progress and results be reviewed?

A structure may be functional, project-based, matrix, networked, or self-managing. In a functional structure, people are grouped by specialist area. In a project structure, members are temporarily organised around an outcome. A matrix combines functional reporting with project or product accountability. In a networked structure, internal teams may work with external partners and distributed specialists.

No structure is universally best. Functional structures support professional depth but can create departmental silos. Project structures support focus but may duplicate expertise. Matrix structures can improve integration but may produce competing priorities. Self-managing teams can increase ownership but require clear boundaries, capability, and access to information.

The central design principle is alignment: the structure should fit the work, the level of uncertainty, the required speed of decisions, and the organisation’s risk exposure.

2. Roles: Formal Positions and Team Contributions

The word role has two related meanings. A formal role is an organisational position, such as project manager, analyst, or supervisor. A team contribution is the pattern of behaviour through which a person helps the group, such as generating ideas, coordinating activity, checking quality, or building relationships.

These meanings should not be confused. A project manager may formally occupy the leadership position but may also contribute as a Coordinator, Implementer, or Monitor Evaluator depending on the situation. Similarly, an employee without a managerial title may provide valuable leadership through expertise or facilitation.

Clear role design should specify:

• purpose and expected outcomes;
• key activities and boundaries;
• required knowledge and skills;
• decision authority;
• relationships with other roles;
• performance standards; and
• mechanisms for review and support.

Role clarity is associated with better coordination, but excessive role rigidity can suppress initiative. Effective teams therefore distinguish between non-negotiable accountabilities and flexible methods of contribution.

3. Belbin’s Team-Role Model

Meredith Belbin’s team-role model identifies nine patterns of contribution that can assist team composition and development. The model is behavioural rather than a system for permanently classifying personality. A person may demonstrate several roles, and the same person may behave differently as task demands, experience, incentives, and team climate change.

The nine roles

The model is useful in three main ways. First, it encourages teams to examine whether important contributions are missing. Second, it helps members recognise that disagreement may reflect different legitimate contributions rather than personal opposition. Third, it supports development conversations about how individuals can adapt their behaviour.

However, Belbin roles should not be used to stereotype people, determine promotion eligibility, or justify excluding someone from a task. Self-perception questionnaires and observer assessments are indicators, not definitive diagnoses. Managers should validate role interpretations through observed behaviour and results.

Applying Belbin responsibly

A team leader can apply the model through the following process:

1. Define the team’s purpose and major work demands.
2. Identify the contributions needed, such as innovation, coordination, quality control, stakeholder contact, and implementation.
3. Discuss members’ preferred and demonstrated contributions.
4. Identify gaps, overlaps, and risks.
5. Agree behavioural adjustments and working norms.
6. Review the pattern after the team has completed meaningful work.

The aim is not to create one of each role. A small team may require members to hold several roles, while a large team may need multiple people contributing in the same area. The relevant question is whether the team has sufficient coverage for its work.

4. Responsibility, Authority and Accountability

These concepts are related but distinct.

Responsibility is the obligation to perform an activity or produce an output. It concerns the work assigned to a person or group.

Authority is the legitimate power to make decisions, allocate resources, approve actions, or direct work. Authority may arise from formal position, delegated mandate, professional licence, expertise, or organisational policy.

Accountability is the obligation to explain decisions and results to an authorised person or stakeholder. Accountability includes answerability and consequences, but it should also include support, feedback, and learning.

A common management failure occurs when responsibility is assigned without sufficient authority. For example, a team may be held responsible for meeting a deadline while lacking access to data, budget, staff, or approval rights. This creates “accountability without control,” which is both unfair and operationally dangerous.

A sound assignment therefore considers three questions:

1. What result is this person expected to achieve?
2. What decisions and resources can the person control?
3. What support, constraints, and escalation routes apply?

Accountability is not the same as blame. Blame focuses narrowly on identifying a person at fault. Accountability examines commitments, decisions, conditions, evidence, and corrective action. A mature organisation distinguishes negligence or misconduct from a reasonable decision made under uncertainty with the information available at the time.

5. Decision Rights

Decision rights specify who may decide, who must be consulted, who must be informed, and who may challenge or escalate a decision. They are particularly important in matrix, cross-functional, and remote teams.

Decision rights should be clarified for decisions that are:

• high cost or high risk;
• difficult to reverse;
• legally or ethically sensitive;
• likely to affect several departments;
• dependent on scarce resources; or
• time-critical.

A useful decision-rights statement includes the decision owner, the decision deadline, the information required, the consultation obligations, the approval threshold, and the escalation route. For example: “The project manager may approve changes within the agreed budget and scope. Changes affecting regulatory compliance or increasing expenditure beyond the approved threshold require sponsor approval.”

Decision rights should be allocated as close as possible to the work, provided that the person has competence, information, and authority. Excessive centralisation slows work and reduces ownership; excessive decentralisation can create inconsistency and unmanaged risk.

6. The RACI Responsibility Matrix

RACI is a widely used tool for clarifying participation in activities or deliverables.

• Responsible (R): performs the work or ensures that the task is completed.
• Accountable (A): owns the final outcome and has authority to accept or approve it.
• Consulted (C): provides input before the activity or decision is completed.
• Informed (I): receives relevant information after or during the activity.

A typical RACI matrix places activities in rows and roles in columns.

The matrix illustrates several principles. Each important activity should normally have one clearly identifiable Accountable role. Several people may be Responsible, but responsibility should not be so widely distributed that nobody knows who is coordinating completion. Consultation should be meaningful rather than a demand for universal agreement. People listed as Informed should receive information proportionate to their legitimate need to know.

Constructing a RACI matrix

1. List outcomes and significant activities, not every minor action.
2. Identify the roles involved, rather than naming individuals where possible.
3. Assign R, A, C, and I based on actual authority and workflow.
4. Check for missing accountability, excessive consultation, and duplicated ownership.
5. Validate the matrix with the people who must perform the work.
6. Publish the agreed version and review it when scope or personnel change.

A RACI matrix is not a substitute for a work plan. It does not specify dates, resources, quality standards, or dependencies unless these are documented elsewhere. It is also not always appropriate to force every activity into a four-letter pattern. Some decisions require formal approval, independent assurance, or two-person controls because of financial, safety, privacy, or regulatory risk.

7. Delegation in Practice

Delegation is the transfer of responsibility for completing defined work, together with sufficient authority and resources, while the delegating manager retains an appropriate level of accountability for the overall result. Delegation develops capability and increases organisational capacity.

Delegation is not abandonment. A manager who says “you own it” but provides no context, authority, access, or feedback has not delegated effectively. Conversely, a manager who requires approval for every minor action has retained control while creating the appearance of delegation.

A practical delegation conversation should cover:

• the intended outcome and why it matters;
• scope, constraints, and quality standards;
• authority and decisions permitted;
• resources, budget, and access;
• milestones and reporting arrangements;
• risks and escalation triggers;
• support and coaching available; and
• the date and method of review.

Delegation can be calibrated. A manager may retain approval of a high-risk decision while allowing the employee to investigate options and implement routine actions. The level of autonomy should reflect competence, task complexity, consequence of error, and trust developed through evidence.

A useful distinction is between monitoring and micromanaging. Monitoring checks progress against agreed milestones and risks. Micromanaging replaces the delegate’s judgement with continuous unplanned intervention. The former supports accountability; the latter undermines it.

8. Accountability Mechanisms

Accountability works best as a system rather than a single performance meeting. Useful mechanisms include:

• clear objectives and deliverables;
• documented decision and action logs;
• milestone reviews;
• agreed performance indicators;
• peer review and quality assurance;
• risk registers and issue escalation;
• after-action reviews;
• transparent approval records; and
• individual development conversations.

Indicators should measure meaningful outcomes, not simply visible activity. For example, the number of meetings attended is usually weaker than evidence that a service met agreed response times and quality standards. Quantitative indicators can be combined with qualitative evidence, customer feedback, professional judgement, and contextual explanation.

Accountability mechanisms should also respect procedural fairness. People should know the standards, have access to relevant information, be able to explain constraints, and receive proportionate consequences. Confidentiality and data protection must be maintained when performance information includes personal or sensitive data.

Applied Case: Riverside Digital Service

The following is an illustrative case.

Background

Riverside College decides to introduce an online appointment system for student support services. The project involves student services, information technology, finance, data protection, and student representatives. The project has a twelve-week target and a limited budget.

Problem

After four weeks, progress is poor. The IT team says requirements are incomplete. Student services believes IT is responsible for deciding the workflow. Finance has been asked to approve several purchases without knowing the total budget. Student representatives are invited to meetings but do not know when their input is required. The project sponsor is receiving conflicting reports.

The underlying problem is not simply technical delay. Responsibility, authority, and decision rights are unclear. The team also lacks a clear balance between implementation, technical expertise, user advocacy, and quality checking.

Analysis

The project leader conducts a role and responsibility workshop. Using Belbin’s framework, the team identifies strong Specialist and Implementer contributions but insufficient Coordinator and Teamworker behaviours. Meetings focus on technical detail, while decisions and stakeholder communication remain weak.

A simplified RACI matrix is then developed:

The team agrees that the project manager coordinates the work and owns day-to-day delivery, while the sponsor retains accountability for the final launch decision. The IT lead receives authority over technical design within agreed standards. The data protection officer has an independent assurance role and cannot be pressured to approve an unacceptable privacy risk.

Approach and outcome

The project manager introduces a weekly milestone review, a decision log, and an escalation rule: any issue likely to affect the deadline, budget, privacy, or service quality must be raised within one working day. Student representatives participate in requirements workshops and user testing rather than every technical meeting.

The project launches two weeks later than originally planned, but within the revised budget and with documented privacy controls. Users report that the system is understandable, and staff know who can approve future changes.

Learning points

1. Delays can be symptoms of structural ambiguity rather than poor individual effort.
2. RACI is most useful when linked to actual decision authority.
3. Stakeholder involvement should be purposeful and proportionate.
4. Independent assurance roles should not be weakened by delivery pressure.
5. Accountability includes transparent revision of plans when assumptions change.

Challenges, Ethics and Contemporary Practice

Role stereotyping

Role models can unintentionally reinforce assumptions about gender, culture, age, disability, or professional background. Leaders should assess observable contribution and provide equal opportunities to demonstrate capability. A quiet communication style should not automatically be interpreted as lack of leadership or teamwork.

Power and psychological safety

A formally consulted person may be unable to speak honestly if the team leader controls rewards or access to employment. Leaders should create conditions in which dissent, uncertainty, and bad news can be raised without retaliation. Consultation is not genuine if disagreement is punished.

Matrix conflict

In matrix teams, an employee may receive priorities from both a functional manager and a project manager. The organisation should define priority-setting rules, resolve conflicting objectives promptly, and avoid holding employees accountable to incompatible demands.

Technology and AI

Collaboration platforms can support shared responsibility matrices, workflow approvals, version control, action tracking, and audit trails. AI tools may help summarise meetings, identify unassigned actions, or detect repeated delays. However, automated suggestions should not determine accountability without human review. Data used in performance monitoring may be inaccurate, biased, or excessive. Organisations should explain monitoring practices, protect personal data, check access rights, and retain human responsibility for consequential decisions.

Contemporary distributed work

Remote and hybrid teams require especially explicit agreements about availability, communication channels, documentation, handovers, and response expectations. Visibility of online activity is not a valid substitute for meaningful outcomes. Teams should judge performance by agreed deliverables and quality, while recognising that caring responsibilities, disability, time zones, and connectivity may affect working patterns.

Best-Practice Checklist

Before finalising team arrangements, leaders should ask:

• Is the purpose expressed as a small number of meaningful outcomes?
• Does every major outcome have one accountable owner?
• Do responsible people possess the authority and resources required?
• Are decision rights and escalation thresholds documented?
• Does the team have sufficient coverage of innovation, coordination, implementation, quality, expertise, and relationships?
• Are consultation and information requirements proportionate?
• Have risks of role stereotyping and unfair monitoring been considered?
• Are milestones, evidence, feedback, and learning built into the accountability process?
• Will the arrangements be reviewed when circumstances change?

Chapter Summary

Team effectiveness depends on more than individual competence. It requires a structure that coordinates interdependent work, roles that clarify expected contributions, authority that matches responsibility, and accountability that is fair, evidence-based, and connected to learning. Belbin’s nine team roles provide a language for discussing behavioural contributions, but they should not be used as fixed labels or selection rules. The RACI matrix clarifies who is Responsible, Accountable, Consulted, and Informed for important activities, although it must be connected to real authority, resources, standards, and decision processes. Delegation transfers defined work and authority while retaining appropriate managerial oversight; it is not abdication or micromanagement. Decision rights and escalation routes are especially important in matrix, cross-functional, hybrid, and high-risk environments. Effective accountability combines clear expectations, monitoring, documentation, feedback, procedural fairness, and improvement. Ethical practice requires attention to power, inclusion, privacy, psychological safety, and the limits of automated monitoring.

Key Terms

Belbin team role: A pattern of behavioural contribution that supports team performance.

Accountability: The obligation to explain decisions and results to an authorised person or stakeholder.

Authority: Legitimate power to make decisions, allocate resources, or direct work.

Responsibility: The obligation to perform work or produce an agreed output.

Delegation: The transfer of defined work and sufficient authority while appropriate oversight remains.

Decision rights: Agreed permissions and obligations concerning who may make particular decisions.

RACI: A matrix identifying Responsible, Accountable, Consulted, and Informed roles.

Responsible: The person or group that performs or coordinates completion of an activity.

Accountable: The role that owns the final result and accepts or approves it.

Consulted: A person whose relevant input is obtained before completion or decision.

Informed: A person who receives relevant information about progress or outcomes.

Team structure: The formal arrangement of work, reporting, authority, and coordination.

Role ambiguity: Uncertainty about expected duties, authority, or performance standards.

Role conflict: A condition in which different authorities or expectations are incompatible.

Decision owner: The person authorised to make or approve a specified decision.

Escalation: Moving an issue to a higher or different authority when agreed thresholds are exceeded.

Psychological safety: A climate in which people can raise questions, concerns, and mistakes without fear of humiliation or retaliation.

Matrix team: A team in which members may have both functional and project or product reporting relationships.

After-action review: A structured reflection on what happened, why it happened, and what should change.

Review Questions

Short Answer Questions

1. Distinguish responsibility, authority, and accountability.
2. What is the purpose of a RACI matrix?
3. Name the nine Belbin team roles.
4. Why is delegation different from abdication?
5. Identify two risks of unclear decision rights.

Long Answer Questions

1. Explain how team structure influences coordination and accountability. Use examples from at least two types of structure.
2. Discuss the benefits and limitations of Belbin’s team-role model in professional teams.
3. Describe a systematic process for constructing and validating a RACI matrix.
4. Explain how a manager can delegate effectively while maintaining appropriate oversight.
5. Discuss the ethical requirements of performance monitoring and accountability in hybrid or remote teams.

Analytical / Application Questions

1. A project has three departments working toward one deadline. Each department believes another department owns final approval, while the project manager can coordinate but cannot authorise expenditure. Diagnose the structural problem and propose revised authority, decision rights, and RACI assignments.
2. A team contains strong idea generation and technical expertise but repeatedly misses deadlines and produces inconsistent quality. Use Belbin’s framework to analyse the likely gaps and recommend behavioural or structural interventions.
3. Design a mini-RACI matrix for implementing a new workplace training programme. Include at least five activities and four roles, then justify your allocation of accountability, consultation, and information rights.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes accountability from responsibility?

A. Accountability concerns explaining results, while responsibility concerns performing agreed work.

B. Accountability is informal, while responsibility always requires legal authority.

C. Accountability means having no consequences, while responsibility means accepting blame.

D. Accountability belongs only to senior managers, while responsibility belongs only to employees.

Correct Answer: A. Accountability concerns explaining results, while responsibility concerns performing agreed work.

Question 2

Which Belbin role primarily contributes by checking detail, quality, and deadlines?

A. Plant

B. Completer Finisher

C. Resource Investigator

D. Teamworker

Correct Answer: B. Completer Finisher

Question 3

In a RACI matrix, who normally owns the final outcome and approves or accepts it?

A. Responsible

B. Accountable

C. Consulted

D. Informed

Correct Answer: B. Accountable

Question 4

Which is the strongest example of effective delegation?

A. Assigning a task without explaining its purpose or deadline

B. Retaining every decision while telling the employee to take ownership

C. Transferring defined work with suitable authority, resources, standards, and review points

D. Giving complete control and refusing to provide support or escalation routes

Correct Answer: C. Transferring defined work with suitable authority, resources, standards, and review points

Question 5

What is a major risk when responsibility is assigned without authority?

A. The employee may have insufficient control over the expected result.

B. The team will always become more innovative.

C. Consultation will automatically become unnecessary.

D. The organisation will have too many decision rights.

Correct Answer: A. The employee may have insufficient control over the expected result.

Question 6

Which Belbin role is most associated with generating creative and unconventional ideas?

A. Implementer

B. Monitor Evaluator

C. Plant

D. Coordinator

Correct Answer: C. Plant

Question 7

What should normally be checked after a draft RACI matrix is created?

A. That every person is both Accountable and Informed for every activity

B. That important activities have clear ownership and responsible people have workable authority

C. That consultation includes every employee regardless of relevance

D. That the matrix replaces the project plan and risk register

Correct Answer: B. That important activities have clear ownership and responsible people have workable authority

Question 8

Which practice best supports fair accountability?

A. Judging performance only by visible online activity

B. Changing standards after results are known

C. Providing clear standards, relevant evidence, opportunity to explain, and proportionate consequences

D. Holding people accountable for outcomes they cannot influence

Correct Answer: C. Providing clear standards, relevant evidence, opportunity to explain, and proportionate consequences

Question 9

In a matrix team, what is a common source of role conflict?

A. Members have no specialist knowledge at all

B. Functional and project managers issue incompatible priorities

C. All decisions are documented in advance

D. The team has a clear escalation route

Correct Answer: B. Functional and project managers issue incompatible priorities

Question 10

Why should AI-generated accountability or performance suggestions be reviewed by humans?

A. AI systems can be inaccurate or biased, and consequential decisions require human judgement.

B. AI tools are unable to store any information.

C. Human review makes data protection irrelevant.

D. Automated tools always produce legally binding decisions.

Correct Answer: A. AI systems can be inaccurate or biased, and consequential decisions require human judgement.