MBA Learning Team Charter Template (Norms, Roles, Conflict)

Learning Team Charter: [Team name, programme and term]

A charter for an MBA study group or assigned learning team: purpose and goals, working norms, roles, meeting cadence, decision rules, a workload ledger, a conflict and escalation process, a psychological safety agreement and a review schedule. It is for teams of four to seven students who will share cases, problem sets and graded projects for a term or a whole core year. Teams that agree these points in week one spend less time later on avoidable friction, and have a fair process ready when something does go wrong. Source basis: team development stages (Tuckman 1965; Tuckman and Jensen 1977), team psychological safety (Edmondson 1999), the conditions for team effectiveness (Hackman 2002), and research on social loafing and team conflict, written in our own words. The worked example uses a fictional team. Replace every [bracketed] value and every row marked Example.

Document control

Approvals

Why a charter works

MBA learning teams are usually assigned rather than chosen, and they are deliberately mixed by industry, function, nationality and quantitative background. That mix is the point: the accountant explains deferred revenue, the engineer builds the model, the consultant structures the slide deck, and everyone learns faster than alone. The same mix also brings different assumptions about how hard to work, how direct to be, when a draft is "done" and who decides. Most team conflict in a core year is not about personality. It is about unstated expectations colliding under deadline pressure.

Three bodies of research explain why writing the expectations down early helps.

Teams move through stages. Tuckman (1965), reviewing studies of small groups, described a developmental sequence whose stages he labelled forming, storming, norming and performing; Tuckman and Jensen (1977) added adjourning. The stages are a description of tendencies, not a fixed timetable, and Gersick (1988) showed that project teams often work in a long first phase and change approach sharply around the midpoint of their time. The practical lesson is that the "storming" disagreements about goals and norms will happen anyway. A charter brings them forward to week one, when the stakes are low and nobody is yet tired or resentful, and it gives the team a planned midpoint review.

Learning needs psychological safety. Edmondson (1999) studied work teams in a manufacturing company and found that team psychological safety, a shared belief that the team is safe for interpersonal risk taking, was associated with learning behaviour such as asking questions, seeking feedback, admitting errors and discussing problems; learning behaviour in turn was associated with team performance. In an MBA team the learning behaviours are exactly what you need: the student who does not understand the WACC calculation must feel able to say so before the problem set is due, not after the grade.

Effective teams have the right conditions. Hackman (2002) argued that a leader's style matters less than whether the team has five conditions: it is a real team (clear membership, interdependent work, some stability), it has a compelling direction, an enabling structure (task design, size, norms of conduct), a supportive context (resources, information, rewards that recognise team work) and expert coaching available at the right times. A charter is how a self-managing student team builds the second and third conditions for itself.

Two further findings shape specific sections. Social loafing, the tendency to exert less effort when individual contributions are hard to identify (Latané, Williams and Harkins 1979), is why the charter makes contributions visible in a workload ledger. Research on intragroup conflict distinguishes task conflict (disagreement about the work) from relationship conflict (personal friction); relationship conflict is consistently harmful, and task conflict is not reliably helpful either (Jehn 1995; De Dreu and Weingart 2003). The charter therefore separates "how we argue about the work" from "how we raise a problem with a person".

1. Purpose and context

Collaboration rules differ by course and by assignment, and many schools now publish course-level rules on the use of generative AI. As of October 2026 these rules vary widely between programmes and even between instructors in the same programme, so record each course's current rule here and check it again before each deliverable; see mba/mba-ai-use-policy-check for a worksheet.

2. Members, strengths and learning goals

Constraints worth stating openly: caring responsibilities, recruiting travel weeks, religious observances, a part-time job, a disability adjustment the member chooses to share, or a commute. Stating them in week one prevents later assumptions that someone is "not committed".

3. Team goals

Disagreement about ambition is common and legitimate. Some members want the top grade in every course; others are prioritising recruiting or a specific concentration. Agree the level of quality the team will aim for on each graded deliverable (for example "strong pass on problem sets, top-quality effort on the strategy project") so that nobody reads a different priority as laziness or perfectionism.

4. Working norms

A useful test for each norm: if a member broke it, would everyone agree that it had been broken? If not, rewrite it.

5. Roles

