3.1. Develop a Common Vision
💡 First Principle: A team that doesn't share the same picture of "done and worth it" will optimize for different things under pressure — establishing a common vision isn't a kickoff-meeting formality, it's the reference point every later trade-off decision gets checked against.
Enablers PMI tests under this task: helping ensure a shared vision with key stakeholders, actively promoting that vision throughout delivery (not just stating it once), keeping the vision current as context changes, and diagnosing root causes when the team's understanding of the vision has drifted or fractured.
A vision that was accurate at kickoff can become stale mid-project — scope evolves, sponsors change, market conditions shift. "Keep the vision current" is tested precisely because candidates default to treating vision-setting as a one-time event rather than an ongoing responsibility.
What a vision is, and where it lives
A vision is a concise, shared statement of the project's purpose and desired end state — the why behind the work and the value it is meant to create. On an adaptive team it usually appears as a product vision statement inside the team charter, alongside the mission, working agreements, meeting cadence, and the Definition of Done (DoD). Vision tells the team where it is going; the DoD tells it when a piece of work has arrived. A charter with a vision but no agreed DoD leaves the team free to argue about completeness sprint after sprint.
Documenting the vision in the project charter is not the same as having a shared one. Stakeholders who did not object to a written charter have not necessarily understood or agreed with it. "Help ensure a shared vision" means actively confirming that understanding — asking key stakeholders to describe the outcome in their own words and resolving the differences you hear.
Building a shared vision
You cannot reconcile differences you have not surfaced, or promote a vision that was never reconciled. The loop back is the "keep it current" enabler.
This is also where leadership style shows. Transformational leadership inspires through vision, motivation, and intellectual stimulation; transactional leadership manages through rewards, penalties, and established procedures. Promoting a vision is transformational work, and a shared vision is one of the markers of a high-performing team, together with psychological safety, mutual accountability, self-organization, and continuous improvement.
Diagnosing drift
Vision drift rarely announces itself. The signals are small:
| Signals of alignment | Signals of misalignment |
|---|---|
| A new joiner can describe the purpose accurately within a week | Team members give noticeably different answers to "what does success look like?" |
| A stakeholder pushes back by citing the agreed purpose | Subteams each treat a different goal as "the point of the project" |
| Trade-offs are argued in terms of the stated value | Priority fights escalate with each side sure it is right |
Common causes are a sponsor change, scope that evolved without the purpose being restated, and team turnover — new members never heard the kickoff. When the sponsor changes, meet the new sponsor proactively to confirm or realign the vision, then communicate any change to the team clearly; do not wait for the team's uncertainty to turn into rework.
⚠️ Exam Trap: Treating a priority conflict between subteams as a scheduling problem. When two groups each believe their priority is correct, investigate first whether they are interpreting an outdated or misunderstood vision differently — resequencing the backlog fixes the symptom and leaves the cause in place.
⚠️ Exam Trap: When a scenario shows a team disagreeing on priorities mid-project, the reflexive answer is often "escalate to the sponsor." PMI more often expects the PM to first diagnose whether the disagreement traces back to a misunderstood or outdated vision, then realign the team directly.
Reflection Question: Describe a project where the team's understanding of "the goal" diverged partway through. What was the root cause, and how would you have diagnosed it faster?
