The kickoff workshop agenda we run before every build

I've produced around ninety builds at Brassfern, and I can tell you within a fortnight which ones had a good kickoff. It's not magic. A good kickoff does three jobs: it makes the plan real (not the proposal version — the actual one, with dates), it surfaces the risks everyone was too polite to mention during sales, and it teaches both teams how to make decisions together before decisions get expensive.

A bad kickoff is a two-hour meeting where someone presents the deck from the proposal phase, everyone nods, and the project starts properly three weeks later when the first misunderstanding arrives pre-loaded with resentment.

Here's the half-day agenda we actually run, verbatim, with the reasoning attached. Steal it.

Before the agenda: who must be in the room

The guest list is the kickoff. Ours for a typical 12-week build: from the client, one decider (singular — the person whose "yes" ends arguments), one day-to-day owner, whoever controls the content budget of the project (writer, marketing lead, domain expert), and one engineer if there's an integration. From our side: the whole squad — designer, engineers, me. Five to nine people total. More than nine and you're running a webinar, not a workshop.

Two rules about attendance, stated in the invite:

The decider stays for the whole session. Kickoffs decay the moment the decider leaves at 10:30 "for a call." The risk round and role mapping exist precisely for them.
No spectators. Everyone in the room has a job in the agenda below. Observers dilute candour; candour is the entire product of this meeting.

The agenda (half-day, 9:00–13:00)

Time	Block	Output
9:00	Walk the plan, then edit it	Annotated plan, decisions started
9:50	Success, defined in numbers	One measurable success statement
10:15	Coffee	—
10:25	"What would make this fail?"	The risk room, named and owned
11:10	Role mapping and cadence	RACI-ish map + weekly rhythm
11:50	Ways of working	Feedback norms, tools, access
12:30	Close: first fortnight	Owners and dates for every action

9:00 — Walk the plan, then edit it (50 min)

I walk the whole plan: phases, milestones, demo dates, dependencies. This takes twenty minutes because it must be legible in twenty minutes — if your plan needs an hour of narration, the plan is the problem. Then the important part: red pens. Where is this wrong? Where does it collide with a product launch, a board cycle, a key person's leave? The proposal timeline was written by people who didn't know your constraints; this is the room where it learns them.

The kickoff plan you end with is worth ten times the proposal plan you walked in with, because it's been corrected by the people it has to survive.

9:50 — Success, defined in numbers (25 min)

One sentence, written collaboratively on the wall: "By [date], [measurable thing] will be true because of this work." "Launch the site" is not it — launch is the baseline, the cost of entry, not the success. Real versions from recent kickoffs: "By October, qualified demo requests run at 45/month, up from 28." "By launch+90 days, support tickets about billing drop by a third."

This sentence later becomes the spine of every status update and the anchor for scope conversations — "does this request move the sentence?" is a much shorter argument than the alternative. If you haven't written a measurement plan yet, this block tells you exactly what it must contain.

10:25 — "What would make this fail?" (45 min)

My favourite block, and the one clients are usually quietest in, at first. Round-robin, one risk at a time, no solutions allowed yet — just fears, spoken out loud and written where everyone can see. I seed it if needed: "I'll go first. My fear is that content arrives in week nine for a week-eleven launch."

Then it pours out. The CEO who might rewrite the headline the night before launch. The legacy CRM nobody's integrated with because the documentation is a lie. The legal review that takes three weeks and nobody owns. This is the risk room, and getting it named in hour two instead of week eight is worth the workshop's entire fee. Every risk leaves the block with an owner and a mitigation, or a note that it's accepted. Accepted is fine. Unspoken is not.

11:10 — Role mapping and cadence (40 min)

We map roles against decisions, not job titles. For each recurring decision type — design sign-off, copy approval, scope changes, release timing — who contributes, who must be consulted, and who decides. The decider discovers here that they can't decide everything; the day-to-day owner discovers what they're actually empowered to approve. We've written separately about aligning stakeholders without design by committee — this block is that article, enacted in forty minutes.

Then the weekly rhythm gets its dates: the demo (ours are Fridays, non-negotiable — demo culture is the heartbeat of the whole engagement), the async written update, the standing decision-point meeting if one exists. Everything lands in calendars in the room, not as a follow-up task that dies in someone's to-do list.

11:50 — Ways of working (40 min)

The unglamorous, load-bearing block: feedback norms ("specific and within 24 hours beats comprehensive and Monday"), which tool is the source of truth (one — the second tool is where information goes to be lost), how to raise a scope change (without drama), permissions and credentials, and — always — content. Who writes, who approves, when it starts. We start content in week one of design now, a habit that came directly from a decade of week-nine scrambles.

12:30 — Close: the first fortnight (30 min)

Every action from the day gets an owner and a date, in writing, before anyone leaves. Then each person — both teams — says in one breath what they personally need to deliver in the next two weeks. It sounds like ceremony. It is, deliberately: it's the moment the project stops being a document and becomes a set of humans with promises. The first two weeks after kickoff have their own dynamics, and they're much happier ones when they start from named commitments.

The artefacts that leave the room

Four documents, all produced live, none longer than a page:

The decision log — started in the first block, appended forever after. Date, decision, decider. The single most valuable document in a project, because it's the antidote to "wait, when did we agree that?" It's also our licence to hold the line kindly in week ten.
The success sentence — pinned to the top of the project space.
The risk room — reviewed at every milestone, crossed off with ceremony.
The role map + cadence calendar — the working agreement.

Failure modes of kickoffs (so you can dodge them)

The replay — presenting the proposal deck again. If the room learns nothing new, you've spent half a day on fan service.
The missing decider — everything role-mapped "tentatively." Tentative decisions are queues.
Risk round theatre — risks stated so diplomatically they carry no information ("resourcing challenges"). Named risks or none.
The follow-up finish — actions captured "to be confirmed later." Later is where kickoffs go to die.

Key takeaways

A kickoff has three jobs: make the plan real, surface the risks, teach the teams to decide together.
Cap the room at nine; require the decider for the whole session; ban spectators.
Write the success sentence in numbers — launch is the baseline, not the goal.
Run "what would make this fail?" before trust is scarcer. Every risk gets an owner or an explicit acceptance.
Start the decision log in hour one and never stop it.
End with owners and dates for the first fortnight, spoken aloud by each human.

FAQ

Half a day — really? What about a full day? Fatigue is the enemy of candour. Half a day, run tightly, beats a full day that dissolves into side conversations after lunch. If the project is genuinely sprawling (multiple workstreams, ten-plus stakeholders), run two half-days a week apart rather than one long day — the gap lets the first day's edits settle.

Should the whole client team attend? No — see "no spectators." One decider, one owner, one content authority, one engineer. Everyone else gets the four artefacts and a standing invitation to the Friday demo, which is where the wider team belongs.

What if the decider genuinely can't attend? Move the kickoff. A kickoff without the decider produces a plan the decider hasn't bought and a role map drawn around an empty chair. It's the one scheduling hill we die on.

Do you charge for the kickoff? It's day one of the engagement, so yes — but the output belongs entirely to the client, artefacts included. If the engagement evaporated after kickoff (it hasn't happened yet, and may the ferns preserve that record), the client would still own a usable plan.

How does this change for a retainer? Compress it into ninety minutes: success sentence, risk round, cadence. Role maps on retainers re-form monthly, which is healthy — but the decision log and the success sentence carry forward unchanged. If you're weighing the two shapes, here's our honest guide.

Want to see how this fits the rest of how we work? Our approach is the long version, and we're one form away from the short one.