Set in stunning Lisbon, Productized 2019 brought together 500+ passionate product creators and builders to exchange ideas, learn from each other, and connect in a meaningful way. The goal of our workshop was to help Product Managers understand how the Design Sprint could be sneaked in Enterprise, and empower the participants to use the framework in a way that meets their needs and fits the existing processes
Forming a cornerstone of product management, the ability to understand what to build next (and what not to!), explain and justify your choices, and make better-informed decisions set apart a good product manager from a great one. However, it is easier said than done. At the end of the day, how do we know if a decision is right or not? And this is where, in my opinion, we can start shifting our mindset.
After my most recent Product School #AskMeAnything session on Slack, I realized how many aspiring Product Managers are convinced they need to obtain an MBA from a business school to break into the field. While I understand the value some see in getting the Masters degree, I disagree with this notion.
More often than not we, as Product Managers, forget to take a step back and ask ourselves “Why?” Why am I including this feature? Why is the development team working on this deliverable? Why are we doing all of this in the first place?
Building and shipping the turd is not going to be your career-defining moment. Most likely, it won’t be something you’ll speak proudly of at your next interview as the best product you’ve ever worked on, however, there is a lot to learn from this experience.
Product managers are given a vision, a team, goals, and tools to build and launch great products that, hopefully, will solve problems for customers. Product leaders set the vision, define the direction, influence and inspire others, align and lead teams, and create value that results in transformational change To join the latter group, master the following tactics.