Two months ago, my job was to have the best answer in the room. Now my job is to choose one, and to live with it.
That sentence is the whole difference between the role I had and the role I have, and nobody quite prepares you for how different it feels from the inside. I stepped into the VP of Product seat at LiveData this summer. Sixty days in, here is what the transition from owning a product to owning Product actually taught me, unpolished.
The Job Is Deciding Now
As a PM, even a senior one, my value was having the sharpest take. I could read the situation, form a strong opinion about what we should do, and make the case. Someone else, eventually, owned the call.
That someone is now me, and the shift is bigger than it sounds. I can no longer just tell people what I think we should do. I have to be the one who chooses, weighing needs across the whole org against a real budget, and then own the outcome whichever way it breaks. Advising and deciding look similar from the outside and feel nothing alike from the inside. The opinion was the easy part. The choosing, knowing that resourcing one thing means starving another, is the job.
I got a fast lesson in it. I was pulled into fiscal-year planning at the eleventh hour and had to make strategic calls almost immediately, with real money attached. The only reason I wasn't underwater is that I'd spent the last year training myself to think at that altitude before I had the title. The habit was already there. I just finally had to sign my name to the decisions.
Putting Down the Old Work Is Harder Than Picking Up the New
Everyone warns you about the new responsibilities. Nobody warns you how hard it is to stop doing the old ones.
Getting the individual-contributor work off my plate, and letting go of things I still had in motion, took longer and felt worse than I expected. There is a real pull to keep doing the work you were good at, especially the work that's nearly finished. But every hour I spent finishing my old tasks was an hour I wasn't doing the job I was actually there to do now. Learning to leave good work unfinished, or to hand it off before it felt done, was one of the least comfortable and most necessary parts of the first two months.
When There's a Gap, You Build Your Way Out of It
The clearest example of what this role can be came from a problem I didn't plan for.
We brought on two new Product Owners into a company that didn't have much of a formal onboarding process, and we did it remotely, which is where a lot of onboarding quietly falls apart. The old playbook would be to write a thick onboarding doc and hope. Instead, I built an onboarding system: the new POs use Claude, wired into our internal context engine, to walk themselves through their first days and pull the product, domain, and process context they'd otherwise spend weeks chasing across documents and people's heads.
It worked better than a doc ever would have. Both POs were contributing meaningfully in about two weeks, and were taking over teams noticeably faster than has been typical here. For a remote hire, two weeks to real value is fast. That result didn't come from a process document. It came from treating an org gap as something to build, which is the same instinct that got me this role in the first place.
The Real Leadership Work Is Making Building Fast and Safe
The more I settle into the seat, the more I think the core of the job is not making the decisions myself. It is building the conditions under which a lot of other people can decide and build quickly without creating chaos.
Concretely, that has looked like revamping how our Product team works and how we engage internal stakeholders, so we spend our hours on the highest-leverage things instead of in status meetings. It has looked like automations that share what's been done and where things stand, so information moves without anyone having to chase it. And it has looked like setting up the guardrails and framing so an engineer can take a PRD and build fast within the right constraints for LiveData, our stack, our patterns, our standards, without having to relitigate the fundamentals every time.
The result I'm proudest of is unglamorous: we have more PRDs and roadmap items genuinely ready to build than we ever have. That is what "owning Product" produces when it's working. Not my personal output, but a team and a system that turn intent into shipped software faster than before. When anyone can build, the leader's job is to make sure the building is pointed the right way and moving without friction.
At a Small Company, You Don't Get to Be Purely Strategic
There's a version of the VP role that lives entirely at thirty thousand feet. That is not this job, and I've stopped pretending it should be.
At a smaller tech company, when your CEO, your CTO, and your VP of Engineering all still write code, the top Product person does not get to float above the individual level. You still drop down and do the work when the work needs it. For a while I treated that as a failure to delegate. I've come to see it differently. In a company where the most senior people still build, staying close to the actual work isn't a distraction from leadership. It's how you keep the credibility to lead builders at all.
Everything Takes Longer to Set in Motion Than You Think
The last surprise is the simplest. As an individual contributor, the gap between deciding and doing is small: you decide, then you go do it. As a leader, that gap is enormous. A decision is just the starting gun. Getting an organization to actually move in the new direction, to change a workflow, adopt a tool, hold a standard, takes far more time and repetition than I expected.
I'm learning to measure progress differently because of it. Not by what I decided this week, but by what's actually moving as a result of decisions I made weeks ago. Patience turns out to be a leadership skill, and it's the one I had the least of coming in.
Owning a product and owning Product are separated by one dropped article, and by almost everything else. One is about having the best answer. The other is about building the conditions for a lot of people to find and ship good answers faster than you ever could alone, and then choosing, and living with it.
Sixty days in, I'm still learning the shape of it. But I know which job I'd rather be bad at first than never get to do.
You stop being paid for your answer. You start being paid for everyone else's.