← VAF·SA Framework
The Velocity Loop is not a separate methodology. It is the cycle that connects Modules 1 through 5 into a single, repeatable practice.
Module 1 constituted the Observe phase. Module 2 constituted the Orient phase. Module 3 constituted the Decide phase. Modules 4 and 5 constituted the Act phase. This module names that structure explicitly and develops the disciplines required to execute each phase with increasing speed and precision.
The Velocity Loop has a single purpose: to reduce the elapsed time between engagement entry and solution delivery. This compression is achieved not by eliminating steps, but by executing each step with sufficient precision to eliminate the need for repetition.
Two engagements of equivalent complexity, commencing on the same date, can produce dramatically different outcomes at the three-month mark. The differentiating factor is not the technical knowledge of the practitioners involved, nor the resources available, nor the seniority of the engagement lead.
It is the operational speed of the analytical and delivery cycle.
Speed without precision produces rework. Precision without operational velocity produces outputs that arrive after the decisions they were intended to inform have already been made. The Velocity Loop is designed to produce neither failure mode: it delivers accurate, decision-enabling artefacts to the appropriate audience at the moment those artefacts are needed.
The practitioner who reads the environment, extracts the intelligence, designs the solution, and delivers the artefact faster than the environment changes holds the advantage. Every other party in the engagement is responding to a situation that has already moved.
The same principle applies in every engagement you will ever walk into. The architect who observes, orients, decides, and acts faster than the environment changes — holds the ground. The architect who waits for certainty before acting is always reacting. Always behind.
Certainty is not the trigger for action. Sufficient information is. The loop incorporates new information as it arrives and adjusts accordingly.
O
Step 01
Observe
Module 1 — Orientation
Establishing situational awareness before first engagement contact. Five intake questions. Four archetypes. Document inventory. Stakeholder map. You are not discovering — you are pattern-matching against what you already know.
O
Step 02
Extract
Module 2 — Intelligence
Get what you need from people who may not want to give it. Ten questions. Plain speech. Vendor interrogation. Information gap map. You know the shape of the answer before you ask the question. Confirm or expose. Nothing else.
D
Step 03
Design
Module 3 — Design
Build the solution. Right tool. Right level. Right audience. context-level diagram. Heat map. Three altitudes. Current state. Target state. Gap. Security embedded. Observability specified. You decide what the solution is. Then you move.
A
Step 04
Deliver
Modules 4 and 5 — Artefacts and Communication
Produce the artefacts. Present them to every room. Raise concerns in writing. Hold the line. The artefact is the delivery instrument. It drives the next decision. The loop starts again from whatever the response reveals.
The four disciplines — Read, Extract, Design, Deliver — are presented in sequence because that sequence applies in most engagements. It does not apply in all of them. The Velocity Loop is continuous and non-linear. The module structure is a starting point, not a constraint.
In an Obfuscation Engagement, intelligence extraction may need to begin before orientation is complete — because you do not know what you are orienting to until you have extracted something from the vendor. In a Silo Engagement, the workshop that belongs to Extract may need to precede the full document immersion of Read — because the room will tell you more in two hours than the documents will tell you in two weeks.
The module sequence is the default path. Archetype recognition determines when to depart from it. Orientation always produces the archetype diagnosis. The archetype diagnosis determines which module runs next.
Obfuscation Engagement
Read → Extract → Read (updated) → Design → Deliver
Intelligence extraction surfaces information that changes the orientation picture. Re-run Read with the corrected information before finalising the current state. The loop runs twice before design begins.
Negligent Void
Read (brief) → Extract → Design → Read (confirmed) → Deliver
Where no documentation exists, document immersion is brief. The workshop creates the baseline. Design begins from the workshop output. A brief return to Read confirms the baseline before artefacts are finalised.
Institutional Paralysis
Read (extended) → Extract → Design → Deliver
The immersion period is extended — sometimes significantly — because the history is complex and deliberately obscured. Extract and Design follow in standard sequence once orientation is complete. Do not compress Read under external pressure.
Silo Engagement
Read (brief) → Extract (workshop-first) → Design → Deliver
The workshop is the primary intelligence instrument. Run it early. The room produces the current-state picture more accurately than any document inventory. Read is brief and supplementary to the workshop output.
New information arrives. The environment shifts. The vendor reveals the data is egress, not ingress. The CISO blocks the integration pattern you chose. The business changes the success criteria after the CIS was signed.
You do not restart the engagement. You do not rerun the full loop. You identify which step the new information belongs to and adjust from there.
This is precision. Not rigidity. The loop is not a conveyor belt. It is a targeting system. You move it to where the problem is.
Trigger
Something you did not know about the environment
A system that was not disclosed. A prior attempt that was hidden. A political dynamic that only became visible after the first workshop. A document that existed and was withheld.
Read. Re-run Module 1 against the new information. Update the archetype diagnosis if it has changed.
Trigger
The intelligence you gathered was wrong or incomplete
The vendor confirmed something in a meeting that their written documentation contradicts. A stakeholder answered a question one way and a document answers it differently. The data flow is not what was described.
Extract. Re-run Module 2. Closed questions. Written confirmation. Independent verification. Adjust the heat map.
Trigger
The design decision needs to change
A constraint emerged that the design does not satisfy. A security control was mandated that changes the integration pattern. An NFR was confirmed that the current architecture cannot meet.
Design. Re-run Module 3 for the affected domain. Issue an ADR that supersedes the previous decision. Update the AoaP.
The loop is efficient because it only touches what changed. If the vendor lied about data direction — you re-run Orient and Decide. You do not restart the entire engagement. The artefacts from the clean steps stand. Only the affected domain moves.
This is not an edge case. It is the common condition.
Across every engagement archetype in this framework — Obfuscation, Negligent Void, Institutional Paralysis, Silo — the EA governance layer was absent. Position papers existed. Standards were published. Nobody applied them. The solution architect inherited the environment and was expected to deliver without the authority the environment assumed they had.
VAF·SA does not require EA support to function. It was built for exactly this condition.
The Authority
The artefact holds the line when no one else will
You do not need a title to produce a Customer Impact Statement. You do not need EA sign-off to run a workshop and produce an Architecture on a Page. The artefact is the authority. It holds the line because it is the evidence — and evidence does not require a job title.
The Pressure
Silence under pressure is not inaction
Three months of immersion while they say you have not moved. Two weeks of intelligence gathering while the vendor pushes for sign-off. The Velocity Loop is running the entire time. You are not stalled. You are Observing and Orienting. The Act step will come. It will be precise. It will be faster than anything they attempted before.
The Escalation
Document the absence. Formally.
If EA support is required and not provided — write it down. Not as a complaint. As an ADR. "This decision was made at SA altitude because EA governance was unavailable." The record shows who was absent. The record shows the decision was not made in a vacuum. The record protects you.
The Standard
Your output is the benchmark
When you deliver what nobody else could — in three months, in the Archetype 3 environment, after twenty-four months of institutional paralysis — the artefact set becomes the standard the organisation measures against next time. Not because you told them. Because the evidence speaks for itself.
These are not aspirational statements. Every decision in every module of this framework was made against one of these four principles. When a decision felt uncertain — when the vendor was pushing, when the practice manager was absent, when the timeline was shrinking — one of these four is the answer.
I
No Process First. Outcome Leads.
The framework is the vehicle. The outcome is the destination. enterprise architecture methodology, security architecture practice, structured delivery governance, context diagram — all instruments. None of them is the work. The work is delivering a solution. When the framework starts to feel like the goal, the principle is being violated. Stop. Return to the outcome. Ask what the client needs to see by Friday. Work backwards from that.
II
Decision Altitude. Every Decision at the Right Level.
Business decisions belong at business altitude. Technical decisions belong at technical altitude. When a technical decision is being made in a business room, stop the meeting. Name the altitude. Move the decision to the right room. When a business decision is being made by a technical team, do the same. The altitude discipline is not bureaucracy. It is the thing that prevents two years of wasted motion.
III
One Artefact. If It Does Not Fit On One Page, The Thinking Is Not Done.
The second page is where incomplete thinking hides. The third page is where nobody reads anymore. One page forces precision. It forces the removal of everything that does not drive a decision. The test is simple: place it in front of the room. If they need a second page to act on it, the first page has not done its job. Rewrite the first page.
IV
Velocity Over Volume. Insight Delivered Fast Beats Documentation Delivered Late.
A complete requirements document produced six weeks after the decision was made changes nothing. An Architecture on a Page produced in week two changes everything. Volume without velocity is overhead. Velocity without accuracy is noise. VAF·SA produces accurate insight at speed — because the loop is running from day one and the artefacts are built on evidence, not on hope.
Velocity over volume is a principle. Clients and governance bodies who commission engagements by the day or the deliverable will eventually ask for evidence that the principle was honoured — that speed did not substitute for rigour. Three measures answer that question. They are simple enough to track without additional tooling and precise enough to be defensible in any review.
01
Time to First Artefact
T2FA
The number of working days from engagement start to the first signed Customer Impact Statement. This is the primary velocity measure. It tracks how quickly the engagement produces its first decision-enabling output — not how quickly activity begins. Activity beginning on day one is not velocity. A signed CIS on day ten is.
Target range: 10–20 working days for standard engagements. Up to 30 for Institutional Paralysis archetypes where extended immersion is required. Anything beyond 30 without a documented reason is a loop that has stalled.
02
Heat Map Closure Rate
HCR
The percentage of heat map cells moved from red or amber to green per week, averaged across the engagement. This measures decision production — not document production. A cell moves to green only when the relevant information has been confirmed and independently verified. A high closure rate with unverified green cells is not velocity. It is compliance performance.
Target range: 15–25% of open cells resolved per active engagement week. An engagement where the closure rate is below 10% for two consecutive weeks has identified a blocking condition. Name it and apply the escalation protocol.
03
Decision Velocity
DV
The number of Architecture Decision Records reaching Accepted status per engagement week. This is the direct measure of architectural progress — each accepted ADR is a decision that will not be re-litigated, a pattern that is locked, and a piece of the design that is confirmed. A high ADR acceptance rate indicates that the loop is producing decisions rather than discussions.
Target range: 1–3 ADRs accepted per active week in the Design and Deliver phases. Zero ADRs accepted for more than two weeks indicates either that no significant decisions are being made, or that decisions are being made without being recorded. Both are problems.
These three measures exist to answer one question: was the speed of this engagement the result of structured analytical work, or of shortcuts that deferred risk to delivery? T2FA measures how fast the foundation was laid. HCR measures how systematically risks were closed. DV measures how rigorously decisions were made. Together they constitute an evidence trail, not a performance metric.
All three measures are available from the artefacts the framework already requires. T2FA from the CIS sign-off date. HCR from the heat map version history. DV from the ADR register. No additional tracking system is required.
Engagement completion is not defined by project management milestones, stakeholder satisfaction at a point in time, or the expiry of a contracted timeline.
An engagement is complete when the artefact set is comprehensive and consistent, the Velocity Loop has run without unresolved gaps, and the delivery team is equipped to execute without ongoing architectural oversight.
This is a specific, objectively testable condition. Each criterion below is either satisfied or it is not.
VAF·SA Engagement Complete
→
All six module gates passed. Every checklist item confirmed across Modules 1 through 5. No items carried forward as "to be resolved."
→
Customer Impact Statement signed. Decision confirmed. Named person. Named date. In writing.
→
Architecture on a Page confirmed by all three zones. Executive, architect, and PM have each read their zone and confirmed it is accurate.
→
Heat map has no blank cells. All red cells have a named owner and a named deadline. All green cells have been independently verified. All grey cells have a documented reason.
→
ADRs cover every significant decision. Status set. Decision makers named. Alternatives documented. Nothing significant decided without a record.
→
All concerns are in writing with owners and deadlines. No verbal-only concerns. No unassigned risks. No undocumented objections.
→
The delivery team can operate without you. They have the artefacts. They have the ADRs. They have the heat map. They know what each red cell means and who owns it. They do not need you in every meeting to know what was decided and why.
→
The loop ran clean. No information emerged late that changed the design without a corresponding ADR. No architectural decision was made informally. The record is coherent from first workshop to final artefact.
The engagement is not done when you leave. It is done when the artefacts can answer every question the delivery team will ask after you leave. Build that record. Then leave.
Six modules.
Two pillars.
One loop.
How to think.
How to talk.
One page.