Integrated workshop

What it is for

The brand, product, and operations meet in the same customer's day. A promise on the website becomes a task in the product and a piece of work for someone behind it. Those connections are worth looking at together.

Use the full workshop when a change crosses those boundaries. Give each part enough time, bring the people who can make the decisions, and keep a shared record as you go. If the question is smaller, choose one of the focused workshops instead.

A bit of everything — brand, product, ops, and marketing in one day.

Tools, in order

Here is where each tool helps. Use an equivalent you already work with if it fits the task and your project’s access requirements.

1. 01

   Before the session

   Notion · Paper or a shared workshop board

   Collect the brand, product, operations, and marketing briefs and mark contradictions before the meeting. Put the decision you need on the first page. Agree on recording, transcription, access, and retention with everyone before starting; handwritten notes are a valid alternative.

   Carry forward A brief, a prepared board, and an agreed capture method.

2. 02

   In the room

   Notion AI Meeting Notes · Paper or a shared workshop board · Phone camera

   Use the recorder to support listening, not to replace a facilitator. Resolve dependencies across disciplines rather than running four unrelated brainstorms. Write decisions and disagreements visibly; photograph the boards with permission. Pause recording whenever someone asks.

   Carry forward Authorized source notes, a transcript if agreed, and labeled board photos.

3. 03

   After the session

   Claude, ChatGPT, or Grok · Notion

   Check speaker names, quotations, numbers, and apparent agreements against the sources. Ask an assistant to draft a joined-up project brief with shared decisions and named unresolved dependencies, with a source ID for each decision and a separate list of open questions. Have participants correct the record before using it as a brief.

   Carry forward a joined-up project brief with shared decisions and named unresolved dependencies

Review the work with partners

We make and revise the work with Claude, ChatGPT, or Grok, then put selected versions on our Studio project pages for partners to review. Check the preview before sharing it. You can do the same with a private prototype or shared document; use a workspace that can access the files you need.

Name the version, say what changed, and ask the question you need answered. Keep feedback with that version and discuss conflicting requests before making the next changes. Confirm approval separately, and keep confidential work in a restricted space.

Delegate the routine work

Turn verified notes into a source-linked table, label board photos, or format the agreed action list. Give the agent only the relevant excerpts and a completed example.

Interpreting disagreement, choosing a direction, and deciding what participants actually approved stay with the facilitator and decision owner.

Sequence prompts, then delegateChoose a model for the design task

Prepare the room

2–4 h + 4–8 h documentation dives

The full stakeholder set: this is the version we run when the engagement covers brand, product, and operations together. Founders and leads stay for the whole session; specialists can rotate in for their part.

Cap the room at ten. The combined version trades depth per topic for the connections between topics: an ops sticky that explains a product sticky is the reason to run it this way.

• One 2–4 hour block with breaks, or two half-days. Whiteboards for four corners: Brand, Product, Ops, Marketing.
• Stickies in four colors, one per corner, so the patterns stay visible when everything gets mixed later.
• Before the session: collect the documentation. After it: 4–8 hours of documentation dives, checking what the wall claimed against the numbers, tickets, and deal notes.

Step 1 · 45–60 min

Four-corner brainstorm

Run the brainstorm from each single-lens script in compressed rounds: brand adjectives, product jobs and pains, ops friction, marketing claims and audiences. Ten to twelve minutes per corner, everyone writing, everything said out loud.

Physically move the group between corners; the change of wall helps restart the flow of ideas. Use the same provocations as in the single scripts.

Step 2 · 45–60 min

Sorting, per corner

Each corner gets its own sort, faster than in the single sprints: brand into yes/no, product into now/next/never, ops into keep/fix/kill, marketing into true/not us. Spend the discussion time where the room disagrees most. That corner is usually the reason the engagement exists.

The stuck-sticky tactics from the single scripts all apply. The facilitator's job is keeping any one corner from eating the day.

Step 3 · 45–60 min

Cross-mapping

This is the step the single sprints can't do. Bring the surviving stickies from all four corners onto one wall and cluster across colors. The patterns to look for cross topics: a brand value with no product behavior behind it, a marketing claim no process can keep true, a product priority that contradicts the brand.

Name the cross-cutting themes, usually three to five, and mark every sticky that contradicts another corner. The contradictions are the agenda for the documentation dives.

Step 4 · 45–60 min

Distilling into the working brief

One document, four short chapters plus a summary: brand values with comparisons; product principles with the now/next/never list; the ops backlog with owners; the message hierarchy with proofs. The summary is the theme list: what ties the four together and what contradicts what.

Then the documentation dives: 4–8 hours checking the wall against reality before anything is presented. What holds up goes into the directions work; what doesn't becomes an open question in the proposal.

What comes out

• The working brief: four chapters (brand, product, ops, marketing), the cross-cutting themes, and the contradiction list, resolved or flagged after the documentation dives.
• The directions are built from this document: generally three or four distinct strategies, presented on the client's workshop page for feedback and sign-off.

Leave the next person enough to work with

Write down what was decided and why, with links to the notes or examples behind it. Keep the open questions alongside the decisions. Someone joining the project should be able to tell which is which without asking you.

Project: [name]
Input sources: [references and permission]
Approved decisions: [choice, rationale, owner]
Assumptions: [what remains untested]
Open questions: [question, owner, due date]
Acceptance checks: [observable pass/fail criteria]
Next step: [person or workflow]
Approval: [name, date, version]

Before you move on

• Can someone who was not in the room understand the result?
• Are claims supported by evidence, with uncertainty labeled?
• Has the responsible person approved the decisions—not just received the document?
• Have you removed private information and checked rights to any assets?

If the summary says something was agreed and you cannot find that agreement in the notes, ask the person who decides before carrying it into the next task.