Collecting competitor ads is easy. Learning from them requires a structure. Without one, a swipe file becomes a collection of visual styles and strong claims that may have little to do with your own customer.

The working map
  1. 01Record what is observable
  2. 02Find the unresolved question
  3. 03Write a testable brief
01

Record what is observable

For each example, write down the audience it appears to address, the problem it names, the promise, the evidence and the next action. Save the context alongside the creative so the screenshot does not become detached from the offer.

Keep observations separate from assumptions. Seeing an ad does not tell you its profitability. A long-running creative might be useful, wasteful or serving a purpose you cannot observe. Treat its performance as unknown unless you have reliable evidence.

02

Find the unresolved question

Look for patterns across several examples. Do they all emphasise speed but avoid implementation? Do they show the product but leave the customer uncertain about compatibility? That gap can become a research question for your own audience.

The aim is to develop an angle supported by your offer. Borrowing a competitor's testimonial, distinctive artwork or unsupported claim does not create a strategy. Use the review to identify what you need to explain in your own way.

03

Write a testable brief

A useful output is a brief such as: “Prospects understand the benefit but worry about setup. Show the setup sequence and name the required inputs.” That gives a creative team a problem to solve.

Compare the resulting message with your existing approach using a suitable test and a defined outcome. Keep the learning even if the creative loses. A swipe file becomes valuable when it changes the quality of the next question.

Share this article

Continue the thread

System Maps

Your default option is part of the offer.

System Maps

Put the important decision where people can find it.

System Maps

Organise the choice before removing the options.