The Importance of Expectation Management
Estimates do not just predict outcomes; they construct the frame through which outcomes are judged.
A man arrives in a waiting room. He is told he will have to wait five minutes. Twenty minutes later, he is eventually called, and he is irritated.
Another man arrives in the waiting room, he is told that the wait may take half an hour. He is called after twenty minutes. Upon being called he is pleasantly surprised, despite being interrupted reading an article.
A third man arrives in the waiting room, he is told to wait indefinitely. He becomes increasingly irritated. He doesn’t know if he has been forgotten or how deeply he can occupy himself whilst waiting. He also waits twenty minutes.
The question arises:
How can three men, who experience the same wait, have such radically different perceptions of it?
This can be explained because such a wait is not experienced purely in terms of duration. It is experienced through the interpretive frame created by expectation.
An estimate does two things at once. It bounds uncertainty, and it creates an expectation.
By bounding uncertainty estimates reduce cognitive load and facilitate co-ordination. If someone is told a wait will be five minutes, they behave differently than if they are told it will be half an hour. They make different decisions about whether to start reading an article, make a phone call, leave the room, or mentally settle in.
The absence of an estimate is therefore not neutral. It creates unbounded uncertainty. The mind has to model a larger range of possible states: has the request been forgotten, will this take five minutes, will this take an hour, should I occupy myself deeply, should I remain alert? This additional uncertainty creates cognitive load.
An estimate does more than predict a future outcome. It constructs the interpretive frame through which that outcome will be evaluated. The same outcome can feel like success, failure, or relief depending upon the prior expectation. A twenty-minute wait is irritating if five minutes were promised, but pleasing if thirty minutes were expected. This is because perception of reality is mediated through expectation.
This is why over-promising is so damaging. It sets the interpretive frame optimistically and in doing so establishes a baseline that reality is unlikely to satisfy, hence disappointment is downstream. Disappointment can be characterised as the difference between expectation and outcome. This is why expectation management is integral to the formation of positive evaluations.
disappointment = expected reality - manifested reality
If we seek to minimise disappointment and increase positive evaluation then shouldn’t we always under promise? The engineering mantra “under promise, over deliver” encodes this preference. However, this discounts the co-ordination inefficiency created by inaccurate estimates and the deleterious effect upon trust.
When expectations are continually subverted, trust degrades, and estimates lose legitimacy. Trust is an asymmetric resource, it is much harder to recover after loss than it is to maintain. Hence, trust maintenance and expectation management become increasingly high leverage work.
This mechanism applies beyond engineering. “Go to university, work hard, and you will get a good job” was not merely advice. It was an expectation-setting mechanism. When the economic conditions changed but the promise remained, disappointment became visceral.
The problem is not that the advice was necessarily bad. It may once have been broadly reasonable. The problem is that it was communicated with certainty and this certainty persisted after the conditions that it relied upon had begun to be eroded.
If successive social expectations are provided with certainty and fail to manifest, the result will be a predictable loss of trust and a loss of legitimacy of such claims.
Setting the interpretive frame pre-emptively matters because it affects how an outcome is interpreted before it arrives. Expectation management is therefore not just the domain of project managers; it is integral to the delivery of engineering work.
In estimation, uncertainty is the most significant variable. Reducing uncertainty early in a project’s life can significantly improve the accuracy of an estimate. Where uncertainty cannot be eliminated, the estimate should reflect it. Firstly, this can be done by padding the estimate proportionally to the magnitude of uncertainty, reducing the risk that uncertainty is later converted into disappointment. Secondly, estimates can also be delivered with confidence claims. This allows the receiver to contextualise the estimate and avoid building too much upon unstable foundations.
When the uncertainty landscape shifts significantly, the estimate should be updated. Communicating this change is important work as if the receiver is unaware of this shift, the project will still be evaluated within an outdated interpretive frame.
Centering expectations also changes how project post-mortems should be conducted. When disappointment appears in such a setting, the question should not only be what went wrong in execution, but whether expectations were realistic, whether uncertainty was communicated, and whether the evaluative frame had been set realistically.
Disappointment is often treated as a reaction to reality. But reality is only half the equation. The other half is the expectation structure through which reality is received.
An engineering outcome is not evaluated in isolation. It is evaluated against what people were led to expect. When expectations are unrealistic, uncertainty is poorly communicated, or estimates repeatedly fail to correspond with reality, disappointment and distrust often follow.
By pre-emptively influencing how work will be interpreted, expectation management is not an industry afterthought. It is a high leverage engineering activity.