The First 10 Minutes We Spend On A Brief

Every event brief that lands in our inbox gets the same first ten minutes.

Not a formal review. Not a scoring rubric. Just four passes — each of them is answering a specific question about whether the brief can support what it's asking for. By the tenth minute we usually know whether we can help.

Here's what those ten minutes actually look like.

The four passes, in order:

1. Read for the feeling target — what the audience should walk out feeling
2. Check for three specific names (or three titles) the experience is really for
3. Name the next decision downstream that this event makes easier
4. Write the Monday sentence in advance — the one people say unprompted

Read for the feeling target (00:00–02:30)

The first thing we do is scan the brief for the feeling — what the client wants attendees to walk out with, emotionally. Not what they want them to know. Not what they want them to have seen.

What they should feel.

Nine briefs out of ten don't answer this. They say things like "engaged," "inspired," "aligned." Those aren't feelings — they're outcomes without a mechanism. The briefs that name the feeling ("reassured that we're the right long-term partner," "understood, finally, by their own company," "confident enough to take the leap") are the ones we know we can design against.

If the brief doesn't answer this, we don't reject it — we ask. Sometimes the answer is already in the client's head; they just didn't write it down. Sometimes it's not, and the conversation that surfaces it is the most valuable thirty minutes we'll have together.

Check for three specific names (02:30–05:00)

Next: who is this experience actually for?

We look for three names — or three titles. Not "the C-suite." Not "our clients." Not "the community." Three specific humans who need to leave changed.

This is where a lot of briefs quietly fall apart. The brief will say "1,000 attendees expected" and then never distinguish between the 3 people whose opinion actually determines whether the event was worth the budget, and the 997 who make up the room. Both matter — but the design has to be built around the three. The 997 are the environment.

When the brief already names three specific people (or three specific personas by title), the rest of the work gets radically easier. When it doesn't, we go looking. Sometimes on the call. Sometimes over follow-up email. But we don't move to design until we have the three.

Name the next decision (05:00–07:30)

The third pass is the commercial question. What decision does this experience make easier to make next?

Every brief we take on ladders to a moment downstream — a deal that closes, a hire that lands, a renewal that survives, a campaign that gets green-lit. If we can name the next decision, the event has a job. Budget conversations get shorter. Trade-offs get clearer. "Should we cut this from the run-of-show?" becomes answerable, because we can ask whether it moves the next decision or not.

At Mochi Collective, we've watched this reframe unlock budget conversations more than once. This is also, incidentally, where finance teams stop pushing back on event budgets. The moment an event is "the setup that gets us to X decision by Y date" rather than "an offsite," the ROI conversation reframes entirely. That's not spin. It's the same event, described in the language of the people signing the invoice. Every engagement we take on ships with a proof report — see how that works in our Impact Measurement practice.

Write the Monday sentence (07:30–10:00)

The last two and a half minutes are the sharpest test. We try to write, in advance, the one sentence the right people will say to each other on Monday morning.

Not a marketing tagline. Not a takeaway from a slide. The actual sentence — informal, unprompted, said in a corridor or over Slack.

If we can write it, we can design for it. Every catering choice, every timing decision, every element of the run-of-show gets held up against the sentence: does this contribute? If it does, keep it. If it doesn't, cut it.

If we can't write the sentence, one of two things is true: either the brief needs more work (and that's what the Brief Diagnostic call becomes), or the event isn't really about what the brief claims it's about. Both are useful things to learn in the first ten minutes.

By the tenth minute, we usually know

The output of these ten minutes is a yes, a maybe, or a "not right now."

Sometimes the honest answer is no — the brief isn't wrong, it's just not what we do best. We say that, and point to whoever we think can help. This costs us nothing and buys enormous trust with people who eventually come back with the right brief.

Sometimes the answer is maybe — the brief has good bones but needs sharpening at the top. This is when we suggest a Brief Diagnostic call: 30 minutes, free, to work through the six questions that fix the top of the brief before we discuss whether to work together on the build.

And sometimes the answer is yes, and we'd love to — the brief already knows what it wants and just needs a team to build it.

Either way, by the tenth minute the client has more clarity than they walked in with. That's the promise. And it happens the same way every time.

Want to know what we'd say about your brief?

The Brief Diagnostic is a free 30-minute conversation where we run these ten minutes on your actual upcoming event, community programme, wellness retreat, or brand activation.

You'll leave with an honest read on whether your brief can land, where it's weak, and what to sharpen before you commit budget.

Book yours: zcal.co/mochicollective/discovery

No deck. No pitch. Just your brief and ten of the same minutes we spend on every one that lands in our inbox.

Related reading:

• 6 Questions That Should Live At The Top Of Every Brief — the questions we use in this process
• 5 Red Flags We Spot In Event Briefs — what the "no" briefs have in common

Mochi Collective — experience design and event curation in Singapore. Events, community programmes, wellness retreats, brand activations.