← VAF·SA Framework
The workshop is the mechanism that converts information asymmetry into shared understanding. Across all four engagement archetypes, the core problem is the same: the right people have never been in the same room. The workshop puts them there and gives the architecture a forcing function to surface every gap, conflict, and unresolved decision.
A meeting discusses. A workshop decides. The difference is structure. A workshop without a designed structure reverts to a meeting within twenty minutes. Meetings produce more meetings. Workshops produce artefacts.
Never open a workshop with a blank page. Open with a strawman — a draft diagram, a partial current-state map, a heat map with every domain showing as open. Give the room something to react to. The strawman is intentionally incomplete. Correcting it together is how shared understanding is built.
The wrong people in the room produces less than no workshop at all. Every extra person who cannot answer one of the ten questions and cannot make a decision is friction. Design the attendee list against a specific purpose: who holds the information you need, who holds the decision authority you need, and who holds the political keys to the doors that are currently closed.
1
Map the three stakeholder categories against the workshop agenda
Decision holders — need to be in the room when the decision moment arrives. Not the whole session. Just that moment. Information holders — need to be available for the technical depth segments. Operations and vendors — separate stream if possible. Mixed rooms with conflicting interests produce defensive answers.
2
Push for the right people, not the available ones
The first attendee list proposed is always the available list, not the right list. The security architect who is "too busy" holds the information that closes three red cells. The data owner who "cannot make that time" is the only person who can answer Question 7. Push once. Push firmly. Document if they refuse.
I need the security architect in the room for the first ninety minutes specifically. That is not negotiable if we are going to close the data sovereignty question in this session.
3
Brief every attendee on their specific role before they arrive
Nobody should arrive at a workshop not knowing why they are there. Send a one-paragraph brief per attendee: "You are there because you hold the answer to X. We will need that answer confirmed in the first thirty minutes." People who know their role perform it. People who arrive unclear become observers.
0:00–0:10
Open with the strawman. Place the draft diagram or partial heat map. Say: "This is wrong. Tell me how."
No preamble
0:10–0:40
Current state confirmation. Walk the strawman. Corrections from the room build the real picture.
Record everything
0:40–1:20
Ten questions — business stream. What are you trying to achieve. What does success look like. What has been attempted.
Business leads only
1:20–2:00
Ten questions — technical stream. Systems. Data flows. Constraints. Integration points.
Technical leads
2:00–2:30
Vendor engagement. Closed questions with named assumptions. Heat map cells named aloud.
Forensic mode
2:30–3:00
Open items. Every red cell assigned an owner and a deadline before the room empties.
No cell unassigned
3:00–3:30
Synthesis read-back. State what you heard, what is agreed, what is open. Confirm in the room before anyone leaves.
Written same day
The opening line matters. Not a welcome. Not a thanks-for-coming. A statement of purpose and a strawman placed on the table.
EXAMPLE OPENING: "I have prepared a draft current-state diagram based on the documentation reviewed to date. It will contain gaps and inaccuracies, and I would welcome the room's corrections. The objective for this session is to confirm the current state, establish the target state requirements, and assign owners to every open question before we close. Shall we begin with the system boundary?"
That opening does four things. States the purpose. Lowers defensiveness by admitting the draft is wrong. Creates a shared task. Gives the room a starting point that is not a blank page.
Conflict Type 01
Vendor vs Technical Lead
The vendor claims the solution does X. The technical lead says it cannot. Both are asserting position. Neither is producing evidence. The room is heating up and the workshop is becoming a negotiation.
Do: Stop both. Reframe. "What are we optimising for here — supportability, risk, or timeline? Let's agree on the constraint and then assess which position satisfies it." Move the argument from ego to engineering.
Conflict Type 02
No Resolution After Two Rounds
You have reframed twice. Both parties have restated their positions. The conflict has not moved. The workshop is now consuming time it does not have on a single unresolved point.
Do: Capture both positions formally. "We have two positions on the table. I am going to record both and elevate this to a governance decision. Neither of you is wrong — this is a decision that needs an authority above this room. We move on."
Conflict Type 03
Political Dynamic Surfaces
Someone in the room is protecting something. Their answers are consistent with an interest, not with the truth. The workshop is being navigated around something they do not want on the table.
Do: Name the heat map cell, not the person. "Domain 07 — Vendor and Commercial — is currently red. The question on the table is: has the vendor commitment been confirmed in writing? Yes or no." The cell is the pressure. Not you.
Conflict Type 04
Nobody Is Talking
The room opened. Nobody responded to the strawman. Silence. Not productive silence — defensive silence. The room has decided to wait you out.
Do: Point to a specific element of the strawman and ask a closed question to one named person. "The data flow I've shown here goes left to right. Is that correct?" One person. One specific element. Closed question. Silence cannot survive a direct, named question.
The E-stop is the moment you call an end to workshop-based resolution and escalate to governance. It is not a failure. It is a discipline. The workshop that runs indefinitely without converging is not a productive workshop. It is an avoidance mechanism.
E-Stop Triggers
If any of these conditions are present, the workshop has reached its limit. Stop. Name the condition. Escalate.
- The same question has been asked twice across two sessions with no resolution.
- A conflict has been reframed twice and both parties have returned to their original positions.
- A decision is required that no one in the room has the authority to make.
- New issues are surfacing faster than existing ones are being resolved — the engagement is expanding, not converging.
- The vendor has deferred the same heat map cell twice. A third deferral is a refusal.
- The workshop has run over time and open items are being carried forward rather than resolved.
When the E-stop fires: state what has been resolved, state what has not, name the decision required, name who needs to make it, and set the deadline. Document it before anyone leaves the room. The workshop has done its job. The governance layer now does its job.
EXAMPLE: "This session has reached the boundary of what workshop-level resolution can achieve on this item. The confirmed outputs are [summary]. The outstanding item—[specific item]—requires a formal decision from [role] by [date]. Without that decision, the design cannot be advanced. I will document this as a formal open item and include it in the risk register before close of business today."
Three outputs are required before close of business on the day of the workshop.
1
Updated heat map
Every cell that was discussed has a new status. Every red cell has a named owner and a deadline. Every new cell surfaced during the session is added. This is not a report of the workshop. It is the living artefact updated by it.
2
Open items list — sent to all attendees
Named item. Named owner. Named deadline. Nothing vague. Not "follow up on security concerns." "Data sovereignty — Domain 02 — confirmed in writing by the CISO — deadline Friday the 15th." Three fields. No exceptions.
3
Updated current-state diagram
The strawman, corrected by the room. This is not a polished artefact yet. It is the confirmed picture of the current state, marked up during the session, cleaned up and distributed the same day. The Architecture on a Page will be produced from this in Module 4. The workshop produces the raw material.
The workshop is not done when the session ends. It is done when the three outputs are distributed. If the outputs are not sent the same day, the decisions made in the room begin to dissolve. Memory is unreliable. Documentation is not.