The mistake of turning a customer into a photograph

What happens when a company thinks it knows its customers, but in reality only knows an outdated version of them?

That risk is more common than it seems.

Organizations invest time in building segments, buyer personas, behavioral profiles, and needs maps. The problem isn’t in doing this. The problem arises when that information is assumed to be valid for too long and begins to be used as if the customer were a stable, predictable, and virtually unchanging entity.

But people don’t work that way.

The same customer may make very different decisions depending on the moment, the urgency, the channel, the economic context, their recent experience with the brand, or even what they’ve just heard from someone else. They may seek autonomy in one interaction and need guidance in the next. They may be price-sensitive today and prioritize convenience tomorrow.

The Importance of the Customer Experience in Competitive Advantage

Even so, many customer experience decisions are still based on profiles that were created months ago and are rarely reviewed with the same rigor as other business metrics.

That’s where the problem begins.

When the customer becomes a snapshot, the organization stops observing them in motion. It begins to design for a representation of reality rather than for reality itself.

And that difference may seem small in a presentation, but it becomes enormous when it affects decisions about service, channels, communication, personalization, customer journeys, and value propositions.

This article does not question the value of buyer personas, segmentation, or customer profiles as working tools. It discusses what happens when those tools stop evolving at the same pace as the people they’re meant to represent—and a question that few organizations ask themselves often enough: How many decisions about experience, service, communication, or value propositions are being made today based on a version of the customer that no longer fully corresponds to reality?

-The problem isn’t taking the snapshot

-The customer changes even if the PowerPoint doesn’t

-A persona is for understanding, not for pigeonholing

-What the customer does today may say more than what they said six months ago

-Signals matter when they change a decision

-CRM doesn’t need more data; it needs context

-Customer Experience should adapt as the customer changes

The problem isn't taking the picture

At a strategy meeting, someone opens a presentation and a slide appears that everyone recognizes. It shows a photo, a fictional name, an age, an occupation, some motivations, frustrations, preferred channels, and a phrase that attempts to summarize how that customer thinks.

The team nods in agreement. Marketing knows this person. Sales does, too. Customer Service has used this profile in a workshop. It’s even possible that this profile has been used to redesign a customer journey or make important decisions.

There’s nothing wrong with that scene.

In fact, building a customer profile is one of the most useful ways to force an organization to stop talking about “the market” as an anonymous mass. Good research allows us to recognize patterns, understand needs, and put a face to behaviors that, when viewed solely in a database, would be difficult to interpret.

The problem begins afterward.

It begins when that slide still appears exactly the same a year later.

When no one asks whether that customer is still buying the same way, whether they switched channels, whether they now shop around more before deciding, whether their relationship with the brand has strengthened or weakened, or whether what was identified as an important need still carries the same weight.

That’s when the snapshot ceases to be a tool for understanding the customer and begins, silently, to replace that understanding.

The ICX methodology is based precisely on an important distinction: researching, building segments, developing Persona Playbooks®, and mapping Customer Journeys generates very valuable initial insights, but those insights begin to lose their relevance if the process ends with the delivery of the document.

We could illustrate this in a very simple way:

We research the customer
↓
We build segments and personas
↓
We design their customer journey
↓
We define recommendations
↓
We deliver the project
↓
The organization continues to operate
↓
The client continues to evolve

The last step is the one that’s usually left out of the presentation.

How to Map the Customer Journey in 2026 to Reduce Churn and Complaints

And that matters because a Persona was never intended to be an exact copy of a person. It is a representation. It summarizes common patterns to facilitate decision-making. The problem arises when we forget that distinction and start treating a methodological construct as if it were a permanent description of every individual belonging to that segment.

Consider, for example, a customer whom a company identified as highly digital. She shops online, looks up information on her own, and almost never uses assisted channels. Everything points to her preferring autonomy.

Until she runs into a problem.

Her order doesn’t arrive. There’s a charge she doesn’t recognize. She needs to modify a contract term or resolve an issue that directly affects her money.

Suddenly, that “digital and independent” customer wants to talk to someone. And she wants it now.

Have You Changed Your Contact Person?

