Assumptions
Assumptions are statements taken to be true without proof in the context of a project or product development. These are beliefs about the product, market, users, or technology that teams accept as true for the sake of planning and moving forward with development, often in the absence of complete information.
Purpose
The purpose of identifying and documenting Assumptions is to make explicit the underlying beliefs that guide decision-making and product development. This helps in prioritising validation efforts, mitigating risks, and ensuring alignment within the team and with stakeholders. By acknowledging and validating assumptions, teams can make more informed decisions and guide the product strategy under conditions of uncertainty.
Types of Assumptions
| Type | Description |
|---|---|
| Desirability | Do customers really want this and will they pay for it? |
| Usability | Will customers be able to understand what this offers and how to use it? |
| Feasibility | Can we build this and maintain it? |
| Viability | Can we make enough money/value from this to make it worthwhile? |
| Third-Party Risk | If we rely on third parties will they behave as we expect them to? |
| Execution Quality | What would happen if we don't execute this well? |
Anti-patterns
- Unchallenged Assumptions: Proceeding with development based on assumptions that have not been critically evaluated or validated.
- Lack of Validation Plan: Failing to outline how and when assumptions will be validated, risking reliance on untested beliefs.