, 10 tweets, 3 min read Read on Twitter
“As a product manager...how do you earn the respect and trust of your team?”

A couple things
1/10 - Don’t hide things from your team in an effort to protect/shield them. That’s weird. It’ll come back to bite you.
#prodmgmt #ux #design
2/10 - Do actual work. Meaningful work. Context-building work. Analysis. Research. Design smart experiments. A good test is whether the team would pay you if they controlled the budget.
3/10 - Act like a member of the team, not as a manager of the team. The second you create a wall...the team will create a wall as well. Consider inviting a facilitator in so you can express your own needs (instead of juggling facilitation and team membership)
4/10 - Take ownership of your decisions. Don’t celebrate when things go well, and make excuses when they don’t (and don’t, don’t, don’t throw your team under the bus). This asymmetry can be maddening for passionate problem solvers.
5/10 - The second it seems like you’re only in this for *you* and your self-advancement...you’ll lose the team. Share all wins. Be humble. This is trust-building/maintaining 101, but too many PMs smack of selfish careerism
6/10 - On the flipside, don’t fake being humble or “deep”. There’s so much talk about humble servant leadership, that you’re seeing people go through the motions in obviously very forced and unnatural ways. Be yourself.
7/10 - Don’t sugar-coat. Master talking about uncertainty with certainty. Explain what you know and don’t know. Be transparent about risks. Let the data/context do the inspiring and census building. Lots of PMs over-use their charisma and salesperson-ship and it backfires
8/10 - Don’t disappear for days on end — “because [your] calendar is sooooo full” — and come back empty-handed. This is an extension of “do actual work” (2). It is one thing to be unavailable. Another thing to ignore your team.
9/10 - Your job is not to keep the team busy or “topped up”. You don’t feed them work. You don’t do story point by engineer spreadsheets. Yuck. Focus on value and opportunity. If you need to back off and rethink things....well do that.
10/10 - Finally...remember engineers make cost/benefit decisions all day. No one wants to add lots of complexity to the product without impact. Consider product as IDD (impact driven development). Give yourself passing tests. Be transparent about those tests. Impact builds trust
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to John Cutler
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!