An expectation is an assumption or requirement about inputs, outputs, behavior, responsibilities, or outcomes. Managing expectations means clarifying them early, aligning them with reality, and adjusting them as circumstances change. Realistic expectations rely on data and attainable goals; unrealistic ones lack factual grounding and can create confusion, frustration, and misalignment. section 11.0 section 11.6
Clarifying a deployment expectation
Alice expects Bob to deploy code changes, but Bob has never deployed before. A useful expectation specifies testing, QA involvement, staging, deployment authority, notifications, and available support. This avoids multiple interpretations while balancing helpful guidance against overly prescriptive instructions. section 11.1.1 section 11.1.2
Manage expectations through a practical cycle:
- Set expectations clearly: state what is expected, why it matters, who is responsible, and what support is available. section 11.6
- Communicate and document expectations, inviting questions and checking understanding to prevent throwaway work. section 11.4.3 section 11.6
- Make expectations mutual: provide training, resources, guidance, feedback, and protection from unnecessary disruption while expecting responsible execution. section 11.4.3
- Negotiate when estimates, priorities, designs, or circumstances conflict instead of silently overcommitting. section 11.6
- Adapt expectations as business needs evolve, explaining the change and its value so people can pivot constructively. section 11.3.4
- Check perceptions and fairness: distinguish agreed standards from personal interpretations, and apply performance expectations consistently while allowing appropriate empathy. section 11.0 section 4.2.2
Figure 11.1 Expectations can be different from what is perceived versus what is expected.
Use the figure to distinguish what people perceive from what others actually expect, a central source of expectation gaps. section 11.0
