A creative team can have plenty of research and still write every brief from memory. Customer language lives in one document, performance results in another, and the reason a concept was rejected disappears into a conversation.
AI can generate more concepts from that fragmented context. Whether those concepts deserve production time is a separate question.
Alex Cooper’s proposed “Brand Brain” brings brand, customer, creative, and performance knowledge into a persistent system. Its useful feature is the connection between context, production, evaluation, and learning, including explicit checks on evidence and claims.
Start with a small version. Every record should help someone choose what to make, what to say, what to test, or what to stop.
Build around one creative decision
Choose one channel, one audience, and one recurring briefing process. Define the decision the system should improve: for example, which customer problem the next creative batch should lead with.
That boundary matters. A customer objection from one market may not apply in another. A result from a promotion may say little about everyday demand. Keeping the initial scope narrow makes these mismatches easier to spot.
The operating loop is straightforward:
- Collect evidence relevant to the decision.
- Turn that evidence into a testable hypothesis.
- Write and check the brief.
- Produce and launch the creative.
- Record results with their measurement limits.
- Decide what to repeat, change, or retire.
The system earns its maintenance time when the next brief can use the reasoning from the previous cycle.
Keep six connected records
You can begin with a shared table and linked documents. The important property is traceability: someone should be able to move from a claim in a brief back to its source, then forward to the creative and its result.
| Record | Minimum useful contents |
|---|---|
| Customer evidence | Observation or excerpt, source reference, date, audience, context, and limits |
| Account context | Channel, objective, offer, landing page, relevant constraints, and measurement caveats |
| Hypothesis | Expected behavior change, supporting evidence, uncertainty, and what would challenge it |
| Brief | Audience, problem, promise, proof, creative variable, destination, and owner |
| Creative and results | Asset identifier, delivered attributes, launch window, spend, outcomes, and comparison conditions |
| Iteration decision | Repeat, revise, retire, or investigate; rationale; owner; and next action |
Use identifiers to connect these records. Preserve the brief that actually produced the asset; later edits should not erase what the team believed before launch.
Keep rejected concepts too, but record a reason. “Unsupported product claim” and “production cost exceeds the available test budget” imply different conditions for reconsideration.
Separate observation from interpretation
An evidence label should explain what a source can support.
A customer describing a concern supports the conclusion that this person expressed that concern in that context. It does not establish how common the concern is. An ad with strong attributed conversions supports a performance observation under its delivery conditions. It does not establish that its headline caused incremental purchases.
For each consequential input, record three things:
- Observation: What was actually said or measured?
- Interpretation: What might explain it?
- Recommendation: What should the team do next?
This separation is especially useful when AI drafts briefs. Otherwise, a tentative interpretation can become a confident product promise after a few rounds of summarization.
A simple evidence label with a written limitation is more useful than an unexplained numerical confidence score.
Put checks before production
Before a brief enters production, its owner should answer four questions: What supports the customer problem? What supports the product claim? What behavior should change? What result would make us reconsider?
Missing support should change the brief. An unverified product claim needs substantiation or removal. An uncertain customer insight can become an exploratory hypothesis, provided the brief keeps that uncertainty visible.
Assign responsibilities explicitly. A strategist owns the hypothesis and brief. Someone with product knowledge checks factual claims. A measurement owner records results and caveats. One person closes the loop with an iteration decision. In a small team, one person may hold several roles.
Refresh context when something material changes, such as the offer, product capability, audience, or landing page. Keep the older evidence for historical interpretation, but mark whether it still applies.
Walk one hypothesis through the system
Consider a hypothetical product whose prospects mention setup effort during research. The team also has an ad about advanced capabilities with promising click-through performance but uncertain downstream value.
The observation is that setup effort appeared in the research. The interpretation is that perceived effort may discourage some prospects. The proposed test is a creative concept that demonstrates the actual setup process.
The brief links to the research, specifies the audience, and identifies the product facts that can be shown. It avoids claiming setup is “instant” unless that claim is supported.
After launch, the team records delivery conditions, spend, conversion, and activation where measurable. Higher click-through alone would leave the original business question unresolved. If clicks rise while activation falls, the next investigation should examine whether the demonstration created the wrong expectation.
The retained learning should describe the audience, promise, conditions, and uncertainty. “Setup ads work” would discard most of what makes the result useful.
Test the workflow before expanding it
To evaluate the process, assign comparable briefing tasks within the chosen channel and audience to either the existing workflow or the new system. Random assignment is preferable where practical. Keep production resources, launch opportunities, and evaluation windows comparable, and define success before results arrive.
Track the cost of the whole workflow: research upkeep, briefing, review, production, and rework. Also track whether concepts reach a usable decision. More briefs are valuable only if they produce worthwhile tests and learning.
Where a credible incrementality design exists, incremental contribution margin per creative-production dollar is a useful business measure. Without that design, label attributed results accurately and keep conclusions provisional. Randomizing the briefing process does not, by itself, make platform-attributed conversions incremental.
Account for rejected briefs and failed launches. Evaluating only published assets can hide costs introduced earlier in the workflow.
Watch for expensive failure modes
The first is documentation without decisions. If a field never changes a brief, review, or iteration choice, question whether it belongs in the minimum version.
The second is circular evidence. AI-generated positioning should not return to the system as customer research. Preserve source types so generated material cannot validate itself.
The third is overgeneralizing winners. Record targeting, offer, placement, landing page, and timing alongside creative attributes. These conditions limit what the team can reasonably carry into the next test.
Finally, maintenance can exceed the value of the learning. Expand the system when a repeated decision needs more context. Treat new folders and automated research feeds as costs with a purpose.
Evidence and limitations
This article draws on an available description of Alex Cooper’s public Brand Brain proposal, particularly its shared creative context and evidence checks. The original post was not independently verified for this article. The reduced schema, ownership model, hypothetical example, and evaluation approach are operator recommendations developed from that framework.
The available material provides no implementation results, cost comparison, or controlled evidence of improved creative performance. It supports testing this operating model; it does not establish that the model improves acquisition costs, contribution margin, or production speed.
Source basis
- An available description of Alex Cooper’s public Brand Brain proposal connecting brand and customer context to creative production, evaluation, and iteration.
- Evidence controls described in the proposal, including source references, claims checks, evidence strength, and missing-context tracking.
- Original operating recommendations; no implementation outcomes or causal performance evidence were available.