ICP Explainer pt 2: Build Their Dreams

One of my favorite product tools, especially when talking to non-product folks, is the Ideal Customer Profile.  That is because it finds that perfect overlap between the deep history of targeted marketing and easy to understand explain metaphors.  Too often when I am talking to business leaders, senior engineers, or customer support staff the theory is too much.  They want a quick mental model they can align their thinking with.  ICP is exactly that.  Also, I get to make fun jokes about Insane Clown Posse.

Fundamentally, an ICP is answering the questions “who are we building this for” and “what problem are we solving for them”.  Which means it is super powerful for when we are having tradeoff or prioritization conversations.  With many of the startup founders I have worked with we have used an ICP to focus limited energy in both product and sales.  With larger companies, I have used to clearly understand who we are saying ‘no’ to and why as well as force conversations about purpose drift.  Super useful.

But also, super dry.

I can give you examples of what an ICP is and then a step-by-step process on how to build them.  I can give you a bunch of anti-patterns and failures with the related cautions.  I can give you all the “it depends” across industries and business models.  And you will get that down there if you want to scroll.  But that’s boring at it doesn’t help with the goal I actually have with most product tools: mental models that help us communicate.

We are writing a novel.  A story of a person with a great need.  One day our main character wakes suddenly up in the middle of the night, sheet damp with sweat and a great anxiety gripping their chest.  They were dreaming of something that would solve their biggest problem, and it was right there, within their grasp.  But as the dream slides away, they are left with a pressing certainty that they will never find the solution.

What is the problem they are having?  What relief will they feel when they solve it?  What are the characteristics of them, as a character, that makes that problem so prominent it is waking them in the middle of the night?  Who are they?  That person is your ideal customer.  They are deeply motivated.  They have a real tangible problem.  And solving that problem will create deep meaningful relief.  The ICP isn’t a mishmash of your existing customer’s characteristics.  It’s not a set of demographics that describes a huge swath of the population (which is somehow always a woman 35-45 with 2 children named Jennifer).  And it can be expressed crisply with clear things it isn’t.

B2B and B2C examples

So, let’s walk through a couple examples and then we can talk about how we build it.

  • Online consumers looking for rare or hard-to-find books (Amazon of the early aughts)
  • Families looking for interactive and collaborative games (Wii)
  • Sales leaders with complex and consultative sales processes looking to organize their sales team’s time and focus (salesforce.com in the early aughts)
  • Hospital and Health System marketers looking for HIPPA-compliant and expert website development and online marketing (CMS company I worked with)
  • Developer-tool companies looking to connect meaningfully with the developer community (social media startup I worked with)

With one of these clear descriptions of who we are serving and what problems we are solving for them I can test out what we should and shouldn’t be doing.  Let’s focus on the complex and consultative sales process tool.  I’m building a product that serves the sales leaders.  I have gotten a request to create marketing attribution fields (where the lead came from).  Do I build it?  Does it help the sales team sell?  Sometimes knowing where the lead came from can help open a conversation.  So I don’t need that information for marketing attribution, I need it to help the sales team start a conversation.  Does it help the sales leadership team?  Yes, knowing which channels are resulting in better sales helps me structure my team’s focus.  So the reason I am building this feature has changed.  I have clarified why I am building a feature (marketing attribution) to the needs of my primary users.

Anti-Patterns

To better understand how to use this tool, it’s important to start with what it is not.  It is not a buyer persona.  This is not the tool you use to fill your sales pipeline or prospect.  Buyer personas are super useful and often contain some of the same demographic and psychographic elements.  However, buyer personas are about who you are targeting with marketing and sales messages.  They will be a lot broader than an ICP because while you can target firmographics (the characters of a company) and demographics it’s a lot harder to target pain points.  Buyer personas are about authority, timeline, budget, and need.  They are a point in time about that sales process.  ICPs are an idealized set of characteristics about the perfect customer, one you will almost certainly never meet.  They are needs forward not personal characteristics forward.

