Why Organizations Struggle to Understand People

Picture of Tony Zambito

Tony Zambito

Share This Post:

How Experience, Assumptions, and Organizational Thinking Can Limit What We Believe We Know About the People We Serve

Several years ago, I was brought in to work with a health insurance company that had introduced a new offering and wasn’t seeing the results it had anticipated.

The company had been serving its market for many years. Its leadership knew the business well and believed it had a strong understanding of its customers, and that confidence was understandable. Years of experience had given the organization real knowledge of the market, of employer relationships, and of the people who relied on its insurance products.

The new offering reflected what was then an emerging direction in health insurance: greater consumer responsibility. With higher deductibles and more responsibility for choosing healthcare services, employees would increasingly be expected to behave like consumers, comparing options and making decisions about cost and care. Leadership believed its customers were knowledgeable enough to make that transition.

The rollout was proving considerably harder than expected.

I was brought in afterward to help figure out why. Through conversations with employees and human resources departments, along with a broader look at how people actually went about making healthcare decisions, a different picture began to emerge. Years of employer-sponsored coverage had shaped how people understood insurance, who was responsible for what, and which choices were theirs to make. Those expectations weren’t going to change just because a new offering required people to behave differently.

The company had built its expectations around how it believed people would respond to the new model. What it hadn’t fully appreciated was how people would read that model through mental models formed over many years. The organization understood the insurance business. It hadn’t adequately understood how people would experience the changes it was introducing.

I’ve thought about that experience often, because it illustrates something I’ve run into throughout my progression with Buyer Personas and Human Understanding. An organization can understand a marketplace as it has existed for years and still misjudge how people will respond when their circumstances change. And sometimes the very experience that gives an organization confidence in its understanding makes it harder to see what it doesn’t know.

When Experience Becomes an Assumption

For much of my engagement work, beginning with the origins and the development of Buyer Personas twenty-five years ago, I’ve worked with organizations trying to better understand the people they serve. One thing I’ve seen repeatedly is that they rarely begin from the belief that they don’t understand their customers. More often, they believe they understand them quite well.

They have years of sales experience, customer relationships, market research, service interactions, and accumulated knowledge. Much of it is valuable, and I’ve never believed organizations should dismiss what they know or assume it’s all wrong. But experience can also become a source of assumptions that go largely unquestioned.

Over time, organizations develop a particular way of seeing the people they serve. Customers become associated with products, purchasing patterns, market segments, or the services the organization provides, and their needs get understood in relation to what the organization offers. That’s a natural tendency. Organizations have goals and responsibilities of their own, and they have to decide where to invest, how to compete, and which opportunities to pursue.

The difficulty comes when that organizational perspective becomes the main lens through which people are understood.

In the insurance example, the company looked at the new offering through the logic of healthcare consumerism: give people more individual responsibility, and they’ll become more deliberate consumers. But the people being asked to make those decisions weren’t starting from the same place. They had years of experience with employer-sponsored coverage and had developed their own expectations about what insurance was supposed to provide, how healthcare decisions got made, and what they were and weren’t responsible for. The company was looking toward a new model of consumer behavior. Employees were interpreting that model through everything they already understood about healthcare.

Neither perspective came from nowhere. Both were built on experience. They just weren’t the same experience.

That’s where experience, however valuable, can turn into an unreliable guide. An organization may understand how people behaved under familiar circumstances without really knowing how they’ll respond once those circumstances change.

Seeing People Through the Organization’s Eyes

I think this is one of the more persistent problems in understanding people. Organizations naturally organize their thinking around the business they’re in. A manufacturer thinks about products and applications, a financial institution about accounts and services, a healthcare organization about coverage and delivery, a nonprofit about programs and participation.

Those perspectives are necessary for running an organization. They just aren’t how people experience their own lives. Nobody starts the day thinking about an organization’s product categories or strategic priorities. People are trying to get something done. They have responsibilities, worries, expectations, and goals, and all of it sits inside circumstances the organization may barely see.

This has always been central to how I think about Buyer Personas: people pursue goals, and those goals take on meaning inside the situations in which people are trying to reach them. Start with the organization’s products or objectives, and it’s easy to miss the larger circumstances shaping what people decide.

That’s why the conversations with employees and HR departments mattered so much in the insurance work. We weren’t gathering reactions to an insurance offering. We were trying to understand how people approached healthcare decisions, what they believed insurance was supposed to do for them, how they thought about financial risk, and what happened when familiar expectations ran into unfamiliar responsibilities.

