How to Thrive as a Product Manager When the Product Already Exists - ProductFTW #74

We have spent a lot of time on this newsletter talking about the experience of being the first product manager at a startup. Zach covered that firsthand, and it is worth reading if you are in that seat. Today I want to focus on something different: what you should do when you join a startup after the product is already live.

To frame this, I think about product management skills in two buckets. The first is 0 to 1, which is the work of turning an idea into something that exists. The second is 1+, which is taking something that already exists and pushing it forward. These require genuinely different skills, and not every product manager can do both well.

I will be honest: I gravitate toward 0 to 1. There is something about starting with a blank canvas and seeing it through to something real that feels like being an artist. You get to make every creative decision, watch the thing take shape, and learn an enormous amount in a compressed period of time. I love that kind of accelerated learning. That said, I do enjoy 1+ work too, and I think it is where many PMs actually thrive.

The challenge with 1+ is the urge to come in and immediately do things “your way.” You look at what exists, and you see all the things you would have done differently. I have felt this myself and heard about it from many others. You must resist this urge. A better approach is to first solidify your understanding, meet your goals within the existing structure, and then shape the product into something new over time as you build trust and learn context.

If you are not sure which PM-skills bucket you prefer, ask yourself a few questions:

• Can you create something out of nothing? 
• Can you see a path that no one else seems to see yet? 
• Do you understand what it takes to build new software from scratch?
• Do you know how to validate an idea through signals when there are no users yet? 

If you answered no to most of those, you are likely wired to be a strong 1+ product manager.

(Yes, I made up this "1+" terminology. It is how my brain organizes the work, and I find it useful, so we are going with it.)

Start by building a complete picture

When you join a company in the 1+ phase, your first task is not to build anything. Your number-one priority is to understand what already exists and why. What did they build? How are they measuring success? What decisions were made along the way, and why were they made that way? You are going to spend a lot of time in conversations with your coworkers in those first weeks, piecing together a snapshot of where the product is right now.

Ideally, you already have some of this context from your interview process. You should know roughly why they hired you and what they expect you to do. If your goal is something vague like "get more users," that ambiguity is a signal to push for clarity early, and, honestly, it is something you should ask about before you accept the offer. "How will I be evaluated in my first 90 days?" is a completely reasonable interview question, and the answer tells you a lot.

Once you have the snapshot-version of the past, you can start identifying the levers that are actually available to you. This is where the 1+ role gets interesting. There was already a vision before you arrived. There was already a strategy. You were (probably) not hired to start over. Your role is to step into that momentum and drive it forward. To do that well, you need to understand the landscape clearly because you cannot move something you cannot see.

Use the advantages you have

Here is what is different about the 1+ that a 0-to-1 PM would love to have: you have real users. That is a significant asset, and one that many PMs do not lean on enough when they start a new role.

Talk to your existing users. They will tell you things your internal data never will. Look for places where users are already sharing unsolicited feedback, which might be Reddit, app store reviews, comments, or anywhere people go to complain (rave) about products like yours. This kind of organic feedback is extremely useful, and it costs you nothing.

At the same time, audit what data infrastructure actually exists. Do you have analytics on the product? Do you know where users are coming from? Has anyone ever talked to a customer? Is there a support channel, and if so, what patterns show up there? If the answer to most of these is no, you’ve now created a roadmap. Those gaps are exactly where you can start building the visibility you need to do your job.

My career includes many stories like this. Much of my work involves joining a company in the middle of a significant transition, whether that is launching their first credit card program or replatforming an existing product, and trying to learn as much as possible while making the biggest impact in the shortest amount of time. What I have noticed across all these transitions is that an outside perspective is an advantage most internal PMs do not have. 

When you are close to a product every day, you stop seeing it the way a new user sees it. You stop questioning decisions that were made two years ago because they have just become the “way things are”. Coming in fresh, without that history, means you are actually in a better position to spot the gaps than the people who built it. The key is learning to use that perspective before it fades, because the longer you are inside a company, the more you start to see things the way everyone else does.

Narrow down to the right lever

Once you understand both the internal context and the external feedback landscape, you can start to get specific about what you are actually trying to move. Is the goal revenue? Conversion? Top of funnel growth? User retention? Something more ambiguous?

Getting clear on the goal lets you work backward. If more users at the top of the funnel means more conversions downstream, then the question becomes: where is the friction? Where are people dropping off? Where are you hearing about pain points, and are those consistent across the channels you are now monitoring? You are looking for the place where a focused intervention can create a measurable result.

The 1+ PM role is fundamentally about making a product that already works, work better for more people. You have context, users, and history to work with. The job is to use all of it.

Now go do the work

Laying the foundation is the unglamorous part of the 1+ role, and most PMs rush through it. If you have done it properly, you now know what the product is trying to accomplish, where the real friction lives, who your users are and what they are telling you, and which lever is most worth pulling right now. Many PMs operate for months without that clarity.

Here is what thriving actually looks like: 

• Pick one goal and go deep on it before you touch anything else. 
• Talk to at least five users before you write a single requirement. 
• Build a relationship with your data by knowing what you are measuring, trusting it is accurate, and checking it regularly. 
• Communicate with stakeholders about what you are learning and why it is shaping your priorities.
• When you feel the urge to recreate something that is working just fine because it is not how you would have built it, pause and ask yourself whether changing it actually moves your goal forward or if you are just redecorating.

The PMs who thrive in 1+ roles are not the ones who come in with the loudest opinions about what should change. They are the ones who earn trust quickly, move a number that matters, and build enough credibility that when they do want to make changes, people are ready to follow them.

About ProductFTW

ProductFTW is a weekly newsletter about product management, with a focus on real-life experiences in startups. We want to help product leaders be successful by giving realistic approaches that aren’t for giant tech companies. We know you don’t have a full-time product designer on each team. We know your software probably hasn’t been used by millions of people worldwide–yet. We’re here to bridge the content gap from building your product and team to scaling it.

Part of the Product Management Leadership & Career Guide — ProductFTW's collected essays on the PM role, leading without authority, hiring, and getting hired.