InfoQ Homepage Architecture Decision Records Content on InfoQ
Articles
RSS Feed-
/articles/accelerating-technical-decision-making/en/smallimage/GettyImages-1481183172-small-1716206161459.jpg)
Accelerating Technical Decision-Making by Empowering ICs with Engineering Strategy
Carta harnesses the power of a small group of senior engineers called navigators to bridge the gap between global strategy and local decision-making, using a written engineering strategy. Navigators replace a need for consensus and boost velocity by combining technical context, domain context, strategic alignment, and judgment to make engineering decisions quickly.
-
/articles/technical-decision-buy-in/en/smallimage/getting-technical-decision-buy-in-using-the-analytic-hierarchy-process-small-1710151223445.jpg)
Getting Technical Decision Buy-In Using the Analytic Hierarchy Process
Making large, important technical decisions is a critical aspect of a senior individual contributor's role. This article examines how Comcast has employed the Analytic Hierarchy Process (AHP), a decision-making framework developed in the 1970s, and adapted it for making technical and non-technical decisions both large and small.
-
/articles/architectural-decision-record-purpose/en/smallimage/has-your-architectural-decision-record-lost-its-purpose-small-1698058555994.jpg)
Has Your Architectural Decision Record Lost Its Purpose?
Architectural Decision Records (ADRs) are important vehicles for communicating the architectural decisions a development team makes about a system. Lacking a clear definition of what is architectural, and also lacking anywhere else to record important decisions, they can start to drift from their original purpose and lose focus and effectiveness.
-
/articles/framework-architectural-decisions/en/smallimage/logo-1679060242842.jpg)
A Simple Framework for Architectural Decisions
This article describes a framework for making architectural decisions using three building blocks: The company's own Technology Radar; Technology Standards; and Architecture Decision Records (ADRs). The framework clarifies decision-making, team involvement, and information on already made decisions and aligns with the company's needs and culture.
-
/articles/effective-architecture-conversations/en/smallimage/have-effective-conversations-with-business-stakeholders-about-software-architecture-small-1677231728391.jpg)
How to Have More Effective Conversations with Business Stakeholders About Software Architecture
Technical leaders must be able to communicate with business stakeholders to effectively design software solutions that meet the business needs and stay within an established cost threshold. Making architectural decisions requires understanding the desired quality attributes that will affect trade-off discussions between technical and non-technical stakeholders.
-
/articles/architecture-skeptics-guide/en/smallimage/a-skeptics-guide-to-software-architecture-decisions-small-1672223516348.jpg)
A Skeptic’s Guide to Software Architecture Decisions
Skepticism is an architectural superpower that helps you to see through false assumptions before you have followed them too far before they have cost you too much time and created so much work that you’ll never completely recover.