When You're Competing on Features, You've Already Lost the Story

This week I was at the Competitive Marketing Summit presenting to competitive intelligence professionals. My talk was about corporate narrative — specifically, what narrative health and breakdown look like from the outside, and why CI teams are well-positioned to read those signals in their competitors.

It was a good conversation. But one idea lingered afterward — less as a point about competitive intelligence, and more as it applies to anyone running a company, leading teams, and individuals trying to understand why their positioning isn’t working. 

The idea is simple: feature competition is often a signal that the foundational narrative isn't doing its job.

The Pattern

You've probably seen this play out. A competitor launches something - a new capability, a campaign, a well-timed announcement that gets forwarded to your Slack channel with a "did you see this?". It circulates quickly. Internally, it triggers the same response: match it, counter it, respond. Show the market you're not standing still.

From the outside, this looks like healthy competition. From the inside, it usually feels like a fire drill.

When those fire drills become routine - when your roadmap starts looking like a response to someone else's roadmap — something deeper is going on. You are no longer operating from strategy. You are reacting. And what looks like a product issue is, more often, a narrative failure.

When your foundational narrative is clear and strong, competitor moves don't pull you off course. You operate on your own terms. You know why you matter, you know what you're building toward, and you can evaluate a competitor's announcement against your own trajectory rather than treating it as a crisis.

Companies without that clarity default to feature competition. In the absence of a strong answer to “why we matter,” activity becomes the substitute.

I wrote about this dynamic from a different angle in Any Game but Chess. That issue was about the choice to compete on someone else's terms versus reframing the competition entirely. Feature wars are what happen when you've already accepted someone else's terms without realizing it.

How to Tell the Difference

Not all feature velocity is misguided. Sometimes you're in a specs-driven market  and parity matters. Occasionally, a competitor genuinely shifts the landscape.

The distinction is this: is the company setting the terms of competition, or responding to terms someone else set?

A company with a strong foundational narrative launches proactively. Their products arrive into a context they have already shaped. The market understands the direction.  The launch feels like a natural next chapter in a story they've been following.

A company under narrative strain launches defensively.. It answers someone else's question. The product may be perfectly good, but it lands in a context someone else created. The company is present, but is not leading.

In Optimization Without Story Is Just Noise, I laid out the hierarchy: Story → Signals → Surfaces. Without the story as the foundation, everything above it — the signals you send, the surfaces where your work shows up — is just mechanics. Feature competition is what happens when you skip the foundation and start building from the middle. You're generating activity. You're producing output. But none of it is anchored to a story about why you matter.

When Activity Replaces Clarity

There's a version of this I explored in When Technology Becomes the Story — the pattern where fluency with new tools gets mistaken for understanding of the business. Feature competition runs on a similar confusion: Shipping more is assumed to compensate for lack of clarity. 

It's not. What you ship is a signal. What you stand for is the story. When the story is unclear, increasing the volume of signals only amplifies the confusion.

The symptoms are subtle but consistent:

• Messaging that shifts quarter to quarter

• Positioning that bends with each competitor move

• Websites that explain what a company does but not why it matters

• Leadership conversations that focus on capabilities when the market is asking about purpose

None of these are fatal on their own. Individually, they are manageable. As a pattern, they indicate a deeper issue: the absence of a coherent narrative foundation.

This Isn't Just a Company Problem

This pattern doesn't just show up in companies. It shows up in careers.

When professionals feel uncertain—about their value, trajectory, or standing—the instinct is to accumulate credentials. More skills, more certifications, more lines on a résumé.

That's the individual version of feature competition. You're matching specs instead of telling a story about why you matter.

The better question is not “what else can I add?” but “can I clearly articulate why I matter?” Without that clarity, additional features don’t resolve the underlying problem.

There's a related tell that's even more common: when you find yourself explaining what you do instead of why it matters. When someone is clear on their value, they talk about impact. They describe the change they create for the people they work with. When clarity fades — when the story drifts — they default to describing activities. Job titles. Responsibilities. Tools they use. The transformation-to-features drift, at the personal level.

And here's the thing: the person who gets picked isn't the one with the most features. I wrote about this in Why Some People Get Picked Early — the signals that get you in the room aren't a list of specs. They're narrative coherence. The candidates who stand out are rarely those with the longest list of capabilities. They are the ones whose story is coherent—whose signals align with their claim, and who can answer “why you, why now” without hesitation. 

In Your Swim Lane Is a Signal, Not a Constraint, I made the case that being trusted for something specific beats trying to be everything to everyone. Feature competition — whether it's a company matching a competitor's roadmap or a person stacking credentials to cover all bases — is the opposite of that. It's answering someone else's question instead of defining your own.

Berkson's Bits

"Who within your organization is internally and externally responsible for your "brand narrative?"

I often find inspiration for these Bits by going back in my Linkedin archives. Considering the recent publication of my book on corporate narratives, I was wondering how long I've been asking that question. I posted that question on Linkedin in June 2014. So, a pretty long time.

What I'm Listening To...

I've had this Jacob Collier cover of the James Taylor classic "You Can Close Your Eyes" on repeat the last week. I think he does it justice.

Whether you're running a company, leading a team, or figuring out your own next move — the diagnostic is the same.

Are you setting the terms? Or are you answering someone else's?

If your roadmap, positioning, or professional narrative is continuously shaped by external moves, the issue is not the response itself. It is the pattern.

Feature competition is a symptom. The question is what it's a symptom of. So whether it's your company or your career — ask yourself: are you setting the terms right now? Or responding to someone else's?

Looking forward to continuing the conversation...

Alan