The Solutions Architecture Framework (SAF)

Overview

The Solutions Architecture Framework consists of five phases: Vision Development and Understanding, Current State Collection and Analysis, Future State Solutions Options Determination and Vetting, Solutions Presentation and Decisioning, and Solutions Realization Planning. Each is covered in its own chapter later in this document.

The SAF is a Value Stream — specifically an Architecture Value Stream — that converts a known problem or vision for change into a vetted and approved solution set for addressing the said problem or vision.

The SAF’s phases, patterns, steps, and many of its artifacts are highly repeatable and reusable to solve any problem, not only Solutions Architecture problems. Consulting firms have run some close variant of this exact pattern — vision and current-state understanding, options development, decisioning, and realization planning — for decades, refining it across countless engagements, typically under their own proprietary or unnamed methodology rather than a shared industry name. What this document offers is not a new invention: it is the first standardized, vendor-neutral, publicly documented version of a pattern the consulting industry has already tested and refined repeatedly, giving it a common name and a common, repeatable structure for the first time. This is a proof-by-precedent claim, not an assertion of novelty — the SAF is a distillation of decades of already-proven practice, which is a different, and arguably stronger, basis for confidence than an untested new invention would be.

Like the Solution Set it produces, the SAF scales to any sized challenge, from a problem one engineer can resolve to an engagement the size of a merger or acquisition. The same five phases apply at either scale; what changes is the depth and duration of effort within each one.

The five phases are loosely sequential, not rigidly linear. As an architect moves forward through them, earlier phase outputs are often revisited and refined as later work surfaces new understanding — a conclusion reached during Vision Development may need adjusting once Current State Collection reveals something unexpected, for example. Work relevant to later phases, particularly Future State Solutions Options, often begins informally well before the phase that formally owns it, as ideas and possibilities naturally surface while earlier work is still underway. This does not relax the phase gates described elsewhere in this document; it means the SAF should be practiced as an iterative, forward-and-backward discipline, not a rigid, one-directional checklist.

Best Practice: Communicate Continuously With the Customer Across Every Phase

Work within each phase, and across all steps of all phases, should never be performed in a vacuum. All such work must be continuously communicated and vetted with the correct stakeholders — including the problem owners, referred to throughout this document as the Customer of the engagement. This is not limited to a single checkpoint; it applies across every phase, from Vision Development through Solutions Realization Planning.

Benefit(s)

Continuous communication with the Customer ensures no surprises — for the Customer, and for the Solutions Architecture team. It also reinforces the credibility case made earlier in this document: a framework built on already-proven practice, applied with continuous stakeholder engagement, is a materially safer basis for confidence than an improvised approach arrived at in isolation.

Best Practice: Treat Phase Sequencing as Loosely Ordered, Not Rigidly Linear

Revisit and refine earlier phases’ outputs as later work surfaces new understanding, rather than treating each phase as closed the moment the next one begins. Where ideas or data relevant to a later phase — especially Future State Solutions Options — surface naturally while earlier work is still underway, capture them informally rather than discarding them until the formally corresponding phase arrives.

Benefit(s)

Treating the phases as loosely sequential, rather than rigidly linear, produces a more accurate and complete engagement: early insights about future-state possibilities do not get lost waiting for their formal phase, and earlier phase outputs stay current as understanding deepens, rather than calcifying into stale assumptions the rest of the engagement is built on.

Anti-Pattern: Treating the SAF’s Phases as a Rigid, Linear Checklist

Treating each SAF phase as fully closed before the next begins — discarding early insights about Future State possibilities that surface during Vision Development or Current State Collection, for example, because “that’s a later phase’s job” — throws away real understanding the engagement has already earned. The SAF’s phases are a structure for organizing the work, not a sequence that forbids revisiting or anticipating.