One HR executive put the problem more plainly than any of the research could have. Just because you believe people are smart enough to choose their own healthcare services, the executive told us, doesn’t mean they’ll want to get their healthcare that way. The company had been asking whether employees were capable of becoming consumers. What it hadn’t adequately considered was whether they wanted to assume greater financial responsibility and sort through the many choices involved in managing their healthcare.

When we ask people about our products, we tend to learn about our products. When we try to understand what people are trying to accomplish and how they experience the circumstances around their decisions, we can discover things well beyond what we thought to ask. And sometimes those discoveries challenge the assumptions that shaped the offering in the first place.

Why More Information Doesn’t Always Lead to Better Understanding

Organizations today can gather extraordinary amounts of information about the people they serve. They can study purchasing patterns, monitor customer interactions, run surveys, analyze behavior, and increasingly use artificial intelligence to spot patterns that would otherwise go unnoticed. All of that is valuable. It can reveal changes, surface problems, and give organizations evidence for better decisions.

But information and understanding aren’t the same thing. Knowing what people do doesn’t always explain why they do it. Knowing what they purchased doesn’t reveal what they were trying to accomplish. And knowing how they behaved in one set of circumstances doesn’t necessarily tell us how they’ll respond when those circumstances change. Historical data describes what happened inside an established environment. It says much less about how people will interpret a different one, especially when the change runs up against expectations built over decades.

That’s the distinction the health insurance work brought into focus for me. The company had substantial knowledge of its existing market, but the new offering changed the circumstances in which employees were expected to make decisions. Understanding those decisions meant looking past established customer knowledge and examining how people made sense of the change itself.

There’s another challenge I’ve seen in organizations too: understanding gets scattered. Sales may understand one part of the customer relationship. Marketing may hold the research and market data. Product development concentrates on usage and functionality, and customer service hears the problems and frustrations that never show up anywhere else. Each view is valuable, and each is shaped by the responsibilities of the function collecting it. I’ve watched different parts of an organization hold pieces of an important story while no one put them together to see the larger circumstances behind people’s decisions.

So the issue isn’t only whether information gets shared. It’s whether the organization can interpret what it knows in terms of the people it serves, rather than only through the needs of individual departments. As AI makes it easier to gather, organize, and analyze information, I think that distinction becomes more important, not less. More information can expand what we know. It doesn’t automatically change the assumptions we use to interpret it.

Learning to See Beyond What We Already Know

As I’ve been developing Human Understanding as an organizational discipline and competency, I’ve become increasingly interested in what it takes for an organization to recognize the limits of its own understanding. I don’t believe the answer is simply more research, better surveys, or greater access to customer data. Those can help, but they don’t address how organizations interpret people in the first place.

Organizations have mental models, just as individuals do. They develop shared beliefs about customers, markets, and how decisions get made, and those beliefs shape strategies, investments, and the questions leaders consider worth asking. Often they’ve been formed by years of legitimate experience, which is exactly what makes them so hard to recognize, let alone question. The insurance company’s experience wasn’t irrelevant. It had served the organization well for years. But a new offering changed the circumstances, and the understanding that had guided the company in the past wasn’t enough to anticipate how people would respond.

Which means understanding people can’t be something we accomplish once and carry forward unchanged. People’s goals may stay fairly consistent while the circumstances around them change a great deal. Their expectations may be shaped by years of experience even as organizations introduce new ways of doing business. And the mental models people use to interpret their choices may evolve differently than an organization expects.

This is why I believe Human Understanding has to be more than a collection of research activities. It requires organizations to examine their own assumptions, understand people’s goals within the circumstances that matter, and recognize when established ways of thinking no longer reflect how people actually experience things.

In last week’s essay, When Understanding Changes the Decision, I explored what happens when organizations encounter insights that challenge the direction they’ve chosen. But there’s a question that comes before that one.

How do organizations recognize when their understanding of people is incomplete in the first place?

The health insurance experience reminded me that the answer often starts with something we rarely think to question: how much of what we believe we know about people comes from their experience, and how much comes from our own?

The more I’ve worked with organizations, the more I’ve come to appreciate that understanding people requires something of the organization itself. It has to be willing to recognize that its own experience, however extensive, is not the same as the experience of the people it serves.

Perhaps that’s one of the most important starting points for Human Understanding as an organizational competency.

Not assuming that everything we know about people is wrong.

But remaining open to the possibility that what we know may no longer be enough.

Categories: