The reasons product managers should deliver the why

Recently , I am confused of work and work in that some have taken place by accident . Much to be thought , more to be learned , faster to be grow up . In the past few days when I am ocuppied in the Product Manager , two different kinds of PM I know and meet show the two aspects of PM : Thinking & Practicing which are the essential and fundmental personality of Internet Product Manager . The bigger challenge I faced with is how to obtain the balance of them ,or to improve and apply them to my job . As for me , it will be a long-time matter to approach .（插播一句中文：勿喷，纯英文博客！小编水平有限，只能发挥到这种程度！请见谅...）

PM is an Artist !

---

Content

You’re a product manager. For the past three months you’ve conducted opportunity assessments, discovered possibilities, and defined solutions. Things went from whiteboard sketches toInvisioncomps to code-based prototypes. You validated assumptions by testing early and often. You even cut features that brought little value. You’ve written detailed technial docs and defined every possible requirement. The visual design is complete, you’ve defined the right product and clearly articulated exactly what needed to be built.

Now it’s up to engineering to figure out how to build it, right?

Wrong ！！！

---

You forgot one of the most important aspects of collaborating with engineers and building meaningful products:delivering the why.

Confidence

In some respects, the why can be far more valuable than any spec or piece of documentation. Teams enjoy interacting with gorgeous prototypes but the real value surfaces when you deliver a story (the why) that helps everyone understand the problem you’re trying to solve. When your team understands the why, you give them confidence that you’re solving the right problem. After all, there’s a lot of problems out there to solve… how do you know you’re solving the right one?

Purpose

Delivering the why also puts your users, the people you’re designing and building for, at the heart of your effort. When you focus on real users and think about building software that improves people’s lives, you feel purpose. And we all need a sense of purpose, right? It’s human nature.

Vision

It’s one thing to undestand the 2.1 release you’re kicking off today, but what about version 3.0? Provide insight into the long-term vision of where things are headed and your team will be grateful. It’s important for everyone to understand we’re you’re heading so they can make better decisions.

If an engineer is focused on 2.1, she may choose one technology over another. If she has awareness of where things are heading, she may choose a different technology because she knows it will work better for what’s needed down the road.

When the team has insight into product vision, they make smarter, more sound decisions because they understand that the current release is just a stepping stone to get to the next major overhaul.

The reasons product managers should deliver the why

---

If you want to make better products, deliver the why and give your team the confidence, purpose and vision they deserve.

作者简介：Danielwong，微博：互联网金融_产品小王；毕业于15年6月，产品小白（PM）。正在孜孜不倦地汲取（互联网）专业的产品知识，在互联网行业总是有太多的观点和想法，而我有时也会按捺不住，提起笔来写下一番感悟/思考，和大家一起分享讨论！个人博客上的观点略显笨拙，请大家不吝赐教！​

原创声明：本文章的最终解释权归产品小王所有，如需转载，请注明文章出处！谢谢...