DEV Community: Pranjal Sarkar

The shift from feature ownership to business ownership

Pranjal Sarkar — Mon, 28 Sep 2026 07:06:08 +0000

There is a moment in every product leader's career where the rules change, and the frustrating part is that nobody tells you it is happening. One day you are being evaluated on delivery, timelines and execution quality, and somewhere along the way the organisation quietly shifts to a completely different scorecard. You are still doing everything you were rewarded for, but the rewards have stopped coming. That is the moment most product leaders first encounter the gap between feature ownership and business ownership.

These are not the same job

Feature ownership is a clearly defined responsibility. You own a scope, you work with engineering and design, you manage timelines, you ship the thing and you move to the next one. When the feature works as expected and lands on time, you have done your job well. That clarity is actually one of the reasons people stay in feature ownership longer than they should. It feels productive. It feels measurable. It feels like progress.

Business ownership removes that clarity and replaces it with something far more complex. When you own a business area, you are simultaneously responsible for revenue, costs, customers, competition and the long-term health of that part of the business. There is no moment where you can declare the work done. The finish line is not shipping. The finish line is what changed in the business because of what you shipped, and that question never fully goes away.

The question you wake up with

One of the clearest ways to understand which mode you are operating in is to pay attention to the question that is already running in your head when you start your day. A feature owner is thinking about timelines, blockers, scope clarity and delivery commitments. Those are real and important concerns, but they are all internal questions about execution.

A business owner is thinking about whether the last thing that shipped actually moved something meaningful, whether customers are responding the way the team expected, whether the revenue assumptions are holding up, and whether the organisation is getting stronger or weaker in the market.

Same product, same team, completely different starting point, and that starting point shapes every conversation and every decision that follows.
Perfect features can still destroy business value

This is the part that genuinely surprises most people when they first hear it. You can ship a feature that performs exactly as designed, lands on time, comes in under budget and scores well in user testing, and it can still damage the business. It might have solved a problem that was not actually costing the company anything.

It might have pulled your best engineers away from infrastructure work that was quietly becoming critical. It might have added a layer of complexity to a product that customers were already finding difficult to navigate. Feature ownership gives you no protection against any of this because your job was to build it well, and you did. Business ownership holds you accountable for the outcome regardless of how well the execution went, and that is a fundamentally different kind of pressure.

What changes when you make this shift

When you move into business ownership, the internal scorecard you keep for yourself has to change completely. Output is no longer the measure. Outcomes are. The question is no longer whether it shipped but whether it mattered, and those two things are far less connected than most product people realise. The conversations change as well. When you walk into a leadership review, nobody is asking how many features shipped last quarter or whether the team hit velocity targets. They are asking what moved in the business, what the numbers look like, what the next strategic bet is and whether you can defend it.

That is the conversation that business ownership prepares you for.
The real transition

Earlier in your career, your job was essentially complete when the feature shipped. At the next level, shipping is just the beginning. The real work starts after release, when you are watching whether revenue moved, whether customers stayed, whether the business got stronger or weaker because of the decision you made. You are no longer measured by what you built. You are measured by what happened to the business after you built it, and that is a very different conversation to be prepared for.

The shift from execution thinking to strategic thinking

Pranjal Sarkar — Mon, 28 Sep 2026 07:02:01 +0000

There is a thinking pattern that every product person develops early in their career, and it is so deeply built into the daily rhythm of the job that most people never stop to question it. You wake up thinking about what is due, what is blocked and what needs to move forward today. You go into meetings with status updates and dependency lists.

You measure a good day by how much got done. That default is execution thinking, and for a long time it is exactly the right way to operate.

The problem is not that execution thinking is wrong. The problem is that it quietly becomes the ceiling.

What Shreyas Doshi got right

Shreyas Doshi makes a distinction that is worth sitting with. He says it is not about how hard you think. It is about the level at which you think by default. That is a subtle point but it changes everything once you understand it. Most product people spend their entire career trying to think harder, move faster and execute better, without ever questioning the level at which their thinking begins. They optimise the engine without asking whether the car is pointed in the right direction.

The level at which you think by default shapes every conversation you have, every priority you set and every decision you make. If your default is execution, you will always be solving for delivery. If your default is impact, you will always be solving for what the business needs to become.

A product leader who has made this shift does not start the day by asking what needs to get done. They start by asking what needs to change in the business. That sounds like a small difference but the downstream effects are enormous. When your starting question is about delivery, you optimise for shipping. When your starting question is about impact, you start evaluating whether what you are about to ship actually moves anything that matters.

That one reframe changes how you run planning sessions, how you push back on requests, how you talk to stakeholders and how you decide what not to build. Everything flows from the default question you are operating with.
Same person, different starting point

This is important to understand because people often assume the shift from execution to strategy requires more time, more information or more seniority. It does not. The person who thinks strategically and the person who thinks execution
ally can have identical experience, identical workloads and identical access to data. The difference is not capacity. It is not even intelligence. It is the level at which their thinking begins each day.

Same effort. Same hours. Same team. Completely different starting point, and that starting point compounds over time into a completely different career trajectory.

