You're a Baby Product Manager — Here's How to Know You're Doing OK and Grow

## How to grow as an accidental, early-career product manager Direct answer: Ship small experiments to learn, define clear success metrics for everything you touch, talk to end users every week, and build predictable stakeholder rituals so your team trusts you to prioritise and protect roadmap time. ## Ship to learn — prototypes beat perfection Release means many things: a paper prototype, an internal demo, a gated beta, or a minimal vertical slice in production. The fastest way to know if you’re on track is to put something in front of users and listen. Use Figma click-throughs, remote moderated tests, or a simple feature flag rollout. Treat every release as an experiment with a clear hypothesis and success criteria. If you fear releasing because the product is "experimental," that’s your signal to test earlier and cheaper. ## Define success: metrics and outcomes, not activity If you can’t measure whether your work moved the needle, you can’t prove progress. For each initiative, choose 1–2 success metrics (activation, retention, task completion time, NPS delta). Keep a short dashboard and report weekly trends to stakeholders — this is how you demonstrate competence and build credibility. If your company lacks instrumentation, prioritise building it: basic funnels and event tracking are the tools that allow you to learn from real users. ## Build a stakeholder rhythm and a mentor network Set recurring, concise cadences: weekly engineering touchpoint, fortnightly demo with stakeholders, monthly discovery review with sales or CS. These rituals reduce surprises and position you as the focal point for product decisions. Find a mentor who thinks differently — ideally someone senior who will push you. Join PM communities, share your problems, and be prepared to iterate on frameworks you learn. Learning is deliberate and iterative. ## Introvert strategies that work in product roles Being introverted is not a barrier — it can be an advantage. Prepare for meetings with an agenda, use written async updates to influence without theatre, and schedule one-on-one chats where you can ask deeper questions. For networking, set a small goal (speak to three new people) and treat it as a practice exercise. Finally, measure your growth: set quarterly skills goals (discovery, metrics, roadmapping, stakeholder management) and evidence them with one small project per skill. ```copy Weekly learning plan template to steal: - Monday: 1-hour customer interviews (3–4 calls) - Tuesday: Analyse last week's experiment data (30–60 mins) - Wednesday: Spec a new prototype and sync with engineering (60 mins) - Thursday: Work on a personal PM skill (course, reading) (60–90 mins) - Friday: Demo + write a short 1-page learnings doc ``` *For more on career positioning and transitions, explore our [Career Strategy](/career-strategy) insights.*