HKSM

Ground rules are team-agreed expectations for behavior, communication, and work practices. They guide how the team collaborates, makes decisions, and handles conflict throughout the project.

Definition

Ground rules are team-agreed expectations for behavior, communication, and work practices. They guide how the team collaborates, makes decisions, and handles conflict throughout the project.

Key Points

• Co-created with the team to set clear expectations for how people work together.
• Kept visible and accessible, and reviewed regularly as the team evolves.
• Framed as specific, observable behaviors to reduce ambiguity.
• Aligned with organizational policies, culture, and the project context.
• Applied consistently, with agreed ways to address breaches.
• Integrated into the team charter and onboarding for new members.

Purpose

• Build shared understanding of acceptable behavior and communication patterns.
• Reduce friction, prevent conflicts, and improve meeting and collaboration quality.
• Create psychological safety by making expectations transparent and fair.
• Speed up decision-making and teamwork by clarifying norms upfront.

Facilitation Steps

• Set the context: explain why ground rules matter and how they will be used.
• Gather inputs: consider culture, time zones, tools, and organizational policies.
• Co-create: facilitate a brainstorm where team members propose behaviors and norms.
• Cluster and refine: combine similar ideas and turn them into concise, actionable statements.
• Validate fit: check alignment with company policies and stakeholder expectations.
• Define enforcement: agree how to remind, escalate, and resolve breaches respectfully.
• Gain commitment: ask for explicit agreement from all members, including remote participants.
• Document and publish: post the rules where the team works, both physical and virtual spaces.
• Embed in routines: reference rules in meetings, retrospectives, and onboarding.
• Review and adapt: schedule periodic checks to update rules as the project changes.

Inputs Needed

• Team charter, working agreements, and organizational policies.
• Stakeholder and team expectations, including cultural norms and values.
• Team composition, roles, time zones, and availability constraints.
• Communication and collaboration tools to be used by the team.
• Lessons learned or retrospective insights from past projects.

Outputs Produced

• Documented ground rules or working agreements accessible to the team.
• Defined reminders and escalation path for handling breaches.
• Updates to the team charter and communication plan, if needed.
• Onboarding guidance for new team members that includes the rules.
• Change log entries when rules are added, removed, or revised.

Tips

• Keep the list short, clear, and behavior-based to improve adoption.
• Phrase rules positively, focusing on what to do rather than what not to do.
• Use check-ins at the start of meetings to reinforce key rules.
• Model the behaviors yourself to set the tone and encourage compliance.
• Invite feedback from quiet voices to ensure inclusivity and buy-in.
• Treat ground rules as living agreements and update them when context changes.

Example

A newly formed, distributed team agrees on rules such as response time targets, meeting etiquette, camera expectations, decision-making methods, and how to raise concerns. The rules are posted in the team workspace and reviewed monthly. As a result, interruptions decrease, meetings end on time, and conflicts are addressed early using the agreed approach.

Pitfalls

• Imposing rules top-down without team input, reducing buy-in.
• Writing vague or subjective rules that are hard to observe or enforce.
• Creating too many rules, making them hard to remember and follow.
• Inconsistent reinforcement, which undermines credibility and fairness.
• Ignoring cultural and time zone differences that affect feasibility.
• Failing to revisit rules as the team or context changes.

PMP Example Question

During early team formation, meetings frequently run over time due to side conversations and interruptions. What should the project manager do first?

1. Ask the sponsor to mandate stricter meeting behavior for the team.
2. Privately warn individuals who interrupt that future incidents will be escalated.
3. Facilitate the team to co-create and agree on ground rules for meetings and collaboration.
4. Document the issue in the risk register and monitor it in future meetings.

Correct Answer: C — Facilitate the team to co-create and agree on ground rules for meetings and collaboration.

Explanation: Establishing team-agreed norms early addresses the root cause and builds buy-in. It is preferable to escalation or unilateral warnings at this stage.