Post-Meeting Briefing Diff — Armbrain Guides

How to compare what you expected going into a meeting with what actually happened -- and use the gap to improve future briefs automatically.

Overview

Before a client meeting, Armbrain generates a brief with key context, open items, and stakeholder notes. After the meeting, reality often looks different: some topics never came up, a surprise issue dominated the conversation, or a stakeholder's priorities shifted.

The briefing diff compares your pre-meeting brief against your post-meeting observations. It categorizes what you got right, what you missed, what was stale, and what surprised you. The insights are stored back into the client mind so future briefs get smarter over time.

When to Use This

Right after a client meeting while the conversation is fresh
During your /cmo-write flow (the briefing diff is integrated automatically)
When you notice your meeting briefs consistently miss something important
After a meeting where the client raised unexpected concerns

Running a Briefing Diff

The easiest way is through the post-meeting follow-up flow:

/cmo-write

Armbrain asks for your meeting observations and automatically compares them against the most recent brief for that client. If you ran /cmo-prep before the meeting, the brief is already saved.

You can also run it directly:

"Compare my Acme brief against what actually happened in the meeting"

Then provide your observations -- what was discussed, what decisions were made, what surprised you.

What You Get Back

The diff organizes findings into four categories:

Category	What It Means
Hits	Things the brief predicted correctly. These confirm your knowledge base is accurate.
Misses	Topics or concerns that were in the brief but never came up. May indicate stale information or changed priorities.
Stale	Information in the brief that turned out to be outdated. A stakeholder changed roles, a budget was cut, a campaign was paused.
Surprises	Things that came up in the meeting that the brief did not anticipate. These are the most valuable -- they reveal gaps in your client knowledge.

Example output:

Briefing Diff for Acme -- April 1 Meeting

Hits (3):
  - Q3 budget concerns (Sarah raised this as predicted)
  - Creative approval bottleneck (discussed in detail)
  - Website migration timeline (confirmed June launch)

Misses (1):
  - Competitor campaign analysis (prepared but not discussed)

Stale (1):
  - Brief mentioned Tom as design lead; he moved to another team last week

Surprises (2):
  - Acme is considering bringing paid media in-house (not in any memories)
  - New VP of Sales joining next month (stakeholder update needed)

2 insights stored as briefing_diff memories.

How It Improves Future Briefs

Every surprise and stale finding is stored as a briefing_diff memory in the client mind. The next time Armbrain builds a brief for this client, these memories inform what to include and what to flag.

Over time, this creates a feedback loop:

Brief predicts what matters
Meeting reveals what actually mattered
Diff captures the gap
Next brief is more accurate

You do not need to do anything to activate this. The stored insights are automatically picked up by briefing in future briefs.

Tips

Do the diff right after the meeting. The longer you wait, the more detail you lose. Even bullet points are enough.
Include surprises especially. "The client mentioned they are considering an agency switch" is exactly the kind of signal that makes future briefs valuable.
Do not worry about format. Your observations can be stream-of-consciousness notes, a pasted transcript summary, or structured bullet points. Armbrain handles the comparison.
Review stale findings. If the same information keeps showing up as stale, it may be worth updating the underlying memory rather than waiting for the brief to catch it each time.