---
title: "Facilitate, Don't Dictate, Architectural Change"
source: "https://virtualddd.com/heuristics/facilitate-dont-dictate-architectural-change/"
authors: ["Michael Plöd", "Beija Nigl", "Kenny Schwegler", "Andrea Magnorsky", "Andrew Harmel-Law"]
tags: ["decentralised decision-making", "facilitating software architecture and design", "software design", "ranking", "sociotechnical systems"]
type: "guiding heuristics"
question: "What is the most effective stance for an architect when driving significant architectural change?"
submitter: "Michael Plöd"
---

# Facilitate, Don't Dictate, Architectural Change

An architect's role is to facilitate understanding and alignment, not to command. This requires empathy and a deep understanding of diverse perspectives to guide change effectively. Avoid hierarchical power plays in favor of collaborative problem-solving.

## Examples

Instead of declaring 'we will use microservices,' engage stakeholders to explore how new architectures address their specific challenges and concerns.