Insights

The Debrief That Turns Silicon Valley Visits Into Decisions

Vlad Kunov · October 29, 2026

The flight home is not the end of your Silicon Valley visit. It is the beginning of the window in which the visit either changes your roadmap or changes nothing at all. Visits decay in the week after landing. The impressions that felt urgent in the room soften into anecdotes, and the anecdotes never become decisions. What separates a visit that compounds from one that evaporates is a structured debrief in the first 72 hours: the sponsoring executive in the room, the impressions converted into a short action list with named owners, and the 90-day checkpoint booked before the team disperses into its normal week.

The method has a documented lineage, the After Action Review, covered in the next section.

This post walks through the full protocol, from the prerequisites you settle before you land through the four questions, the one-page action list, the sponsor's precise role, and the 90-day checkpoint. It closes with the pitfalls that kill debriefs before they start.

Why the Week After the Flight Home Decides Everything

The visit rarely fails in Silicon Valley. It fails in the seven days after landing, when a strong itinerary meets a full inbox and produces nothing that survives the normal week. Picture a hypothetical Australian leadership team returning from five days inside Google, NVIDIA, Tesla and Airbnb (the SV Executive Academy five-day AI immersion format), then a long flight into a diary nobody cleared. The trip delivered impressions, conversations, exposure. That is input. The roadmap changes only when someone writes a decision, attaches a name and fixes a review date.

No reviewed source quantifies post-visit decay, follow-through or decision rates for executive study tours. Treat the 72-hour debrief window as recommended practice, not a researched finding. A working debrief produces three artefacts: a one-page action list, a named owner on every line and a booked checkpoint before the team disperses. Miss one and you have a trip, not an intervention. For the structural difference between immersion and tour, see What a Silicon Valley Executive Immersion Program Actually Delivers (Beyond Networking). For target outcomes, read What Should a Silicon Valley Executive Immersion Actually Accomplish?.

What the After Action Review Teaches About Debriefing a Visit

The method has provenance worth borrowing. The US Army developed the After Action Review (AAR) in the 1970s to debrief events immediately after they happened, and its four-question spine, as this protocol applies them, is simple: what did we want to happen, what actually happened, why the difference, and what do we do differently next time? Those questions drive Step 2. Public Health Ontario, summarising FEMA's HSEEP, sets an outer limit of three months for an AAR, requires lessons to be linked to planned improvement efforts, and says a review should produce an action plan. That is public health emergency guidance, not corporate travel, so treat three months as a ceiling. The same guidance says AARs rely on open, honest and equal interaction; a neutral facilitator is desirable, though any team member can facilitate. This sits in tension with a sponsor-present debrief, which later sections resolve. AAR practice distinguishes informal reviews, corrected on the spot, from formal reviews after a defined event. A visit is an event: use the formal version, with a date. Design the tour so this debrief has something to review: How to Structure a Corporate Innovation Tour of Silicon Valley That Goes Beyond Campus Photos.

Prerequisites: Who Is in the Room Before You Land

Lock the room before you board. Confirm the sponsoring executive's attendance before departure, not after the team returns; if the sponsor cannot make the first available slot, move the date rather than run a session without them and call it a debrief.

Block ninety minutes in the return week before departure day, listed as the visit's closing session so it reads as part of the trip, not an add-on.

Choose the facilitator deliberately: a neutral person, not the most senior voice, from the group, L&D or outside. AAR guidance calls a neutral facilitator desirable, and in rooms with a wide seniority gap, that desirability becomes acute, a practitioner judgement, not a Berkeley finding.

Cap the room at six to nine people who were on the visit. No observers or substitutes reading someone else's notes. A tight room enables the debrief rituals that convert exposure into organisational action.

Ban slides and trip photographs. Fix the output in advance: one page, three to five actions, each with a single named owner and first checkpoint date. Decide circulation now: the one-pager reaches sponsor and room within 24 hours; only action lines travel further. Availability begins with choosing the right programme.

Step 1: Hold the Debrief Within 72 Hours of Landing

With the room and output pre-set, timing is the first decision, as in the immersion program formats and durations set before departure. Adopt a 72-hour working rule: hold the debrief within three days of landing. The case is practical, not measured; no study in the reviewed sources quantifies post-visit memory decay. Memory is still specific, the itinerary still concrete and the return-week diary not yet refilled. A session three weeks later reconstructs the visit rather than reviews it. Book the first working morning the sponsor is genuinely available, allowing for jet lag from the US west coast. If that slot slips past a week, run it anyway. Stop at ninety minutes; longer sessions drift into storytelling and the action list never gets written. Rebuild the factual base first: itinerary, people met, systems seen and claims made to you. That prevents the group debating what happened instead of why. Keep the wider organisation out; colleagues receive the action list, not the raw conversation. Candour in the room is a precondition for a useful list.

Step 2: Run the Four Questions, Not a Show and Tell

