TOPIC: Why does PMBOK treat stakeholder expectations differently?

Trying to understand why PMBOK makes a distinction between stakeholder requirements and expectations. Aren’t both just inputs from stakeholders that shape the project?

Is it just a matter of what’s formally captured vs what’s assumed? Or is there more to it in terms of how you manage each? Appreciate any clarity.

Michael,

A requirement is fundamentally different from an expectation.

Requirements must be satisfied in order for a project to be accepted/completed. (Example: The "on" light must be green.)

An expectation is more what the stakeholder "thinks" the project will look when completed or how the project is performed. (Example: "I thought you were going to put the "on" light next to the switch")

Clearly, project requirements must be clearly communicated between the stakeholders. That is usually done at the early stages of the project. Managing stakeholder expectations is done throughout the project.

Hi Michael,

I agree with Harry, and I’d add that requirements are what stakeholders explicitly communicate and can be documented and verified, while expectations are often unstated but still crucial for stakeholder satisfaction.

As a project manager, part of your job is to uncover those hidden expectations through effective communication and active listening — that’s why we say PM work is 90% communication!

-Elena