It’s not who we want to be when we grow up.  It’s who we want to be right now.  If you are currently looking at horizon 2 or 3 explorations, you want to develop an ICP specifically for those experiments and test against it to see how you are getting penetration.  Often startups will start with an ICP and test to see if they get traction within that persona.  If they don’t then they tweak the ICP.  Companies with an existing customer base should have an ICP for their core business and then experimental ICPs for potential innovation that are adjacent to the core business.  I sell into hospitals and I want to experiment with selling into other highly regulated businesses, that is a new ICP and I need to better understand the demographics and pains of that new customer set.  Large companies may have multiple ICPs for their core business, like the Fortune 500 company I worked with.  The mistake is muddying them together into one ICP.  That quickly becomes an “everything for everyone” model.  Your ICP must have someone you are saying “no” to.  Sub divide to where you have product/market fit (PMF) even when, often, it is the same product across multiple PMF models.

It is not a current customer profile like account management will use.  Nor will it be user journeys that UXR and product will develop.  This isn’t how the current users interact with the current offerings.  It’s about what the ideal customer needs because of the deep need we are solving for them.

Similarily, in B2B, you must be conscious that your buyer isn’t always your user.  So much like the sales leadership vs sales team example above, the ICP is incorporating all those people together.  The problem you are solving is the intersection of the needs of the buyer and the needs of the user.  You can’t focus all on one or other.

Building an ICP

We are going to go about this in this pattern Pain Points -> Attributes -> Demographics Profile

To build an ICP start by answer the question “What problem are we trying to solve”?  It may be easier to reverse this question and ask “Thinking about my most ideal customer, what problem do they have that they currently find unsolvable”?  Write it all down.  Then go through each problem and statement and ask “do I want to solve this problem?” until you have a set of problem statements (customer pains) that you want to solve.

Now having a problem statement, you can start to think about characteristics of a customer with that problem.  If you have existing customers, this can be looking at commonalities of those customers that are related to the problem statement.  Here is my handy cheat sheet of characteristics to segment based on:

Now you have a profile.  Test it.  Look at each attribute and say “is this really compelling?” and “does this change customer motivation?”.  Must like all marketing profiles become, well, me.  It’s easy to just reduce yourself to the most common demographic properties of your population.  The name Jennifer was really popular in the 80s, women 35-45 have a lot of buying power, and that demographic is really likely to be married with 2 kids.  None of those characteristics are likely to be compelling to any particular problem statement.  I don’t need software to organize my kid’s schedules because I am in my 40s and married.  Having kids is compelling.  But likely being a busy professional and upper income are more impactful on that need.

Application

Once I have a ICP that I have walked around the organization it become a foundation for conversations we have with stakeholders and inside the team.  Does this feature help our ICP?  What are we saying no to?  Do our recent customers look like our ICP?  If there is slide, what is it and does it mean we need to adjust the ICP or we are starting to muddy our value proposition?  How recently have we talked to a customer who looks like our ICP?  What needs did they have that we aren’t currently solving?

Note: I don’t use AI to help write my posts or create example pictures. The segmentation cheat sheet is my creation and is also present in my Build Things People Want talk.  I did use AI  to create the header image, in this case ChatGPT with the prompt “create an image of glenngarry glen ross in the style of insane clown posse”.

ICP explainer: Segment the World!

One day, a few years ago, I was chatting with an enterprise architect about some of the prioritization and focus issues the team was facing.  I told him “our real problem is that we don’t know our ICP”.  To which he paused for a long beat and said “Insane Clown Posse?”.

Fair enough.  I grew into product building at an early B2B CRM company before the rise of salesforce.com steeped in Glenngarry Glen Ross, Alan Cooper’s personas, and Angus Jenkinson’s customer segmentation strategy.  I have a coffee mug that boldly proclaims, “Ritalin is for closers”.  He grew up bleeding his ears with death metal while generating beautiful code.  Fair enough. An Ideal Customer Profile (ICP) sits at the intersection of emerging marketing trends and deep thinking about product intention for who we are selling to. Let’s break it down.

A Brief History of Targeted Marketing

Back in the late 90s and early 00s we were going through a major transition in how we thought about marketing and sales, driven by the move from mass marketing to personalized marketing enabled by the internet.  There was a deep divide between large companies, who were trying to serve everyone, and small companies, who were embedded in the needs of their community. Now instead of just blasting a message “drink my sugary beverage” with compelling images and social pressure, you could target certain demographics with marketing, and products, specifically suited to their needs.  By the early aughts, the internet made it possible for small producers to find their niche markets and customers to be more exacting in their needs.  Webpages popped up to serve these needs.  Instead of having the choice between two sugary carbonated beverages, consumers could demand, and find, a wide assortment of specialty products: probiotic, low sugar, fruit juice based.  The world exploded with options, and the search engines came to help organize (and monetize) it.  By the end of the aughts we have social media, YouTube, and targeted marketing.  And a lot of noise.

