3 Things I Wish I Knew About Product Management at the Start

When I coach product managers, I try to anchor on experience—real stuff you only learn from getting it wrong a few times. Here are three truths I wish I understood earlier. They would've changed my approach overnight.

Our hope is that you read this and whatever you learn from it today, you can start using tomorrow.

---

1. The Power of Vision Clarity and Alignment

"I used to think vision was a ‘nice-to-have.’ Now I know that not having a clear, customer-centered vision means everyone fills in the blanks differently—and that kills momentum."

I see this mistake often. Teams jump into roadmaps without alignment on vision. When that happens, you're not leading—you're reacting.

I coach PMs to build clear, repeatable vision statements rooted in real customer pain points and measurable business outcomes. That’s why I created the 777 framework—seven questions each for vision, strategy, and roadmap. It brings structure to ambiguity.

If you're a junior PM, stop assuming the vision has been “set.” Ask:

• Is it written down?

• Does everyone interpret it the same way?

• Is it focused on what the customer needs, not just what the org wants to ship?

If the answer is no, write it. Share it. Refine it. That’s leadership.

Still unsure? Ask each stakeholder to explain what they think the vision is. Listen to the differences. Capture the common themes. Use that to draft the first version. Holes will be poked—good. Feedback is a gift. Keep refining until your stakeholders and co-creators align and believe in it.

---

2. Strategy Is Not a Roadmap—It’s Guardrails

"If I had known earlier that strategy isn’t a list of projects, but a set of principles and trade-offs that protect the customer and the business from chaos, I would’ve made far better calls."

Let’s keep this simple: A roadmap says what you’ll do. Strategy filters what’s worth doing. Every initial idea should pass through that filter.

Take this example.

You're a B2C eCommerce brand selling t-shirts. Your strategy includes:

• Maximize repeat customer rate

• Lower cost-per-conversion through better personalization

• Build brand equity through eco-conscious design

Now, someone pitches a feature idea: “Let’s launch a virtual try-on tool.”

Filter it.

• Does it drive repeat purchases? Maybe—it could reduce returns.

• Does it reduce CAC? Doubtful—it’s likely expensive to build and promote.

• Does it reinforce brand equity? Possibly, if it enhances the experience without greenwashing.

Now you’re evaluating the idea based on impact, not just how shiny it looks.

Good strategic pillars give you lenses. Ask:

• Does it reinforce trust?

• Does it help us be more of a one-stop shop?

• Will it improve time-to-value for the customer?

Then take it deeper. Does this move the KPI tied to that pillar?

Every pillar should have a KPI. If you can’t tie an initiative to one, pause. You might be solving for the wrong thing. If the KPI is a lagging indicator, then look for proxies that can help you determine if you are heading in the right direction.

---

3. You Don’t Need Authority to Be the Most Influential Voice in the Room

"I thought product management was about having the best ideas. Turns out it’s about making everyone else's ideas better."

At Product Protege, we teach this early.

You’re not here to show off your IQ. You’re here to raise the collective IQ of the room.

Here’s what “glue work” looks like in practice:

• Run every idea through structured frameworks —not opinions, but well constructed opportunities

• Use our pitch deck format or Epic Definition Guide to create clarity

• Pull in design, QA, analytics, and business early

Be the person who takes the messy doc with 20 bullet points and turns it into a structured, prioritized artifact that actually moves the team forward.

You don’t need permission. You just need process and empathy. If you need some guidance, check out some of our options here.

---

Bonus: Don’t Just Use Frameworks—Bend Them

Frameworks aren’t the goal. Outcomes are.

Early in your career, follow the rules. Learn how they work. Understand what success looks like when applied correctly.

But eventually, you’ll realize something: frameworks can’t know what you know.

You sit in every meeting most likely, right? You know which engineer pushes back on certain edge cases. You know which stakeholder has decision power. You know which gaps QA is stressed about.

No framework accounts for that. So tweak the playbook. Shortcut it when needed.

Prioritize efficiency over purity.

You’re not paid to follow frameworks. You’re paid to ship outcomes.

---

If you’re a junior PM reading this, ask yourself:

• What is one part of your current strategy that lacks a clear KPI?

• Have you documented your vision in a way your team can rally around?

• What rule could you bend this week to move your product forward?

Until Next Time!

Jason @