Roles, Norms and the Team Charter
4 min read
Lesson objectives
- Define a role through responsibility, output and dependencies rather than job title alone.
- Write working norms as observable behaviors rather than general slogans.
- Build a concise team charter combining purpose, goals, roles, responsibilities and ways of working, with revision when conditions change.
Clarity Does Not Mean More Job Titles
Every member may know their job title yet still be unclear about who prepares a decision, who supplies inputs, or who receives the output. We therefore define a role operationally through three questions: What responsibility or decision does it carry? What output is expected? What does the role depend on, and who depends on it? These questions reveal overlap and gaps better than titles alone.
Norms are agreements about how team members work together. “We respect each other” is a useful value but not yet an operational norm. A more observable norm is: “We critique the idea rather than the person; when we disagree, we state the evidence or assumption and give the proposer a chance to respond before deciding.” Observable behavior lets the team reinforce the norm without turning it into a moral label about individuals.
A Team Charter Turns Expectations Into a Reviewable Agreement
A recent reference describes a team charter as a shared document covering purpose, goals, member roles and responsibilities, and how members will work together. Its value is not the document format itself but the conversation that exposes assumptions before they become problems. The charter may need revision as membership, responsibilities or the nature of work changes.
A useful charter does not need to be long. A short-lived team may use one page covering purpose, two or three goals, key roles and decision rights, dependencies and handoffs, communication and meeting norms, how disagreement and escalation work, and when the charter will be reviewed. It should not invent authority the team does not have or reproduce organizational policies in a way that conflicts with the source policy.
Roles can change without titles changing. If a data specialist is absent for two weeks, “we will help each other” is not enough. The team should state who covers which decisions, what cannot be delegated, and what delay triggers escalation. CCL’s team-effectiveness guidance emphasizes defined responsibilities and understanding workflow, linking the charter back to alignment from Lesson 1.
Lesson summary
Team clarity comes from responsibilities, outputs, dependencies and observable working norms. A team charter combines purpose, goals, roles and ways of working in a reviewable agreement, but it does not grant authority beyond the team’s actual remit.