Imagine this: A MedTech product manager is standing in front of a chief physician, presenting a new device. He talks about the 7-inch touchscreen. The two flexible tubes. The connectors on the back. The integrated storage.
The chief physician listens. Nods. And doesn't buy.
The problem: The PM explained everything correctly. And still communicated nothing that mattered to the customer. He listed features. He didn't solve a problem. He didn't promise an outcome. He gave the physician no reason why this device would make their daily work better.
That's called Feature Fucking. And it's the most common communication mistake in product presentations.
Why PMs get trapped in feature language
Product managers are hired, evaluated, and promoted for their technical knowledge. They spend their time writing specifications, briefing engineers, and creating regulatory documentation. Their language is precise, technical, and comprehensive.
That's right and necessary. But that language can be counterproductive in customer conversations because customers don't think in features. They think in problems. In goals. In risks they want to avoid.
Antonio Damasio's research in neuroscience has shown that without emotion, people can have serious difficulty making decisions. For Sales, the implication is clear: If you present facts alone, you leave an important part of decision-making out of the conversation. Communicating consequences and outcomes makes it tangible why a decision matters to the customer.
The transformation: From feature to value proposition
Here's the same product twice: once as a feature list, once as value-based communication. Both are true. Only one sells.
| What the PM says (Feature) | What the customer hears (Value) |
|---|---|
| “7-inch high-resolution touchscreen” | “All parameters at a glance, even in difficult OR lighting conditions. No misguided actions caused by unreadable displays.” |
| “Two flexible tubes, 120 cm long” | “Greater freedom of movement when positioning the device: no readjusting, no repositioning. Less hands-on time, more focus on the patient.” |
| “Integrated locking system” | “No unintended disconnection during the procedure. Patient safety without an additional step.” |
| “Plug-and-play installation, no service technician required” | “Ready to use in under 5 minutes. No waiting, no service costs, and no scheduling with IT.” |
| “Wireless module, Bluetooth 5.0” | “Technology in your pocket: all data available on the tablet, even outside the procedure room. Documentation directly at the patient's bedside.” |
| “Compatible with existing systems (HL7 FHIR)” | “No parallel IT environment. Zero migration effort. The data goes where your workflows already live.” |
| “Modular design, replaceable components” | “Downtime reduced to under 2 hours. No need to replace the entire device when something fails, only the affected module.” |
“No chief physician buys a touchscreen. They buy fewer errors, less downtime, lower liability risk, and more time for their patients.”
Why marketing communication doesn't come naturally to PMs
What most PMs were never taught
Whose problem am I solving? What matters to this person at 7 a.m.? What keeps the chief physician awake at night, and what keeps the OR coordinator busy?
A feature is an output. An outcome is what changes in the customer's world because of it. PMs are trained to think in outputs. Customers buy outcomes.
“Safety,” “control,” “trust,” and “simplicity”: These are emotional anchors. Technical precision is necessary internally. In a customer conversation, it can create distance.
Procurement wants cost. The chief physician wants safety. Nursing leadership wants ease of use. The same product needs three different value stories.
What value selling training for PMs looks like
Build a feature inventory
List every technical feature without evaluating it. That's the starting point, not the finished product.
Run the “So what?” test
For every feature, ask: “So what?” What does this mean for the customer? You're not close to the real value until you've asked the question three times.
Build a value map for each persona
Chief physician / Procurement / Nursing / IT: Each gets a different message. Not the same deck for everyone.
- Role-play with Sales: The PM plays the seller. Sales plays the customer and pushes back: “Why should I care?” This trains value language faster than any seminar.
- Win/Loss Reviews: Why didn't the customer buy? More often than not, the answer lies in the communication, not the product.
- Customer visits: PMs join field sales meetings, not to present, but to listen to what customers actually ask.
- One-Pager Discipline: One A4 one-pager for every product, written entirely in the customer's language. If you can't do that, the value proposition isn't clear yet.
A product manager who can't communicate in the customer's language is a liability to Sales in customer conversations, not an asset. Value selling isn't an optional marketing skill. It's a core capability that determines whether a product that deserves to sell actually does.
Sources: Damasio (1994), Descartes' Error: Emotion, Reason, and the Human Brain, Putnam.
Published June 2026