ICP, Persona, and JTBD

The foundation of every growth decision. ICP, real personas vs failed ones, jobs to be done, segmentation, and the research methods that produce insight.

Why these foundations matter

Every growth decision depends implicitly on who the customer is, what they need, and why they choose. Teams without clear ICP, persona, and JTBD work make decisions on hunch — about messaging, channels, product, pricing. The work to clarify these foundations rewards every downstream decision.

The mistake: treating persona work as a checkbox exercise. The discipline: treating it as ongoing research that gets sharper over time.

ICP defined for growth

ICP in growth marketing is the description of who your best customers are at the company-level (B2B) or segment-level (B2C/DTC). It's not the buyer persona — it's the kind of customer that produces the most value.

• B2B ICP: Industry, size, technographic, business model, growth stage, geography.
• B2C/DTC ICP: Demographic, psychographic, behavioral, life-stage, geography.
• SaaS ICP often includes: Use case, technical maturity, team size, integration patterns.

Without ICP, every acquisition program targets "everyone" — which means it targets no one effectively.

Personas

Personas describe individual buyers/users. Common failure modes:

• Demographic personas. "Marketing Mary, 35, suburban mom" — doesn't inform marketing decisions because demographics don't predict behavior in most categories.
• Aspirational personas. What we wish our customers were like rather than what they actually are.
• Composite personas. Averages across diverse customers; describe nobody.
• Stuck personas. Created in year one; never refreshed despite customer base changing.

What works

• Personas built from real customer interviews and behavioral data.
• Role-based for B2B (champion, decision-maker, user, blocker).
• Behavioral-based for B2C (heavy user, occasional user, prospect, churner).
• Refreshed annually with new research.
• Tied to JTBD (why does this person buy?).

Jobs to be done

JTBD framework: customers don't buy products; they hire products to do jobs. The job is the underlying motivation, not the feature consumption.

• Clayton Christensen's milkshake example: McDonald's discovered morning milkshakes were "hired" for the commute job — needed to be filling, easy to drink one-handed, last 30 minutes. Different from afternoon milkshakes.
• Functional job: What practical task is being done?
• Emotional job: How does the customer want to feel?
• Social job: How does this affect how others see them?

JTBD interview structure

1. Identify a recent purchase decision.
2. Trace back: when did they first realize they had this need?
3. What changed? What event triggered awareness?
4. What did they consider? What did they try?
5. What pushed them toward your solution? What pushed them away from alternatives?
6. What anxieties did they have?
7. What happened after the purchase?

Segments

Customer behavior varies more than personas typically capture. Real segmentation often surfaces:

• Heavy users vs light users. Same demographic, vastly different behavior.
• Buyers by motivation. Convenience-driven vs price-driven vs quality-driven.
• Lifecycle stage. New vs established vs lapsed customer.
• Channel preference. Mobile-first vs desktop-first; email-engaged vs not.
• Decision style. Quick decision vs research-heavy.

Research methods

• Customer interviews. 10–30 in depth; reveal motivation patterns.
• Win/loss interviews. Why did this person buy? Why did this prospect choose competitor?
• Sales call transcripts. Gong, Chorus, etc.; what prospects actually ask.
• Customer support tickets. Friction patterns; common questions.
• Behavioral data analysis. Segments derived from product usage patterns.
• Surveys. Validation of qualitative findings; broader scale.
• NPS / CSAT. Promoters and detractors interviewed for different signals.
• Social listening. Reddit, Quora, LinkedIn comments in your category.

Applying these frameworks

• Messaging. Speaks to JTBD; uses customer language; addresses anxieties.
• Channel selection. Goes where this audience actually consumes.
• Pricing. Aligned with perceived value, not cost-plus.
• Product roadmap. Features aligned with jobs customers hire for.
• Content strategy. Topics aligned with persona's consideration journey.
• Conversion paths. Designed for the segment's decision style.
• Retention programs. Tailored to lifecycle stage and use pattern.

Advanced playbook

• Annual customer research cycle. 10–20 interviews; refresh personas and ICP; informs strategy.
• Win/loss program. Ongoing interviews with closed-won and closed-lost; quarterly synthesis.
• Behavioral segment analysis. Clustering analysis on usage data; reveals segments demographic personas miss.
• JTBD per pricing tier or product line. Different jobs may justify different products.
• ICP exclusion criteria. Explicit list of who NOT to target; saves budget on poor-fit acquisition.
• Persona pressure testing. Annual exercise: are these personas still accurate? Does usage data agree?
• Persona-driven onboarding. Onboarding flows branch by persona, not one-size-fits-all.
• Customer advisory board. Ongoing voice-of-customer input from top customers.
• Sales-marketing-product persona alignment. All teams use same persona language; reduces friction.
• External validation. Industry research, analyst reports, competitive analysis triangulated with internal research.

Common mistakes

• Personas built once, never refreshed.
• Demographic-only personas; behavior not captured.
• Aspirational personas; not real customers.
• JTBD ignored; selling features instead of solutions to jobs.
• No segmentation; treating all customers identically.
• No customer interviews; research replaced with internal opinion.
• ICP not documented; acquisition spend unguided.
• No exclusion criteria; budget wasted on poor fit.
• Personas not shared across teams; sales/marketing/product use different language.
• No win/loss program; learning leaks away.
• Behavioral data not analyzed; segments derived only from intuition.
• No JTBD interview discipline; surface-level customer understanding.

Operating checklist

• ICP documented with firmographic/demographic + behavioral criteria
• ICP exclusion criteria explicit
• Personas based on real customer research
• JTBD documented for top personas
• Behavioral segments identified from usage data
• Annual customer research cycle
• Ongoing win/loss interviews
• Personas refreshed annually
• Personas shared across sales, marketing, product
• Customer advisory board active
• External validation of personas
• Personas inform messaging, channels, pricing, product

---

Part of the Growth Marketing Foundations series.