[gombosg]

At $job we're using the DACI framework for this kind of architectural decision making and it works really well!

The framework defines roles (driver, decision maker etc) which helps with the process.

So a document (with a template similar to an RFC) is made by the driver. Contributors read and comment on it, then after all questions have been answered, a final meeting is held to make the decision along with the approver.

When the decision has been made, we go with it!

It's a really smooth process in practice, with very little friction. Way better than endless debates over and over on the same topic!

https://www.atlassian.com/team-playbook/plays/daci

[bdg]

Really cool link, I will need to try DACI. It reminds me a bit of RAPID ( https://www.bain.com/insights/rapid-tool-to-clarify-decision... ) but possibly more light-weight.