TEAM CHARTER
Internal Governance & Mutual Accountability Contract
Team Charter Overview
A team charter defines how your group will collaborate to deliver high-quality work for your project.
It clarifies expectations, ownership, and communication norms before pressure builds.
Teams that make these commitments explicit early tend to coordinate faster and produce stronger deliverables.
Mission & Standards
⚖ Research Foundation
Aaron et al. (2014); Hillier & Dunn-Jensen (2013): Most student groups never become teams because they skip the deliberate "forming" work. Research on team charters in business education shows that completing a charter is the "necessary first step" to evolve from a loosely connected group — where members pursue mostly individual goals — into a team with a shared identity and mutual accountability.
The written mission statement creates a psychological contract: an implicit set of mutual expectations about effort, quality, and participation that all members carry. Unlike a legal contract, this contract lives in perception — but its violation causes real damage: disillusionment, reduced effort, and resentment that compounds across the project timeline. When that contract is made explicit and co-signed, it is far harder to violate without social consequence.
📘 Concept + Example
What is a Psychological Contract? It is the set of unspoken beliefs team members hold about what they owe each other and what they can expect in return. A Firm Mission Statement externalizes this contract into a single sentence that answers: "Why does our work together matter, and what standard will we hold ourselves to?"
❌ Weak Mission "We will work hard and do our best on this project." — Aspirational but unverifiable. No member can be held to this because "doing your best" means different things to different people.
✅ Strong Mission "Our team will deliver a polished final deliverable for our client that satisfies the agreed quality standard, synthesized under one professional voice, with every citation verified by a named team member before submission." — Specific, outcome-oriented, anchored to the client and quality standard.
✅ Best Practice Guidance
How to write a mission statement that actually governs:
- 1. Name the client and the deliverable. Reference your client and team deliverable explicitly. Vague missions are abandoned; specific ones are remembered when pressure is highest.
- 2. State a quality standard, not just an effort standard. "Reasonable efforts" is the professional standard you are applying to your client — use the same bar for yourselves. Ask: would a supervising partner be satisfied with this output?
- 3. Include one behavioral commitment. The best mission statements contain a "how we operate" clause — e.g., "...with every contribution reviewed by at least one peer before submission." This converts aspiration into protocol.
- 4. Write it together, out loud — do not let one person draft and circulate. The friction of negotiating the language IS the pedagogy. Disagreement in this moment is a preview of the real teamwork challenges ahead, and resolving it now builds the trust you will need in Week 5.
0 / ~75 words
Roles & Ownership
⚖ Research Foundation
Simms & Nichols (2014); Katzenbach & Smith (1993): "Social loafing" — people reducing effort when working in groups — is not a character flaw. It is a structural problem. When individual contributions are invisible and effort is unattributable, people rationally reduce their input. This effect, first documented by Ringelmann in rope-pulling experiments, scales with group size.
The structural fix is named, visible, strengths-based roles: assigning each person a domain of ownership they cannot disclaim raises identifiability, sets differentiated expectations, and transforms a group (where outputs are the sum of separate parts) into a team (where the whole depends on how well roles interlock). Katzenbach & Smith's landmark definition of a team requires complementary skills and mutual accountability — not just shared effort.
📘 Concept + Example
Group vs. Team — the critical distinction: In a group, "you do your part and I'll do mine" is sufficient. Four people write four sections and staple them together. In a team, the tasks are non-separable: my section cannot succeed unless your section is complete and aligned, because the client is reading one document, not four memos.
Group Model ❌
Researcher finds sources → sends to others → each person writes their section → PM staples the night before deadline. Reads like four different authors; logical gaps are invisible until graded.
Team Model ✅
Research Coordinator curates sources against a brief set by the PM. Lead Editor synthesizes against a shared framework. Technical Lead packages only after the Editor has signed off. Each role only works if the others deliver.
Use the Role Explorer (Browse All Roles →) to understand the full scope, accountability, and risk profile of each available role before making your selections.
✅ Best Practice Guidance
How to assign strengths-based roles that will hold:
- 1. Use your Strengths Inventory data — do not volunteer based on seniority or social comfort. The person with the strongest executing-strength profile should manage the timeline, not whoever talks the most. Mismatched roles are the single biggest source of preventable team friction.
- 2. Define what each role actually owns. For each role, complete the sentence: "This person is the last one who touches [X] before it goes to the partner." If you cannot complete that sentence, the role is not defined — it is just a label.
- 3. Distinguish authority from task. The Lead Editor has authority to require revisions from anyone. The Research Coordinator has authority to reject unverified sources. That authority must be agreed to explicitly in this section, or the role is hollow when the pressure is on.
- 4. Name the handoff points. Specify when and in what format each person delivers their work to the next. Vague handoffs — "when it's ready" — are where teams revert to groups. Concrete handoffs: "Section 2 draft to Lead Editor by Thursday 5PM in the [FINAL] Google Drive folder."
Firm Persona
Not sure which role fits you best? Try the Firm Persona Assessment for a quick recommendation before assigning roles.
Required Role Assignment
Assign exactly one Project Manager in the Roles & Ownership section. That assigned Project Manager is the person who submits the final charter deliverable to Canvas.
| Counsel Member (Name/Contact) | Primary Strength | Functional Firm Role |
|---|
Operating Norms
⚖ Research Foundation
Hunsaker et al. (2011); Andrade et al. (2023): Systematic reviews of team failures in higher education find that teams most often collapse not because members dislike each other, but because they never built the coordination infrastructure that makes collaboration mechanically possible. Response latency ambiguity (no one agreed how fast to reply), document chaos (multiple "final" versions floating simultaneously), and meeting drift (no agenda, no decision log) are engineering problems, not personality problems — and they have engineering solutions.
This section mirrors the quality standard you are designing for your client. Your client must demonstrate "reasonable efforts" to protect sensitive information. If you cannot design governance infrastructure for your own four-person firm, you are not yet ready to design it for a client company with dozens of employees and multiple external relationships.
📘 Concept + Example
The four operational decisions every team must make explicitly: Leaving any of these implicit guarantees a coordination failure before Week 3.
Where do binding task assignments live? Not everywhere. Example: "All task assignments in the team Slack #tspp-work channel. Personal texts carry no obligation."
How fast must you acknowledge a direct question? Example: "Direct @mentions acknowledged within 6 hours weekdays; 12 hours weekends."
When does the firm meet synchronously? Example: "Every Thursday 7–8 PM via Zoom. Excused absence requires 24h advance notice to the PM."
Where is the one authoritative project draft? Example: "Google Drive [link]. Only the Lead Editor may push to the FINAL folder. All other edits stay in Working Drafts."
✅ Best Practice Guidance
How to set operating norms you will actually keep:
- 1. Calibrate to the hardest constraint, not the ideal. If one member works nights, your "respond within 6 hours" rule must still work for them. Set the norm based on the person with the most constrained schedule — that is the norm everyone can honor without resentment.
- 2. Make norms testable. "We will communicate regularly" is unenforceable. "Direct @mentions acknowledged within 6 hours" is testable. Only testable norms can feed the escalation ladder in Section 05 — if you can't point to a specific missed norm, you have no grounds for escalation.
- 3. Separate the tool from the norm. Slack is a tool; "acknowledged within 6 hours" is the norm. If the team switches tools mid-project, the norm survives the change. Don't write norms that only work inside one app.
- 4. Designate a Document Custodian by name, not by role. Name the specific person who holds the "ground truth" draft. Document control failures — where members simultaneously edit different versions — cause more synthesis disasters than any content disagreement. This is preventable with one clear rule.
Synthesis & AI
⚖ Research Foundation
Smith (1994); Hillier & Dunn-Jensen (2013): Smith's landmark research on team task structure distinguishes additive tasks — where individual contributions can be cleanly summed — from non-separable tasks, where the quality of the whole depends entirely on how well the pieces interconnect. A team deliverable is non-separable by design.
If your Stage 2 Inventory identifies a high-priority client asset but your Stage 4 Mitigation section contains no specific protocol for it, the plan has failed — even if both sections are individually well-written. Synthesis is not copy-editing; it is structural alignment across the entire document. Teams that skip this planning step produce work that reads like four attorneys who have never spoken to each other.
📘 Concept + Example
Coordinated vs. Synthesized work — what each looks like:
Coordinated ❌
Each member writes their section independently, PM combines the night before the deadline. Result: four different voices, inconsistent fact references, and logical gaps between sections that the professor finds before the client does.
Synthesized ✅
Team agrees on a shared analytical framework and vocabulary before anyone writes. Lead Editor audits logical chains across sections. Devil's Advocate stress-tests every major claim. Final document reads as if one senior attorney wrote it.
AI Policy — example language to adapt:
"Generative AI may be used for initial brainstorming and outlining (disclosed in a footnote). AI may not draft final text submitted to the client. All AI-generated research must be traced to a primary source by the Research Coordinator before inclusion. Any undisclosed AI use is a violation of this charter and subject to the escalation ladder."
✅ Best Practice Guidance
How to build a synthesis workflow that survives the final week:
- 1. Establish a shared analytical template before anyone starts writing. The Inventory table structure, the Risk Matrix rating scale, the Mitigation measure format — agree on these in Week 2, or you will spend Week 6 reconciling incompatible structures instead of improving content.
- 2. Assign cross-section accountability explicitly. The Lead Editor is specifically responsible for verifying that every High-Risk item in Section 2 appears in Section 4 mitigation. This is a structural audit, not copyediting. Build it into the timeline as a separate deliverable.
- 3. Run a "logical chain" check before every stage submission. For each top 3 priority items, trace it: Inventory → Risk rating → Mitigation measure → Enforcement trigger. If the chain breaks anywhere, the deliverable is incomplete — regardless of how polished the individual sections are.
- 4. Write your AI policy for the worst-case scenario. Do not write it for how you intend to behave — write it for the moment when a member is under pressure at 2 AM and tempted to shortcut. The policy must be specific enough that a violation is objectively identifiable, not a matter of interpretation. Vague AI policies are not policies; they are alibis.
0 / ~60 words
0 / ~60 words
Escalation Protocol
⚖ Research Foundation
Andrade et al. (2023); Hillier & Dunn-Jensen (2013): Studies of student team dynamics in business education find that process conflict — disagreements about scheduling, workload distribution, and role boundaries — is the strongest negative predictor of perceived team effectiveness (β < −0.386, p < .001). The typical student response is binary: either immediately escalate to the instructor (damaging relationships and professional reputation) or suffer in silence until resentment compounds into a crisis.
A graduated escalation ladder solves this by creating legitimate, face-saving intermediate options that depersonalize conflict. It also mirrors how real law firms operate: internal performance management before client exposure or bar complaint. The goal is not to punish — it is to give the team the tools to self-govern before external intervention becomes necessary.
📘 Concept + Example
What does a real escalation look like at each level? Use these as a model when completing the ladder below.
Peer-to-Peer
Member misses an internal draft deadline with no notice. Affected peer sends a direct private message within 24h: "The Section 2 draft was due to me at 5 PM. I need it by tomorrow noon to stay on schedule — is there a problem I can help unblock?" Most issues resolve here.
PM Intervention
Pattern continues after a Level 01 conversation. PM convenes a 15-min check-in, names the specific missed charter commitment, asks the member to recommit to a revised deadline. PM writes a two-sentence note in the shared Drive: date, what was agreed.
TA Mediation
PM emails the TA with a brief factual summary (dates, missed commitments, Level 01–02 conversations). This is a request for structured mediation — not a complaint. The TA's role is to help the team find a workable path, not to adjudicate blame.
Professor / Partner Review
Internal governance has collapsed. Trigger example: a member has missed three or more internal deadlines, has not responded to a Level 02 PM intervention, and the project stage deadline is within 72 hours. Level 04 should be defined objectively — not as a feeling.
✅ Best Practice Guidance
How to write an escalation ladder that will actually work under pressure:
- 1. Define triggers as observable facts, not characterizations. "When a member misses two consecutive internal deadlines" is observable and undisputable. "When a member is not pulling their weight" is a characterization that every party will interpret differently. Objective triggers prevent the ladder from becoming a weapon in interpersonal conflict.
- 2. Specify the exact "ask" at each level — not just the label. Level 01 is not "talk to them." It is a specific communication, within a specific timeframe, with a specific request for a commitment. Write the ask in your response field below so there is no ambiguity about what Level 01 actually requires.
- 3. Make Level 04 narrow and high-threshold. The more specific and hard-to-trigger Level 04 is, the more legitimate the whole ladder feels. If Level 04 is vague or easy to reach, members will escalate prematurely and the deterrent effect collapses. Reserve it for genuine governance failure, not disagreement.
- 4. Agree on the documentation protocol right now. After any Level 02+ conversation, one person — the PM — writes a two-sentence note in the shared Drive: date, what was discussed, what was agreed. This log protects all members and provides objective evidence if peer evaluations are later disputed by any party.
VI. Execution & Professional Covenant
By signing below, we formally adopt this Charter as our binding internal governance protocol. We acknowledge that our individual standing in the firm and final peer evaluation metrics are tied to these standards.