Opening the book…
A team charter connects the problem, purpose, scope, goals, authority, resources, and expected results. It helps members begin with a shared understanding and provides a reference when priorities change.
Effective teams include people who know the work and represent affected functions and shifts. Ground rules support respectful participation, while clear decision authority prevents confusion about approvals. Realistic schedules and specific management commitments make the assignment possible.
Teams may experience changing patterns of orientation, disagreement, coordination, performance, and closure. Leaders can respond by clarifying expectations and providing the support needed at each point. Action and decision logs make responsibilities visible. Measures show whether completed tasks produced a useful result.
Sustained improvement requires continued participation, fair recognition, and a planned transfer to an accountable process owner. Closing a project should leave the organization able to maintain and review the work.
Checking that an agreed action was completed is separate from checking that it achieved its purpose.
Key Terms
|
Team charter |
Purpose |
Scope |
|
Goal |
Deliverables |
Scope creep |
|
Functional representation |
Diversity |
Ground rules |
|
Psychological safety |
Decision authority |
Decision rule |
|
Escalation path |
Work plan |
Milestone |
|
Agenda |
Resources |
Sponsor |
|
Resource commitment |
Forming |
Storming |
|
Norming |
Performing |
Adjourning |
|
Action log |
Decision log |
Accountability |
|
Outcome measure |
Process measure |
Balancing measure |
|
Recognition |
Handoff |
Process owner |
|
Sustainment plan |
|
|
Review Questions
1. What information belongs in a team charter, and how can the team use it after the first meeting?
2. Explain the difference between a purpose, a goal, and a deliverable.
3. Why should a charter state what is outside the project’s scope?
4. How can a team include knowledge from people who cannot attend every meeting?
5. What is the difference between ground rules and decision authority?
6. How do dependencies affect a project schedule?
7. What specific commitments should a team request from its sponsor?
8. Describe the five stages in the model developed by Tuckman and extended with Jensen. Why should it be used flexibly?
9. How do action logs and decision logs support accountability in different ways?
10. Distinguish outcome, process, and balancing measures using the freezer-alarm example. Why does a zero denominator prevent calculation of a performance percentage?
11. What should be included in a handoff and sustainment plan, and why should the process owner be involved early?
Apply Your Understanding
1. A label-review team receives the assignment “reduce errors” but has no defined product group, baseline, deadline, or approving authority. Draft a brief charter outline that identifies the missing decisions. State what information you would collect before choosing a numerical goal.
2. A sample-receiving team has six day-shift members and no evening-shift members. Evening staff report that revised paperwork is difficult to use when deliveries arrive together. Propose a membership and meeting plan that gives evening staff meaningful input while maintaining routine work coverage.
3. A maintenance improvement team has an approved six-week schedule. Its technical specialist becomes unavailable for two weeks, and equipment testing depends on that specialist’s review. Explain how the team should revise its plan and what decision it should request from the sponsor.
This page titled 9.12: Chapter Summary was last modified on Thu, 05 Nov 2026 10:56:23 GMT and is shared under a CC BY-SA 4.0 license and was authored, remixed, and/or curated by Emalee MacKenzie.
The book could not be loaded just now.