The same thing happened in B2B sales, which I got to watch firsthand from my first product job at a lead management and customer relationship company working with large multi-nationals.  It was no longer enough to manage your supply chain, distribution network, and brand reputation.  Now you needed to think with more precision about who you were selling to.  Enter concepts that are still with us today: personas, buyer journey, segmentation, and ideal customer profile.  To be clear, these concepts were always there, unnamed in the dusty corners of pitch rooms.  Companies always have differentiated products into different markets, see also: the different sizes of candy bars or packaging of soap at different retail locations.  But what happened was an acceleration of need for this deep thinking and an explosion of competition.  Not only could big companies have more ways to segment customers, but smaller companies could quickly identify and build into gaps.  Pets.com didn’t survive but targeted marketing sure did.  Just remember that congressional testimony about the Facebook business model from Zuckerberg: “Senator, we run ads”.  User data, micro-targeting, segmentation is a standard operating process now.  You must be a lot more intelligent about your “who” to survive.  Stop smirking Mark.

Enter the Blue Ocean Strategy

Another important aspect of this trend is the impact of the Blue Ocean Strategy and long-tail marketing.  In 2004, Renée Mauborgne and W. Chan Kim publish a book that basically says that instead of competing in the same market everyone else is, the red ocean, find the place where there is an underserved customer base.  I say that out loud and it sounds obvious, but it was anything but in practice.  Remember we are at an age when scale is a major factor in success.  Big companies survive through inertia and small companies can only get so big before they are eaten.  The SMB market is overwhelmingly either hyper local or suppliers to the big boys (like the company I worked for).  A concept we saw deeply tested by the 2001 Enron scandal and shattered in the 2008 lehman brother collapse during the financial crisis.  Big companies fail too sometimes.

When you look at market opportunities, if you look where other companies already are you must spend your time making a value-cost trade off and differentiate on either quality or cost.  This “red ocean thinking” drives the middle out of a market and results in either high cost “specialized” or brand goods or a race to low-cost efficiency.  Luxury handbags are an example of the former, Walmart is an example of the latter.  The classic example of blue ocean strategy for me is the Wii.  When the Wii arrived on the video game market in 2006 it was revolutionary.  With it’s shorter play times and more party game style, it was going after a totally different interaction pattern and market.  It really was a precursor to the phone games that now take up way too much of my screen time.  Standalone gaming systems was already a deeply competitive and saturated market with Playstation and Nintendo sucking up all the air, and occasionally Xbox producing something reasonable (gotta give love to Grand Theft Auto).  By 2006 it was a market that had falling into an arm’s race based purely on computer specs.  But the Wii wasn’t for teenage boys (and girls thank you very much) in their parent’s basements (and dorm rooms).  It was suddenly targeting their parents with memorable, collaborative experiences.  With games that were about getting up and moving, and interacting with people in the same room, it was a totally different concept.  It could include the entire family.  But there were two absolutely genius things the inventors of the Wii understood that it took years for the rest of the market to catch on to:

  1. Parents are the ones with the money, not the kids
  2. Kids becomes adults

Because, fundamentally, they changed the value proposition for a gaming console into a market that really had no competition.  Atari started the market, really, in 1977.  The Nintendo first hit the states in 1985 with Playstation following in 1994 and Xbox in 2001.  By 2006 the Blue Ocean that Atari and Nintendo had discovered had become bloody.  But also, the children (cough me and my brother cough) who begged their parents for those early gaming systems (I still miss my duck hunt) had grown into adults.  Gaming had become mainstream, and with it, what some (read: me but not my brother) wanted from it was evolving.  There was still a market for gaming systems targeting people who wanted to spend hours immersed in a story (teenagers) but there was now an acceptable market for adults who want to casually game.  I will also point out that Wii may have been the first gaming system to understand that half the population is female and we don’t just don’t want “pink it and shrink it”.  That’s the wrong way to do segmentation.  The Wii did it right. Again, same thing happens with B2B it’s just the consumer goods examples are so much easier. 