Probably not.

The context has changed.

That nuance may seem minor, but it has significant consequences. If the company designed its customer experience assuming that “this type of customer prefers self-service,” it might continue to steer them toward FAQs, chatbots, and forms at the very moment when they most need human assistance.

The picture wasn’t necessarily wrong. It just couldn’t tell the whole story.

That’s why customer insight requires two things that are sometimes confused.

On the one hand, it needs structure: segments, personas, customer journeys, needs, and moments of truth. Without them, it’s very difficult to turn thousands or millions of interactions into something understandable.

On the other hand, it requires movement: recent behavior, transactions, feedback, changes in the relationship, new preferences, and signals that let us know whether what we thought we knew is still true.

In the ICX methodology, the early stages build that foundation using data, behavior, the Voice of the Customer, and research, and transform it into segments, Persona Playbooks®, and Customer Journeys. But the model doesn’t end there: it incorporates an ongoing phase of intelligence and activation designed to keep that knowledge alive, detect changes, and enable the experience to respond to them.

That difference completely changes the conversation.

It’s no longer just about asking:

“Who is our customer?”

We also have to ask:

• Are they still behaving as we expected?
• What has changed since we created this profile?
• What recent signs do we have of its relationship with us?
• Are we confirming our hypotheses or simply repeating them?
• Is the experience we designed still appropriate for what they need today?

Photographs still have value. They help us recognize the person in front of us.

The danger lies in stopping to look at them because we think we already know them.

And that’s where the next problem arises: while our presentations remain unchanged, the client doesn’t stand still.

It’s also helpful for you to know:

What is Customer Experience and what is it for?

Customers change, even if the PowerPoint presentation doesn't

Six months after that meeting, the presentation remains exactly the same.

The same person. The same motivations. The same pain points. The same journey. Even the same phrase that summed up what that client expected from the brand.

There’s just one detail: the client who inspired all of that has now been in a relationship with the company for six more months.

They either made a purchase or didn’t. They tried another channel. They compared alternatives. They had a good experience or accumulated several small frustrations. Perhaps they started spending less, switched categories, filed a complaint, stopped responding to communications, or began dealing with a different branch.

None of that automatically changes the chart.

And that’s where one of the most common contradictions in Customer Experience arises: we devote a great deal of effort to building knowledge about the customer, but far less to asking ourselves how long that knowledge will remain valid.

Time, by itself, does not render research incorrect. A deep-seated need can persist for a long time. Some expectations change slowly, and certain patterns can remain perfectly useful years later.

What does change much more rapidly, however, is the specific relationship a person has with a company.

Let’s consider a customer who has been shopping regularly for three years.

In January, they make four purchases.
In February, four times.
In March, three times.
In April, twice.
In May, one.
In June, none.

From the Person’s perspective, nothing has likely happened. He is still roughly the same age, has the same occupation, similar needs, and many of the characteristics that allowed him to be classified in the first place.

From the perspective of their behavior, something is happening.

January → February → March → April → May → June
4 purchases → 4 → 3 → 2 → 1 → 0

That sequence tells a story that no static description alone could convey.

Maybe they found an alternative. Maybe a recent experience strained the relationship. Perhaps their financial situation changed, they no longer need the product as often, or they’re simply shopping differently.

The data doesn’t yet explain why. But it’s already telling us something very important: the relationship has changed.

That’s where a more mature approach to customer experience begins to ask different questions.

Not only that:

Who is this customer?

Also:

What's going on with this customer?

The difference between the two questions may seem semantic, but it completely changes the way the experience is managed.

The methodology we’re using as the basis for this article specifically incorporates metrics capable of tracking these trends: recency and frequency of purchase, spending trends, retention by cohort, time to churn, reactivation rate, category affinity, reliance on promotions, and value by segment, among others. On the experience side, it includes metrics such as NPS by segment, Voice of the Customer feedback, complaints, moments that most impact the experience, and validation of persona attributes.

None of these metrics can replace a Persona.

What they do is something different: they allow us to verify whether the story we tell about the customer still aligns with the story the customer is writing through their behavior.

