From Coding to Customer Focus

Juggling between a development role and product management can be challenging. I have seen many developers make the transition to become product managers over the years. However, it’s important to understand that project management and product management are very different disciplines.

As a project manager, you’re focused on delivering defined requirements and managing scope, schedule, and resources. But product management is all about understanding customer needs, defining strategy, and delivering value. The mindsets are almost opposites.

When I first started spending part of my time on product management responsibilities, I really struggled with the differences. I often fell back into thinking like a software engineer focused on technical solutions. I had to go through an unlearning and relearning process:

Unlearn:

• Viewing requirements primarily through a technical lens. I was used to focusing on elegant architectural solutions rather than customer needs.
• Jumping to technical architecture without gathering actual user needs. I had to stop assuming I knew what users wanted.
• Getting excited about new technologies that didn’t offer clear value to customers. I had to shift my mindset to prioritize customer ROI over tech for tech’s sake.

Relearn:

• Looking at requirements from the customer’s perspective first. I needed empathy to understand what users really needed.
• Communicating with customers to gather requirements that address real problems or desires. This knowledge was powerful in defining valuable products.
• Driving products forward based on functionality and experience, not technical implementation. I focused on the “what” first, then the “how.”
• Considering how every product decision could improve value to the customer and business. I learned to think bigger picture about product strategy.
• Influencing without formal authority by storytelling and selling vision. Technical excellence was no longer enough.
  

The unlearning and relearning were challenging but ultimately helped me evolve into a much more well-rounded product manager.

For example, I initially got excited about using new bleeding-edge frameworks and technology, even if they didn’t align with our user needs. I had to train myself to always link back to concrete value for customers, rather than just what was innovative. This meant developing skills like user empathy, storytelling, and selling vision – very different from my past specialized technical work.

The transition was especially tricky because I was still embedded in the same development team. If I could do it over again, I would try to switch products or join a different company when making the shift. Getting outside of my existing engineer mindset would have been easier.

Overall, moving from development to product management required me to fundamentally change how I thought about requirements and prioritization. I had to learn to put customer’s perspective first, and then think about technical implementation. It was a challenging but rewarding shift that made me a much more well-rounded contributor over time.

A dwarf miner sitting at stone craved desk @SomberSaurus