A deliverable lead is not the person who does most of the work. The lead plans the split, integrates the pieces, checks consistency (numbers, terminology, formatting) and submits. Use business/raci if a deliverable has many contributors.

6. Meeting cadence and format

Default agenda for a 90-minute session:

1. Check-in and agenda (5 minutes).
2. Each member's headline answer in one minute, without interruption (10 minutes).
3. Disagreements: list them, then resolve the largest first (40 minutes).
4. Decisions, owners and dates read back by the note-taker (10 minutes).
5. Open questions to bring to class or office hours (10 minutes).
6. Process check: one thing that worked, one thing to change (5 minutes).
7. Buffer (10 minutes).

Taking turns for the headline answer before any discussion protects independent thinking: groups that discuss before everyone has stated a view tend to converge on whoever speaks first.

7. Decision rules

"Consensus" here means that every member can support the decision, not that every member thinks it is the best option. Ask explicitly: "Can everyone live with this and defend it in class?" Silence is not agreement.

8. Workload and contribution ledger

Planned versus actual hours make contributions visible, which reduces social loafing and also protects the member who is quietly doing more than a fair share. Agree a trigger: for example, a member whose share of total hours is more than 5 percentage points away from an equal share over two weeks is raised at the weekly check-in as a planning question, not as an accusation. Hours are an imperfect measure (a skilled modeller may need fewer hours), so the discussion is about whether the split still feels fair.

Excel set-up: share in column D is =C2/SUM($C$2:$C$6); the flag is =IF(ABS(D2-1/COUNT($C$2:$C$6))>0.05,"review","ok").

9. Conflict and escalation process

Separate the two kinds of conflict. Task conflict ("I think the discount rate is too low") is handled in the meeting with evidence and the decision rules of Section 7. Relationship conflict ("you keep dismissing my points") is handled privately first, with specific behaviour and its impact, not with labels about personality.

Some issues bypass the steps entirely: suspected academic integrity breaches, harassment or discrimination, threats to anyone's safety or wellbeing. Go to the school's designated office or the instructor directly, using the process your programme publishes.

10. Psychological safety agreement

We agree to the following behaviours, which make it easier for every member to ask, admit and challenge:

• Anyone can say "I do not understand this yet" without explanation or judgement, and the team treats it as useful.
• We critique ideas and analysis, not people. We say "this assumption looks high" rather than "your model is wrong".
• The person who finds a mistake in their own work and says so is thanked.
• We ask the quietest member for their view before closing a discussion.
• We do not share a teammate's mistakes, struggles or personal information outside the team.
• Before every graded deliverable we run a two-minute round: "What part of this are you least sure about?"
• Disagreement with the facilitator or with a majority view is expected, especially from the devil's advocate.

Edmondson's construct is about the team climate, not about being comfortable or lowering standards. A psychologically safe team can be highly demanding; members simply do not fear humiliation or punishment for raising questions, concerns or errors.

11. Review checkpoints

12. Filled example

Example. Learning Team 4 at a fictional programme ("School A") has five members: Hana (supply-chain analyst), Kwame (army logistics officer), Lucia (marketing at a consumer-goods firm), Mateo (software engineer) and Priya (audit associate). Kwame is in a time zone eight hours behind for the first two weeks while finishing a posting.

The cadence of two 90-minute sessions and one 30-minute check-in a week amounts to 3.5 hours of meetings per member per week, or 42 hours over a 12-week term. The team agreed this was the maximum and that sessions would end on time.

Workload ledger after week 4 (planned 14 hours each, 70 in total):

At the week-4 check-in the facilitator raised Kwame's share as a planning question. Kwame explained that the time-zone gap had kept him out of two work sessions; the team moved one session to a time that suited both time zones and gave him the lead on the next case write-up, where asynchronous work suits his situation. The flag was cleared at the midpoint review. Nobody waited for the end-of-term peer evaluation to raise it.

13. Change log

Common mistakes

