Grounded Architecture

Redefining IT Architecture Practice in the Digital Enterprise

by Željko Obrenović, Chief Architect at AVIV Group

Download a book:

  • PDF (FREE)
  • EPUB (FREE)
  • Amazon: Kindle | Paperback | Hardcover (coming soon)

    Introduction

  • Introduction

    This book will share my approach to running an IT architecture practice in larger organizations based on my experience at AVIV Group, eBay Classifieds, and Adevinta. I called this approach "Grounded Architecture," highlighting the need for any IT architecture practice to stay well-connected to all levels of an organization and led by data.
  • Context: Fast-Moving Global Organizations

    The Grounded Architecture approach has evolved in the context of global, loosely coupled organizations that are diverse, with nonlinear growth dynamics, and under transformation pressures.
  • Goals: Adapting, Growing, and Using Data

    I identified the following needs that an architecture practice should support: Executing At Scale, Adaptivity, Improving the Quality of Decision-Making with Data, and Maximizing Organizational Alignment & Learning.
  • Grounded Architecture Framework

  • Grounded Architecture Framework: Introduction

    I introduce three elements of Grounded Architecture Framework: Lightweight Architectural Analytics, Collaborative Networks, and The Operating Model.
  • Lightweight Architectural Analytics

    Lightweight Architectural Analytics serves as a medium to create a complete, up-to-date picture of critical elements of the technology landscapes of big organizations. The platform provides an architecture-centric view of data about a technology landscape based on source code analyses, public cloud billing reports, vibrancy reports, or incident tickets.
  • Collaborative Networks

    We should not take our architectural talent for granted. Architects are difficult to hire because they need in-depth technical, domain-specific, and managerial knowledge. Therefore, we must support, organize, and leverage architecture talent.
  • Operating Model: General Principles

    Operating Model defines how, by leveraging Lightweight Architectural Analytics and Collaborative Networks, we perform activities that help an organization reach its goals. Examples include supporting teams in their daily work, tracking tech debt, performing technical due diligence, standardizing processes and documentation, and defining cloud, data, and platform strategies.
  • Cooperation-Based Operating Model: Six Simple Rules

    The Six Simple Rules approach emphasizes that you must set up organizational structures based on cooperation in today's complicated business environment. To deal with complexity, organizations should depend on the judgment of their people, and these people cooperate to utilize the organization's capabilities to cope with complex problems.
  • Operating Model: Nudge, Taxation, Mandates

    Architecture practice should support governance models that are adaptable to organizations' complex and diverse needs. I see a technology governance model as a well-balanced hybrid of three different styles of governing: nudging, taxes, and mandates and bans.
  • Transforming Organizations with Grounded Architecture

    When the Grounded Architecture Framework is in place, it can significantly impact an organization's functioning: Executing At Scale, Adaptivity, Improving the Quality of Decision-Making with Data, and Maximizing Organizational Alignment & Learning.
  • On Being Architect

  • On Being Architect: Introduction

    I introduce guiding principles that generalize my view on what it means to be an architect in practice.
  • Building Skills

    A typical architect's skillset includes hard (technical) skills, soft (people & social) skills, product skills, business skills, and decision-making skills.
  • Making Impact

    Architects' work is evaluated based on their impact on the organization. They must demonstrate that they identify, tackle, and deliver on strategic problems, have a deep and broad influence, and deliver solutions that few others can.
  • Leadership Traits

    My view of architecture leadership is inspired by David Marquet’s work and Netflix’s valued behaviors.
  • Thinking Like an Architect: Architects as Superglue

    Architects in IT organizations should develop as “superglue,” people who hold architecture, technical details, business needs, and people together across a large organization or complex projects.
  • Thinking Like an Architect: Balancing Curiosity, Doubt, Vision, and Skepticism

    Balancing curiosity, doubt, vision, and skepticism is essential for driving sustainable innovation and change in organizations.
  • Architects' Career Paths

    Architects' career paths ideally stem from a strong engineering background. Hiring architects requires constantly raising the bar to ensure a strong and diverse team structure.
  • On Human Complexity

  • On Human Complexity: Introduction

    I introduce several resources that I use as inspiration for developing the complexity awareness of human complexities.
  • The Culture Map: Architects' Culture Compass

    Architects work with many different cultures in multinational organizations. I have found Erin Meyer's work, The Culture Map, to be a beneficial tool for architects to work harmoniously with people from various cultures and backgrounds.
  • The Human Side of Decision-Making

    Decision-making is a human activity subject to human biases and limitations. Fundamental biases influencing decision-making include outcome, hindsight, and confirmation biases.
  • Effortless Architecture

    A summary of lessons learned from Greg McKeown's Effortless book, which offers invaluable insights that are particularly relevant for IT architects and software engineers. McKeown's emphasis on simplifying tasks and processes is crucial in the tech industry, where complexity often dominates.
  • Expanding the Architect's Toolkit

  • Expanding the Architect's Toolkit: Multidisciplinary Approaches

    I introduce several resources that I use as inspiration for developing architecture skills related to execution and governance.
  • Architecture Practice in Product-Led Organizations

    Regarding product development, I recommend two resources for architects: “Escaping the Build Trap: How Effective Product Management Creates Real Value” by Melissa Perri and “The Discipline of Market Leader” by Michael Treacy and Fred Wiersema.
  • Decision Intelligence in IT Architecture

    Decision intelligence is the discipline of turning information into better actions. It includes strategies for improving decision-making, reliable data-driven decisions, and avoiding biases.
  • Economic Modeling: ROI and Financial Options

    I sketch two methods of determining the economic value of technology investments and architecture: the return on investment metaphor and the financial options metaphor.
  • Summary

  • Summary

    A brief summary of this book.
  • To Probe Further: Online Appendix Overview

    An overview of the resources in the online appendix.
  • APPENDIXES

    Appendix 1: Inspiration and Further Learning

  • Favorite Quotes

    My favorite quotes about architecture.
  • Bookshelf

    External key resources inspiring my work.
  • Appendix 2: Tools for Developing Soft Skills

  • Resources for Managing, Growing, and Hiring Architects: Raising the Bar

    Pointers to resources for managin, growing and hiring architects. When growing and hiring architects, it is crucial to continually raise the bar, ensuring that the team is composed of highly skilled and diverse individuals who can contribute unique perspectives and expertise.
  • Architect Archetypes

    Explores various architectural leadership archetypes and frameworks, including Will Larson’s Staff roles, Gregor Hohpe’s movie-inspired metaphors, Gergely Orosz’s software engineer archetypes, and TOGAF’s structured approach, providing insights to help architects define their roles and responsibilities effectively.
  • Resources for Effective Communication

    A summary of several resources that can help you communicate more effectively, provide good feedback, and lead tough conversations.
  • Appendix 3: Pragmatic Knowledge Resources

  • ISO 25010 Standard

    ISO/IEC 25010 standard focuses on product quality and system quality models providing a reasonably complete yet compact source for understanding software maintainability, security, reliability, and efficiency.
  • Cloud Design Patterns

    A mix of key distributed and messaging system topics combined with modern public cloud engineering themes.
  • High Performing Technology Organizations

    A summary of characteristics of high-performing technology organizations.
  • Appendix 4: Software Tools

  • Tools

    Tools I've built and use in daily architectural work.
  • Software Tools: Examples and Screenshots

    Screenshots of concrete tools I built as a part of Lightweight Architectural Analytics websites.
  • Building Lightweight Architectural Analytics

    A few practical tips on building lean architecture dashboards and documents (e.g., to create Lightweight Architectural Analytics) using simple, widely available tools.
  • Appendix 5: Other Things

  • Cheat Sheet

    Key points from all sections in one place.