Who it's for
The people who make things
Run it at handoff, once the guide, templates and tools are live and a few weeks before launch. It's for the client team that will produce the brand day to day. It is not the whole-staff roadshow and not the AI design skill session; those are separate trainings.
Most of the room
Staff who use templates
Program, development and operations staff. They make Word documents and decks, and they need the words and a few rules, not a design class.
2–4 people
Marketing and comms
The team that makes social posts, flyers and emails in Canva with the brand fonts, and reviews what everyone else makes.
Optional
Outside designers
Freelancers and agencies the client hires. Invite them, or send them the recording and the guide link afterward.
Outcomes
What the team leaves able to do
We judge the session by what people can do on their own the next week, not by how complete the tour of the guide was.
Say it
Explain the brand's purpose and promise in one sentence of their own, before anyone mentions the logo.
Make it
Start a real piece from the right template, using the guide's tools, and export it correctly for print or screen.
Catch it
Spot the most common mistakes for this brand and know the fix for each one.
Route it
Know which tool is theirs, who reviews what, where to ask questions and what happens on launch day.
Roles
Four Hyperakt roles, named in advance
One person can't present, watch the clock and take notes. Assign the roles the day before. On the client side, the brand lead opens the session and one maker drives the live build.
Usually the CD
Presenter
Runs the system, live build, spot-the-fix and how-it-runs blocks. Stops talking at eight minutes and asks a question.
Usually the strategist
Words lead
Leads the purpose and promise block and the say-it exercise. Answers any question about messaging.
Usually the PM
Timekeeper
Holds every block to its time, signals the presenter at minute seven, and runs the closing Q&A.
Anyone else
Recorder
Records the session, logs every question and the answer given, and sends the recording and deck within 24 hours.
Prep
Before, during and after
Ask for real material as early as you can; with the invite is best. Without it there is nothing to build live, which is how the first session lost its hands-on half.
The day before
- Ask each attendee to bring one real item from their rebrand list: a flyer, a slide, a social post, a report cover. Send the ask through the client lead.
- Check the invite list. Whoever owns words should be there. Ask the client lead about anyone missing.
- Write the deck from the live guide, not from memory. Copy rules from the guide pages and check every slide against them.
- Build the spot-the-fix mockups: 4 or 5 pieces, each with one mistake drawn from the client's real pain points.
- Check the templates and Canva brand kit match the latest guide before you build in them live.
- Pick one guide link and use only that one, in the deck and the follow-up.
- Assign the four roles and fold in any training questions the client sent.
The day of
- Open the tools before the call: the guide, the template you'll build from, the guide's makers and Canva, each in its own tab.
- Collect the items people brought and pick one for the live build.
- Agree who drives the live build: a client maker, or the presenter sharing their screen.
- Start recording as the session opens. Say that it's recorded and will be shared.
- Put the guide link in the chat in the first five minutes.
Within 24 hours
- Send the recording and the deck to every attendee and the client lead, the same day if you can.
- Send the question log, with an answer for anything we said we'd look into.
- Fix the guide wherever the session showed a rule was unclear or missing.
- Update this playbook: add a row to the lessons and bump the version.
The session · 60 minutes
Run of show
Words first, then the system, then hands-on. No one talks for more than eight minutes without asking the room a question. Times are a starting point; the order is not.
Open with the stakes
The client lead says why this matters and when it happens: the last day for old materials and the launch date. Then we say what everyone leaves with: the guide, the templates, the rules and one place to ask questions.
MoveLet the client open. The brand belongs to them, and the room hears that from their own leader.
Done whenEveryone knows the launch date and what they'll have by the end of the hour.
The brand in one breath
Purpose, promise and personality, taken word for word from the live guide. Many staff believe a rebrand is just a logo. Starting here shows them it isn't. End with the say-it exercise.
MoveRead the promise once, then ask three people to say it in their own words.
Done whenThe room has heard the promise in at least three voices that aren't ours.
The system is a trampoline
"A trampoline, not a straitjacket." The six foundations, with only this client's specifics: logo, color, type, the signature graphic elements, photography and grid or layout. One slide each, one rule that matters most, one example. Then the order of work: audience and purpose, then format, then start from the guide's closest layout.
MoveStop at minute eight and ask: "Which of these will you use first?"
Done whenSomeone other than us has asked a question.
Brand architecture, in two minutes
How programs, funds and campaigns sit under the brand, and the one rule that prevents most trouble: nobody makes a new logo for a program without sign-off from the brand owner.
MoveSay the sign-off rule plainly, and name the person who signs off.
Done whenPeople know who to ask before they make a new mark.
Live build
Build one real item someone brought, from the client's own template and the guide's tools. See the live build steps.
MoveNarrate the decisions, not the clicks: why this template, why this color, why it's ready to export.
Done whenA finished piece the client could use this week is on screen and exported.
Spot the fix
Show the mocked mistakes one at a time. The room calls out what's wrong and how to fix it. See the exercise.
MoveWait for an answer before you reveal one. Silence is fine for ten seconds.
Done whenThe room, not us, has named most of the fixes.
How it runs
Tools by audience, who reviews what, the one brand channel, export and print settings, and the launch plan. Details in How it runs.
MoveOne slide per topic. Ask the client lead to confirm the channel and the reviewers out loud.
Done whenEach person knows their tool and who reviews their work.
Questions, then what's next
Open questions first. Close with a single "what's next" slide: when the recording and deck arrive, and any follow-on sessions already in the plan. That slide is the only place services come up.
MoveIf a question is about something we could build for them, log it and answer in the follow-up.
Done whenWe end on time with every question logged.
Start with the words. The logo comes second.
Exercises
Three ways to get the room working
Each one puts the client's own words or work on screen. None of them needs software installed in the room.
Words block · 3 min
Say it in your words
- Show the promise on screen and read it once.
- Hide it. Ask each person to write it in one sentence of their own, in the chat or on paper.
- Read three aloud. Point out what each one kept and what it lost.
- Show the original again.
Live build · 10 min
Build one real piece
- Pick an item someone brought, and the format and tier it belongs to.
- Start from the client's template, never a blank page.
- Swap in their copy.
- Add a graphic element from the guide's tools (a pattern or frame maker), then check color balance and contrast.
- Export twice: a PNG at 2x for screens and a PDF for print.
Spot the fix · 10 min
Find the mistake
- Build 4 or 5 mockups the day before, each with one mistake.
- Base every mistake on a pain point the client has named, not a generic list.
- Show each one. The room says what's wrong and how to fix it.
- Show the corrected version next to it.
Spot-the-fix examples
Area Foundation
- A pink flood: the brightest color covering far more than its share of the piece.
- Body text set on the bright pink.
- The two-tone wordmark on a colored ground, where it should be one color.
- A straight accent rule where the guide uses a brushstroke.
- A made-up logo for a fund.
Futureful
- The signature graphic used twice, or in flat color instead of a gradient.
- The graphic placed over a bright color.
- Type in a color other than the two approved text colors.
- The same color combination repeated across a whole piece.
- A logo altered, rotated or recolored.
How it runs
Tools, reviews and launch
This block is what keeps the brand consistent after we leave. Settle the answers with the client lead before the session, so it's a summary, not a debate.
Office
For most staffWord and PowerPoint templates with the Office fonts. Most people will only ever touch these, so show them first and keep it simple.
Canva
For marketing and commsThe brand kit, the templates and the brand fonts. Social posts, flyers and event graphics start here.
Pro tools
For outside designersThe guide, the source files and the logo package. They license the brand fonts themselves.
Governance
Who reviews what
Name the team that reviews and the three points it reviews: the brief, the first draft and the final. Anything new, like a program logo, goes to the brand owner.
One channel
One place to ask
A single shared channel for brand questions, in whatever tool the client already uses (Teams or Slack). Answers there become updates to the guide.
Export
The right file for the job
PDF for print. PNG at 2x for screens. Pantone specs for anything printed by a vendor. The office printer is not a proof: its colors will be off.
A clean-break launch
1 month out
The plan is ready
The launch plan is written and owned, and the last day for old materials is set.
Launch day
Switch everything at once
A website banner, one article that tells the story, and the first post in a social series.
Launch week
Keep it moving
The rest of the social series and a newsletter. No old materials go out after launch.
What went wrong before
Lessons from earlier sessions
The first version of this training ran with Futureful (Sep 15, 2026). The framing landed, and one attendee called it the most comprehensive design class they'd sat through. These are the things we changed for the next one.
What worked, so we kept it
- "A trampoline, not a straitjacket" as the frame for the system.
- A clear order of work: audience and purpose, then format, then start from the guide's layouts.
- Plain governance: who reviews what.
- One shared channel for brand questions.
- A clean-break launch plan, ready a month ahead.
What we learned
- Start with the words. Opening on the logo confirms the belief that a rebrand is just a logo.
- Talk less than eight minutes at a stretch. We talked for 30 minutes before the first question, and nobody interrupted even though they were invited to.
- Teach to the whole room. Most staff only use the Office templates. A design-heavy session makes them stop asking questions.
- Ask for real material ahead. We didn't, so the live build was cut.
- Make sure attendees have opened the tools. Otherwise questions drift to narrow cases in tools they don't own.
- Do the exercise in the session. "Everybody play designer and share back" came up at minute 48. Spot the fix is that idea, built in.
- Write the deck from the live guide. Slides written from memory contradicted the guide and were fixed on the day.
- Make it interactive. An earlier client told us a walkthrough they could have read in a document or watched as a video wasn't enough.
- Keep services out. Offers to build things diluted the training. They now get one slide at the end.
Changelog · v0.1 (Oct 19, 2026): first playbook, written from the Futureful session and the Area Foundation session plan. Update it after the Area Foundation session on Oct 20.
Sources · Area Foundation Brand Training deck, Oct 20, 2026 · Futureful Brand Training recording (Fathom) · Futureful Brand Training deck · Earlier client feedback, D & J Daily, Oct 9