And this isn’t unique to retail.

At a bank, a customer may still belong to the same segment even as they begin to reduce their balances, stop using certain products, or increase their service inquiries.

At an insurance company, a customer may renew their policy for several years without any issues until a bad experience during a claim completely changes their perception of the company.

In a B2B company, an account may retain exactly the same firmographic profile—industry, size, revenue, location—while decreasing its use of the service, changing its internal contact, or beginning to explore alternatives.

At a university, a student does not cease to belong to a certain profile just because they begin to show signs of dropping out. But those signs are precisely what should change the way the institution interacts with them.

The profile remains the same.

The relationship does not.

Some information is descriptive, while other information is advisory.

This distinction is very helpful in understanding the problem.

Some data helps describe the customer:

• who they are;
• which segment they belong to;
• what needs they typically have;
• what their general preferences are;
• what behaviors characterize similar people.

And there are other signs that indicate something is changing:

• they shop less frequently;
• they increase or decrease their spending;
• they abandon an interaction;
• they switch channels;
• files a complaint;
• becomes less satisfied;
• stops using a service;
• changes their usual behavior;
• returns after a period of absence.

The first set helps establish context. The second set helps interpret the moment.

A company needs both.

That’s why the CX Intelligence methodology is based on a different approach than a one-time study that’s then filed away. Initial insights are supplemented with transactional data, digital behavior, purchase history, surveys, feedback, and analytical models that allow us to continue observing what happens next.

This also forces us to accept an uncomfortable truth: a good decision made based on outdated information can turn into a bad decision without anyone having made an obvious mistake.

A campaign might have been perfectly designed for a particular segment when it was created.

A customer journey may have accurately reflected the most significant pain points when it was researched.

A persona may have accurately represented a group of customers when it was developed.

The problem arises when the organization continues to use those responses without reformulating the questions.

Because while the company sticks to its definitions, the customer gains new experiences.

And each experience can alter—even if only slightly—what the customer expects from the next one.

That’s where we need to make an even more important distinction: if a customer can behave differently without necessarily ceasing to belong to the same profile, then a Persona shouldn’t function like a box into which we place people.

It should function as a tool that helps us understand them.

And that’s not the same thing.

Learn more about this key topic for reducing churn:

CX as an Early Warning System for Critical Processes

A Persona is meant to help us understand, not to pigeonhole

And that’s not the same thing.

A Persona can help us better understand a group of customers. It can organize scattered information, reveal patterns, explain motivations, and provide different teams with a common language to discuss the experience.

What it shouldn’t do is become a label that determines, in advance, how we expect a person to behave.

Let’s imagine that a company has identified one of its customer profiles as “practical and independent.” This is a customer who values speed, prefers to solve problems on their own, and uses digital channels whenever possible.

The description works.

That is, until that same customer needs to make a decision they consider important.

They no longer want to figure it out on their own. They read comparisons, ask other people, review terms and conditions, call an advisor, and maybe even visit a branch.

Has he stopped being practical and independent?

Not necessarily.

You may still be practical and independent in most of your interactions. What changed was the importance of the decision you were facing.

That detail is crucial because People tend to summarize behavioral trends, not write the script for every future interaction.

When we forget that difference, we start to pigeonhole people.

The organization stops thinking:

“Customers with these characteristics tend to behave this way.”

And it begins to assume:

“This customer behaves this way.”

It seems like a small change in the sentence. In practice, it’s huge.

The Persona is a lens, not a box

Perhaps a more useful way to visualize it is this:

Real customer
↓
has needs
↓
experiences different situations
↓
exhibits different behaviors
↓
leaves clues throughout the relationship
↓
shares some patterns with other clients
↓
Person

The Persona emerges at the end of that exercise in understanding. Not at the beginning of the client’s journey.

However, once it has been developed, many organizations end up reversing the flow:

Persona → “this client is like this” → let’s design everything based on that conclusion.

That’s when a tool created to simplify complexity begins to obscure it.

The ICX methodology treats segments, Persona Playbooks®, and Customer Journeys precisely as models built on evidence—not as conclusions that are never revisited. The logic starts with combining data, behavior, the Voice of the Customer, and research; converting that evidence into experience models; and subsequently maintaining them through a continuous process of intelligence and activation.