1. Writing values instead of behaviours ("we respect each other"), so nobody can tell when a norm is broken.
2. Letting one member write the charter alone; others sign without owning it.
3. Never reviewing the charter, so it describes the team of week one, not the team of week eight.
4. Making the most experienced member the permanent lead on every deliverable, which blocks everyone else's learning goals and overloads that member.
5. Dividing a deliverable into pieces that nobody integrates, producing a report with four styles and inconsistent numbers.
6. Treating silence in a meeting as agreement.
7. Avoiding all disagreement to keep the peace; unresolved task issues return later as relationship conflict.
8. Raising contribution problems for the first time in the final peer evaluation.
9. Ignoring course-specific collaboration and AI rules, or assuming one course's rule applies to all.
10. Letting meetings rebuild the analysis together instead of reviewing work prepared in advance.

Self-test

1. Name the five stages in Tuckman's sequence as extended by Tuckman and Jensen (1977).
2. What did Edmondson (1999) find about the relationship between team psychological safety and learning behaviour?
3. List Hackman's (2002) five conditions for team effectiveness.
4. Why does a workload ledger reduce social loafing?
5. What is the difference between task conflict and relationship conflict, and how does this charter handle each?
6. Rewrite the norm "we are responsive" as an observable behaviour.
7. In the filled example, why was Kwame's share flagged, and what is the computation behind the flag?
8. Which issues should bypass the team's escalation steps?

My notes and next steps

What I will do differently in this team: [ ]. One norm I find hard to keep: [ ]. Next checkpoint date: YYYY-MM-DD.

Sources and further reading

• Tuckman, B. W. (1965). Developmental sequence in small groups. Psychological Bulletin, 63(6), 384-399.
• Tuckman, B. W., and Jensen, M. A. C. (1977). Stages of small-group development revisited. Group and Organization Studies, 2(4), 419-427.
• Gersick, C. J. G. (1988). Time and transition in work teams: toward a new model of group development. Academy of Management Journal, 31(1), 9-41.
• Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350-383.
• Hackman, J. R. (2002). Leading Teams: Setting the Stage for Great Performances. Harvard Business School Press.
• Latané, B., Williams, K., and Harkins, S. (1979). Many hands make light the work: the causes and consequences of social loafing. Journal of Personality and Social Psychology, 37(6), 822-832.
• Jehn, K. A. (1995). A multimethod examination of the benefits and detriments of intragroup conflict. Administrative Science Quarterly, 40(2), 256-282.
• De Dreu, C. K. W., and Weingart, L. R. (2003). Task versus relationship conflict, team performance, and team member satisfaction: a meta-analysis. Journal of Applied Psychology, 88(4), 741-749.
• Further reading (by name only): Edmondson, The Fearless Organization (2018); Robbins and Judge, Organizational Behavior; OpenStax, Principles of Management (CC BY-NC-SA 4.0), chapter on teamwork.

Answer key

1. Forming, storming, norming, performing, adjourning.
2. Team psychological safety was associated with learning behaviour (asking for help, seeking feedback, discussing errors), and learning behaviour was associated with team performance.
3. A real team, a compelling direction, an enabling structure, a supportive context and expert coaching.
4. Social loafing increases when individual contributions cannot be identified; the ledger makes each member's contribution visible every week.
5. Task conflict is disagreement about the work (assumptions, methods, recommendations); relationship conflict is personal friction. Task conflict is resolved in meetings with evidence and the decision rules; relationship conflict is raised privately first with specific behaviour and impact, then through the escalation steps.
6. For example: "We reply to team messages within 12 hours on weekdays."
7. His actual hours were 9 of 70, a share of 12.9%, which is 7.1 percentage points below an equal share of 20%, beyond the agreed 5-point trigger. Excel: =9/70 and =ABS(9/70-1/5)>0.05.
8. Suspected academic integrity breaches, harassment or discrimination, and threats to safety or wellbeing.

Revision history

Standard and licence note

Based on published research on team development (Tuckman 1965; Tuckman and Jensen 1977; Gersick 1988), team psychological safety (Edmondson 1999), team effectiveness conditions (Hackman 2002), social loafing and intragroup conflict, summarised in original wording. The Situation-Behavior-Impact model referenced in the conflict process is a trademark of the Center for Creative Leadership and is named only to identify the method. This template is original text written for this collection; it is not a school's official team contract and is not affiliated with or endorsed by any business school or publisher. Check your programme's current rules on teamwork, peer evaluation, collaboration and AI use before relying on it. All people and teams in the example are fictional. Template licence: MIT.