Sponsored by
Most career-switchers walk into their first PM role and get blindsided.
Not because they weren't smart enough. Not because they picked the wrong company.
Because nobody told them what the mistakes actually were before they made them.
I've been through this transition. I've coached others through it.
Here are the 10 mistakes that cost people the most, and exactly how to skip them.
Mistake #1: Believing the job description.
"Strategic product visionary who shapes the roadmap." That's the posting. The reality is 40 minutes aligning two engineers who want the same thing but can't agree on what to call it. A meeting that should've been an email. Eleven Slack messages about where the spec is.
💭 The job description is marketing. The actual job is coordination, clarity, and unblocking people who are smarter than you in their domain.
How to skip it: Accept by week one that execution and alignment is the job. Stop waiting for the strategic work to start. You're already doing it.
Mistake #2: Hiding where you came from.
New PMs who switched from other roles spend their first months trying to sound like "real PMs." They bury their domain knowledge. They pretend the past didn't happen.
That's the mistake. Your customer context, your industry experience, your time in rooms with real users — that's worth more than any framework a PM bootcamp teaches.
💭 The people who hired you didn't want another generic PM. They wanted someone who already understood the problem. Stop apologizing for that.
How to skip it: Lead with your background. It's not a liability. It's the only thing that makes you different from everyone else who read the same product books.
Mistake #3: Performing certainty.
New PMs have an answer before the question finishes. It's a tell — and everyone in the room sees it.
Performed confidence doesn't build trust. It destroys it.
💭 The most dangerous person in the room isn't the one who doesn't know. It's the one who doesn't know and acts like they do.
How to skip it: "I don't know, let me find out" is the most credible sentence in year one. Say it. Then actually go find out, faster than they expected. That's how you build a reputation when you have no track record.
Mistake #4: Optimizing for the loudest stakeholder.
The person who sends the most Slack messages, books the most meetings, and pushes the hardest is not always the one whose yes you need.
💭 Urgency is not the same as importance. Learn the difference fast — it'll save you months of wasted alignment work.
How to skip it: Learn to identify the real decision-maker. They usually say the least — they don't need to perform. Find them early. Win them first. Everything else gets easier.
Mistake #5: Skipping the writing.
If you can't write the idea clearly, the idea isn't clear yet. Most PMs go straight to the meeting. They talk through half-formed thinking, waste everyone's time, and wonder why nothing moves.
💭 A document isn't a deliverable. It's a thinking tool. If writing it feels hard, that's the point — you're finding out what you don't actually know yet.
How to skip it: Write before every meeting. If you can't make the case on paper, you won't make it in the room. And you shouldn't.
The Ultimate Guide for Usage-Based Pricing for SaaS and AI
Implementing usage-based pricing successfully requires more than just a pricing strategy. It requires financial and operational infrastructure capable of handling dynamic pricing models, real-time usage signals, and increasingly complex monetization approaches.
In this guide, you'll learn ⤵
Strategic Advantages + Implementation Guidance
AI Use Cases for Usage-Based Pricing
Insights from SaaS & AI finance leaders on overcoming challenges and maximizing UBP.
Mistake #6: Walking in with answers instead of questions.
Early on I thought my job was to prove I belonged by having the best ideas. That's not the job.
The PMs who got promoted fastest weren't the ones with the best solutions. They were the ones who kept killing bad problems before they became expensive mistakes.
💭 "Are we solving the right problem?" is worth more than any answer you could walk in with. Ask it before every project kickoff.
How to skip it: Ask "are we solving the right problem?" before you propose anything. One good question beats ten good answers.
Mistake #7: Touching the process before earning the trust.
The best prioritization framework in the world doesn't matter if the engineering lead doesn't trust you yet. And that trust takes longer to build when you're new to the company and new to PM at the same time.
💭 Nobody wants process from someone they don't trust yet. Earn the relationship first. The framework can wait two weeks. The relationship can't.
How to skip it: Start with the people. Understand what they care about, what they've tried before, and what's burned them. Then — and only then — suggest how to change the process.
Mistake #8: Expecting to feel competent quickly.
Most people don't feel like they know what they're doing for the first six to nine months. That's not failure. That's calibration. But most people interpret it as a sign they made the wrong call — and they quit before it clicks.
💭 You can't assess year one from inside month three. Give yourself a real runway before you decide whether this was the right move.
How to skip it: Build for the discomfort in advance. Know it's coming. Commit to a 9-month runway before you evaluate.
Mistake #9: Not asking enough questions.
You'll get a laptop and a Slack invite. The real information — who holds the power, what the team has tried and abandoned, what "good" actually looks like — none of that is written down anywhere.
💭 The new person asking questions looks curious. The experienced person who stopped asking looks complacent. Use the window while you have it.
How to skip it: Ask more questions than feels comfortable. Ask the obvious ones. Ask the naive ones. You'll never have this much permission to not know things again.
Mistake #10: Treating the hard part as a sign you made the wrong call.
The transition is hard. The first year is hard. That's not a signal. That's the cost of doing something that actually changes your trajectory.
💭 The people who made it through didn't feel more confident than the people who quit. They just stopped relitigating the decision every time it got uncomfortable.
How to skip it: Make the decision once. Commit to the full first year before you evaluate. Then evaluate.
Nobody figures out Product Management. Not in year one. Not ever.
The PMs who make it through don't have it figured out. They just stopped waiting until they did.
At some point they accepted that the role is mostly uncontrollable, the politics, the shifting priorities, the stakeholder who changes their mind, the roadmap that gets blown up in Q3. You can't control any of it.
What you can control: how well you understand the problem. How clearly you write. How quickly you follow up. How well you listen before you talk.
The ones who survive year one aren't the ones who got it all figured out. They're the ones who stopped trying to, and put that energy into the small things they could actually move.
Year one is the last time everything is new.
Stop trying to control it. Start working with it.
Next week: the one thing every PM I've coached did in their first 90 days that made everything easier. Don't miss it.
- Stef
PS: If you're making this transition and trying to figure it out alone, you don't have to. I run a PM community on Skool with weekly case study practice built specifically for career-switchers. Real problems, real feedback, no theory.
The people inside move faster. That's not an accident.
→The Product Move - a Skool community + newsletter very similar to mine all about breaking into product
→ Innovate Disrupt or Die – Strategic insights on innovation and disruption
→ Marketing Alec – AI-powered marketing strategies
→ Practical Marketing – No-BS marketing tactics that work
→ Two Dads in Tech – Honest conversations about tech careers and life
→ Cooking Agile – Agile practices made practical
→ Seedradar AI – Startup and AI trends to watch
→ The Centaur – Stay irreplaceable in the age of AI