person Author: Process Fellows
Typically the terms Need, Expectation, and Requirement are distinguished as follows:

1. A Need describes a fundamental problem or desire of a stakeholder that should be addressed. It is often vague and not directly actionable. Needs arise from the stakeholder’s context, goals, or challenges.
   Example: “I want to be able to work faster.”
2. An Expectation is a stakeholder’s specific idea or assumption about how a Need might be fulfilled. It is subjective and can be expressed explicitly or implicitly.
   Example: “I expect the system to automatically suggest options.”
3. A Requirement is a documented, verifiable, and actionable specification derived from a Need or Expectation. It serves as the basis for design, implementation, and testing.
   Example: “The system shall display three relevant suggestions to the user within 2 seconds.”

Summary:

• Need: motivates development
• Expectation: expresses a concrete idea
• Requirement: a clearly defined, verifiable specification describing what is expected to be fulfilled

This distinction helps structure the process of eliciting, analyzing, and documenting requirements.