---
title: "A Decision Is What Gets Implemented"
source: "https://virtualddd.com/heuristics/a-decision-is-what-gets-implemented/"
authors: ["Krisztina Hirth", "Andrea Magnorsky", "Kenny Schwegler"]
tags: ["decision-making process", "deep democracy", "facilitating software architecture and design"]
type: "guiding heuristics"
question: "When is an architectural decision considered final and effective?"
submitter: "Kenny Schwegler"
---

# A Decision Is What Gets Implemented

An architectural decision is not a document or a declaration; it is the implemented reality. A decision only becomes effective when the team understands, commits to, and implements it. Without team buy-in, any top-down decision is merely a suggestion that is likely to be ignored or poorly executed.

## Examples

An architect can decide on a design, but if the team is not convinced, they will not implement it. The decision is only real once the team says 'yes, we want to do it like this' and builds it.