PM Live 2026 · Smolarz Auditorium, Tel Aviv

The Good Enough Trap

How we stopped chasing giants' features and found our winning strategy — and what every product manager can learn from it.

Speaker Tomer Hevlin
Title VP of Product, Morphisec
Date May 19, 2026
Read time ~8 min
Read the story
Act 01 — The Problem

When the numbers
don't lie

Two years ago, I walked into a boardroom at Morphisec. The CEO, VP Sales, and senior leadership were all there. Usually these meetings buzz with energy — new features, big dreams. That day felt like a funeral.

The numbers weren't lying. Sales had dropped quarter after quarter. Our average deal size had eroded to unprofitable levels. And we all knew why: the market had shifted beneath our feet. Microsoft Defender for Endpoint was everywhere, accessible and cheap. CrowdStrike had become a monster. Our message of "we fill the gaps" stopped working — because the gaps had closed.

"We looked at the market, saw everyone rushing to Exposure Management, and said: great — us too."

— The decision that almost killed us

And so we entered what I now call "The Good Enough Trap." A salesperson would beg: "The customer says if we just add this one feature, they'll drop product Y and buy us instead." So we got to work. Feature after feature, following the playbook — design partners, discovery sessions, all of it. A year later, we had built a shiny new Exposure Management product.

We had 6–7 excellent features. Our competitors had 30. Customers looked at us and asked: "This is nice — but why would I buy this from you instead of Palo Alto?" We had become a Feature Factory. And we were losing.

01
The Trap
Reacting to competitors' features creates a race you can't win. You're always behind, always smaller.
02
Feature Factory
When every sprint is driven by "the customer asked for it" or "the competitor has it" — you've lost strategic control.
03
The Wake-Up
80% of our planned roadmap was maintenance or chasing competitors' tails. We could see it, all at once, on the wall.
Act 02 — The Myth of Value

Why your prioritization
framework is lying to you

We all grew up on prioritization methodologies. RICE. Value vs. Effort. MoSCoW. We open Excel, score Value, score Effort, get a magic number. We feel like scientists. I want to say something hard: these frameworks are part of the problem.

They worship Value — and that sounds logical. "Always deliver value to customers." But here's the thing: our Exposure Management features had value. Customers wanted them. They passed every RICE filter. But they didn't help us sell. Why? Because value is table stakes. Your competitors have value too. Sometimes more.

"The question isn't 'how much value does this deliver?' The question is: 'does this make a customer choose us over a competitor?'"

— The shift that changed everything
The Old Way
Prioritize by Value

Customers happy → but so are your competitors' customers. You end up in a crowded middle where nothing stands out and no one remembers you.

The New Way
Prioritize by Differentiation

Value makes customers satisfied. Differentiation makes customers choose you. Only one of these wins deals.

Act 03 — The Practical Workshop

The Spotlight Matrix

We gathered every Product Manager in a room with a giant whiteboard and a thick stack of Post-its. The instruction was simple and brutal: write every feature currently in the Roadmap, Backlog, or in your head. One Post-it per feature.

Then we introduced the framework. Two axes. Every feature gets placed on the grid.

← LOW · DIFFERENTIATION · HIGH →

The Spotlight Matrix

Spotlight Zone
Invest here
High differentiation, low parity. Only you can offer this. This wins deals.
Safe Bet
Maintain carefully
Everyone has this AND it's differentiating. Strategic parity play.
Nice to Have
Low priority
Unique, but nobody cares. Interesting but not decision-making.
Commodity Trap
Avoid / cut
Everyone has it, no one notices. This is where roadmaps go to die.
Ransomware Recovery
Memory Key Extraction
Zero-day Prevention
Threat Intel Feed
SIEM Integration
Custom Dashboard
Export Report
Email Notifications
Vuln Scanning
Asset Inventory

← LOW · PARITY (being like everyone) · HIGH →

"When we put the matrix up — 80% of our planned work for the next year was sitting in the bottom right. The commodity trap. We could see it, right there, yellow on white."

