Direct answer: Design taught me to care about the user's actual moment-to-moment experience, development taught me to respect the true cost of every feature, and product management taught me that the hardest part of building products is neither designing nor coding, it's deciding, clearly and early, what not to build.
What design taught me
As a product designer, I learned that most "obvious" UX problems aren't obvious to the people who built the system, you only see them by watching real users struggle in real time. It also taught me humility about my own assumptions: the design I was proudest of was rarely the one users actually preferred in testing.
What development taught me
Moving into full-stack engineering changed how I evaluate feature requests forever. A feature that sounds like "just a small addition" in a product meeting can be a two-day change or a three-week change depending on what it touches underneath, and you can't tell which without understanding the system. This is the single biggest gap I see between non-technical PMs and their engineering teams.
What product management taught me
Product management is where I learned that saying no is the actual job. Design and engineering both have a bias toward making things, better, more polished, more complete. Product management's core value is deciding, with real conviction, what's not worth building right now, and being willing to defend that decision when it's unpopular.
Why this path makes me a better consultant
Having sat in all three seats, I don't advise founders from theory, I've personally felt the tension between what design wants, what engineering can realistically ship, and what the business actually needs this quarter. That's the tension every product decision lives in, and most consultants have only ever seen it from one side of the table.
The throughline
Across all three roles, the same lesson kept reappearing in different forms: the product is not the artifact (the screen, the code, the roadmap), it's the outcome for the user and the business. Everything else is just the current best guess at how to get there.
FAQ
Is it worth learning to code as a product designer? Not necessarily to write production code, but understanding how your designs actually get built changes which trade-offs you're willing to fight for versus let go.
Do product managers need a design or engineering background? No, but PMs without either background should deliberately build enough fluency in both to have real conversations with each function, not to do their jobs, but to ask better questions and earn credibility.
What's the hardest transition: design to dev, or dev to PM? For me, dev to PM was harder, engineering has clear correctness (code works or it doesn't); product management's decisions are judgment calls under uncertainty, with no compiler to tell you when you're wrong.
Curious how this background applies to your product? Book a free strategy session.