ok: "buyer personas"

one of my biggest lessons of the last year is that when sales/marketing think "personas", they are thinking:

"we need to teach people how to sell"
"we need the fastest way to close deals"
"I need to teach a junior salesperson who to prospect"

1/n
...their goal is actually the *least* amount of complexity/information needed to do their jobs.

IOW, say one message will resonate everywhere, or one qualifier will get you "buyers"

....well, one "persona" will do

When you understand this ... 2/n
...it makes sense why product/ux and sales/marketing often butt heads when it comes to research.

There's a tendency to couple

Research

with

Artifact/Tool

3/n
...showing up at the table with a lot of in-depth research on the journey, the complexity of customer environments, the nuances of different people in mind...

actually causes dissonance

"WAIT. I CAN'T USE THIS TO SELL"

This was my AHA...

4/n
...when you are doing research for sales in marketing you are actually doing TWO things

Research

and then:

creating simplified models (internal products, on some level), that help people do their jobs faster internally

The latter will be by definition lossy/incomplete

5/end
...

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with John Cutler

John Cutler Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @johncutlefish

4 Dec
work in B2B SaaS?

something I've learned, and re-learned over and over -- at @Amplitude_HQ especially talking to so many teams.

It is vital -- absolutely vital -- to understand your product in the *broader landscape* of a customers workplace.

Why? 1/n
...when talking to a customer about your product, you will always trigger the instinct for them to be helpful and provide information about YOUR product. Which is good...

...but also a challenge.

The reality is that your product is a tiny part of their world. 2/n
"What problems are you having?"

Customer: "Um, well, [some task related to your product]"

(remembering to focus on goals)
"Oh no, what is your GOAL?"

Customer: "Um, well, [some goal related to your product]"

All good, except, again, this is a tiny part of their world. 3/n
Read 6 tweets
20 Nov
when you've found your team prematurely converging -- jumping to specifics too early -- what were some contributing factors?
...this is a weird one, but often it seems to happen when the bulk of the team is tied up with something, and a smaller group -- e.g. designer and PM -- are under pressure to "tee up" the next thing
...when the team lacks psychological safety? people just want to get it over with, so they just go with whatever seems like a reasonable deal to make the need to collaborate go away
Read 10 tweets
17 Oct
A collection of things from the vault! Wading through 1000s of images shared on twitter.

1/n: Adding assumptions and constraints to a "tree" of nested bets...
2/n: Getting specific about principles ... and avoiding vanilla statements
3/n: The iceberg of product complexity ... what we don't see when we just ponder "level of effort"
Read 13 tweets
15 Oct
a little product lesson

we often experience situations where we are faced with overlapping problems

it looks a little like this ... 1/n
...except, often no one really takes the time to define the problem(s). Instead they brainstorm a bunch of ideas predicated on implicit perceptions of the problem(s)

the danger here, of course is that... 2/n
...if you bring three people together they might each see different things

One person sees one problem

One person sees two slightly overlapping problems

One person sees a parent problem with three child problems 3/n
Read 7 tweets
10 Oct
Funny thing is that I both agree some people are really good at certain things

AND I also believe that certain environments are conducive to elevating everyone such that one person being really good at something doesn’t mean much (though it is helpful)

1/n
The difference boils down to predominantly team oriented views of our work vs individual oriented views.

If you got all the best ppl at doing X in the world together and put them in a room… the differences would be minimal

In their org they are…. 2/n
Much better than everyone at X. They might even be 10x at it. If you leave them alone to do X they will outperform everyone at X.

But in a team setting, you’ll also need to do Y and Z. And A, B, and C.

Being 10x at X doesn’t mean much. 3/n
Read 4 tweets
1 Oct
genuine question

the first instinct or product / design folks when getting a new gig is to talk to customers. LOTS of them. As quickly as possible.

...but in other roles, this is a foreign concept.

assuming great intent and high skill in their respective domains...

why?
...could the intent be there, but it is more a question of fear, and feeling like you are being put on the spot?
another could be ...

whereas a product/design person knows what signals to look for

other people will assume that the customer will not be able to tell them something they don't know?
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(