6 product management lessons from @cagan that resonated like woah.
Lesson 1: It doesn't matter how good your engineering team is if they are not given something worthwhile to build… If you're just using your engineers to code, you're only getting about half their value.
Lesson 2: There are many reasons ideas don’t work.
- Value: Will the user buy this (or choose to use it)?
- Usability: Can the user figure out how to use this?
- Feasibility: Can our engineers build this?
- Business viability: Can our stakeholders support this?
Lesson 3: Tackle risks up front, rather than at the end. Strong product teams understand risks and embrace them rather than deny them.
Lesson 4: Prioritize business results, not product ideas.

Tell the team what you to accomplish & how the results will be measured & let them figure out the best way to solve it.

Modify roadmaps to state problems rather than features that may or may not solve them.
Lesson 5: Many teams give up on their product vision far too soon.

Even with ideas that prove to have potential, it typically takes several iterations to get the implementation of the idea to the point where it delivers the necessary business value.
Lesson 6: There is nothing wrong with a PM bringing a strong POV, but you must constantly demonstrate to your team that you're open minded, know how to listen, & you want & need their help in coming up with the right product.

Only bring solutions that meet the constraints.
You can follow @adrienneziluca.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled: