In partnership with
Thank you to our sponsors who help support this newsletter:
Between meetings, speak your follow-ups. Done before the next one starts.
You have seven minutes between calls. That's enough time to type one email or dictate five.
Wispr Flow turns your voice into clean, professional text inside any app. Walk out of a meeting, speak your action items, follow-ups, and notes — Flow formats everything and you paste it where it needs to go. Email, Slack, Notion, your CRM.
Works on Mac, Windows, and iPhone. 89% of messages sent with zero edits. Used by teams at OpenAI, Vercel, and Clay.
Thank you to our sponsors who help support this newsletter:
Trade from the subway, golf course, or toilet
Liquid enables users to go long or short on any market from your phone or desktop 24/7.
No matter what time of day it is or where you are, you can monitor the situation with Liquid.
Jay was an engineering lead, looking over at the Product Management team and thinking: “That looks like a pretty sweet gig.”
They weren’t buried in code reviews. They weren’t on-call at 2am debugging outages. They seemed to spend their time talking strategy, discussing features, setting direction, and getting access to leadership. Jay figured, “I’m already building the product. How hard can it be to define it?”
He became a Product Manager and found out he was wrong. Very wrong.
Like many engineers before him who have made the transition to Product Manager, he underestimated what it actually takes to succeed as a Product Manager. He stumbled. He learned the hard way.
I’ve seen plenty like Jay burn out or boomerang back to engineering after a painful stint in product management.
If you’re thinking about making the leap, are in the middle of it, have done it, or know someone who’s considering it, here’s what you need to know.
Product Management Isn’t What Engineers Think It Is
The biggest mistake engineers make is thinking Product Management is just a different flavor of building. That it’s basically development but with more say over what gets built.
Here’s what usually happens:
They assume PM is just writing specs and prioritizing tickets.
They think their technical knowledge will make them “better” than the average PM.
They believe watching PMs up close means they understand the job.
They don’t.
Product Management is a business function that’s responsible for continuously delivering profitable customer value.
It involves:
The ability to gain deep customer insights.
Market savvy and commercial instincts.
The ability to influence, seek alignment, and empower others.
Facilitating trade-offs in the face of imperfect information.
Storytelling.
Delivering economic outcomes.
Most importantly, it’s about the customer and the business — not the tech.
Without realizing this shift, most engineers either:
Stay too focused on technical details and lose the room, or
Overcompensate by ignoring the tech entirely and lose credibility.
Either way, they fail.
What Happens When You Get This Wrong
If you walk into Product Management with the wrong mindset, it doesn’t just slow you down. It can wreck your career momentum:
You frustrate your teams by micromanaging implementation details.
You alienate stakeholders because you can’t speak the language of customers, go-to-market, or business.
You miss the mark on strategy because you optimize for outputs instead of outcomes.
You lose confidence fast, and once leadership senses you’re out of your depth, the runway gets short.
I’ve seen promising new product managers who were former tech leads sidelined within months because they couldn’t make the leap. It’s not that they weren’t smart. It’s that they completely misunderstood and underestimated the job.
And while it’s hard to course-correct in a PM role after you’ve burned trust, it’s not entirely impossible.
Here’s the playbook.
How to Make the Leap — And Stick the Landing
Here’s what I wish I knew before I made the switch, and what I coach others to do now.
1. Fall in love with the problem, not the solution.
Your job as a Product Manager is not just about building elegant solutions. It’s to solve problems worth solving.
More fundamentally, it’s shifting your identity from “builder” to “business grower.” This means:
Spending more time with customers than code.
Caring more about unit economics than architecture diagrams.
Championing business outcomes, not just release outputs.
2. Study the craft deeply.
You wouldn’t expect someone to become a great engineer simply by shadowing someone else for a few months. Being a product manager is no different.
Read widely outside the field.
Talk to experienced and successful PMs and product leaders in the trenches. Learn how they think, make decisions, navigate orgs, and seek alignment.
Get obsessed with understanding customers, markets, and business models.
3. Get a mentor who’s done it before.
This is an accelerant.
Find someone who’s made this transition successfully.
Ask them to critique your business thinking.
Use them to reality-check your instincts and blind spots.
A good mentor can save you years of painful trial and error.
4. Choose your first PM role wisely.
Not all PM jobs are created equal. A bad environment will sink you no matter how hard you try. Look for:
Strong product culture: somewhere you can learn the craft.
Supportive cross-functional peers, especially on the commercial side.
A product with actual customers and usage data, so you can practice real product discovery.
5. Shut up and listen (at first).
When you first make the transition, it’s tempting to want to “fix” things fast. After all, that’s what you were paid to do as an engineer. Don’t.
Spend your first 60-90 days listening.
Meet with customers, peers, execs. Understand their pains and goals.
Your job is to learn the job before trying to change it.
The fastest way to build credibility is to show you understand before you prescribe.
One Last Thing
You’re starting over.
Moving from Engineering to Product Management isn’t a promotion, nor a lateral move. It’s a career reset. You’re not the senior engineer anymore. You’re the rookie PM.
That’s a hard pill to swallow for a lot of smart, successful engineers. But embracing that humility is the price of admission.
If you get it right, you build a whole new set of muscles: influence without authority, customer empathy, commercial awareness, and strategic thinking.
But only if you’re willing to be a beginner again.
Already in PM?
If you’ve already made the leap and it’s not going as smoothly as you hoped, you’re not alone. Plenty of ex-engineers hit a wall in PM after the honeymoon period.
The good news is that you can still course-correct. A few things to focus on immediately:
Stop trying to be the technical PM. Your technical expertise is a bonus, not your job description. Reframe your value around customer impact and business outcomes.
Get closer to customers. Fast. There is literally no faster way to level up than hearing real problems in customers’ own words.
Ask for feedback constantly. From peers, commercial folks, your manager, leadership, and, yes, even the R&D team. The more data you get on your blind spots, the quicker you close the gap.
Audit your calendar. Are you stuck in execution cycles? Are you skipping discovery work? Are you avoiding difficult ROI discussions? Your calendar tells the truth about your focus.
Reconnect with your ‘why.’ Why did you make this move? What did you hope to gain? Refocusing on your personal goals can reignite your motivation and guide your development.
And if you’re really stuck, don’t white-knuckle it. Get a coach, join a product community, or find a mentor who’s been in your shoes.
There’s no shame in being behind. But there’s risk in staying there.
Your Move
If you’re serious about making the jump, do it with your eyes open:
Audit your motivations.
Get clear on what the job really is.
Build a real learning plan.
I recommend doing this even if you’ve already made the transition to Product Management.
Don’t wing it. Don’t assume proximity to PM, a training course, or a few years of hard knocks equals competency.
This career path is incredibly rewarding. But it’s earned, not granted.
That’s all for today.
Have a joyful week, and, if you can, make it joyful for someone else too.
cheers,
shardul
Here are 4 ways I can help you today:
Executives: Eliminate Decision Drag and Drive Commercial Impact. I help organizations build the product strategy and discipline need to turn technology into a high-margin business. Let’s discuss your next phase of growth. Let’s discuss your next phase of growth.
Product Leaders: Invest in Your Product Operating Model. Stop the “delivery drone” cycle and unlock your team’s true potential as a strategic business function. Schedule a Strategy Call Today.
Product Managers: Get 1:1 Street Smart Career Guidance. From 1:1 coaching to a resume review to a mock interview, get real-world strategic feedback from an executive who has hired, mentored, and promoted at every level, whether you’re breaking into PM or are rising to the leadership ranks. Book a Coaching Session Today.
Aspiring and New PMs: Learn the Unvarnished Truth on What the Job Really Is. It’s one of the most misunderstood roles in tech. It can be a meaningful role for the right people. But only when entered with realistic expectations, self-awareness, and intent. Get the unvarnished truth about the role before you commit your time, money, and entire career. Get Early Access Here Today.
Shardul Mehta
I ❤️ product managers.