A Product Manager, or product leader, is responsible for defining product strategy, prioritizing development and ensuring that the product creates value for both users and the business. The role carries significant responsibility, but limited formal authority, and requires the ability to influence decisions across teams, leadership and stakeholders. This makes the Product Manager a key role in modern product development and product management.
When focus became the biggest challenge
In 2018, I was exhausted. Not because I disliked my job, quite the opposite. I had a role I enjoyed, with more decision-making power than many other Product Managers. But after many years in a company that lived in constant startup mode, with reorganizations and shifting priorities, it started to wear me down.
Every time we got close to a goal, the direction changed. As a hybrid of Product Manager, Product Owner and Project Manager, I was responsible for strategy, backlog and deliveries. But every time we built momentum, resources were moved, and we had to start over. Eventually, it felt like trying to climb two mountain peaks at the same time. I was constantly in motion, but I did not experience the progress I was working so hard to create.
That was also when I truly understood what makes the Product Manager role so demanding. You have to lead without authority, influence without deciding, and balance user needs, technical limitations and business goals. At the same time, others often have the final say when priorities are made.
When the product team works in a data-driven and user-centered way, while leadership has to consider finances, investors and strategic concerns, friction naturally occurs. The challenge is not necessarily that anyone is wrong, but that different perspectives pull in different directions.
That experience taught me something that reaches far beyond product management. When everything is important, nothing is important. Focus is not just a product skill. It is one of the most important leadership skills there is.
What does a Product Manager do?
At the core of the Product Manager role is the ability to balance technical possibilities, business goals and user needs in order to develop products that the market wants and the company can deliver. The PM acts as the link between technology, market and business, and therefore has to understand what should be built, why it matters, and how it fits into the company’s strategy.
But even though these basic principles apply in all companies, the role can have very different areas of responsibility depending on the company’s size, industry and business model. Since the title “jack-of-all-trades” is not usually found on the organizational chart, the Product Manager often ends up filling that role.
Different types of Product Managers
Although the basic principles are the same, there are several variations of the Product Manager role. What type of Product Manager a company needs depends on the product, the market and the organization’s needs. In practice, the roles often overlap, but these are among the most common variants.
Technical Product Manager
A Technical Product Manager (TPM) has a strong understanding of technology and works closely with developers and architects to define technical requirements and solutions. The role is common in technology companies and SaaS businesses where the technical complexity of the product requires the Product Manager to understand both business needs and technical consequences.
Strategic Product Manager
A Strategic Product Manager focuses primarily on the market, competitive landscape and the company’s long-term goals. The role often involves market analysis, product strategy, positioning and identifying new opportunities for growth. This type of Product Manager is often found in larger companies and B2B markets.
Growth Product Manager
A Growth Product Manager works to create growth through analysis, experimentation and continuous improvement. The goal is to increase user engagement, conversions and customer loyalty. The role is particularly common in startups and digital services, where A/B testing, product data and user insight are central.
Go-To-Market Product Manager
When a product is being launched or brought into new markets, it is often a Go-To-Market Product Manager who leads the work. The role focuses on commercialization, pricing, distribution and collaboration between product, marketing and sales to ensure a successful launch.
Internal Product Manager
An Internal Product Manager is responsible for internal systems and digital work tools. The goal is to make work processes more efficient, improve the user experience for employees and ensure that the organization has the tools it needs to work effectively.
Responsibility without authority
What all these roles have in common is significant responsibility, but limited formal authority. A Product Manager is often responsible for the product’s direction, priorities and results, but rarely has personnel responsibility or decision-making authority over the people who will do the work. You cannot order developers, designers, sales teams or leaders to do something, but you are still expected to ensure that the product moves forward, that the teams collaborate, and that the goals are reached.
It is precisely this combination that makes Product Manager one of the most influential, but also one of the most demanding functions in an organization. Progress is created through communication, trust and influence, not through authority. You rarely get buy-in because you decide, but because you manage to bring people with different interests together around a shared direction. In many ways, the Product Manager role therefore resembles politics more than traditional leadership.
Product Manager, Product Owner and Project Manager
In theory, Product Manager, Product Owner and Project Manager are three different roles. In practice, the boundaries are often much more fluid. In many companies, especially smaller or rapidly growing organizations, a Product Manager also acts as Product Owner, and sometimes the role overlaps with Project Manager. This often happens because the business does not have the resources or the need to separate the roles completely. The result is that one person both develops strategy, prioritizes the backlog and follows up on deliveries.
A simple way to understand the differences is to look at the questions the different roles primarily try to answer:
| Role | Focus area | Key question |
|---|---|---|
| Product Manager (PM) | Product strategy and long-term success | What should we build, and why? |
| Product Owner (PO) | Backlog prioritization and development | How should we build it? |
| Project Manager (PM) | Planning, resources and execution | When will it be delivered, and who does what? |
In practice, responsibilities vary from company to company. Some Product Managers work almost exclusively with strategy and market insight, while others also handle backlog, sprint planning and project follow-up.
I have personally had roles where I essentially combined all three functions. I worked with product strategy and business development as a Product Manager, prioritized backlog and development tasks as a Product Owner, and was also responsible for planning, coordination and deliveries as a Project Manager.
The advantage of such a hybrid role is that you gain insight into the entire value chain, from idea and strategy to development and delivery. That can create a stronger connection between vision and execution.
The challenge is that the roles often pull in different directions. As a Product Manager, you may want to pause and reconsider the strategy. As a Product Owner, you have to prioritize the next sprint, while the Project Manager in you would rather keep the plan on track and deliver on time. When all these roles live in the same head, you sometimes end up negotiating with yourself. Then the biggest challenge is not necessarily other people, but the ability to remain neutral between the different perspectives.
What separates a good Product Manager from a mediocre one?
There are many frameworks, courses and certifications that describe what a Product Manager should know. Most people eventually learn product strategy, backlog prioritization, user insight and analytics tools. Still, there is a big difference between filling the role and mastering it.
Over the years, I have observed that the best Product Managers are rarely the ones who know the most models or use the most buzzwords. More often, they are the ones who can balance conflicting interests without losing sight of the direction.
- They understand the business
A good Product Manager does not just see the product. They understand how the product contributes to the company’s goals, revenue and long-term strategy. They are able to connect user needs to business value.
- They understand the users
Many people say they are customer-centric. The best ones are curious enough to challenge their own assumptions and listen to what users actually need, not just what they say they want.
- They communicate well
Product Management is largely about communication. You need to be able to speak with developers, designers, leaders, sales teams and customers, often on the same day. The ability to translate between these environments is often more important than technical expertise.
- They prioritize
Every organization has more good ideas than time and resources. A skilled Product Manager is able to say no to good initiatives in order to make room for the most important ones.
- They are able to stay neutral
This is one of the hardest things, and perhaps the most underrated skill. A Product Manager must be able to set personal preferences aside and evaluate alternatives based on what creates the most value for users and the business. When sales wants one thing, developers another and leadership a third, the ability to see the bigger picture is crucial.
- They create progress
The best Product Managers make things happen. Not because they have the most authority, but because they are able to create progress through people who do not report to them.
When Product Manager becomes several roles in one
When I first became a Product Manager, I quickly realized that the role was far broader than the job description suggested. In theory, the job was about product strategy and product development. In practice, it was about everything that could influence the product’s success.
I worked in a startup with international customers and limited resources. The product was the very nerve center of the company, and everything had to fit together. Features, user experience, accessibility, invoice text, onboarding and customer communication all influenced how the product was perceived. At the same time, we did not have dedicated specialists for every area.
While larger competitors could have dedicated Product Managers for hardware, software and different markets, I had to deal with the whole picture.
That taught me that Product Management is rarely about the product alone. The role is about understanding the connections between technology, people, business and customer experience. The smaller the organization, the broader the responsibility often becomes.
Perhaps that is why many Product Managers describe themselves as the organization’s jack-of-all-trades. Not because the role lacks direction, but because it has to fill the gaps between disciplines that might otherwise end up working separately.
Why the Product Manager role is about influence, not authority
You can certainly say that the success of a product is the Product Manager’s responsibility, but in practice the result depends on the entire organization. A PM can contribute strategy, priorities and direction, but is also dependent on leadership giving the strategy time to work.
I have seen this in practice. In a previous role, I experienced how strategy and focus could shift faster than the market had time to respond. What was a focus area one quarter was replaced by something new before customers and partners had time to build trust in the product. The result was an organization that was constantly heading toward something new, but rarely got the full value from what had already been developed.
This is not unusual. When new opportunities appear, it is tempting to adjust course in order to stay competitive. But without anchoring and continuity, both teams and partners can lose direction.
For a Product Manager, it can feel like balancing on a tightrope in strong wind. You can work as strategically as you want, but if the wind keeps changing, the job becomes more about staying upright than moving forward.
That is also why the Product Manager role is more about influence than control. When you cannot use authority, you have to create support in other ways. It starts with understanding what motivates the people around you. Developers are often concerned with quality and technical debt, sales wants features that make it easier to win customers, while leadership focuses on growth, risk and profitability.
The better you understand these perspectives, the easier it becomes to bring the organization together around shared priorities.
At the same time, gut feeling is rarely enough. User insight, analytics and data provide a more objective basis for decisions and make it easier to explain why some initiatives should be prioritized over others. Just as important is the ability to communicate a clear direction. People are rarely motivated by a backlog or a list of tasks. They are motivated by understanding what problem needs to be solved and why it matters.
Perhaps that is why the Product Manager role in many ways resembles politics more than traditional leadership. You rarely get buy-in because you decide, but because you are able to build understanding, create support and bring people with different interests together around a shared goal.
My experience: When the direction keeps changing
As a Product Manager in a company with global video conferencing solutions, I learned the hard way what it is like to have significant responsibility, but limited authority, while focus and priorities keep changing.
I took initiative, pushed the strategy forward and worked to help us reach the market. We often reached our goals, but not necessarily in the most efficient way, because new initiatives, changing priorities and shifting focus meant that progress was rarely as good as it could have been.
The challenge was not that we adjusted course from time to time, that is a natural part of product development. The challenge arises when it becomes a pattern, and much of the energy goes into reorientation rather than execution because new priorities keep appearing before the existing ones have had time to work.
In hindsight, I see that I could have been clearer. I wish I had the confidence I have today to say: «If we are going to prioritize this, we have to deprioritize something else.» Back then, I tried to solve the challenge with more effort, while today I know that sustainable product management is just as much about focus as it is about execution.
For me, this may have become the most important lesson of all: A strategy creates no value until it is given time to work. That is why good product management is not only about choosing what to do, but also about protecting priorities, daring to say no and giving the organization the opportunity to build on what already works.
