Modern Enterprise Architecture: Architecting for Outcomes
Keywords
Summary
131 words
Critical Evaluation
Value of the Information & Strength of the Argument
The talk provides valuable insights from a seasoned practitioner, offering a clear and actionable framework (ABCD) for modernizing EA. The argumentation is coherent and well-structured, building on established concepts like Conway’s Law, Team Topologies, and Domain-Driven Design. Rohrer effectively uses anecdotes and examples from his experience to illustrate the pitfalls of traditional EA and the benefits of a modern approach. However, the argumentation is largely prescriptive and based on personal experience rather than empirical evidence, which limits its generalizability.
Scientific Rigor, Source Quality, Title Accuracy
The talk references several credible sources, including Martin Fowler’s articles, the HBR article on complexity, and books like ‘Sooner Safer Happier’ and ‘Team Topologies’. These sources are relevant and support the key arguments. The title accurately reflects the content, which is a focused discussion on modernizing EA. The talk is a personal perspective, not a systematic review, so the scientific rigor is moderate. The speaker’s credibility is high given his role and experience.
167 words
Title / Content Match
The title accurately reflects the content, which focuses on modernizing enterprise architecture practices to achieve business outcomes.
Quality & Reliability
7/10
Talk by a practitioner with 30+ years of experience, grounded in established concepts (Conway's Law, Team Topologies, DDD) and referencing credible sources (Fowler, HBR, books). However, it is largely anecdotal and prescriptive, lacking empirical data or systematic evidence.
Chapters
Cited Sources
- Who Needs an Architect? — Referenced in the context of the architect's role within the team.
- Is Design Dead? — Referenced in the context of evolutionary design and architecture.
- Taming Complexity — Referenced in the context of managing complexity in modern enterprises.
- Sooner Safer Happier — The book co-authored by the speaker, which provides the framework for outcomes.
- GOTO Copenhagen 2025 session page — Page for the talk, including slides and abstract.
Concurring Sources
- Who Needs an Architect? — Supports the idea that architects should be part of the team, not separate.
- Taming Complexity — Supports the need to manage complexity in modern enterprises.
External References
Contribution & Novelties
The talk synthesizes existing ideas into a coherent framework for modern EA, emphasizing outcomes over outputs and continuous governance. It offers a practical perspective from a large, regulated enterprise. The ABCD framework is a useful mnemonic for practitioners.
Pour aller plus loin :
- Conway’s Law — The foundational concept that organizational structure influences system design.
- Team Topologies — A book and methodology for organizing teams around value streams and cognitive load.
- Domain-Driven Design — A software design approach that aligns system boundaries with business domains.
85 words
Radar Profile
The radar profile shows a balanced score across all dimensions, with slightly lower scores in technical depth and information quantity, reflecting the talk's focus on organizational and process aspects rather than deep technical details. The high reliability score indicates a trustworthy practitioner perspective.