---
title: "Revisit Decisions When Context Changes"
source: "https://virtualddd.com/heuristics/revisit-decisions-when-context-changes/"
authors: ["Andrea Magnorsky", "Andrew Harmel-Law", "Kenny Baas-Schwegler"]
tags: ["adr", "decision-making process", "decentralised decision-making", "facilitating software architecture and design"]
type: "guiding heuristics"
question: "How do we know if a long-standing architectural constraint is still valid?"
submitter: "Andrew Harmel-Law"
---

# Revisit Decisions When Context Changes

Decisions are made based on the context at a specific point in time, such as team size or available technology. Documenting this original context allows you to determine if it has changed enough to justify revisiting the decision. This prevents historical choices from becoming unchallengeable dogma.

## Example

A decision was made when the company was a 12-person startup. Now that it is a 200-person scale-up, the team can re-evaluate that choice because the original context has changed.