A requirement is written and agreed; an expectation is what is in the stakeholder's head, and it often goes unsaid. A hospital director may approve the requirements for an appointment system while quietly expecting the crowding at reception to drop within a month. If you don't uncover that early, you can deliver every requirement and still leave him unhappy. So ask early: "How will you know this project succeeded?" and record the assumptions people are building their expectations on.
Stakeholders sometimes expect conflicting things: finance wants the lowest cost, the doctors want the most features. The PM's job isn't to pick a side alone, nor to please everyone with promises that can't be kept. The job is to bring the parties together, show the impact of each option, and help the decision-maker decide: the sponsor in a predictive setting, or the product owner ordering the backlog in an agile one. The backbone of all of this is transparency: clear, honest information that everyone can see.
Expectations are managed continuously, not once. Demos and sprint reviews let people see the real product early, so their expectations adjust before they become a shock. Status reports must be honest; hiding a delay or painting the indicators green only postpones the problem and makes it bigger. When someone asks for something outside the scope, say "no" constructively: acknowledge the value of the request, explain its impact on time and cost, and offer the right path, such as a change request or adding it to the backlog to be prioritized.
Common exam situations: a stakeholder who keeps changing their mind, or who bypasses the process and asks developers directly. The first step is neither to escalate nor to quietly do what was asked, but to have a private conversation to understand why, then gently guide them back to the agreed process. The stakeholder engagement assessment matrix helps you see the gap: each person has a current and a desired level out of five: unaware, resistant, neutral, supportive, leading. You then plan how to move each person from where they are to where you need them.
💡 Key points
- An unspoken expectation is more dangerous than a written requirement; uncover it early by asking about success criteria.
- When expectations conflict, facilitate and let the sponsor or product owner decide; don't choose alone.
- Demos, reviews, and honest reports adjust expectations before they become a shock.
- Engagement levels: unaware, resistant, neutral, supportive, leading; plan to close the gap.
🌍 Real-life example
On a student portal project for a university in Kuwait, the dean of student affairs kept phoning developers directly with new requests. The PM didn't escalate or ignore it; he asked to meet the dean and asked why things felt so urgent. It turned out the dean feared the portal wouldn't be ready before registration. They agreed the dean would attend the sprint review every two weeks, and his requests would go through the product owner to be prioritized. At the next review the dean saw the registration screen working, his worry eased, and the side calls stopped. In the engagement matrix he moved from "resistant" to "supportive".
📖 Key terms
| English | العربية |
|---|---|
| Expectation | التوقع |
| Assumption | الافتراض |
| Transparency | الشفافية |
| Sprint Review / Demo | مراجعة السبرنت / العرض التوضيحي |
| Stakeholder Engagement Assessment Matrix | مصفوفة تقييم إشراك أصحاب المصلحة |
| Unaware / Resistant / Neutral / Supportive / Leading | غير مدرك / مقاوم / محايد / داعم / قائد |