Guía de respuesta · Product management
What product managers post on X, reply angles that start an actual conversation, six sample post and reply pairs, and the mistakes to skip.
Product people on X post frameworks, prioritisation fights, launch retros, notes from user interviews and a steady stream of opinions about roadmaps. Founders who act as their own PM and designers who moved into product post here too.
Replies work because most PM posts are claims that depend on context: company size, stage, B2B or consumer. A reply that adds the context where the claim breaks, or asks how it held up in practice, turns a broadcast into a discussion, and the author usually joins in.
01
"Always talk to five users before building." These invite the case where the rule fails, which the author has often thought about.
02
A feature shipped, a number moved or did not. Ask what they measured and over what period.
03
Saying no to sales, working with engineering, roadmap politics. Replies based on experience do best here.
04
Getting a first PM job, what interviews test, how the role differs between companies. Concrete advice beats encouragement.
01
"This works at 20 people. At 200, who owns the call?" A specific boundary is more useful than disagreeing, and easier to answer.
02
After any launch story, ask for the metric and the time window. It shows you know how these stories usually go, without accusing anyone.
03
One line on a trade-off you actually faced: what you picked and what it cost you. PMs collect these.
04
Say how the advice looks from engineering or from support. PMs value that view and rarely get it in their replies.
05
The roadmap slide with every item in Q3, the prioritisation matrix where everything is high impact. Gentle and recognisable.
Posts de ejemplo escritos para esta página; ninguna cuenta real.
Publicar
Hot take: roadmaps with dates are promises you can't keep. Use now, next, later.
Responder
works until sales asks which quarter "later" is. what do you tell them, or do they get a separate deck?
Publicar
We killed a feature this week that 4% of users used daily. Support tickets dropped and nobody complained. Yet.
Responder
did the 4% skew toward your biggest accounts? that's the version of this story that ends with a call to the CEO
Publicar
Best discovery question I know: "Tell me about the last time you did this." Hypotheticals get you polite answers. The last time gets you the actual workflow.
Responder
the follow-up that works best for me is "what did you do right after?" that's usually where the workaround they'd never mention shows up
Publicar
Every PM should be able to write basic SQL. Change my mind.
Responder
agree, with one caveat: the risky PM is the one who can write the query but doesn't know the events table double counts mobile sessions
Publicar
Shipped our biggest feature of the year today. 9 months, 3 teams, 1 very tired PM.
Responder
congrats. what was the first thing users asked for once it was live? for me it's always the part we cut in month 7
Publicar
PMs: stop writing 10-page specs. Nobody reads past page two.
Responder
engineers do read the edge cases section if it's on page one. we moved it to the top and the questions in standup dropped by half
Pruébalo con un post real
Pega cualquier post en el generador de respuestas para X gratis y obtén tres respuestas como estas, escritas para ese post concreto.
Generador de respuestas para X gratis