Why most product people never make this shift

The execution default is not just a habit. It is also reinforced by the environment. Most product organisations reward delivery. Standups are about blockers. Reviews are about velocity. Roadmaps are about timelines.

When every system around you is measuring output, it takes a deliberate act of will to keep your own thinking anchored at the level of impact. The pull towards execution is constant, and most people follow it without realising they have a choice.

The shift only happens when you consciously decide to question your default, and then defend that new default against an environment that will keep pulling you back towards the comfortable clarity of execution.
The title change means nothing without this shift

This is the part that catches most people off guard. You can be promoted into a leadership role and still be operating with an execution default. The new title does not automatically change the level at which you think. You will still run your days around delivery, still measure yourself by what shipped and still frame every problem as an execution problem that needs to be solved faster or more efficiently.

Strategic thinking is not something that comes with the role. It is something you have to deliberately build, protect and return to every single day. Until that default changes, the title is just a label. The actual shift in how you lead has not happened yet.

What executives actually expect from a product leader

Pranjal Sarkar — Mon, 28 Sep 2026 06:53:35 +0000

Every leadership review includes a conversation most product leaders are completely unprepared for. Not because they have not worked hard enough or shipped enough or managed their stakeholders well enough. But because they have been preparing for the wrong conversation entirely.

The executives in the room are not asking about features. They are not asking about timelines or velocity or roadmap completion. They are asking about the business, and that is a fundamentally different conversation.
That gap between what product leaders prepare for and what executives actually evaluate is one of the most expensive misunderstandings in a product career.

The measurement changes completely

When you lead products, organisations do not evaluate you on what you shipped. They evaluate you on what changed because of what you shipped. Those are not the same question, and the difference matters enormously. A feature shipped is an output. A business that grew, a team that got stronger, a market position that improved, a customer base that expanded, these are outcomes. Executives think in outcomes because outcomes are what the business runs on.

In every leadership review, whether it is stated explicitly or sitting quietly underneath the surface conversation, the questions being asked are the same. Did the business grow? Did the team get stronger? Did you take the right decisions at the right time? These are not performance review questions. They are the fundamental questions of leadership accountability, and they are being answered by your track record whether you are prepared for them or not.

Owning beyond the roadmap

One of the clearest expectations that executives have of product leaders, and one that most product people underestimate, is the expectation of business ownership. Not product ownership. Not roadmap ownership.

Business ownership. That means you are accountable for things that sit well outside the boundary of what your team directly builds and ships.
Revenue is your concern. Customer retention is your concern. Competitive positioning is your concern. The long-term health of the business area you lead is your concern. The roadmap is just one instrument you use to address those concerns. When executives look at a product leader, they are looking for someone who understands that the roadmap serves the business, not the other way around. That shift in framing changes everything about how you make decisions, what you escalate, what you push back on and what you take ownership of without being asked.
Bringing a point of view

Beyond accountability, executives expect something that is harder to describe but immediately recognisable when it is missing. They expect you to walk into a room with a point of view. Not a status update. Not a list of options with pros and cons laid out for someone else to decide.

A point of view. Here is where we should go. Here is why. Here is what we need to do about it.

That is a specific kind of leadership behaviour and it requires a specific kind of preparation. It means you have done the thinking before the meeting. It means you have looked at the business, understood the context, weighed the options and arrived at a position you are willing to defend. And critically, it means you do this without being asked. The executive who has to ask their product leader for a recommendation has already learned something about that leader that will quietly shape every future conversation.

The leaders who get trusted with more responsibility are the ones who show up with the agenda, not the ones who wait for the agenda to be handed to them.

You are not executing the plan. You are the plan.

There is a shift that everything else depends on, and it is this. At the execution level, your job is to take a direction that has been set and deliver it as well as possible. At the leadership level, you are the direction. You are the one who looks at the business, understands where it needs to go and makes the case for how to get there. The plan comes from your judgment. The priorities come from your reading of the market and the organisation. The decisions come from your understanding of what the business actually needs.

Executives are not looking for someone to execute their thinking. They already have people for that. They are looking for someone who brings their own thinking, who can be trusted to look at a complex situation and arrive at the right conclusion independently, who does not need to be told what matters because they already know.

That is what product leadership looks like from the executive seat. And until you understand that, you will keep preparing for an evaluation that nobody in that room is running.

How the scope of ownership changes when you move up

Pranjal Sarkar — Mon, 28 Sep 2026 06:40:31 +0000

There is an assumption that most product people carry into leadership without realising it. They assume that moving up means doing the same job with a bigger team, a bigger roadmap and a bigger budget. More of everything, but fundamentally the same work. That assumption is what makes the transition so disorienting for so many people, because

leadership is not a bigger version of the job you already do. It is a different job with different rules, different measurements and a completely different kind of accountability.

The scope does not just expand when you move up. It transforms.
You own the outcome, not the output

When you lead a product, what you own is the outcome. Not the feature. Not the roadmap. Not the sprint plan or the release schedule. The overall outcome of the business area you are responsible for. And outcomes, unlike features, do not have clean boundaries. A feature has a scope document. An outcome does not. It stretches across teams, quarters, market conditions and customer behaviours that you can influence but never fully control.

