3.3 Building Shared Understanding

Project Management Professional PMP

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Fundamentals

1.1 About the PMP Exam 1.2 What is a Project? 1.3 Project, Program & Portfolio Management 1.4 The Project Manager Role 1.5 PMBOK 7 Principles Overview 1.6 Performance Domains Overview 1.7 What Changed in the July 2026 PMP Exam

2 Chapter 2: People Domain Part 1

2.1 Managing Conflict 2.2 Leading a Team 2.3 Supporting Team Performance 2.4 Empowering Team Members 2.5 Training & Development 2.6 Building a Team 2.7 Removing Impediments

3 Chapter 3: People Domain Part 2

3.1 Negotiating Project Agreements 3.2 Collaborating with Stakeholders 3.3 Building Shared Understanding 3.4 Engaging Virtual Teams 3.5 Defining Team Ground Rules 3.6 Mentoring Stakeholders 3.7 Emotional Intelligence

4 Chapter 4: Process Domain - Planning

4.1 Determining Project Methodology 4.2 Integrating Project Planning 4.3 Planning & Managing Scope 4.4 Planning & Managing Schedule 4.5 Planning & Managing Budget 4.6 Planning & Managing Quality 4.7 Planning & Managing Resources 4.8 Planning & Managing Procurement

5 Chapter 5: Process Domain - Execution & Control

5.1 Executing with Urgency for Value 5.2 Managing Communications 5.3 Assessing & Managing Risks 5.4 Engaging Stakeholders 5.5 Managing Project Changes 5.6 Establishing Project Governance 5.7 Managing Project Issues 5.8 Managing Project Artifacts 5.9 Knowledge Transfer & Closure

6 Chapter 6: Business Environment Domain

6.1 Planning & Managing Compliance 6.2 Evaluating & Delivering Benefits 6.3 External Environment Changes 6.4 Supporting Organizational Change

7 Chapter 7: Agile & Hybrid Approaches

7.1 Agile Mindset & Values 7.2 Scrum Framework 7.3 Kanban & Lean 7.4 Extreme Programming (XP) 7.5 Hybrid Project Management 7.6 Agile Planning & Estimation 7.7 Agile Metrics & Tools

8 Chapter 8: Predictive (Waterfall) Approaches

8.1 Predictive Lifecycle 8.2 Scope Management 8.3 Schedule Management 8.4 Cost Management 8.5 Quality Management 8.6 Risk Management Process 8.7 Procurement & Contracts 8.8 Change Control

3.3 Building Shared Understanding

Key Takeaways Explain This Topic AI

Shared understanding requires all parties to have the same mental model of project goals, constraints, success criteria, and working approaches

Expectation management begins early and continues throughout the project - unmanaged expectations are the primary source of stakeholder dissatisfaction

Consensus building doesn't mean unanimous agreement; it means reaching decisions all parties can accept and support

Team agreements and social contracts establish how the team will work together, make decisions, and resolve conflicts

Visual techniques like story mapping, personas, and prototypes are powerful tools for creating shared understanding across diverse stakeholders

Last updated: January 2026

One of the greatest challenges in project management is ensuring all stakeholders share the same understanding of what the project will deliver, how it will be accomplished, and what success looks like. Misaligned expectations are the root cause of most project conflicts and dissatisfaction.

What is Shared Understanding?

Shared understanding means all parties have the same mental model of:

• Project objectives and success criteria
• Scope boundaries and constraints
• Roles, responsibilities, and decision rights
• How work will be conducted
• What trade-offs are acceptable

Without shared understanding, stakeholders make assumptions that lead to conflict when reality differs from expectations.

Managing Expectations

Expectation management is proactive - you shape expectations rather than react to them.

The Expectation Gap

• Reality Expectation Result
• Delivered > Expected Delight
• Delivered = Expected Satisfaction
• Delivered < Expected Disappointment
• Key Principles
• Set expectations early - The beginning is when expectations are most malleable
• Be specific - Vague commitments create vague expectations
• Document agreements - Written records prevent "I thought you said..."
• Communicate changes immediately - Early warning prevents surprise
• Under-promise, over-deliver - Create positive gaps when possible
• Common Expectation Areas

• Area Expectation to Manage
• Scope What's included vs. excluded
• Quality Standards, acceptance criteria
• Timeline Milestones, delivery dates
• Resources Availability, skills, commitment
• Communication Frequency, format, responsiveness
• Change process How changes are requested and approved
• Consensus Building

Consensus doesn't mean everyone agrees completely - it means reaching a decision all parties can accept and support.

