Persona Shifting

Thinking Tools6.3 Implementing the Action Plan

Draws on Eugene Schwartz's stages of awareness (Breakthrough Advertising, 1966), Alan Cooper's personas (The Inmates Are Running the Asylum, 1999), and William Ury's going to the balcony (Getting Past No, 1991).

Takes on the viewpoint of one named reader, their role, prior beliefs, mood, and awareness of the problem, before drafting, so a message starts where that reader is.

One product-update email, three named readers, four ways to open it

The draft opened with the feature's name. Pick a reader, then the opening to send them: the line under the rows says how it lands and, when it misses, which opening meets them. Owen is unaware of the problem, Priya knows the product and doubts it, and Ines is most aware. Illustrative.

The reader

The first line

  • Pick a reader and a first line to see how it lands.Misses: three weeks in, Owen does not know reconciliation is a problem, so Version 4.2 ships Auto-Match tells him nothing and he files it unread. Try the Friday chore.Meets him: an unaware reader needs the problem named in his own words first. The Friday afternoon you spend ticking payments against invoices can now take ten minutes.Misses: 3,610 matched payments answers a doubt he does not have yet. Until he sees Friday's ticking as a chore, the number means nothing. Try the Friday chore.Misses: a setting for a feature he does not know he needs. Try the Friday chore.Misses: a feature name and the word new read as the vendor talking about itself, and she stops there. Try proof on her own data.Close, and still a miss: she knows the chore well. What she doubts is that automatic matching works, so she needs proof before any claim.Meets her: a doubtful reader needs proof first. On your own March bank file, 3,610 of 3,800 payments matched themselves, and each match shows the rule that made it.Misses: she will not switch on a feature she expects to recheck by hand. Try proof on her own data.Close: she knows exactly what it is, but has to read a paragraph to find the setting. Try where to switch it on.Misses: she asked for this two years ago, and a line describing the problem wastes her time. Try where to switch it on.Works, and slower than she needs: she is already convinced and wants the next step. Try where to switch it on.Meets her: the most aware reader needs only the next step. The automatic matching you asked for is live: turn it on under Settings, then Payments.
  • Misses: three weeks in, Owen does not know reconciliation is a problem, so Version 4.2 ships Auto-Match tells him nothing and he files it unread. Try the Friday chore. (reader: Owen, new clerk, opening: The feature's name)
  • Meets him: an unaware reader needs the problem named in his own words first. The Friday afternoon you spend ticking payments against invoices can now take ten minutes. (reader: Owen, new clerk, opening: The Friday chore)
  • Misses: 3,610 matched payments answers a doubt he does not have yet. Until he sees Friday's ticking as a chore, the number means nothing. Try the Friday chore. (reader: Owen, new clerk, opening: Proof on their data)
  • Misses: a setting for a feature he does not know he needs. Try the Friday chore. (reader: Owen, new clerk, opening: Where to switch it on)
  • Misses: a feature name and the word new read as the vendor talking about itself, and she stops there. Try proof on her own data. (reader: Priya, finance director, opening: The feature's name)
  • Close, and still a miss: she knows the chore well. What she doubts is that automatic matching works, so she needs proof before any claim. (reader: Priya, finance director, opening: The Friday chore)
  • Meets her: a doubtful reader needs proof first. On your own March bank file, 3,610 of 3,800 payments matched themselves, and each match shows the rule that made it. (reader: Priya, finance director, opening: Proof on their data)
  • Misses: she will not switch on a feature she expects to recheck by hand. Try proof on her own data. (reader: Priya, finance director, opening: Where to switch it on)
  • Close: she knows exactly what it is, but has to read a paragraph to find the setting. Try where to switch it on. (reader: Ines, controller, opening: The feature's name)
  • Misses: she asked for this two years ago, and a line describing the problem wastes her time. Try where to switch it on. (reader: Ines, controller, opening: The Friday chore)
  • Works, and slower than she needs: she is already convinced and wants the next step. Try where to switch it on. (reader: Ines, controller, opening: Proof on their data)
  • Meets her: the most aware reader needs only the next step. The automatic matching you asked for is live: turn it on under Settings, then Payments. (reader: Ines, controller, opening: Where to switch it on)

An example

A billing software company was about to send one product-update email to four thousand customer accounts. The draft opened with the feature's name and the word new. The product marketing lead stopped before sending and named three readers, each built from real support calls. Owen, a clerk three weeks into the job, did not know reconciliation was a problem; to him, ticking payments against invoices every Friday was just the work. Priya, a finance director, had seen automatic matching fail before and expected to recheck everything. Ines, a controller, had asked for the feature two years earlier and wanted the setting.

The lead placed each on the awareness ladder and read the draft's first line as each of them. Owen would not open it, Priya would stop at the feature name, and Ines would hunt for the switch. She split the list three ways, wrote a different opening for each, and kept the body the same. Twice as many accounts turned the feature on in the first month as had for the last release.

Why it works

Most messages fail at the first line, and they fail on starting point more often than on substance. A writer opens from where the writer stands, fully aware of the problem and the fix, and the reader who is not there yet finds no way in. Naming one specific reader forces concrete questions that a description of an audience never raises: what does this person believe already, what happened to them this week, and what will they do with the first sentence. The awareness ladder turns those answers into a choice of opening. An unaware reader needs the problem named in their own words, a doubtful one needs proof before any claim, and a fully aware one needs only the next step. The body can stay the same; the entry point changes.

The thinking behind it

Eugene M. Schwartz Eugene M. Schwartz, a direct-response copywriter, held in Breakthrough Advertising (1966) that copy should meet readers at their stage of awareness, which runs from unaware of the problem to most aware of the product. The ladder in this tool is his: the rung decides what the opening sentence must do. It is a practitioner's classic and makes no claim to be research; its test is whether the reader keeps reading.

Alan Cooper Alan Cooper, a software designer often called the father of Visual Basic, brought personas into interaction design: specific archetypal users, built from interviews with real ones, for whom a product is designed. He began using them in 1983, and The Inmates Are Running the Asylum (1999) made the method widely known. The habit of giving the reader a name, a role, and a situation comes from him.

William Ury William Ury, a negotiation adviser with a doctorate in social anthropology, described going to the balcony in Getting Past No: Negotiating with Difficult People (1991): stepping back from an exchange before reacting to it. Persona shifting borrows the move for the moment of pushback, when a writer or speaker steps out of their own position long enough to see the objection as the other person sees it.

How to run it

  1. Name one reader. Give them a first name, a role, how long they have held it, and something they have said recently.
  2. Place them. Picture where and when they will meet the message, on what device, and what else is competing for them.
  3. Find their rung. Decide whether they are unaware of the problem, aware of it, aware of fixes, aware of yours, or ready to act.
  4. List what they believe. Write down what they already think about the topic and where your message will collide with it.
  5. Write the first line as them. Draft the opening from inside their position and ask whether they would read the second sentence.
  6. Repeat for each distinct reader. When the readers sit on different rungs, write a different opening for each and keep the body shared.
  7. Reread cold. Come back a day later as the reader and mark every place they would drift or stop.

Where it goes wrong

The first failure is the composite reader. A persona called the finance team averages several people into no one, and the copy comes out generic; if the persona has no name and no recent quote, it is still a segment. The second is empathy without a decision. Writing that the reader is busy and skeptical changes nothing until it changes the first sentence, so check that every note in the persona leads to an edit. The third is a persona built from the writer's guesses. When the beliefs and quotes come from no conversation, the draft fits an imagined reader; take them from support calls, interviews, or sales notes.

When to use something else

  • Personas. When a product team needs lasting archetypes of its users to design for, past one message.
  • Empathy Map. When a group needs to agree on what one customer says, thinks, does, and feels before anyone writes.
  • AIDA. When the reader is known and the work is ordering the message from attention through to the action.

Where it sits in SOLVE eX

Go to the source

  • Breakthrough Advertising, Prentice-Hall, 1966
  • The Inmates Are Running the Asylum, Sams, 1999
  • Getting Past No: Negotiating with Difficult People, Bantam, 1991

Back to the catalog