With the record rebuilt, run four questions borrowed from the After Action Review method (this article's working adaptation of the method).

One, desired outcomes. Read the pre-trip brief aloud. What was this visit meant to change, and whom was it meant to inform? With no brief, writing one for the next trip becomes the first action.

Two, actual outcomes. What did you see or hear that was not in the brief? Collect names, numbers, demonstrations. Chase surprises, not confirmations.

Three, why the difference. Which assumptions held, which broke? Push past impressions to decisions you would now make differently, and log claims the group could not verify.

Four, what changes. The only question producing output. Test each candidate: would this change a budget, a hire, a platform choice or a roadmap quarter? If not, it is context.

Guard against the highlights reel. If the session becomes a recap of impressive demos, the facilitator interrupts and returns to question three, where the gap between expectation and reality sits.

Capture dissent. One holdout who thought the visit missed the point is worth more than unanimous enthusiasm. This is not a consensus exercise. Still shaping the trip? Read Ready to Turn a Trip Into a Transformation?.

Step 3: Convert Impressions Into One Page With Named Owners

With dissent captured in the notes, question four has to leave a written artefact. Cap the list at three to five actions. A twenty-line list signals that nothing in particular will happen; one page can be reviewed line by line at the checkpoint. Use a fixed line format: action, one named owner, first checkpoint date. Owner means a person, never a department, committee or pair. Shared ownership is the most reliable way for an action to disappear. This named-owner rule is professional practice, not a sourced finding. FEMA's HSEEP linkage does support tying lessons to planned improvement efforts, so the action list must connect to a real decision, not sit as commentary. Sort lines into classes: decisions the leadership team can take now; pilots to test within 90 days; matters requiring investigation before commitment. Each class carries different owners and evidence requirements. Send the one-pager within 24 hours to the sponsor and the room only. Anything that survives that reading is real; anything dropped was never going to be funded. Keep the page versioned. The checkpoint reviews status against the lines and dates agreed in the room, not a fresh set of priorities drafted later.

The action list lives or dies on candour, and the sponsor is a design problem here. AAR guidance holds that reviews depend on open, honest and equal interaction; this method seats the sponsor in the room regardless. The sources do not resolve that tension, so treat this as a proposed design.

Put the sponsor last on the speaking order. They hear the candid version before framing a conclusion, rather than setting the tone in five minutes while the room edits itself.

Define the job: listen, decide, commit resources. Not steer the analysis or defend the funding decision. A sponsor who interrogates impressions turns the debrief into a report to the boss. Open with one sentence setting permission (I am here to listen, I will commit what makes sense, I will not grade the visit), then hand the room to the facilitator.

Watch for candour dying: silence after the sponsor speaks, fast agreement, the usual voices dominating. Call a short break and restart with the quieter half of the room.

Close with a specific duty: what will be adopted, what will be tested, who will hear about it. Commitment spoken aloud turns a list into a mandate, and a provider's readiness to support that is a practical evaluation criterion.

Step 4: Book the 90-Day Checkpoint Before Anyone Disperses

The sponsor's closing commitment needs a date attached before the room empties. Send the calendar invitation during the debrief, with the sponsor, the owners and the facilitator in the same meeting. A date agreed in the room is a commitment; one agreed by email afterwards is a suggestion.

Frame the checkpoint as a review of the action list, not a second debrief. It runs the same three to five lines, each with a status and a decision: continue, escalate or die.

Ninety days is a deliberate design choice: long enough for a pilot to produce evidence, short enough to interrupt drift. The closest published benchmark, PHO's three-month outer limit for completing an AAR after a public health emergency, is a different context, but the logic of not letting momentum stall applies.

Ask the hard question: did this change anything, or has it become a status update? Each line is renewed on evidence, killed explicitly, or escalated to a decision with a budget attached.

Close the loop publicly. The sponsor states what was adopted, what was dropped and why, so the organisation learns that a visit produces decisions, not a document nobody reopens. If most lines stall, treat it as a design problem for the next visit, not a reason to abandon the method.

Pitfalls That Kill Debriefs Before They Start

The checkpoint protects the method after the fact; these pitfalls kill it before it starts.

Debriefing too late. No corporate source benchmarks debrief timing; the closest analogue is public health emergency guidance recommending completion within three months of an event, a different context, but the direction is the same. A corporate diary refills from Monday, and delay is the most common reason a good visit produces nothing.
Inflation. A fifteen-workstream project plan will not be reviewed. Three to five lines is the method, not a formatting preference.
Hierarchy. When the most senior person speaks first, the room reports rather than reflects, and the gap between expectation and reality never surfaces.
Confusing the informal fix with the formal review. Informal reviews correct on the spot. A visit needs the formal version: written output, named owners and a date.
No owner, no date. A department is not an owner. "Next quarter" is not a date. The checkpoint exists to catch lines written to look decisive.
Retrospective theatre. If the session exists to celebrate the trip and reassure the sponsor, cancel it and spend the ninety minutes elsewhere.

Conclusion: The Debrief Is the Deliverable

Avoid the pitfalls and the method holds. Run the debrief inside 72 hours of landing, Step 1's timing rule, with the sponsoring executive in the room and a neutral facilitator asking the four questions from Step 2. Compress the output to one page with named owners, as Step 3 requires. Book the 90-day checkpoint in the room before anyone disperses, treating it as a review of the list, Step 4's discipline. Manage the sponsor deliberately, as the sponsor section sets out: listen first, speak last, commit out loud, and move the date rather than run the session without them. Be candid that the 72-hour rule is recommended practice, not a measured finding; the defensible part is the structure, a documented review method, an action plan, named owners and a booked review date. Then judge the visit by what changed in the roadmap, the budget or the hiring plan ninety days later. The debrief, not the itinerary, is the deliverable.