Consensus vs. Other Decision Methods

• Method Description When to Use
• Unanimous Everyone fully agrees Rare, time-consuming
• Consensus Everyone can live with decision Important decisions needing buy-in
• Majority vote More than 50% agree Democratic, faster than consensus
• Expert judgment Specialist decides Technical decisions
• Authority Leader decides Urgent situations, deadlock
• Building Consensus

Define the decision clearly - What exactly are we deciding?

• Gather input from all parties - Ensure everyone is heard
• Identify common ground - Start with areas of agreement
• Address concerns systematically - Don't dismiss objections
• Generate options - Create alternatives to consider
• Test for consensus - "Can everyone support this?"
• Document the agreement - Capture the decision and rationale
• When Consensus Fails

If consensus cannot be reached:

• Identify the specific blocking issues
• Escalate with clear options and recommendations
• Accept the escalated decision gracefully
• Commit to the decision once made
• Handling Conflicts of Expectations

When stakeholders have conflicting expectations, the project manager must navigate carefully:

Sources of Conflict

• Type Example
• Scope conflicts Marketing wants features; Engineering wants simplicity
• Priority conflicts Each stakeholder believes their needs come first
• Resource conflicts Multiple projects compete for same resources
• Timeline conflicts Stakeholder expects earlier delivery
• Quality conflicts Different standards across stakeholders
• Resolution Approaches

• Approach Description Best For
• Confronting/Problem-solving Face the conflict directly, seek solution Most situations - addresses root cause
• Collaborating Work together to find win-win Complex issues with creative solutions
• Compromising Each party gives something up When time is limited
• Smoothing/Accommodating Emphasize agreements, minimize differences Preserving relationships
• Forcing/Directing Use authority to decide Emergencies, clear right answer
• Avoiding/Withdrawing Postpone or sidestep Trivial issues, cooling-off needed
• Best Practice: Confronting/Problem-solving

The PMI generally recommends confronting (also called problem-solving or collaborating) as the preferred approach because it:

• Addresses the root cause of conflict
• Creates lasting solutions
• Strengthens relationships through honest dialogue
• Builds shared understanding
• Team Agreements

Team agreements (also called working agreements or social contracts) establish how the team will work together.

What Team Agreements Cover

• Area Examples
• Communication Response time expectations, preferred channels
• Meetings Start on time, agenda required, participation
• Decisions How decisions are made, who has authority
• Conflict How disagreements will be handled
• Quality Code review expectations, testing requirements
• Availability Core hours, remote work, time off
• Feedback How feedback is given and received
• Creating Effective Agreements
• Involve the whole team - Agreements imposed aren't owned
• Be specific and actionable - "Respect each other" is too vague
• Start with few critical agreements - Don't overwhelm
• Review and update regularly - Adjust as the team matures
• Hold everyone accountable - Including the PM
• Example Team Agreement
• Meetings start on time; latecomers join without disrupting
• All voices are heard before decisions are made
• Disagree during discussion; commit once decided
• Reply to teammate messages within 4 business hours
• No work communications after 7 PM or on weekends
• Definition of Done must be met before moving stories to complete
• Techniques for Building Shared Understanding
• Visual Techniques

• Technique Description Best For
• Story mapping Visual representation of user journey and features Product scope
• Personas Fictional users representing key segments User needs
• Prototypes Working models of the solution Requirements validation
• Process maps Visual workflow representations Operations
• Architecture diagrams System structure visualization Technical alignment
• Collaborative Techniques

• Technique Description
• Workshops Facilitated sessions bringing stakeholders together
• Design thinking Empathy-driven problem solving
• Joint requirements sessions Stakeholders define needs together
• Reviews and demos Regular feedback on work-in-progress
• Definition of Done Team agreement on completion criteria
• Social Contracts in Agile

In Agile environments, social contracts formalize team behaviors:

• Elements of an Agile Social Contract
• Values we share - What we believe is important
• Behaviors we expect - How we act toward each other
• Practices we follow - Our working methods
• Consequences for violations - How we handle breaches
• Reinforcing Social Contracts
• Reference in retrospectives
• Post visibly in team space
• New team members review and commit
• Revisit when conflicts arise
• Update based on lessons learned
• Key Takeaways
• Shared understanding prevents conflicts from misaligned expectations
• Manage expectations proactively - set them early and adjust continuously
• Build consensus through systematic dialogue and problem-solving
• Confront conflicts directly rather than avoiding them
• Create team agreements that define how you'll work together
• Use visual and collaborative techniques to align diverse stakeholders

Loading diagram... Process for Building Shared Understanding