Reddit reviews The Lean Product Playbook: How to Innovate with Minimum Viable Products and Rapid Customer Feedback

This is a great resource: https://www.oneweekpm.com. This course is a great place to start.

Hitchhiker's Guide to Product Management ( great blog ):

Books to read after the course: https://yilunzh.com/pm/

INSPIRED: How to Create Tech Products Customers Love: https://www.amazon.com/INSPIRED-Create-Tech-Products-Customers-ebook/dp/B077NRB36N

The Lean Product Playbook: How to Innovate with Minimum Viable Products and Rapid Customer Feedback: https://www.amazon.com/Lean-Product-Playbook-Innovate-Products/dp/1118960874

Shipping Greatness: Practical lessons on building and launching outstanding software, learned on the job at Google and Amazon: https://www.amazon.com/Shipping-Greatness-Practical-launching-outstanding/dp/1449336574

Hope this guides help.

the lean product playbook is excellent, (no this is not an affiliate link, nor am I the author) https://www.amazon.com/Lean-Product-Playbook-Innovate-Products/dp/1118960874/ref=sr_1_1?ie=UTF8&qid=1549985813&sr=8-1&keywords=lean+product+playbook

Gotcha. That really sucks, and I mean that in the most meaningful way possible haha.

That type of thinking is the complete opposite of "agile" development, where typically there is a budget, but product owners and devs work together, iteration-by-iteration to determine what needs to change. If an "estimate" is carved in stone, then it's not an estimate anymore, but a fixed-bid project--again, the complete opposite of what developing with agility is supposed to be.

Sounds like a good starting place is learning about lean development and building a minimum viable product, since they're so sensitive about estimate granularity. That manager will have to learn to lead building a very minimum viable product, with as minimally necessary a valuable feature set as possible.

I recommend reading:

• The Lean Startup by Eric Ries
  
• The Lean Product Playbook
  
• Inspired

Your intuition is 100% spot on and defines the difference between a product-oriented approach and a market-oriented approach.

Product Orientation states that somebody already has an idea for a product they're attempting to sell, they just need to figure out how to sell it. This is usually the case with things like restaurants, for example, who specialize in a particular category of food, but also usually the case for somebody who feels they can improve the field they already work in. This mindset believes with the correct sales push, anything can be sold. It's also where we got the phrase "location, location, location".

Market Orientation takes the opposite approach and asks, "what problems are there in the world that need solving" and then attempts to build a product revolving around that. This mindset requires an immense amount of research as well as the flexibility to work within whatever field your research suggests and goes against the "follow your dreams" mantra we've been taught as kids.

Generally speaking, product orientation is considered a bit dated and market orientation is more successful. That said, the age of the internet is changing this theory a bit. From my perspective, product orientation is still a valid strategy, it just has a higher risk of failure.

But with all that said, the book I'm grabbing that pyramid from (The Lean Product Playbook) assumes you've already designated a product you're working on. It's less for the entrepreneur and more for the average product designer working for a company who already have a product in mind.

Here's a link to the book if you felt like learning more about it:
https://www.amazon.com/Lean-Product-Playbook-Innovate-Products/dp/1118960874

> Here's a link to the book if you felt like learning more about it: https://www.amazon.com/Lean-Product-Playbook-Innovate-Products/dp/1118960874

Thanks for the link. How much does this book differ from Lean Startup Method? I've read that, but would be willing to give this one a shot if you think it's worth my while.

edit: ordered it anyways. Currently reading "User Story Mapping" by Jeff Patton but will dive in as soon as I'm finished, thanks for the reco.