There is one word that is particularly important in this logic: evidence.

A Persona should not be relied upon simply because it is well-designed, because the presentation was approved, or because the organization has been using it for three years.

It should be justified because customer behavior continues to support the hypotheses it contains.

That is why CX Intelligence even includes the validation of persona attributes as part of the analysis.

That changes the relationship we have with the tool.

We no longer just ask:

“Which Persona does this customer belong to?”

We can start asking more useful questions:

• Which attributes of this persona are still present?
• Which ones seem to have lost importance?
• Is this Person exhibiting behaviors more typical of another profile?
• Does the current context explain an exception?
• Are we seeing an isolated case or a pattern that is beginning to repeat itself?
• Do we need to modify the model?

The “Person” then ceases to be a rigid classification and becomes a hypothesis that reality can confirm, refine, or challenge.

The same client may seem like different people to us

Let’s return for a moment to the practical, self-reliant client.

• On Monday, they check their balance using an app and take care of it in less than a minute.
• On Tuesday, they purchase a recurring product without asking for help.
• OnWednesday, they receive a charge they don’t recognize.
• OnThursday, they need to change an important term of their service.

In just two days, you can go from wanting zero human interaction to considering it essential to speak with someone.

If we looked only at the initial interactions, we would conclude that they need self-service.

If we looked only at the most recent interactions, we might think exactly the opposite.

Both interpretations would be incomplete.

The interesting thing isn’t deciding which of the two represents the “real customer.” Both do.

What changes is the moment they are experiencing.

And this explains why personalization based solely on profiles can fall short. Knowing that someone belongs to a certain segment helps establish a foundation. But to decide what experience to offer them right now, we also need to understand what’s happening in their relationship with the company.

The methodology itself brings this idea to CRM through variables such as Persona Affinity, Relationship Health, Current Signal, and CX Opportunity. In other words, the profile remains relevant, but it coexists with signals that allow us to interpret the current state of the relationship.

That nuance is important.

It’s not about eliminating Personas in favor of thousands of completely individualized experiences. That would be unrealistic for most organizations.

It’s about avoiding the opposite extreme: designing as if all customers who share a profile should always receive the same response.

Design based on patterns; act based on context

Perhaps that is the most practical distinction.

Patterns help with design.
Context helps with decision-making.

A Persona can help us define the type of language that usually works, the most relevant channels, the predominant needs, or the friction points we need to address.

But when it comes time to interact with a specific person, we need something more.

We need to know if they’ve just made a purchase.

• If it’s been weeks since they last did.
• If they had a problem.
• If they responded negatively to a survey.
• Whetherthey’re strengthening their relationship with the company.
• If is scaling it back.
• If is repeating a usual behavior or if something has just changed.

Because a company may know the Person perfectly well and still get the experience wrong.

Not because their research was poorly conducted.

But because it was responding to who it thought the customer was, when the situation required understanding what the customer is actually experiencing.

And that’s exactly where the next step in this conversation begins.

If we want to prevent a Persona from becoming a mere box, we have to look beyond its description.

We have to look for the clues left by the real person.

Because, in many cases, what the customer is doing today can tell us more about the experience they need than what they told us when we researched them six months ago.

Is your experience truly aligned with what your customers expect?

Discover the ideal time for your UX strategy:

When to Implement UX Design in Your Business Strategy

What comes next in this series

This article is the first in a three-part series on how to keep customer knowledge from freezing in place. Here we looked at why a Persona is meant to help us understand rather than to pigeonhole. The conversation continues in Customer behavior signals that should change your decisions, where we explore why what customers do today can say more than what they said six months ago and when a signal deserves to change a decision.

The series closes with Your CRM doesn’t need more data, it needs customer context, which covers what intelligence should reach the CRM and how to make Customer Experience keep learning as the customer changes.

If you want to review how current your organization’s segments, Personas and journeys really are, our Customer Experience team can support you through that diagnostic.

Request a diagnostic

Complimentary initial diagnostic