This is the first and most important thing that changes. The unit of ownership shifts from something you can define and deliver to something you have to continuously move towards. You are no longer managing a clearly bounded piece of work. You are responsible for a direction and everything that happens in the pursuit of it.

When you own a feature, accountability is relatively contained. If something goes wrong, the scope of the failure is limited. When you lead a business area, accountability works differently. You are responsible for the decisions you make, for results that come from teams you directly manage, for teams that report into those teams, and for failures that happen three levels below you in the organisation.

Distance from the execution does not reduce your accountability. In many ways it increases it, because the further a failure is from your direct line of sight, the more it reflects on the systems, culture and judgment you have built around you.

That is the weight of leadership that nobody fully prepares you for. You own the decisions. You own the failures. You are accountable fully, completely and without exception, regardless of who made the specific call that led to the outcome.

Accountability cannot be delegated

This is the part that surprises people most when they first step into a leadership role. You can delegate execution. You can delegate decisions within defined boundaries. You can build teams that operate largely independently. But you cannot delegate the accountability that comes with the scope you carry. No matter how big your team gets, no matter how many layers of management sit between you and the day to day work, the accountability for the outcomes of that entire system stays with you.

That is not a burden that lightens with experience or seniority. If anything, it becomes more visible as you move up, because the stakes get higher and the consequences of getting it wrong become more significant for more people.

That is what changes when the scope changes

The title changes. The team size changes. The budget changes. But the most fundamental change is this. You are no longer accountable for a piece of work being done well. You are accountable for a part of the business being healthy, growing and moving in the right direction. Everything you do, every decision you make, every team you build and every priority you set is in service of that accountability.

Understanding that shift, really understanding it and not just intellectually acknowledging it, is what separates the people who grow into leadership from the people who hold a leadership title while still doing the previous job.

Why great PMs don't automatically become great product leaders

Pranjal Sarkar — Mon, 28 Sep 2026 06:35:00 +0000

Product careers have a transition that nobody really prepares you for. You have spent years getting better at your craft. You know how to run discovery, manage stakeholders, write a sharp PRD, prioritise under pressure, and ship consistently. You are good at this.

The organisation recognises it. Then, somewhere along the way, expectations change, and the skills that got you here stop being enough.
That transition is not a promotion. It is a transformation. And most people miss it entirely.

Two different games

Managing a product and leading a product are not two versions of the same job. They are two different games with different rules, different success criteria and different capabilities required to play them well.

The skills that make you an exceptional executor- clarity of scope, speed of delivery, precision in communication, management of dependencies, these are real and valuable. But they are not the same skills that make you an effective product leader. They were built in a different context, rewarded by a different system and designed to solve a different kind of problem.

This is the part that most organisations never communicate clearly enough. They promote people based on performance, which is a measure of execution quality, without explaining that leadership readiness is an entirely separate dimension. You can be the strongest performer on the team and still be completely unprepared for what the next level actually requires.

The real test is in the decisions

One of the clearest places where this gap shows up is in how product leaders deal with decisions. Not just the act of making a call, but the entire process around it. Thinking it through properly before committing. Standing behind it when the environment shifts. Defending it with evidence when people in the room start pushing back.

Execution does not build this muscle. When you are executing, most of the important decisions have already been made above you. Your job is to deliver within those constraints as well as possible. That is a valuable skill but it is not the same as the skill of deciding the first place, owning the consequences of it and being able to explain your reasoning to a room full of people who may not agree with you.

Judgment, honesty and preparation

Deciding where to move next as a product leader requires a kind of judgment that goes well beyond what the data tells you. Data gives you a picture of the past. Leadership decisions are almost always about an uncertain future where the information is incomplete, the stakes are high and the right answer is not obvious. The judgment to navigate that uncertainty is built through experience, reflection and a willingness to be wrong and learn from it. It is not something you can acquire by shipping faster or running better sprint reviews.

Validating a decision requires a kind of intellectual honesty that is uncomfortable to practise. You have to be genuinely willing to look at what you do not know, what assumptions you are making and where your own thinking might be wrong. Most product people, trained to project confidence and move with urgency, never develop this habit because it feels like the opposite of what got them recognised.

And defending a decision with proper evidence, in a high-stakes conversation with executives who are challenging your thinking, requires a level of preparation that most product people have never needed to build. Not because they are not capable of it, but because nobody ever asked them to do it before.

Thinking differently, not working harder

The mindset that product leadership requires does not come from doing more of what you are already doing. Working harder, shipping faster and managing more complexity will make you a better executor. It will not make you a better leader. The shift comes from fundamentally rethinking what your job actually is.

Your job is no longer to deliver. Your job is to make the right calls about what is worth delivering, to build the judgment to know the difference, to develop the discipline to validate your thinking before you commit and to build the habit of defending your decisions with clarity and evidence when it matters.

That is a completely different way of thinking about the work. And until that shift happens in how you see your own role, the title change will be a label sitting on top of the same old default.