Paste this into your next Notion or Google Doc brief. The template is educational by design: it forces teams to define outcomes, audience cognition, narrative, experience map, and measurement before money is spent on production.
Most event failures begin as brief failures — vague objectives, undefined objections, and no agreement on what “good” means fourteen days later. Teaching teams to brief well is therefore a commercial skill, not merely a project-management habit. Use the sections below as a shared contract among marketing, sales, partners, and creative.
1. Business outcome
What must be true 14 days after the event? Specify pipeline, meetings, or partner commits in language a finance stakeholder can audit. Avoid atmosphere goals that cannot be inspected.
Write outcomes as observable states: number of qualified meetings booked, partner-sourced opportunities influenced, or enablement actions completed. Name the owner for each outcome. If two teams claim success using incompatible definitions, rewrite until one sentence can be audited. Educational briefs convert ambition into inspectable learning goals.
2. Audience
Titles, industries, and the objection they walk in with. Name the educational gap: what do they misunderstand today that the room will correct?
Be precise about who should not attend. Exclusion criteria protect peer density and learning quality in Hong Kong’s compact market. Document the buyer’s likely mental model — for example confusing a category with a feature, underestimating migration risk, or over-weighting brand familiarity — so speakers can teach against that model rather than delivering generic product tours.
3. Narrative
One story arc for stage, booth, and follow-up email. Include a 60–80 word definition of your category claim and five draft FAQs the room is likely to ask.
The narrative section is the syllabus. Stage, booth, and email must teach the same definition, mechanism, and implication. Draft FAQs before the night so hosts are not improvising claims. After the event, replace draft answers with language that actually surfaced in the room and publish updates on owned pages where appropriate. That is how briefs feed content and GEO systems.
4. Experience map
Arrival → engagement mechanic → capture → exit gift → sales SLA. Each step should produce either learning, data, or a next-step commitment.
Assign an owner and an output to every step. Arrival should set cognitive context (pre-read acknowledgment or question card). Engagement should force structured dialogue, not only networking. Capture should map to CRM fields for role, interest, and objection. Exit should hand a single CTA. Sales SLA should define response timing and talk-track alignment. If a step produces only atmosphere, redesign it before production locks spend.
5. Measurement
Leading indicators (RSVP quality, pre-read completion) and lagging indicators (opportunities, partner commits). Schedule a retrospective that updates the FAQ and narrative kit.
Leading indicators tell you whether the learning design worked before pipeline fully forms. Lagging indicators tell you whether commercial discipline followed. The retrospective is mandatory: within two weeks, review which objections appeared, which partners restated the story accurately, and which brief sections were ignored in execution. Update the template so the next event inherits institutional learning rather than resetting to folklore.
How to run the brief as a workshop
Facilitate the five sections live with stakeholders in one working session. Do not send a blank document and hope for asynchronous clarity. Time-box each section, write decisions in the room, and refuse to approve production until outcomes, audience exclusions, narrative definition, experience owners, and KPIs are explicit. For partner co-hosted nights, add lead routing and approved claim lists as mandatory annexes.
A practical facilitation sequence is forty-five to sixty minutes: outcome and audience first, narrative second, experience map third, measurement last. Capture disagreements in writing. If sales and marketing cannot agree on the fourteen-day success definition, production will amplify that conflict rather than resolve it. Treat unresolved brief items as blockers, not as “to be decided later.”
Moxie can facilitate this brief live with your regional team — book a conversation. The facilitation goal is shared understanding, not decorative slides.
