Hello world. I don’t usually write real blog posts. But, I’ve been doing quite a bit of thinking about goal setting, alignment, and product management lately, and ended up drafting the following rant on how I approach aligning day to day work with a big, overarching goal.
Apologies that the original audience wasn’t intended to be you, so not everything is artfully dissected and explained. Just a little something I’m pondering and thought could inspire some thinking on setting goals and ensuring that they a) make sense and b) inform day to day decision-making and prioritization.
Continue reading “Product Management: Whys and Hows”
I hope that my role in saying “no” to everything doesn’t scare you away from continually telling me “yes.”
The first thing we need to clarify is the difference between needs and features. We often make the mistake of equating product features with user needs.
– Rian van der Merwe in How to Avoid Products that Fail
“If you are going to build something, you have to be able to think about all aspects of the business, you have to understand that if you build a product, you then have to market it, you have to know how the economics work, how users respond to it, and you have to be able to motivate a team to build and sell it….
“I fundamentally believe that we should always challenge ourselves to build a better business on a daily basis, because if we don’t, someone else will.”
– Mathew Smith, in Getting to Here in Product Management
In my experience, decisions are being made at all the wrong levels of most organizations. Executive teams are dabbling in product and portfolio prioritization while product managers are trying to determine (or guess) the product strategy. Shouldn’t it be the other way around?
– Steve Johnson, On Product Management
Profound simplicity is when you take all of that complexity and you master it… until all that is left is utter and complete simplicity.
– Aziz Musa on “Delivering a Pure Product“
“Fight this instinct. Your product management, QA and development teams should be using judgment to decide what should continue to exist and not just blindly adding everything that used to exist.”
On factoring in ‘complexity cost‘ into design and product development by Kris Gale