When Everything Is Possible, Coherence Becomes the Work

The Moment I Started Hearing the Same Question Everywhere

Last week, I sat in on three very different conversations.

One was with a data team frustrated that their dashboard suite felt “impressive but unused.” Another was with a founder who kept postponing a design system because their product was “still changing every week.” The third was a research debrief where we couldn’t explain why trial users were dropping off after they’d activated the core feature.

Different products. Different stages. Same unease.

No one thought they had a feature problem. What they couldn’t articulate was something quieter: what exactly are we asking people to understand, trust, and commit to right now? In a landscape where building is faster than ever, the hard work has shifted. It’s no longer about making things possible. It’s about making them coherent.

As a product strategist, I’ve learned to pay attention when the same tension shows up in different rooms. That usually means the craft is moving under our feet.

Speed Didn’t Break Our Products — Optionality Did

Most of the current discourse frames our moment as a speed problem. Too many features. Too many tools. Too much shipping. There’s truth there, but it’s incomplete.

What’s actually changed is optionality.

Today, teams can:

• Spin up new features with minimal marginal cost
• Launch micro-SaaS ideas into hyper-niches almost overnight
• Re-architect frontend and backend choices late in the game
• Swap AI capabilities in and out as they mature

From a delivery standpoint, this is extraordinary. From a user standpoint, it’s destabilizing.

When everything is possible, nothing is anchored by default.

I saw this clearly in a data product I advised last year. The team was exceptional — senior PMs, thoughtful designers, strong engineers. Over 18 months, they shipped dozens of features requested by real customers. Adoption metrics looked healthy in isolation.

But when we mapped usage flows end-to-end, something unsettling emerged: no two customers described the product the same way.

“It’s like five good tools sharing one login,” one user said.

This wasn’t a failure of execution. It was a failure of coherence.

A McKinsey study from 2023 found that products with a clearly articulated value narrative outperform peers by up to 30% in user retention, even when feature sets are comparable. The delta isn’t capability — it’s comprehension.

Optionality without strategy doesn’t feel empowering. It feels unfinished.

Design Systems, Data Systems, and the Myth of “We’ll Do It Later”

The same pattern shows up in the design system debate.

I keep hearing: “Once the product settles, we’ll formalize things.”

But that assumes products stabilize before users form expectations. They don’t.

Every weekly change teaches people something — about what’s reliable, what’s experimental, and what they shouldn’t get too attached to.

In one startup I worked with, the absence of a design system wasn’t just a visual issue. It created behavioral noise:

• Buttons that meant “commit” in one flow meant “preview” in another
• Tables that supported bulk actions sometimes, but not always
• Empty states that alternated between helpful and vaguely apologetic

Individually, these were minor. Collectively, they taught users to hesitate.

And hesitation is expensive.

Research from Baymard Institute shows that 69% of users abandon workflows due to uncertainty, not difficulty. They don’t leave because they can’t proceed. They leave because they’re unsure whether they should.

A design system, at its best, isn’t about consistency for its own sake. It’s about preserving intent under change.

What should this product feel confident about, even while everything else evolves?

That question is strategic, not aesthetic.

The New Conversion Problem Is Interpretive, Not Persuasive

A lot of recent writing frames customer acquisition as a “hesitation problem.” I think that’s exactly right — but not in the way growth teams usually interpret it.

We tend to respond to hesitation with:

• More onboarding
• More tooltips
• More copy explaining the same thing in three ways

But hesitation rarely comes from lack of information. It comes from conflicting signals.

I saw this starkly in a SaaS trial analysis earlier this year. The team had instrumented everything: activation events, feature usage, time-to-value. Classic funnel.

What surprised us was this: users who explored more features in the first 48 hours were 18% less likely to convert than users who did less.

More engagement, worse outcome.

When we reviewed session recordings, the pattern was obvious. Power users were trying to reverse-engineer the product’s “real purpose.” They were scanning for a center of gravity.

They didn’t find one.

People don’t commit when they’re impressed. They commit when they’re oriented.

This is where product strategy quietly intersects with research craft. Metrics told us what was happening. Interviews revealed why:

“I wasn’t sure which way was the right way to use it,” one trial user said. “So I didn’t want to bet my workflow on it yet.”

That’s not a pricing problem. It’s a judgment problem.

Working Without a Map Doesn’t Mean Working Without a North Star

Product folks like to romanticize ambiguity. We talk about “learning as we go” and “working without a map.” There’s wisdom there — but also a trap.

Ambiguity is only generative when something else is stable.

In teams I see struggling right now, three things are often moving at once:

1. The product’s core use case
2. The system structure (design, data, architecture)
3. The story being told to users

When all three shift simultaneously, learning collapses into noise.

Contrast that with a team I advised in the healthcare space. Regulatory uncertainty forced constant iteration. But they anchored on one invariant principle:

“We reduce the cognitive burden on clinicians at decision time.”

Every feature, every UI choice, every roadmap tradeoff was tested against that sentence.

They still moved fast. They still changed direction. But users described the product with uncanny consistency.

Strategy, in practice, is deciding what doesn’t get to change this quarter.

Not forever. Just long enough for people — users and teams — to build trust in their own understanding.

What I’m Advising Teams to Do Differently Right Now

These conversations have changed how I guide product teams. Less about roadmaps. More about interpretation.

Here’s what’s proving useful:

1. Name the Product’s Current Center of Gravity

Not the vision. Not the eventual platform. The now.

• What is this product unmistakably for today?
• What kind of user should feel immediately seen?
• What problem should feel boringly well-handled?

If your team can’t answer this in one sentence, users definitely can’t.

2. Audit for Conflicting Commitments

Look for places where the product promises incompatible things:

• Flexibility and strict guidance
• Power and approachability
• Speed and deliberation

You can hold tensions — but only if you acknowledge them explicitly.

3. Treat Systems as Narrative Infrastructure

Design systems. Data models. Onboarding flows.

These aren’t internal hygiene. They’re how the product explains itself over time.

A 2024 Nielsen Norman Group report found that users form a mental model of a product within their first three meaningful interactions. After that, inconsistency feels like betrayal, not experimentation.

4. Measure Orientation, Not Just Activation

Ask research questions like:

• “If you had to explain this product to a colleague, what would you say first?”
• “What would you not use this product for?”

Clarity shows up as much in exclusions as in enthusiasm.

Why This Feels Harder Than It Used To

None of this is about teams getting worse at their jobs. It’s the opposite.

We’re better builders than ever. That’s exactly why judgment matters more.

When constraints were external — slow releases, expensive infra, limited tooling — coherence emerged by necessity. Now it has to be chosen.

And choice is uncomfortable.

It requires saying no to plausible futures. It requires letting some users be confused now so others can be confident. It requires holding the line when new capabilities tempt us to redraw the story yet again.

I’ve felt this personally. As a consultant, it’s far easier to help a team add something than to help them decide what to stand behind.

But the products that last — the ones people trust with real work — don’t win by being endlessly adaptable.

They win by being understandable at the moment of commitment.

The Quiet Shift I Don’t Want Us to Miss

The conversations happening right now — about strategy over features, systems amid change, hesitation over acquisition — are all pointing to the same truth.

The center of product work is moving from construction to sensemaking.

From Can we build it? to What will people believe about it once we do?

That’s not softer work. It’s more demanding. It asks us to care not just about outcomes, but about the mental and emotional labor we impose along the way.

If there’s one thing I hope teams take seriously this year, it’s this:

In a world where everything is possible, coherence is the most generous thing you can offer.

Not because it’s elegant. But because it respects the human cost of figuring things out.

And that, more than any feature, is what earns commitment over time.