Skip to main content
All field notes

OrgX / Journal

Field note

We Generated 75 Ad Concepts. The Useful Part Was Killing 60.

The point was not volume. It was forcing the system to find the few ideas with enough pain, specificity, and visual tension to deserve production.

In the April 2026 creative sprint described here, we considered 75 ad concepts, narrowed them to 15 production specifications, and selected five directions worth making. Those are internal selection counts, not evidence that the ads improved conversion or outperformed another process.

Judge the idea before spending production effort on it. The team needs to explain why it chose the survivors.

The three offers needed different messages

The sprint covered three OrgX offers. MCP addressed the builder carrying context between AI clients. Core addressed the founder coordinating initiatives, decisions, and work. Amplify addressed teams with a campaign brief but insufficient production capacity.

An asset for one audience could not simply be recolored for another. The builder needed to understand the connection and retrieval workflow. The founder needed to see how the operating record relates work to decisions. The campaign buyer needed to inspect actual output and its fit to the brief.

Internal selection stageCount
Concepts considered75
Production specifications15
Directions selected5

The historical counts describe internal selection, not conversion, savings, or a controlled comparison.

We used the product surfaces, positioning, objections, and brand constraints as input. Those inputs let us judge whether a concept expressed the offer, instead of applying one vague standard of visual quality.

Make rejection explainable

The original April account favored the MCP direction “Stop re-explaining your business to every AI tool.” Its documented rationale was the recognizable work of repeating context across clients. It rejected generic “connect your tools” framing because that described capability without making the buyer’s problem concrete.

Those are the published creative argument and rationale. The concept bank, individual rejection records, production specifications, and selected assets remain unpublished here; readers cannot audit all 75 choices from this article.

A practical rejection note identifies the defect. Does the concept target the wrong reader? Can the product support the promise? Does the visual make the claim legible? Is the proposed action appropriate to the destination?

Preserve that reason so later variants do not revive the same problem.

The original hiring-cost comparisons were creative candidates, not demonstrated savings. They need independent evidence before use in an ad.

Carry one surviving idea forward

Here is an illustrative production pass for an MCP concept about repeated briefings. Write the intended audience and problem beside the concept. Specify the decision record the visual needs to show. Identify which copy describes supported behavior and which wording would overpromise recovery across clients.

Next create a production specification: layout, exact text, product reference, dimensions, and destination. Produce the asset, inspect the rendered version, and compare it with that specification. If the source record cannot be shown accurately or the message needs a long explanation, revise the idea before generating more assets.

The artifact should travel with its brief and review. That lets another reviewer distinguish a deliberate choice from a convenient image the generator happened to produce.

Selection is not market validation

The five surviving directions were the team's production choices. Their survival did not establish that buyers understood them, that the channel would deliver them effectively, or that the offer was right.

The counts also do not establish a cost reduction. To make that claim, a comparison would need the production work actually avoided, the cost of selection, and the same acceptance standard across both processes. This field note does not contain that experiment.

Audience testing comes after internal review. Keep the audience, channel, asset version, and observed response with the result. A failed campaign may reveal a weak offer even when the image follows the brand perfectly; a successful result may have explanations other than the generation method.

For your next campaign, start with a brief and a few different concepts. Reject them for named reasons. Turn only the strongest candidate into a production specification, then inspect the finished asset at the size and destination the audience will see.

Read the brand-content method for the brief and review questions. If you want another person to assess the record, bring one concept, its specification, and its final asset to a proof review. The question is whether the work earned the next step, not how many ideas the system generated.

OrgX research & field notes Explore all field notes