Wag the Long Tail Marketing

In October 2004, Chris Anderson publishes an article in Wired magazine called “The Long Tail” which he later turned into a book in 2006.  The concept here, again, feels obvious in retrospect but was revolutionary at the time.  If you think about market demand on a chart there is a lot of demand for a few products and then there are a bunch of products with a really niche market demand.  Most companies obey Sutton’s law and go after products where there is the most market demand.  “Why do you rob banks?” “Because that’s where the money is.”  But that means there is a lot of need in those niche markets that are harder to solve.  Enter the internet and catalog management most famously visible with early Amazon.  When they were just a book seller they differentiated themselves by providing a very expansive catalog.  While you could go to any bookstore to find the newest best seller, if you were looking for a niche book you just couldn’t find it without going to a specialized seller.  Enter the internet and not only could those niche book producer start to find their market easier but a company like Amazon could include those niche books in their catalogue without risk.  You don’t have to stock it if no one buys it. 

By 2004 the economic reality Anderson could point to is that sales into those niche markets could outperform the bestsellers with lower competition (blue ocean), higher conversion rates, and better brand loyalty.  There are a lot of other reasons why early Amazon was successful which is probably a different blog post but I’ll drop another here for context: they understood they weren’t selling books.  They were selling trusted access to niche markets.  In the early aughts Amazon was a safe place to give your credit card number to get those specialized items.  Way safer than going to “momandpopbooks.org”.

Long tail marketing is born because of digitalization and better market access.  Sits on top of blue ocean strategy, social media, and segmentation strategy.  It then helps give birth to the influencer which I am, of course, too old to understand.  But all of these factors, together, break the old ways of marketing.  Companies can no longer sell “everything to everybody” and perhaps they never could.  The last decades have seen the end of “everything stores”, also known as department stores, like Sears.  It’s not just the move online but also the ability to easily create niche products, find segmented customers, and compete in markets that were incredibly inefficient to target before, and therefore were left to companies without scale.  So we come to today with all these factors changing the how we go to market and who we target.  Enter Insane Clown Posse… I mean, cough, Ideal Customer Profiles.

Tune in Next time, same Bat-Post, same Bat-Blog

This was going to be one post talking about ICP, modern considerations, how to build it and apply it, and cautions and anti-patterns.  But I was having too much fun with the history, and I think the context is too often glossed over.  So, we will continue with application next time.  And maybe I’ll even try to drop some sick rhymes.

Note: I don’t use AI to help write my posts.  I did use search, and the associated embedded AI that is everywhere, to find the actual dates, links, and references I made throughout this post because I wanted to provide credit where it is due.  I also used Google Gemini to create the header image because I couldn’t resist Glenn2dope Glen Violent J.

It Depends

Early in my career, I moved into a new company as the only product leader for the engineering, network, and desktop support teams.  I went from having 2 direct reports to (eventually as I rebuilt the team) 21 and department head responsibilities.  Knowing I was going into a leadership position with a team that had had significant management turnover, I started with some small group and one on one meetings to get a sense of where the team was and what they needed.  In one of these meetings, a senior engineering told me that I was there is “help us build things people want”.  She was tired of building products that went unused and were then deemed a “failure”.  The software was built right, the team was high performing, but the gap between what they were building and what the market was buying was enormous.

Throughout the companies I have worked at, teams I have led, and products I have built “build things people want” has continued to be my clarion call.  It has wormed its way into conference talks and blogs.  It has helped me find clarity in difficult conversations with sales and account teams.  And it has become more nuanced and more complex as the challenges of building products has become more complicated.  Who are the people we are building for?  How do we know what they want?  When do we drive based on instinct and when on user data?  What kinds of experiments help us better answer these questions?  What kind of commercialization is required?  When do we trade-off between speed to market (I want it now) and performance and reliability (I want it dependable)?

Recently, I have found another phase slipping into my mouth more and more: “It Depends”.  I have had to shed the comforting clarity that we are here to “build things people want” for the situational awareness, and yes anxiety, that there isn’t a clear right answer most of the time.  What works with one company, customer base, team, market environment, or existing product and tech debt doesn’t easily translate to another.  It is exciting to realize there is no rulebook but also terrifying that each moment is a rebuilding of the rules.  Some things stay the same but the complexity, as it always was, is in the details. 

