
The Making of a Decision • Andrea Magnorsky • GOTO Copenhagen 2026
Title history
- The Making of a Decision • Andrea Magnorsky • GOTO Copenhagen 2026 — observed on 20261117-0328 UTC (YouTube)
Keywords
Summary
106 words
Critical Evaluation
Value of the Information & Strength of the Argument
The talk offers valuable insights into the often-overlooked socio-technical aspects of decision-making in software engineering. It provides a coherent synthesis of existing theories (e.g., DIKW, leverage points) and practical frameworks (ADR, advice process). The argumentation is solid, grounded in personal experience and references to well-known literature, though some claims could benefit from more explicit evidence. The interactive elements (audience scenarios) help engage the audience but do not dilute the substantive content.
Scientific Rigor, Source Quality, Title Accuracy
The speaker references several credible sources, including ‘The Dawn of Everything’ by Graeber and Wengrow, ‘Pedagogy of the Oppressed’ by Paulo Freire, and a paper on charisma. However, she does not always provide precise publication details or URLs, relying on audience familiarity. The title accurately reflects the content, which systematically dissects the decision-making process. No significant discrepancies were noted between the advertised topic and the delivered talk.
153 words
Title / Content Match
Excellent alignment: the talk dissects the anatomy of a decision, covering power, knowledge, and practical tools.
Quality & Reliability
7/10
The talk provides a thoughtful framework for understanding architectural decisions, drawing on established concepts (DIKW pyramid, leverage points, advice process) and references several notable books (e.g., 'Pedagogy of the Oppressed', 'The Dawn of Everything'). However, many sources are mentioned without specific citations or dates, and the presentation relies heavily on personal experience and anecdotes.
Chapters
- Intro
- How many times have significant desicions happened like you expected it
- What is a architectural decision?
- Acquisition
- Replacement of a business critical third party
- Anatomy of a decision
- Anatomy of power in a decision
- Anatomy of knowledge in a decision
- What now? - Understanding generates options
- Tools - Larger groups
- ADR Template
- Tools - Small groups
- Outro
Cited Sources
- GOTO Copenhagen 2026 session page — Official session description and slides download
- Speaker's personal website — Additional resources and contact
- Speaker's GitHub — Speaker's code and projects
- Speaker on X (Twitter) — Speaker's social media
- GOTO Conferences Bluesky — Conference updates and community
Concurring Sources
- Architecture Decision Records (ADR) – GitHub repository by ThoughtWorks — Supports ADR practice as a standard for recording decisions
- Team Topologies – official website — Provides a model for organizing teams to improve flow and decision-making
Dissenting Sources
External References
Contribution & Novelties
The talk provides a structured lens for understanding architectural decisions by framing them through the dual lenses of power and knowledge. It bridges theoretical concepts (DIKW, leverage points) with practical team practices (ADR, advice process). The main contribution is articulating how these elements interact in socio-technical systems and offering actionable strategies for improving decision transparency and accountability.
Pour aller plus loin :
- Architecture Decision Record (Wikipedia) — Core concept discussed; useful for documenting decisions.
- DIKW pyramid (Wikipedia) — Foundational model for understanding knowledge hierarchy.
- Advice process (Wikipedia) — Decentralized decision-making method highlighted in the talk.
- Team Topologies official site — Model for organizing teams to optimize flow, referenced by speaker.
- The Dawn of Everything (Wikipedia) — Book cited for sources of power.
122 words
Radar Profile
The radar profile shows strong scores in quantity and quality of information, with moderate technical depth and reliability. This indicates a talk that is rich in content and well-structured, but not extremely technically deep, making it accessible to a broad technical audience.