Person vs Persona: Resetting GTM Strategy by Focusing on Real People
When you build around a “persona” you get sanitized models; when you build around a “person” you get real engagement, retention, and community-driven growth.
We talk incessantly about ICPs, personas, and segments. In most GTM teams, these are sacrosanct, even fetishized, as if they hold the secret to unlocking rational decision-making, predictable retention, efficient pipeline. If only! Here’s the problem: while personas have their place, they’re not people. And when your strategy treats personas like people, you’re designing for the average instead of the individual, driving a wedge between your go-to-market strategy and the messy, emotional, human reality of your customers.
At a recent dinner I attended with other GTM leaders, a guest mentioned how Gen Z’s trust operates on what they called a “vibe check.” That line stuck with me. It captured something I’ve been thinking about for a while: GTM teams rely so heavily on personas that they often miss the nuances of real people. I’ve seen this repeatedly in community-led growth initiatives, cross-functional GTM alignment efforts, and product-community integrations. It’s time we stop confusing persona for person.
A persona is a model. A person is real.
When we talk about a persona, what we usually mean is a composite: role, title, industry, pain-point bucket, decision-maker checklist. It’s tidy. It fits nicely into spreadsheets, slide decks, and demand-gen campaigns. But a person doesn’t fit that neat box. A person is also dealing with uncertainties, emotions, competing priorities, and politics, often irrational ones.
Why this matters for GTM and community-driven engagement:
Personas direct you toward product features, value propositions, and messaging templates. Persons push you toward listening, empathy, and nuance.
Personas create discrete handoffs where marketing owns “the persona” up front, sales picks it up in outreach, and CS manages “the same persona” in renewal. Persons demand alignment across functions because one human experiences the company as one brand.
Personas optimize for average behavior. Persons optimize for diversity of behavior, for outliers, and for growth levers through advocacy and community.
In other words, designing around a persona often leads to fragmentation of experience. Designing around a person leads to alignment.
How this plays out in GTM and community
If your company has a “persona” mindset you might see:
Marketing develops templated campaigns: “VP of Engineering, innovation in regulated enterprise.”
Product builds “modules for that persona”: “Dashboard for VP metrics.”
CS segments “that persona” as a renewal cohort: “All renewals where VP of Engineering signed off.”
Each team increments the persona’s “representation” in isolation. They forget that behind that persona is a human with a job, a team, a political mandate, a weekend hobby, maybe a side hustle. They bring their personal context to every interaction, even if we ignore it.
If instead you bring a “person-centric” mindset, your GTM strategy shifts. You start asking:
What are the emotional stakes this individual has beyond the job title?
What community or peer group does this person belong to, and how can we tap that?
How does this person’s journey through marketing, product, community, and CS feel as a continuous thread rather than three separate handoffs?
How might this individual become an advocate or network connector, not just a unit to convert or retain?
Take a real example: dbt Labs built its product around analytics engineers, but its growth engine wasn’t just a persona narrative. The company leaned into real people; practitioners who wanted connection, peer learning, conference meetups, and contributions to open source. Their community generated a meaningful portion of inbound leads, and product adoption grew via word of mouth through these humans, not just an ICP checklist.
For cross-functional GTM alignment across marketing, product, CS, and community, this matters deeply. When you treat people as personas, each function builds for “their version” of that persona. But the customer only experiences one company. When you treat people as people, you align the touchpoints: marketing creates relevant invitations, community fosters connection, product delivers value, and CS drives outcomes together.
Why personas persist (and when they become a trap)
Personas endure because they offer simplicity in complexity. In B2B, especially, you have to distill myriad variables (industry, org size, role, decision process, etc.) into something digestible. The danger comes when:
A persona becomes the strategy instead of a tool.
You stop drilling into actual motivations, behaviors, communities, or peer networks behind the persona.
You rely on historical data and assume the persona remains stable, when real people and markets are shifting fast.
In that same dinner conversation about Gen Z’s “vibe check,” I pushed the group to think about what that means for modern GTM. If your strategy for Gen Z-influenced buyers still treats them as traditional personas defined by role, title, or budget authority, you’re missing how they actually evaluate trust, community, and peer signal. One letter separates “persona” from “person,” but the gap between them is huge.
How to shift from persona-driven to person-centered GTM
Here’s how to reorient your GTM strategy without throwing out persona work entirely:
1. Map actual journeys, not just idealized ones.
Go talk to real users in that persona bucket. What were they doing just before discovery? What peer forums do they belong to? What frustrations moved them to search? Use these qualitative insights to enrich the persona and make it human.
2. Audit cross-functional touchpoints through the human lens.
Marketing, community, product, and CS each play a part. At every handoff, ask: “What will this person think, feel, and do here? What cues matter?” If each team builds for the persona without coordinating the human flow, you’ll hear complaints like “We were promised one thing and delivered another.”
3. Design your community as a place for real people, not just customers.
If you’re building a scalable community, don’t focus only on “users of product X.” Build for “practitioners who care about topic Y.” That subtle shift expands your reach from the immediate persona to the human motivation behind it. Community then becomes a GTM lever across retention, advocacy, and adoption.
4. Measure behaviors that reflect people, not just personas.
Don’t just track the percentage of persona X who convert. Track how many members of the network contribute, refer, or co-create. These are signals of person-level engagement. For example, dbt tracks contribution, advocacy, and community journey, not just headcounts.
5. Iterate your persona based on what real people show you.
Your “ideal persona” was a hypothesis. Let it evolve by observing people. Ask what different contexts they’re in, what adjacent roles matter, and which peer networks they’re embedded in. Over time the model adapts and becomes richer.
Say it with me: personas are not people
If your GTM strategy refuses to grapple with the complexity of real people, if it stays anchored in tidy persona boxes, you’re limiting your ability to build engaged communities, differentiated product experiences, and aligned customer journeys. But if you make the shift—designing for people who exist, not just personas you invented—you open the door to deeper engagement, stronger retention, and a community-led growth flywheel instead of a segmented funnel. Personas aren’t useless. But person-centric thinking should be your default.
Decoded Takeaways
When you treat customers as personas you design for “average.” When you treat them as people you design for connection, diversity, and meaningful engagement.
GTM alignment improves when all functions build for the same human experience, not isolated persona fragments.
Community is a powerful lever for shifting from persona to person because it reveals motivations, networks, and peer behavior that personas alone miss.
Real people show you what the persona model leaves out—peer context, emotional stakes, and unexpected use cases. Use that to iterate and grow.
Measuring person-centric signals like contribution, advocacy, and referral gives you a fuller view of community-led growth, adoption, and retention than just tracking “persona X sign-up rate.”