AAA Cycle: Align-Agree-Apply - Architecture Insights

Overview

AAA is a guiding discipline and principle for software development: a way of thinking that provides guardrails against the most common mistakes organizations and development teams make. It transcends any specific methodology, operating from the software architect’s perspective on what truly matters.

AAA is about how we value before how we work.

Align

We establish and value human connection. Before we talk about solutions, timelines, or technology, we connect with people. Alignment is not about extracting requirements; it's about building understanding and trust.

Agree

We value shared commitment on how we will accomplish what we're aligned on. Agreement isn't just documentation or sign-offs; it's mutual understanding and genuine commitment to walk the path together.

Apply

We value delivering on agreements. Notice that "deliver" is not the focus; applying the agreement is. We honor the commitments made to the people we aligned with.

Nearly every failed project makes the same mistake: it starts with solutions, jumps to plans, and treats delivery as the goal. AAA deliberately reverses this. The need comes first, then genuine human agreement, then disciplined application of what was agreed.

When you walk into that first stakeholder meeting, you don't need a project plan. You need to connect with people, understand their world, and establish the foundation for meaningful agreement.

Not a Checklist, But a Discipline

AAA presents specific activities, deliverables, and decision points, but these are examples of the discipline in practice, not rigid steps to follow. This discipline applies whether you’re using Scrum sprints, Kanban flows, or waterfall phases. It transcends methodology because it addresses something deeper: how architects think about and engage with the work itself.

Trust Over Politics

Strict frameworks like Scrum often function as defensive mechanisms: ways to protect yourself from stakeholders and vice versa. They create systems of politics rather than trust. Yes, these frameworks are based on truth and provide valuable starting points for organizing teams. But they can become rigid checklists that substitute for genuine human connection.

When Structure Becomes a Shield

The problem isn't having structure; it's when that structure becomes a shield instead of a bridge. When "following the process" matters more than solving the problem. When ceremonies become rituals emptied of meaning.

AAA calls us back to something more fundamental: focusing on what we value. Not “Agile” the branded methodology with capital-A ceremonies, but “agile” the principle of being responsive to reality. Not defensive processes that protect territories, but disciplines that build trust.

Yes, use frameworks. Use their ceremonies and practices. But stay open to discovery and change within each event, each schedule, each unique situation. The framework serves the values (connection, commitment, and honored agreements), not the other way around. When a framework ceremony stops serving those values, you adapt it. That’s the discipline AAA represents: being flexible about how while remaining unwavering about what matters.

The Three Phases

Phase 1: Align with the Need

Understand the problem space before making commitments. Build trust with stakeholders, surface constraints, and establish shared understanding of success. Alignment produces a foundation of mutual understanding with real stakeholder buy-in, not just signatures from people who feel heard.

→ Phase 1: Align Guide

Phase 2: Agree to the Plan

Transform aligned understanding into concrete, approved technical plans. Design the solution, validate critical assumptions, and secure commitment on approach and resources. Agreement produces authentic commitment because everyone helped shape the path forward.

→ Phase 2: Agree Guide

Phase 3: Apply the Agreement

Execute the agreed plan with discipline while maintaining continuous alignment. When reality requires changes, return to Align or Agree rather than silently drifting from what was committed. Application produces working software that meets the needs you aligned on, built the way you agreed.

→ Phase 3: Apply Guide

Visual Journey

                     ┌─────────────────────────────────────┐
                     │         FEEDBACK LOOPS              │
                     │  Discovery triggers realignment     │
                     └─────────────────────────────────────┘
                                       │
        ┌──────────────────────────────┼──────────────────────────────┐
        │                              │                              │
        ▼                              ▼                              │
 ╔═══════════════╗            ╔═══════════════╗            ╔═══════════════╗
 ║     ALIGN     ║            ║     AGREE     ║            ║     APPLY     ║
 ║───────────────║            ║───────────────║            ║───────────────║
 ║    Human      ║    ───►    ║    Shared     ║    ───►    ║   Honored     ║
 ║  Connection   ║            ║  Commitment   ║            ║  Agreement    ║
 ╚═══════════════╝            ╚═══════════════╝            ╚═══════════════╝
        │                              │                              │
        ▼                              ▼                              ▼
 ✓ CONNECTED                   ✓ COMMITTED                    ✓ VALUE REALIZED
        │                              │                              │
        └──────────────────────────────┴──────────────────────────────┘
                                       │
                              Cycle repeats at every level

Each phase builds on the previous one. You can’t genuinely agree without first aligning, and you can’t honor agreements that were never truly made. When new information breaks alignment, go back and re-align. When the plan proves infeasible, go back and re-agree. This isn’t failure; it’s the discipline of maintaining integrity.