How My Nine Errors Shaped My Journey as a Product Manager
Written on
Chapter 1: Embracing Failure
It has been three years since I embarked on my journey in the tech sector. During this time, I’ve donned various roles and, admittedly, stumbled frequently. Surprisingly, I view these missteps positively; failure is often the most effective teacher. Here, I’d like to highlight a few notable errors from my experience, hoping they serve as a learning tool or inspiration for your own reflections.
Section 1.1: The Danger of Ignoring Reality
We faced a critical deadline for delivery, yet consistently wrapped up our sprints with about 40% of the backlog still incomplete. Each sprint, we convinced ourselves that we would align with the roadmap eventually. Deep down, I recognized the impending chaos but chose to cling to false optimism. When the inevitable occurred, we had to remove an entire sprint from our roadmap just to catch up with outstanding tasks, a situation that could have been mitigated had I acted sooner.
Lesson learned: When faced with recurring issues, take decisive action rather than relying on hope.
Section 1.2: Neglecting Design for Performance
Initially, we prioritized designing and developing the website before considering SEO. We soon discovered that not only did specific page structures matter for SEO, but performance also significantly impacts it. It became clear that using high-resolution images while expecting optimal PageSpeed Index (PSI) scores was unrealistic.
Lesson learned: To excel in SEO, prioritize performance from the design stage.
Chapter 2: Miscommunication and Assumptions
The first video discusses common pitfalls in product management interviews, emphasizing how certain mistakes can lead to significant setbacks.
Section 2.1: Confusing Messaging with Communication
While managing a project with a tight budget, I kept the client updated through weekly email reports, assuming that he understood the situation. Unexpectedly, he reacted strongly to the budget overruns a few weeks later, claiming it was the first he had heard of these issues, despite acknowledging my previous communications.
Lesson learned: Ensure that your communication is clear and confirms mutual understanding, not just a message sent.
Section 2.2: Overlooking Critical Assumptions
As a product owner for a new service, we identified a risky assumption about our dependency on point-of-sale (PoS) software. After a brief workshop, we concluded there were no dependencies and moved on. However, three months later, we discovered we had overlooked vital changes needed on the PoS side, causing a six-month delay in our launch.
Lesson learned: Treat your riskiest assumptions with the seriousness they deserve and verify them thoroughly.
Section 2.3: Delaying Performance Testing
In developing a platform for integrating newly acquired marketplaces, we followed a waterfall approach and postponed performance testing until two months before launch. The result was a lengthy process to resolve issues that could have been identified much earlier.
Lesson learned: Conduct performance tests early and often, rather than waiting until the end.
Chapter 3: The Importance of Strategic Thinking
The second video highlights common mistakes product managers make regarding their resumes, drawing from extensive experience reviewing thousands.
Section 3.1: Presenting Ideas Without Buy-In
While working as a corporate product manager, I proposed improvements to our development process. Unfortunately, presenting these ideas without prior individual discussions resulted in immediate pushback and rejection. I learned to refine my ideas and gain support before presenting them collectively.
Lesson learned: For significant changes, garner support from key stakeholders beforehand.
Section 3.2: Launching Without a Go-to-Market Strategy
After spending months building a marketplace, we launched it without a clear strategy to gain traction. Reflecting on this, it was evident that our product was not optimized for any growth channel, leading to its stagnation.
Lesson learned: From day one, prioritize a distribution strategy alongside product development.
Section 3.3: Underestimating Payment Complexities
In scoping a subscription feature, we began development without finalizing payment methods. This oversight led to unexpected integration issues and complications that we had not anticipated.
Lesson learned: Recognize the complexities involved in payment systems early on.
Section 3.4: Losing Sight of the Big Picture
While focusing on the number of messages sent in a chat-like extension for a CRM platform, I lost sight of the broader business goals. The metric was meaningless in our context, highlighting the danger of getting caught up in micro-optimizations.
Lesson learned: Always keep the overarching objectives in mind to ensure meaningful progress.
In summary, these experiences, though challenging at the time, have significantly contributed to my growth as a product manager. I am grateful for each mistake and eagerly anticipate future learning opportunities. I encourage you to embrace your own missteps and view them as valuable lessons on your journey.