← VAF·SA Framework
Skip this module and spend the first few weeks acquiring information that structured pre-engagement analysis would have surfaced before the first meeting. The cost is measured in weeks.
The cost is not theoretical. It is measured in weeks, repeated across every engagement where this discipline was bypassed.
Every engagement has a history. Failed attempts. Contested decisions. Information nobody volunteered. It does not disappear because the briefing omits it. Module 1 surfaces that history before anyone has chosen what to tell you.
Module 1 is not discovery. Discovery assumes a blank slate. Orientation assumes a history — decisions made, attempts undertaken, information withheld — and establishes that picture before any new activity begins.
These five questions are not discovery questions. They orient you to the environment before you enter it. If they cannot be answered before engagement begins, answering them becomes the first output of the first workshop.
1
What has already been attempted?
Every stalled engagement has a history. That history contains the real problem. "Nothing" is itself diagnostic. An incomplete answer means someone is withholding. Both are useful information.
2
Why did it fail or stall?
The stated reason is sanitised. "Budget" means someone did not prioritise it. "Resource constraints" means no one owned it. "Technical complexity" means the vendor could not deliver and the organisation accepted it. Translate the answer.
3
Who owns this on paper — and who actually owns it?
Formal and informal ownership are rarely the same. The person on the project charter is not necessarily the person whose decision resolves the problem. Identify both before the first meeting.
4
What documentation exists and where is it?
Absent documentation is as diagnostic as present documentation. Gaps are evidence. Contradictions are unresolved decisions. Outdated documents are unmade choices. Map the landscape before reading it.
5
Who benefits from this succeeding — and who benefits from it failing?
Politics is the environment architecture operates in. The obfuscating vendor, the resistant team, the absent EA — all have a reason. Find it early. Name it. It will shape every workshop that follows.
Every engagement falls into one of four archetypes — or a combination of two. Get this wrong and you deploy the wrong posture. Wrong posture costs weeks.
Information exists and is being deliberately withheld. The vendor, the client, or an internal party has a vested interest in preventing full disclosure.
Signals
- Vendor confidence without documentation
- Vague answers to direct data flow questions
- Completed POC not being shared
- Decisions made with no audit trail
- Egress described as ingress
VAF Concepts
- Information Asymmetry
- Governance Drag — Deliberate
- Decision Altitude Collapse
Posture — Forensic. Every answer is a hypothesis until independently verified. The heat map is the interrogation instrument. Every blank cell is deliberate, not accidental. Go to unofficial channels. Hold the line until every cell is answered.
Nothing has been done. No documentation. No data classification. No security assessment. No vendor alignment. The engagement exists on paper. It has no architectural foundation.
Signals
- No architecture documents available
- Vendor in transition — merger, rebrand, migration
- Requirements described verbally, never written
- Security concerns listed as "to be addressed later"
- Digital strategy absent or outdated
VAF Concepts
- Negligent Void
- Cost of Inaction — Visible
- Integrity Gap
Posture — Constructive. You are not uncovering what exists. You are building the foundation from scratch under time pressure. The workshop creates the baseline. The heat map identifies every domain needing a decision before design can begin.
The organisation has attempted this before. Multiple times. By multiple parties. No one will own it. History is being withheld or denied. Budget has been spent. Nothing has been delivered.
Signals
- "We haven't really started yet" — 18+ months in
- No handover between previous attempts
- Documents exist but are not being shared
- Pressure applied to you before delivery begins
- $10k+/month spend with nothing to show
VAF Concepts
- Institutional Paralysis
- Governance Drag — Political
- Non-Ownership Cost
Posture — Immersive and Silent. Three months of ingestion if the environment requires it. Read everything. Say nothing under pressure. Discharge the work. Do not complain. Do not fight. Deliver.
Capability exists. The solution is achievable. The parties who need to collaborate have never been in the same room. The problem is human, not technical.
Signals
- Business units with overlapping requirements who have never spoken
- Technical teams with relevant capability never engaged
- "We didn't know they were doing that"
- No shared vocabulary between business and technical
VAF Concepts
- Silo Architecture
- Decision Altitude Collapse
- De-siloing Instrument
Posture — Facilitative. The workshop is the solution. Getting the right people together and establishing a shared language solves 70% of the problem before design begins. Architecture follows alignment.
Existing documentation — however incomplete, contradictory, or deliberately obscured — runs through this protocol. Not cover to cover. Decision-first. What was decided, when, by whom, with what authority. The gaps in that picture are the real intelligence.
Read for decisions first. Read for detail only when the decision landscape is clear. Detailed document review conducted before mapping the decision landscape systematically produces blind spots: the practitioner acquires detailed knowledge of what exists while missing the analytical significance of what does not.
Phase 1 — Inventory
- Request every document. Accept whatever is provided without comment.
- Catalogue: title, date, author, scope, status.
- Note what is absent. Gaps are as diagnostic as content.
- Do not read in depth yet. Build the map first.
Phase 2 — Pattern Reading
- What was decided? When? By whom? With what authority?
- What was attempted and stopped — and why?
- Where are contradictions between documents?
- What vendor commitments are documented vs. claimed verbally?
Phase 3 — Gap Analysis
- Map document coverage against the heat map domains.
- Every domain with no documentation is an open risk.
- Every domain with contradictory documentation is an unresolved decision.
- The heat map skeleton is now populated. Module 3 assigns red/amber/green.
Phase 4 — Synthesis Position
- You now know more about this engagement than anyone who handed it to you.
- You do not say this yet. Complete the workshop. Verify independently.
- Then state it — in writing, with evidence, in the artefact.
The formal authority structure tells you who can sign. The informal authority structure tells you who actually decides. The interest structure tells you who wants this to succeed and who wants it to fail. All three required before the first workshop.
Category 01
Decision Holders
Who can say yes. Who can say no. Who can block with silence. Map the formal authority structure. Then map the informal one. They are rarely the same.
Category 02
Information Holders
Who knows what you need. Who will share it. Who will not. DBAs, security teams, vendors — none of them will volunteer information without a structured request. Name them. Engage them directly in the workshop.
Category 03
Interest Holders
Who benefits from this succeeding. Who benefits from it failing. Politics is the operating condition, not the problem to solve. Find the interest structure early. It explains everything that follows.
Domain A
Architecture Environment
- Does an EA practice exist? Is it functional?
- Are there architecture standards or reference architectures in use?
- What governance gates exist between design and delivery?
- Is the EA involved in this engagement?
Domain B
Delivery Environment
- What methodology is in use — iterative delivery, structured delivery governance, sequential delivery, or hybrid?
- What is the delivery timeline and what are the hard constraints?
- What has already been committed to contractually or politically?
- What budget has been spent and what remains?
Domain C
Vendor Environment
- Who are the vendors? What is each relationship?
- What has each vendor already proposed or committed to?
- Are there existing contracts that constrain the solution?
- What does the vendor roadmap show for 12–36 months?
Domain D
Organisational Environment
- What is the organisation's risk appetite?
- What compliance and regulatory obligations apply?
- What has failed before — and why?
- Who owns the problem today and who will own the solution tomorrow?
ALL ITEMS BELOW MUST BE CONFIRMED BEFORE PROCEEDING TO MODULE 2
Engagement archetype identified. Primary and secondary if mixed. Posture confirmed.
Five intake questions answered — or formally flagged as unknown and added to workshop agenda.
Document inventory complete. All available documents catalogued. Gaps documented.
Immersion protocol initiated. Phase 1 complete. Phases 2–4 in progress or complete.
Stakeholder map complete. Decision, information, and interest holders named.
Environment diagnostic complete. All four domains answered or formally open.
Heat map skeleton populated. Domains mapped, open cells documented.
Module 2 workshop structured. Streams defined, attendees confirmed, objectives set.
Proceeding without completing this module means proceeding without the intelligence base required for accurate design. The cost of that deficiency compounds throughout the engagement and consistently exceeds the time investment required to complete this module.