As product managers it often feels like we spend a lot of time trying to find repeatable processes and the perfect document.  While these things are valuable, it takes us away from those details and nuances.  Perhaps it is simply my dislike of external structure, but I find myself wanting to explore that space of “it depends” more, while still holding on to that drive to “build things people want”.  Because I do think there are mental models and, yes, structures that can help us navigate the ambiguity.  But also, it’s work worth doing and maybe along the way of my own explorations I can help others untangle these knots.  Also, I have been told by my teams before that they miss my “Jennie-isms” once we re no longer working together. So hopefully a little humor and interesting stories along the way as well.

CodeMash Conference 2023 – Consuming Endangered Pachyderms

Slides

Blogs on related topics

Mental Model Minute: Seven Levels of Authority

We are all growing and learning as professionals in a collaborative workspace. It can be helpful to take a step back and look at different models of individual and team behavior. A “mental model minute” takes just a moment to describe a different view on how to perform or interact better that we can react…

The Next Right Thing

You’ve seen Frozen 2, right?  I mean, if your household is anything like mine, it’s playing on repeat in the background as children scramble, color, and fight.  Admittedly, I have only sat and watched it end to end once.  Still, there is one part of the movie that stick out to me and, I think,…

Build Things People Want

When I started at my current company, the mandate I was given by the developers was to help them build things people want.  It is something I have heard over and over again from developers throughout my career.  And frankly, it’s a goal that the organization and the developers should be aligned on.  The business…

Also check out other presentations.

CodeMash Conference 2023 – The Interview Lab

Slides

Blogs on related topics

Processes for Establishing Teams

Often when I am coming into a new team much of the work I am doing, while I get up to speed on the product and market, is helping the team focus and work together.  Over the years I have come across, modified, and developed several tools to help facilitate establishing teams, norms, and roles. As…

Mental Model Minute: Intent Based Leadership

I have so many things to share with you but so many discussions I have been having keep leading me back to this Mental Model Moment I thought I would share. And it’s easy, because it’s the author and this great illustrator do so much of the work for me. On the other side I…

Remote Work is Here to Stay

As operations leaders across the world stumble and struggle to figure out their “return to work” strategies, I have been reflecting on the nature of the fundamentally collaborative work we do in software development and what it will look like in this new world.  I don’t know what the post-Covid world of work will look…

Also check out other presentations.

KCDC 2022 – Build Things People Want

Super excited to be presenting at KCDC about building things people want. This is one of my favorite topics and it provides a lot of opportunity to dig deeper into topics.

Slides


Blogs on This Topic

Mental Model Minute: A Decision Making Model

Collaboration is good. Making decisions is good. These two things don’t have to be in conflict. I have seen a lot of small but growing companies where this feels like an either/or choice but it doesn’t have to be. The key is knowing who makes the decision and how much input is required. The more explicit we can be…

The Next Right Thing

You’ve seen Frozen 2, right?  I mean, if your household is anything like mine, it’s playing on repeat in the background as children scramble, color, and fight.  Admittedly, I have only sat and watched it end to end once.  Still, there is one part of the movie that stick out to me and, I think,…

Customer Intimacy and Segmentation

The biggest mistake young companies make is trying to sell everything to everyone.  It is impossible to get a clear value proposition or distinct competitive advantage without a targeted market segment.  The biggest mistake older companies make is not realizing when the market has changed and that segment is consolidating, shrinking, or shifting.  Both of…

Formulating Problem Statements

This morning, my children were arguing over spoons.  At breakfast it is my 5-year-old Finley’s job to get out the silverware for herself and her sister.  My Thalia, in the meantime, is just about to turn 3 and is fully feeling her control issues.  Every morning they use these particular baby spoons to eat their…

Build Things People Want

When I started at my current company, the mandate I was given by the developers was to help them build things people want.  It is something I have heard over and over again from developers throughout my career.  And frankly, it’s a goal that the organization and the developers should be aligned on.  The business…

Finding the First Thin Cut

