Develop a common vision

PMP ECO · People (33%) · Task P1. Create a shared, compelling picture of why the project exists and what "done" looks like — and get the team and stakeholders behind it.

What it is

A vision is the north star: a concise statement of the project's purpose, the outcome it delivers, and the criteria by which success will be judged. In PMBOK® 8e it lives in two artefacts — the project charter (purpose, measurable objectives, success criteria, high-level scope) and the team charter (the shared values and ways of working the team commits to). Vision is not a slogan; it is the reference the project manager returns to whenever priorities compete.

Why it matters

• Alignment. Every later decision — scope trade-offs, risk responses, change requests — cascades from the vision. Without it, each stakeholder optimises for their own goal.
• Motivation. Teams commit to purpose, not tasks. A clear "why" sustains effort through the hard middle of a project.
• Authority. The charter formally authorises the project and the PM. It is the document you point to when someone tries to bolt on unfunded scope.

Where you do it in VanillaPM

Open the project's Charter and complete the purpose / objective and success criteria sections, then the Team → Charter tab for the team's values and working agreements. Both are governed documents — versioned, and the source that later plans inherit from.

Walked example — Coral Ridge Resort

The Coral Ridge charter states the vision plainly:

"Design and build Coral Ridge Resort — a 10-storey, 220-key five-star hotel on the Cox's Bazar coast, with sea-facing rooms over the beach and hill-facing rooms over the ridge — delivered to brand standard, on budget, and opening in time for the winter tourist season."

That single sentence encodes the measurable success criteria the team returns to: Marriott brand standard, a $48M budget with reserves, and an opening before winter 2028. The team charter adds the values a coastal five-star build demands — safety-first (piling and high-rise work over a storm-exposed site), quality to five-star finish, and community respect (beach access is a live issue).

The artefact

• Project Charter — purpose, measurable objectives, success criteria, high-level scope, PM authority.
• Team Charter — shared values, decision rules, working agreements.

Best practices & pitfalls

• Do make the vision specific and measurable — "five-star brand standard, $48M, winter 2028", not "a great hotel".
• Do co-create the team charter with the team; imposed values don't stick.
• Do revisit the vision at phase gates — a two-year build's context shifts.
• Pitfall: a charter written once and never referenced. If it doesn't settle a real argument, it isn't doing its job.

On the PMP exam

Vision sits in the People domain and leans on servant leadership. Expect situational questions where a team is drifting or stakeholders pull in different directions — the best answer usually re-anchors everyone on the charter's purpose and success criteria rather than adding process. Remember the charter is what authorises the PM and the project.