Mindful Communication: Converse in the Language of the Listener
Listening, not articulacy, is the core PM communication skill — and it has a method
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 6
- Confidence
- 92%
Gautam inverts the usual advice that PM communication means speaking and writing well. The load-bearing skill is listening — being wholly present in the conversation you are in, letting a frustrated user vent without interrupting, extracting the root cause from the vent, and then speaking back in the listener's own vocabulary rather than yours. The pause-before-reacting mechanism from her meditation practice is what makes each of these possible.
Origin
Upasna Gautam's synthesis of a decade of mindfulness teaching with product management; she credits Dale Carnegie's How to Win Friends and Influence People, which her father made her read at ten years old, as the foundation of her communication skills.
Core principles
- 01Speaking articulately and writing well are worthless if you are not listening
- 02Be in one conversation at a time, entirely
- 03When a user vents, shut your mouth — the root cause is inside the vent
- 04Speak the listener's vocabulary, including their internal nicknames and lingo
- 05You are not required to have the answers; you are required to know where to get them
- 06Being a user of your own product makes you a proxy, not the user
How to run it
- 1
Be deeply aware of the conversation you are in
One conversation at a time. When talking to a user, you are only talking to that user. Presence is the precondition for everything downstream.
- 2
Let the vent run
When a user is angry that a feature does not behave as promised, do not defend, explain, or correct. Stay silent and let them finish.
Pro tip The urge to defend is reactivity — apply the pause here specifically.
Watch out Interrupting to explain the roadmap terminates the flow of information you actually need.
- 3
Extract the root cause
After listening, distill what the underlying problem actually is — as opposed to the surface complaint or the feature they asked for.
- 4
Check your assumptions at the door
Ask whether you are actually hearing them or filtering through your own assumptions because you happen to use the product yourself. Being a light user makes you a proxy, never the user.
Pro tip Gautam freelanced for CNN to feel the pain — useful for empathy, but she still refused to treat herself as the user.
Watch out Substituting your own product usage for real user conversations is the fastest route to building the wrong thing.
- 5
Respond in their language
Speak back using the listener's vocabulary — their workflow terms, their nicknames for CMS objects, their lingo — not technical or product jargon. Expect to speak several different languages as a PM.
Pro tip Collect and use each team's internal nicknames for things; it signals you have actually been in their workflow.
- 6
Raise the frequency
Ask how far you are from your users, how frequently and how consistently you speak with them, and how early in the process. More frequent, more consistent and earlier is always better.
In the wild
Product and editorial at CNN historically did not talk to each other. Gautam prioritized listening in every stakeholder interaction, spoke to journalists in their vocabulary rather than CMS terminology, and made direct customer conversation continuous rather than episodic.
→ She names this the minor change with the most outsize impact on team performance: a previously fragmented structure became a unified partnership built on mutual trust and respect.
Gautam moved into her first official PM role at CNN after a decade in data and search infrastructure. When she asked her boss why he took the chance on her, he cited her communication and relationship-building skills — specifically that engineers listened to her and she listened to them.
→ Her boss's view: that combination is really, really hard to teach — it outweighed the absence of prior PM experience.
Common mistakes
Optimizing for articulacy over listening
PMs train on writing and speaking well. Those skills cannot be effective if you are not listening, because you will be eloquently addressing the wrong problem.
Assuming you are the user because you use the product
Gautam started freelancing for CNN and briefly thought it made her a user. It did not — what her journalists do day-to-day is drastically different. Treating yourself as a proxy for the user overwrites their feedback with your assumptions.
Performing omniscience
PMs are expected to have all the answers, and faking it blocks the listening that would produce them. Knowing where to go to get the answer is the stronger position.
Is it for you?
Best for
Product managers and internal-platform leads working with expert users whose domain vocabulary and workflow differ sharply from the product team's
Not ideal for
Contexts where decisions must be made without user access and speed of assertion beats depth of understanding
From the transcript
“when one of my journalists is venting because this feature is not working the way we told them it was going to I am shutting…”
“lets you do things like conversate in the language of The Listener so when I'm talking to my journalists worked I'm not using technical terms”
“but if you listen and you know where to go to get the answers that in itself is like a tremendous place to be”
“I always think the more frequently and the more consistently and earlier on in the process that you're having those conversations the better”
From the episode
An inside look at how CNN builds product
Upasna Gautam