— The moment the team understood

There was resistance. PMs fought for their features. "But we promised this in the QBR!" "The engineers already started!" But as we went feature by feature, the picture became undeniable. We were building things that would make us adequate — not exceptional.

Stop lighting up the whole room.
Pick one corner. Aim the biggest spotlight you have. That's how you get noticed.

The metaphor that stuck: imagine a huge dark room — your market. Your instinct as a PM is to light up every corner. A small lamp here (email notifications), a small lamp there (custom dashboard). You're running from side to side. But everything is dim. Nothing stands out. The customer can't see anything except chaos.

The Spotlight Matrix says the opposite: turn off all the small lights. Pick the one point where you're strongest, and blast a single massive spotlight on it. That's what customers remember. That's what wins deals.

Act 04 — The Pivot & The Valley

Stopping everything.
Starting over.

Our research confirmed it: customers bought Morphisec for one burning problem — Ransomware Protection. The kind that competitors couldn't solve to their satisfaction. We heard phrases like "peace of mind," "I sleep well at night," "I don't even know you're there — and that's exactly what I want."

The features we thought were critical? "Nice." Or: "We already have that in product X." So we made the call: stop building Exposure Management features. Stop chasing. Become the best ransomware prevention product in the world.

The Decision
Halt the Exposure roadmap
We stopped releasing Exposure features. Release notes got smaller. Customers and sales teams noticed. "What's happening? Why has the feature pace slowed?" The vacuum was uncomfortable.
Valley of Despair
The two hardest months
Old features paused. New Ransomware features still in development. Nothing ready to ship. This is the moment most teams break and go back to building generic features "just to ship something." We held the line.
Shifting the Narrative
Retraining Sales
"When a customer asks why we don't have X — don't apologize. Tell them proudly: we don't have it because having it would make us like everyone else. We gave that up to give you something no competitor has." Slowly, the team stopped apologizing for what was missing and started attacking with what was unique.
The New Product
Features that only we could build
Ransomware-specific capabilities: preventing data exfiltration used in double-extortion attacks, extracting encryption keys from memory to free files at no cost, one-click recovery for encrypted files. Customers who saw the new roadmap lit up. "I've never seen this anywhere else."
The Result
The team caught fire
Engineers who had been "production workers" — copying dashboards, adding export buttons — became inventors. They were solving puzzles nobody had solved before. The energy spread to Customer Success, Marketing, Sales. A single sharp message replaced ten muddled ones.
The Valley of Despair — Every Bold Pivot Goes Through Here
Valley of Despair Decision Momentum TIME → MOMENTUM →
The Framework

What to take
back to the office

Product managers are not order-takers filling Excel sheets based on sales demands or competitor features. We're directors deciding where to point the camera — and which lights to turn off so the spotlight hits what actually matters.

1
Stop prioritizing by value alone — prioritize by differentiation
Value makes customers satisfied. Differentiation makes them choose you. Your RICE score doesn't capture this. Add a "Does this make us unique?" filter to every feature decision.
2
Map your entire roadmap on the Spotlight Matrix
Get your team together. Post-its on a whiteboard. Two axes: Parity (x) and Differentiation (y). You'll see the commodity trap visually. What you see will be uncomfortable — that's the point.
3
Talk to customers about pain, not features
We discovered ransomware was the burning pain by listening, not by looking at what competitors offered. Ask: "What would make you sleep better at night?" Not: "Which feature would you add?"
4
Be proud of what you don't build
Saying no to features is the hardest PM skill. Train your sales team to say: "We don't have that — and we're proud of it. Because we spent that capacity building something no competitor has."
5
Survive the Valley of Despair
Every bold pivot goes through a painful gap between decision and results. The temptation to revert is massive. Get leadership alignment before you start, manage expectations proactively, and use Maintenance Mode for old features.

Find your
Spotlight

Open your roadmap tomorrow morning. Don't look for what to delete. Look for what to illuminate. Find the one feature only you can build — and aim everything at it.