Documentation

Field study 01 · Creative operations

A campaign room where strategy, copy, and visuals share one memory

A creative director, strategist, client lead, and specialist agents move from a living brief to campaign concepts without rebuilding context at every handoff.

Illustrative field study. This playbook is assembled from current Dana4 capabilities. It is not a claim about a named customer or guaranteed campaign performance.

The situation

A campaign rarely fails because the team cannot make another draft. It slows down because the brief, source research, visual references, feedback, and rationale live in different tools. The copy agent sees the prompt but not the moodboard. The designer sees the moodboard but not the client correction made yesterday. A human becomes the integration layer.

Dana4 makes the campaign workspace the integration layer instead. Documents hold the artifacts; threads keep discussion attached to the artifact; people and agents join the same workspace; and repeated sequences become automations.

People

Creative director, strategist, designer, account lead, and client reviewer.

Agents

Arlo for research and synthesis, Alek for visual generation, plus any invited specialist.

Shared artifacts

Campaign brief, brand guide, audience notes, moodboard, concept directions, and launch copy.

Durable context

Document conversations, searchable history, topic groups, and the workspace knowledge graph.

The working pattern

  1. The creative director writes the brief in a shared document and links the brand guide.
  2. Arlo researches the category and posts findings into the brief conversation.
  3. The strategist narrows the territory; Alek generates visuals from the same context.
  4. The team records the chosen direction and keeps the rejected rationale with it.

The important detail is where the conversation happens. Instead of opening a detached chat and pasting a brief, the team starts from the brief itself. A prompt such as @arlo.dana4 compare these three positioning territories against /Brand guide gives the agent a bounded workspace, a visible source document, and a thread where the answer remains discoverable.

When a visual direction is ready, the team can tag Alek in that conversation. The generated asset and the discussion that produced it stay connected to the campaign rather than disappearing into a personal image history.

Workspace setup

AreaSuggested contents
strategy/Campaign brief, audience, positioning, competitive notes
brand/Voice, visual system, claims, prohibited language
concepts/One document per creative territory and its feedback
production/Approved copy, assets, channel adaptations
ThreadsQuestions and decisions attached to the document they affect
AutomationsRecurring research, status summaries, and asset preparation

Start small. A brief, a brand guide, Arlo, and Alek are enough for the first cycle. Add another agent only when it owns a distinct capability the team can name and evaluate.

What becomes reusable

The first campaign teaches the workspace how this team works. The team can then turn the stable parts into a workflow:

  1. research the market and audience;
  2. create one dated research document;
  3. post a short summary into the campaign channel;
  4. ask a specialist for concepts using the stored research;
  5. leave final selection and approval with the creative director.

Use automation for repeatable preparation, not for hiding creative judgment. The brief, selected direction, and reasons for approval should remain legible to the people accountable for the work.

What to look for

This pattern is working when the team can answer these questions without reconstructing history:

  • Which brief and brand rules produced this concept?
  • What did research change?
  • Who chose this direction, and why?
  • Which other documents and conversations belong to the same campaign topic?
  • Can a new contributor understand the current direction before the next meeting?

The output is not merely more content. It is a campaign memory that the next human or agent can inherit.

Try it

  1. Create a workspace for one campaign.
  2. Add the brief and brand guide as separate documents.
  3. Invite Arlo and Alek from the workspace member dialog.
  4. Open the brief and ask Arlo one research question using / to reference the brand guide.
  5. Continue the discussion in the resulting thread, then ask Alek for one visual direction.
  6. Open Threads → Grouped to see how the conversation connects back to campaign documents.

See every use case →