My goal in any product development effort is to get an iteration in front of users as quickly as possible so I can see real users interact with it and respond to their emerging needs. The quicker I can build that first MVP, the sooner the feedback loop of engaging with users can take over.…


Videos on This Topic

Formulating Problem Statements
Hypothesis Testing
Story Mapping
Story Splitting

Processes for Establishing Teams

Often when I am coming into a new team much of the work I am doing, while I get up to speed on the product and market, is helping the team focus and work together.  Over the years I have come across, modified, and developed several tools to help facilitate establishing teams, norms, and roles. As always, no tool is exactly right for all teams. Adapt and change for the nature of the team you are dealing with.

Norms

Goal

Establish a common set of team level rules for how we collaborate and interact.  This can be everything from SLAs around PRs to the number of meetings we have, from how we handle conflict to support rotations.

This process should be team led.  The team leader should be a participant in the discussion.  As such it can be very difficult for the team leader to also facilitate the discussion.  A team norms discussion also becomes a way the team actively works through their communication and conflict management style.  If possible, it is better to do this synchronously.  The conversation is part of the point.  Approximately an hour should suffice for this discussion.  Some teams can do multiple exercises (norms + mandate or norms + decision making) in one session.  Once norms are established, they should be updated over time.

Process

Let the team know you will be doing an exercise so they can think about it in advance.  The prompt is “Think about a team you worked on that was great.  What made it great?  Think about a team you worked on that was terrible.  What made it terrible?”  Capture one thought per sticky.

Then group stickies together into themes.  Talk through the stickies in each theme together as a group.  As a facilitator make sure that people are engaging in debate on whether that idea is important to them as a team or not.  This will allow you to come to a set of statements that basically boil down to “We believe…”

Examples

From a very mature team with a lot of baggage, this set of norms evolved over the 2 years the team existed. This example is only a subset of the total norms the team had. They did a remarkable job of holding each other accountable by simply saying “thank you for following our team norms”.

At a very different company, a very different result. This was a team coming out of a lot of process whiplash.  Also, they were globally distributed (designer in India, team lead in South Africa) so there was a lot of concern for async communication and clear hand offs.

Roles and Responsibilities

Goal

Clearly define who owns what part of a process or has decision making power is essential to clean hand offs and action.  While many activities fall clearly into one job title (HR is a great example of a job with clear boundaries) in the space between Product and Engineer, or between levels in an organization, things can be a lot murkier.

This process can either be leader with team or leaders among themselves depending on where you are seeing grey areas.  It is best that anyone who’s position is being defined is part of the process.  This process requires a willingness to engage in some difficult discussions about both skills and responsibilities and can become heated so it’s best to have someone with position power that can break an impasse.

This process should be done in conjunction with establishing a DACI process or establishing a 7 levels of authority so you can clearly talk about both the “owner” of a process and who should be involved in the decision and how involved.

Process

This is a classic card sort exercise focused on job responsibilities.  This should happen in two phases.

Phase 1: Collect responsibilities

Bring the affected group together to collect all the responsibilities that need to be defined and owned.  Working alone capture one responsibility per sticky.  This can be as simple as “review a PR”, as mundane as “schedule meetings”, or as complex as “architectural direction”.  Set a timer for the independent brainstorming.  At the end of that time, go through all the items and group them and chose a “winning” card to represent each group of ideas.  Take these cards to a new clean area.

Phase 2: Card sort

Have boxes for each of the roles you are trying to define.  Together as a team determine which box each sticky belongs in.  If the sticky belongs in multiple boxes, duplicate it.  If a sticky represents a “decision owner”

Example

Most of this kind of discussion I have done has been in person, so I don’t have a captured shot.  This is a heavily cleaned up example from our process of hiring a Head of Eng and establishing teams with a “pod captain” for each.

Decision making structure

Goal

Sometimes it is helpful to separate the Roles and Responsibilities discussion from the decision-making structure.  This can especially be true when there are a lot of people involved in decision making and it can be separate from the actual job responsibilities.  This has been the case for my current role as we have moved from a single Engineer team of 25 to 5 pods with pod captains.

Process

Same as ‘roles and responsibilities’ card sort with the initial part focused on decision making stages.  In our process we also added in the variable of where and how the decision should be made and SLA because of how async we are.

Example