Imagine a project manager who starts every morning chasing updates. They open five tools, message six people and still cannot tell whether Friday’s deadline is in trouble.

Then they find a product that helps them see what needs attention and decide what to do. They spend less time checking and more time moving the work forward. They can close the laptop without wondering what they have missed.

Ask what they like, and they might tell you the product is easy to use. That is a reasonable answer. But it may only partly describe the change they have experienced: their working day feels manageable again.

The company sees a customer using project management software. The person using it may feel they have regained control.

That is where I would begin a conversation about positioning.

The business needs to understand that change well enough to keep making it possible as it grows. Otherwise, it can improve the product by its own measures while taking away the progress the customer experienced.

A transformation does not have to be dramatic. Someone finishes a difficult task, makes a decision with more confidence or feels comfortable somewhere they used to feel out of place. What matters is that something meaningful becomes different for them.

That change gives substance to the position a business can earn in people’s minds. Repeated experience creates an expectation. Your name starts to mean something because people associate you with what becomes possible.

Delivering a useful benefit does not automatically make it yours to own. Competitors may provide it too. The strategic work is deciding which change you will build the business around, then making choices that give people a distinctive reason to associate it with you.

For our software company, protecting that sense of control might mean refusing features that make the product harder to navigate, even when a large prospect offers to pay for them.

Making that choice requires understanding more than the words customers use to describe the product.

People can experience value without having a complete explanation for it. They may recognise that something feels different before they can say why. That gives us a responsibility to investigate. It does not give us permission to invent a flattering story about their motives.

A first purchase may depend on a recommendation, a promise, price or availability. Experience then confirms, changes or disappoints the expectation. Even repeat buying is an incomplete signal: habit and the difficulty of switching can keep a customer around.

The question I want the business to keep answering is what is becoming better for this person, and which decisions make that possible.

As a company grows, the connection between those two things can become harder to see. The product team owns the release schedule. Sales owns new contracts. Support owns response times. Finance owns the cost base. Each responsibility matters, and each team needs a way to judge its work.

But the customer experiences the combined result. Completing each department’s assigned tasks does not, by itself, give someone control of their working day. The whole experience has to help them get there.

Go back to our imagined software company. It adds more dashboards, more notifications and more settings. Each addition answers a request. People spend more time inside the product, and the company celebrates increased engagement.

Meanwhile, the project manager has started checking everything again.

The company may still be selling the same product under the same name. It may even be serving more customers. Yet it has begun to weaken the change that made the product valuable to this person.

This can happen through decisions that each have a sensible explanation.

In his February 2007 memo, Howard Schultz described how Starbucks’ automated espresso machines improved speed and efficiency while obstructing customers’ view of drink preparation and their contact with baristas. He also questioned the combined effect of packaging and store-design decisions on the experience. He acknowledged his own part in those decisions.

The memo records Schultz’s diagnosis; it cannot establish how much those changes affected sales. It raises a useful question: who checks what happens to the customer when each department improves its own part?

The subsequent machine choice makes the question more useful. Starbucks introduced the lower-profile Mastrena in 2008. Its announcement described a design intended to improve visual contact between baristas and customers while supporting consistent drink preparation.

The design recognized both requirements. It treated the customer benefit as something the equipment needed to support. One reason this kind of damage can be hard to catch is that customers may keep buying even as their experience weakens.

Someone might give you the benefit of the doubt. They might stay because changing suppliers is inconvenient. They might renew a contract while quietly looking for an alternative.

For a while, the business can be living off trust it earned under earlier conditions.

That creates a dangerous possibility: the saving appears before the loss becomes visible. The cost of an experienced employee is easy to identify. The effect of losing someone who understood your customers may take longer to reveal itself. A decision can look successful while its consequences are still developing.

That makes it worth examining what you are removing before the revenue tells you whether it mattered.

Pressure to grow introduces another risk: copying the operating model of a much larger competitor. The larger company may make that model work through scale, distribution or buying power. The smaller company could lose its difference without gaining those advantages. Adopting the same process does not mean competing on the same terms.

For a founder who senses that happening, it can feel like a lesson in trusting instinct over the advice that led them there. Regret does not establish that instinct would have produced a better decision. It does make me wonder whether the analysis captured what the founder feared losing.

An instinct may contain an understanding the founder has not yet learned to explain. They may sense that a proposal removes something customers depend on, while the analysis measures a different set of consequences. Their discomfort could also reflect a personal preference the customer does not share.

Both the customer who feels the benefit and the founder who senses its loss can struggle to explain what matters. The business needs to make that understanding clear enough for other people to act on it.

The useful next step is to make the concern specific. What do you expect customers to lose? Which part of the experience carries it? What evidence would support your concern, and what would make you reconsider?

That gives judgment something to work with. It also gives the team a way to understand the concern instead of repeatedly waiting for the founder to approve or reject a plan.

The same scrutiny has to apply to the instruction to stay true to the early days.

A founder might once have called every customer personally. Those calls helped people feel understood and helped the founder learn. Years later, requiring everything to pass through the founder could leave customers waiting days for a response.

The original practice is intact. The benefit is disappearing.

Preserving that benefit may now require a trained team, better records and the authority to act without asking permission. The way the company works changes so the customer can continue to receive the care that mattered.

The distinction for leaders to hold onto is what must endure for the customer, and what we are willing to change inside the company to keep delivering it.

Being unusual has no automatic value. Neither does following a familiar playbook. A process earns its place through what it enables, including the reliability and economics required to keep doing the work.

A business has to pay its people, maintain its product and invest in what comes next. A customer benefit that the company cannot sustain will eventually disappear. Protecting it may require better systems, a different price, a narrower offer or a refusal to serve requests that make the core experience worse.

The hard work is distinguishing what the customer would happily lose from what they would deeply miss. Both can appear as costs in the same budget. Bring that distinction into the next consequential decision.

Take the plan to automate onboarding, remove a service, change an incentive or pursue a larger customer. Describe what the person on the receiving end can do today because of the way you work. Be concrete enough that somebody could tell you the description is wrong.

Ask customers about specific moments. What did they do that they would previously have delayed? What stopped worrying them? What disappointed them after a change? Compare their accounts with what you observe, including the experiences of people who left.

Then trace how the proposed decision affects that experience. If it removes a conversation, what did the conversation accomplish? If it moves work to the customer, how much effort have they inherited? If it adds options, can people still make the decision they came to make?

Ask the people closest to the work how the team could hit the new target while making the customer’s situation worse. Their answers can expose a weakness in the target before anyone is rewarded for exploiting it.

Pair the internal measure with evidence of the change you intend to preserve. For our project manager, more time in the product would be difficult to interpret on its own. Can they spot a problem, decide what to do and move on without chasing everyone for reassurance?

Read the cases behind the numbers. Watch someone do the work. Look for experiences that contradict the story you want to tell.

Then give someone the authority to act on what you find. A team that can report a problem but cannot change the rule causing it is left explaining the same disappointment more politely.

This becomes especially demanding when the rule belongs to you. You may have proposed the target, promised it to the board or built your reputation around the practice. Protecting the customer benefit can require giving up the satisfaction of being right.

That is where positioning becomes a business decision with consequences for budgets, authority, product design and the work people are rewarded for doing.

You can keep the name, the product and the story while losing the change people once experienced. You can also redesign substantial parts of the business and become more faithful to it.

Before approving the next improvement, ask: will this decision help us keep making that change possible, or gradually take it away?