“Making It Right”: A New Smashing Book on Product Management For A Startup World
- July 24th, 2014
- 0 Comments
You’ve seen this occur a thousand times. An classification struggles with a high spin of inner unrestrained and artistic disharmony that group leaders don’t know how to hoop any more. To move sequence into projects, a new product manager is appointed, underneath outrageous expectation, and with misleading responsibilities and large goals tangible within a really brief timeframe. That’s when things customarily go south, ensuing in unsuccessful projects, dejected teams and unhappy clients.
That’s since we’ve teamed adult with a author and crony Rian outpost der Merwe, a comparison product manager with a sociology and UX background, to emanate a new unsentimental book to assistance product managers in a digital space manage projects effectively — a right way, with a right strategy, in a right time, with a right team. Making It Right is a book about usually that: what product government is, what it isn’t, since it’s important, and how to proceed it strategically and meaningfully to get things finished well. Available today.1
What The Book Is All About
In a startup world, success is tangible by a peculiarity and strech of a product. The categorical purpose of this book is to assistance product managers who work privately with digital projects build improved — reduction complex, some-more focused, reduction extensively and some-more intelligent — products. By featuring lessons schooled and warning signs from real-life projects, a book provides a structured horizon for strategic product management to assistance product managers build a right products, during a right time, for a right people with usually a right volume of routine involved.
82
93104
The book isn’t endangered with epitome models and fanciful concepts. Based on ideas detected in tangible projects, it explains a roles and responsibilities of product managers in a fast, stretchable startup environment. It facilities a characteristics of successful product managers and also provides a horizon and unsentimental superintendence for product formulation and product execution. If your association has to residence these issues or you’re looking for a hands-on book to beam we by product management, this is a book for you.
The Structure Of The Book
The book’s structure has two categorical parts: product planning; and product execution.
- Product planning explains how to figure out what to build and when. You’ll learn opposite ways to accumulate user needs, business needs, and technical needs. The territory breaks down product find and looks during since it’s vicious to conclude a problem before jumping to product solutions. You’ll know what goes into a vital product plan, how to prioritize what problems to work on, and how to emanate effective, stretchable roadmaps for product development.
- Product execution gets into a nuts and bolts of shipping a product. You’ll learn how to select a right problem clarification (what problem are we perplexing to solve?) and how to heed between organic and technical specifications (how will a problem be solved?). The territory touches on user-centered design, gaunt UX and how to exam product hypotheses by quick, lightweight prototypes.
- Finally, a book provides recommendation on how to settle an efficient operative routine with group members by a “build, iterate, QA, release” process, and explains how to magnitude a success of a solutions being built, and how to feed those commentary behind into a product roadmap.
This Is What You’ll Learn From The Book
Let’s be honest: product manager is not a many moving pursuit title, yet it’s a vicious position for building a good product and shipping it in time. In fact, it’s not something that everybody can do. Good product managers need imagination and specialized skills that have to be acquired and mastered first. You competence not learn them all from this book, yet you’ll know accurately what we need and how to request these skills strategically.
In Getting It Right, you’ll learn:
- Roles, responsibilities, characteristics and common tasks of a good product manager,
- Where product government fits into an classification and since an executive mandate for PMs is a exigency for success,
- How to change user needs, business needs, and technical needs in product discovery,
- How product discovery, product roadmaps, and strategic product plans support a product’s development,
- How to redefine business needs by expelling bad income streams and posterior good income streams,
- How to avoid, minimize, and pay down technical debt that places aria on your product,
- Why many products destroy and what a warning signs for failures are,
- Why minimum fascinating products competence be improved than minimum viable products,
- When prioritizing themes, not projects or features, can assistance businesses to urge a peculiarity of a product (the Amazon approach),
- When product roadmaps fail, when they work well, and how to set adult a good one yet timelines and recover dates,
- Tools, techniques, workflows, and strategies for building prototypes fast with a “design studio” approach.
- Practical discipline and a checklist on how product managers can effectively start operative during a new company.
Table Of Contents
CHAPTER
TITLE
DETAILS
Chapter 1
Roles And Responsibilities Of The Product Manager
Summary • What is a product manager, and what do they do any day? This section starts by explaining since a product manager purpose is so important, including some common arguments against a role. Most of a section discusses a characteristics of a good product manager, and how they describe to day-to-day activites.
Keywords • product/market fit • common tasks • product government • market-driven proceed • characteristics • I-shaped people • feedback routine • validation smoke-stack • schlep blindness • exigency for success • integrity • roles • responsibilities • care • partnership • culture.
Chapter 2
Uncovering Needs
Summary • This section introduces a product formulation process, and dives low into a processes of building a strong bargain of user needs, business needs, and technical needs. The starting indicate for formulating products is — always — needs. Not what we assume would be cool, yet what users or a business need to be successful. This section explains how to expose and request those needs.
Keywords user needs • business needs • technical needs • product find • exploratory investigate • settlement investigate • comment investigate • bad/good income streams • dim patterns • product’s life cycle • investigate • usability • income • technical debt.
Chapter 3
Product Discovery
Summary • Uncovering needs is one thing. Figuring out how to spin those insights into a successful product is something else entirely. This section discusses since so many products fail, and how to beget and prioritize ideas that won’t fail.
Keywords • usable, invalid products • fishbone diagrams • a 5 ways • personas • patron tour maps • KJ-Method • Kano Model • Amazon’s proceed • product marketplace fit • problem clarification • vital product devise • prioritization.
Chapter 4
Product Roadmaps
Summary • Product roadmaps can be controversial, to a indicate where some trust they shouldn’t even exist. This explains since we can’t live yet a roadmap, and how to emanate flexible, useful skeleton to iterate towards improved products.
Keywords • product roadmap • expectations • elements of a roadmap • product legislature • recover schedule.
Chapter 5
Defining A Product
Summary • This section shifts from formulation to execution by articulate about generating ideas and prototypes to conclude what you’re going to build. It also discusses “design studio”, a really effective routine to get teams endangered in a clarification process.
Keywords • problem clarification • [user] has [problem] when [trigger] • supposition contrast • settlement studio • prototyping.
Chapter 6
User-Centered Design And Workflows
Summary • The whole product government routine has an undercurrent of user-centered design, so this section takes a slight road to plead a details and outs of this settlement methodology. It also explains how product managers can expostulate and be endangered in a process. The section ends with a brief contention on manageable settlement workflows.
Keywords • bill estimates • shopping time • acquisition, activation, activity • manageable settlement • calm initial • settlement library • usability • wireframes • prototypes • iteration • data-driven settlement • manageable settlement • workflows.
Chapter 7
Specifications
Summary • Specification can be a unwashed word, yet it doesn’t have to be. This section explains what specs are, since they are still important, and how to emanate specs that are indeed used by developers and a rest of a business. The pivotal is to sojourn flexible, to combine and usually request what’s indispensable to know and build a product.
Keywords • organic selection • technical selection • selling selection • use cases • upsurge charts • deliverables • energetic specs • permitted specs • devise outline • success metrics • rival investigate • devise range • risks • a final 20 percent.
Chapter 8
Build And Release
Summary • This section is especially focused on how product managers work with developers to build and recover products once they’re defined. It talks about builder vs. manager culture, and how product managers can assistance developers be many effective.
Keywords • engineering • growth • peculiarity • culture.
Chapter 9
Assess And Iterate
Summary • We mostly forget to magnitude what we’ve built. This section explains a essential step of sourroundings adult a right success measures and feedback loops to safeguard that a right information exists to continue to make product improved with any iteration.
Keywords • investigate triangulation • analytics • A/B contrast • facilities • primacy/newness effects • information • assembly enlightenment • environment.
Chapter 10
Product Management In Agile
Summary • This book is methodology-neutral, yet it’s unfit to inspect complicated product government yet deliberating how it fits into an stretchable framework. This section discusses how product government relates to product ownership, and how to be a good product owners yet losing steer of a incomparable role.
Keywords • stretchable • purpose of a settlement • “good enough” • right-fidelity specifications • scrum • product tenure • stretchable UX.
Chapter 11
Getting Started
Summary • Most books finish with a summary. This one ends with a call to action. What should a product manager do during a initial thirty, sixty and ninety days on a job? The speculation is nice, a horizon is nice, yet how do we indeed burst in, and start being a product manager? A few unsentimental discipline and a roadmap for removing started a right way.
Keywords • initial 30 days • vital product devise • final 30 days • product devise • product execution.
Author’s Note
Finally, here are a few records from Rian himself:
“The book came about since we saw a lot of people in organizations perform some of a activities that make adult a purpose of product management. The problem is that really few people take a holistic perspective of a product, and this is not a purpose that should be separate adult into little pieces. So, we see selling people doing some settlement and research, business analysts doing some spec writing, developers handling a product backlog, and so on.
All this yet a chairman who is obliged for a overall vision, prioritization, and execution of a product. we wish to yield a finish horizon for product government that is dubious to whatever growth routine people use (agile, etc.). This book is my common try to do usually that.”
Written by Rian outpost der Merwe. Reviewed by Francisco Inchauste. Cover settlement by Francisco Inchauste. Inner illustrations designed by Anna Shuvalova. 190 pages. Available today.
Get a eBook
The eBook is already available5 in PDF, ePUB and Amazon Kindle formats, and of march it’s also supposing in a Smashing Library, so if we are a subscriber already, a book is patiently watchful for we in your dashboard. Also, if we have an Amazon Kindle, we can get a eBook on Amazon.com for $0.996 — accessible usually for a subsequent 24 hours though.
If you’re meddlesome in a printed edition of a book, greatfully submit a form7 and we’ll do a best to make it happen.
82
93104
So here we go! We’re looking brazen to your feedback and your thoughts, and we wish that a book is going to be useful and profitable for we and to your company. Product government doesn’t have to be tedious and done poisonous with formidable processes — this is since we combined a book in a initial place. Happy reading, and happy learning!
Footnotes
- 1 https://shop.smashingmagazine.com/checkout/cart/add?product=651
- 2 https://shop.smashingmagazine.com/making-it-right-product-management-for-a-startup-world.html
- 3 https://shop.smashingmagazine.com/checkout/cart/add?product=651
- 4 http://www.amazon.com/dp/B00M0KTVTO
- 5 https://shop.smashingmagazine.com/checkout/cart/add?product=651
- 6 http://www.amazon.com/dp/B00M0KTVTO
- 7 https://smashingcoding.wufoo.com/forms/making-it-right-printed-book/
- 8 https://shop.smashingmagazine.com/making-it-right-product-management-for-a-startup-world.html
- 9 https://shop.smashingmagazine.com/checkout/cart/add?product=651
- 10 http://www.amazon.com/dp/B00M0KTVTO
↑ Back to topShare on Twitter
“Making It Right”: A New Smashing Book on Product Management For A Startup World
Nenhum comentário:
Postar um comentário