Introduction: The Person Behind the Product
Think about an application you use regularly.
Maybe it's a banking app, a shopping website, a hotel booking platform, or a service that helps you organize your daily life.
Now think about the experience of using it.
Why does it have certain features? Who decides which problems the next update should solve? How does the company determine whether customers actually benefit from a change?
Those decisions don't happen automatically.
Behind many successful products are people responsible for understanding what customers need, identifying opportunities, and helping teams determine what to build and why.
One of those people is often a Product Manager.
I've spent years working in product management, particularly in digital technology and marketing environments. I've worked across websites, mobile experiences, content platforms, and teams responsible for delivering customer-facing functionality.
One of the most important lessons I've learned is that building something successfully doesn't necessarily mean you've built the right thing.
A team can deliver a feature on time, meet every technical requirement, and still discover that customers don't use it or that it doesn't solve the intended problem.
That's why product management exists.
Product managers help organizations make informed decisions about the products they create, improve, and maintain.
In this article, I'll explain what product managers do, what they're responsible for, the skills they need, and what the career looks like in practice.
You don't need a technical background or previous product experience to understand the fundamentals.
Let's start with the most basic question.
1. First, What Is a Product?
Before we define product management, we need to understand what a product actually is.
A product is something created or provided to deliver value to a particular group of users or customers.
Some products are physical.
Think about a vehicle, a coffee maker, or a pair of running shoes.
Other products are digital.
Examples include:
- A mobile banking application.
- A hotel reservation website.
- An online learning platform.
- A customer loyalty program's digital experience.
- A business reporting dashboard.
- Software that helps companies manage employees.
- An application that helps people plan meals.
Some products combine physical and digital experiences, while others are services supported by technology.
A product doesn't have to be something customers purchase directly.
For example, an internal scheduling system used by hospital employees may be a product even though patients never see it and no one purchases it separately.
What matters is that the product serves identifiable users and provides value.
Products Are Not Just Collections of Features
But the product is more than the collection of features.
The overall experience is intended to help travelers find and reserve accommodations conveniently and confidently.
A good product manager understands that distinction.
Customers don't usually open a booking application because they're excited to interact with a date picker.
They open it because they want to book a room.
The features are tools that help them accomplish that goal.
The product exists to solve a problem or fulfill a need.
Understanding that principle is the foundation of product management.
2. What Is a Product Manager?
A product manager helps determine what a product should accomplish, which problems it should solve, and how it should evolve to create value for customers and the organization.
Let me simplify that.
A product manager helps answer questions such as:
- Who is this product for?
- What problem are we trying to solve?
- Why is that problem important?
- What should we build or improve?
- Which opportunities deserve attention first?
- How will we know whether our solution worked?
- What should we learn or change next?
Product management involves connecting customer needs, business objectives, and the capabilities of the teams building and supporting the product.
A product manager works with many different people to make those connections.
They might collaborate with designers, engineers, analysts, marketers, customer service teams, executives, and other business stakeholders.
But here's something important to understand:
A product manager isn't necessarily the person who designs, codes, markets, or sells the product.
Instead, they help the organization make decisions about the product and coordinate the understanding needed to move it forward.
Depending on the company, they may have significant decision-making authority or share that authority with business leaders and other product professionals.
The title doesn't automatically mean they manage employees.
Just like project managers, many product managers influence teams without being the direct supervisor of the people doing the work.
3. What Does a Product Manager Actually Do?
The responsibilities vary across industries and organizations, but several activities are common.
Understanding Customers and Their Problems
Good product management begins with understanding people.
Who uses the product?
What are they trying to accomplish?
Where do they struggle?
What causes frustration?
What would make their experience better?
Product managers may learn about customers through interviews, surveys, usability studies, support feedback, analytics, and collaboration with research teams.
For example, imagine customers regularly abandon a hotel booking application before completing their reservations.
A product manager shouldn't immediately assume the solution is to add a new button or redesign the entire application.
They should first investigate why customers are leaving.
Perhaps the pricing isn't clear.
Perhaps the booking process requires too many steps.
Maybe the application is slow, or customers encounter errors when entering payment information.
Different problems require different solutions.
The product manager's job is to help the team understand the problem before committing to a solution.
Connecting Product Decisions to Business Goals
A product also needs to support the organization behind it.
A business might want to increase revenue, improve customer retention, reduce operating costs, or make an existing service more efficient.
Product managers help connect these goals to opportunities for improving the product.
For example, a hotel company might want more customers to complete reservations through its mobile application.
That business objective creates an opportunity to investigate and improve the booking experience.
But the goal isn't simply to build more features.
It's to improve an outcome that matters.
Defining Product Direction
Product managers help establish where a product should go.
This may include contributing to a product vision, defining goals, evaluating opportunities, and communicating priorities.
A product vision describes the future experience or value the organization wants to create.
A product strategy explains the choices and approach intended to move toward that vision.
A product roadmap communicates planned or potential areas of work over time.
You don't need to master those terms today. We'll explore them in greater detail later in this guide.
For now, think of product direction as answering:
Where are we trying to go, and why does it matter?
Prioritizing What Matters Most
One of the hardest parts of product management is deciding what not to build.
There are almost always more ideas than time, money, and people available to deliver them.
Customers request features.
Executives have priorities.
Sales teams want improvements.
Developers identify technical work.
Designers uncover usability problems.
All of these inputs may be important, but they can't necessarily happen at once.
Product managers help evaluate opportunities based on customer impact, business value, effort, risk, evidence, and strategic importance.
Sometimes the best decision is to delay a popular feature because a more serious customer problem needs attention.
Other times, the right decision is to improve something that already exists instead of introducing something new.
Prioritization is not simply choosing which request arrived first or which stakeholder speaks the loudest.
It requires judgment.
Helping Teams Understand What to Build
Once an opportunity has been prioritized, the product manager works with the team to clarify the problem, desired outcomes, requirements, and constraints.
Depending on the organization, they may create or contribute to:
- Product requirements.
- User stories.
- Acceptance criteria.
- Product roadmaps.
- Backlog priorities.
- Feature descriptions.
- Success measures.
These are tools for helping people develop a shared understanding.
A product manager might explain that customers need to understand the total cost of a hotel reservation before entering payment information.
Designers can then explore how that information should appear.
Engineers can determine how to calculate and display it.
Quality assurance specialists can test whether the experience behaves correctly.
The product manager contributes the customer and business context that helps guide the work.
Evaluating Results
Product management doesn't end when a feature launches.
After release, someone needs to understand whether the change actually helped.
Did more customers complete reservations?
Did the number of support complaints decrease?
Did users understand the new experience?
Did the improvement introduce unexpected problems?
Product managers work with analysts and other teams to evaluate results.
If the change doesn't produce the expected outcome, the team may need to investigate further and adjust its approach.
Launching a feature is an output. Improving the customer or business result is an outcome.
That distinction is central to product management.
4. A Real-World Example: HarborStay Hotels
Let's return to the fictional hotel company we introduced in our first lesson.
HarborStay Hotels operates a mobile application that allows travelers to search for and book hotel rooms.
The company has noticed that customers frequently abandon the reservation process before completing a booking.
Leadership wants to improve the experience.
In PC-01, we explored how a project manager might coordinate the delivery of changes to the booking application.
Now let's look at the same situation through the eyes of a product manager.
Step 1: Understand the Problem
Rather than immediately asking developers to redesign the booking screens, the product manager begins by gathering evidence.
They might review booking analytics, customer support complaints, usability research, and feedback from travelers.
Imagine the team discovers that many customers leave when they reach the final pricing screen.
Further investigation suggests that some travelers are surprised by additional fees appearing late in the process.
This gives the team a more specific problem to solve.
Step 2: Define the Desired Outcome
The product manager works with stakeholders to establish what improvement would look like.
For example:
Help travelers understand the total reservation cost earlier in the booking process, with the goal of reducing avoidable booking abandonment.
Notice that this statement describes the customer problem and desired outcome.
It doesn't dictate the exact screen design.
Step 3: Explore Solutions
The product manager collaborates with designers and engineers.
The team might explore showing estimated total prices earlier, improving fee explanations, or simplifying the pricing summary.
Each option has benefits, costs, and technical considerations.
The product manager helps evaluate the alternatives.
Step 4: Prioritize the Work
HarborStay has other ideas competing for attention.
Some stakeholders want a new loyalty feature.
Others want additional room filters.
Another team wants to improve application performance.
The product manager helps determine where the pricing transparency problem fits among those priorities.
If the evidence suggests that pricing confusion is a major reason customers abandon reservations, addressing it may be more valuable than adding another feature.
Step 5: Support Delivery
Once the team agrees on an approach, the product manager helps clarify requirements and acceptance criteria.
They work with designers, engineers, testers, and stakeholders as questions arise.
The project manager, if one is assigned, may coordinate schedules, dependencies, delivery risks, and milestones.
The two roles collaborate, but they are not necessarily responsible for the same decisions.
Step 6: Measure the Outcome
After the improvement launches, the product manager reviews the results.
Did booking completion improve?
Are customers still reporting pricing confusion?
Did the change help some customer groups more than others?
The team uses that evidence to determine what to do next.
This is an example of product management as a continuous process of understanding, deciding, delivering, learning, and improving.
And it's important to remember that HarborStay is a fictional teaching example. Actual responsibilities and decision rights differ across organizations.
5. What Does a Typical Day Look Like?
A product manager's day can vary significantly depending on the company, product, and stage of development.
Some days involve customer research and strategy.
Others involve technical discussions, reviewing designs, answering questions, or evaluating results.
Here's one illustrative schedule.
8:30 AM
Review Product Performance
Examine customer behavior, recent product changes, feedback, and key performance indicators.
9:00 AM
Team Coordination
Meet with designers, developers, and other delivery partners to clarify priorities and discuss questions.
10:00 AM
Customer Problem Review
Work with a researcher or analyst to understand why customers are struggling with a particular experience.
11:00 AM
Requirements Discussion
Review a proposed improvement and help the team understand the problem, expected behavior, and success criteria.
1:00 PM
Stakeholder Conversation
Meet with business leaders to discuss opportunities, trade-offs, and product priorities.
2:30 PM
Roadmap and Backlog Review
Evaluate upcoming work and determine whether priorities still align with customer needs and business objectives.
4:00 PM
Product Decision and Follow-Up
Document a decision, clarify the reasoning, and communicate next steps to the people affected.
This isn't a universal schedule.
A product manager at a small startup might handle many responsibilities directly.
At a large organization, research, analytics, product design, engineering, delivery management, and product operations may be handled by specialized teams.
The product manager's responsibility is to help connect those activities to a coherent product direction.
6. What Skills Make Someone a Good Product Manager?
When people first hear about product management, they often assume they need to know how to write software.
Technical knowledge can be valuable, especially when working with digital products.
But coding is not a universal requirement for becoming a product manager.
Several foundational skills matter across industries.
Curiosity
Product managers need to ask questions.
Why are customers struggling?
Why does the business want this feature?
What evidence supports our assumptions?
What might we be overlooking?
Curiosity helps prevent teams from solving the wrong problem.
Communication
A product manager needs to explain problems, priorities, trade-offs, and decisions to people with different backgrounds.
That means translating between business, customer, design, and technical perspectives.
Analytical Thinking
Product managers work with evidence.
They may examine customer behavior, performance trends, research findings, or financial information.
You don't need to be a professional data scientist, but you should become comfortable asking what the available information actually tells you.
Prioritization and Judgment
Every product faces competing demands.
A product manager must help determine which opportunities matter most and explain the reasoning behind those choices.
Collaboration
Product management is a team activity.
You need to work effectively with people who bring different expertise, opinions, and responsibilities.
Business Understanding
Product decisions should support a meaningful objective.
That may involve revenue, efficiency, customer satisfaction, retention, safety, or another organizational goal.
Understanding the business context makes product decisions more useful.
Adaptability
Customer needs change.
Technology evolves.
Competitors introduce new experiences.
Research sometimes proves that an original assumption was incorrect.
Good product managers are willing to learn and adjust.
Empathy
Empathy means making a genuine effort to understand what other people experience.
For product managers, this includes customers, users, colleagues, and stakeholders.
It doesn't mean agreeing with every request.
It means taking people's needs seriously while making responsible decisions.
7. Do Product Managers Need to Be Technical?
This question comes up frequently, especially among people considering a career change.
The answer depends on the role.
A product manager responsible for a highly technical developer platform may need substantial knowledge of software architecture, APIs, security, or infrastructure.
A product manager working on a consumer application may need a strong understanding of user experience, analytics, experimentation, and digital product delivery.
A product manager working on a physical product may need industry-specific manufacturing, supply chain, or regulatory knowledge.
Not all product managers write code.
However, product managers should understand enough about their product and delivery environment to communicate effectively, evaluate trade-offs, and make informed decisions.
In my own work across digital experiences and content technology, understanding how systems connect is important.
A change that looks simple to a customer may involve content management, integrations, design requirements, analytics, and multiple teams.
You don't need to become the expert in every system.
But you do need to understand how the pieces fit together well enough to ask useful questions and recognize dependencies.
For beginners, I recommend learning the fundamentals of the industry you want to enter rather than trying to master every technical subject at once.
8. Where Do Product Managers Work?
Product management exists in many industries.
In technology, product managers may work on mobile applications, websites, software platforms, artificial intelligence products, or internal business tools.
In financial services, they may help improve digital banking, payment systems, or customer account experiences.
In healthcare, they may work on patient portals, scheduling systems, clinical software, or medical technology.
In retail, they may focus on ecommerce experiences, inventory platforms, loyalty programs, or checkout systems.
In travel and hospitality, they may help improve booking experiences, customer loyalty, mobile applications, or operational systems.
In manufacturing and physical goods, product management may involve market needs, product specifications, lifecycle planning, pricing, and coordination across commercial and technical teams.
The title can mean different things across industries.
That's why reading job descriptions carefully matters.
Some organizations expect product managers to own product strategy and outcomes.
Others use the title for roles that emphasize delivery coordination, requirements management, or business analysis.
Neither the job title nor the industry alone tells you everything about the position.
9. What a Product Manager Is Not
There are several misconceptions worth clearing up.
A product manager is not automatically a project manager.
Project managers generally focus on coordinating delivery within project constraints.
Product managers generally focus on product direction, customer problems, priorities, and outcomes.
There can be overlap, especially in smaller organizations.
A product manager is not necessarily a software developer.
They work with technical teams but may not personally write code.
A product manager is not automatically the boss of the development team.
Many product managers influence without direct supervisory authority.
A product manager does not personally design every screen.
Product designers bring specialized expertise to the experience.
A product manager doesn't simply collect feature requests.
They investigate problems, evaluate opportunities, and help determine which work is worth pursuing.
A product manager doesn't always have final authority over every product decision.
Decision-making responsibilities vary by organization.
And perhaps most importantly:
A product manager's success isn't measured only by how many features get released.
The real question is whether the product is creating meaningful value.
10. Project Manager vs. Product Manager: A First Look
Now that we've introduced both professions, let's compare them at a high level.
| Question | Project Manager | Product Manager |
|---|---|---|
| Main focus | Coordinating delivery | Guiding product direction and outcomes |
| Key question | How do we deliver the agreed work effectively? | What problems should we solve, and why? |
| Typical concerns | Scope, schedules, resources, dependencies, risks | Customers, business goals, priorities, product performance |
| Common artifacts | Project plans, milestone schedules, status reports, risk logs | Product strategies, roadmaps, requirements, prioritized backlogs |
| Success considerations | Agreed deliverables, time, cost, quality | Customer value and business outcomes |
| Work horizon | Often a defined project with an endpoint | Often the ongoing life of a product |
These are useful distinctions, but real organizations aren't always this neatly divided.
Some companies combine responsibilities.
Others have product owners, program managers, delivery managers, or technical leads who share portions of this work.
We'll explore these differences in depth in PC-03.
For now, remember this:
Project management helps organize how work gets delivered. Product management helps determine what work is worth doing and whether it creates value.
Both are important.
11. How Can You Start Exploring Product Management?
You don't need to wait until someone gives you the title of Product Manager to begin learning how product managers think.
Start by examining products you already use.
Choose a mobile application, website, or service you're familiar with.
Ask yourself:
- Who is the intended customer?
- What problem does the product solve?
- What does the product do particularly well?
- Where do users encounter frustration?
- What evidence would help me understand the problem?
- What improvement might create meaningful value?
- How would I know whether that improvement worked?
You can also explore entry points such as associate product manager positions, product analyst roles, business analyst roles, product operations, and related positions.
Some people transition into product management from design, engineering, marketing, customer support, operations, or project management.
There is no single universal career path.
However, entry-level product management roles can be competitive, and some employers expect prior industry experience even for junior positions.
That's why practical experience, evidence of problem-solving, and the ability to explain your thinking can be valuable.
We'll dedicate an entire lesson to entering product management without previous experience.
For now, focus on learning the fundamentals.
12. Try It Yourself: Think Like a Product Manager
Let's practice.
Imagine HarborStay Hotels has asked you to investigate why customers abandon its mobile booking process.
You are not being asked to design a new application.
You're being asked to understand the problem and recommend a sensible next step.
13. Key Takeaways
If you remember only a few things from this article, remember these:
-
A product delivers value to a group of users or customers. Products may be physical, digital, internal, or service-based.
-
A product manager helps guide what a product should accomplish and how it should evolve. Their work connects customer needs, business goals, and delivery capabilities.
-
Product management starts with understanding problems. Building features without understanding customer needs can create activity without meaningful value.
-
Prioritization is central to the role. Product managers help teams make informed choices about what matters most.
-
Product managers work across disciplines. They collaborate with designers, engineers, analysts, stakeholders, and other specialists.
-
Launching is not the finish line. Product managers evaluate whether changes actually improve customer and business outcomes.
-
You can begin developing product thinking now. Observing products, investigating problems, and practicing evidence-based decisions are useful starting points.
What's Next: Project Manager vs. Product Manager
You now have an introduction to both careers.
You understand that project managers help coordinate the delivery of work and product managers help guide the direction and outcomes of products.
But what happens when both roles work on the same initiative?
Who decides what gets built?
Who manages deadlines?
Who talks to stakeholders?
And which career might be the better fit for you?
In our next lesson, we'll put the two roles side by side, explore where their responsibilities overlap, and examine how they collaborate.
Next article: PC-03 — Project Manager vs. Product Manager: What's the Difference?
Part I — Understanding the Careers | Lesson 03
This article is part of The Project Manager & Product Manager Career Guide by Brad Merritt, an educational series designed to help beginners understand both professions, explore career opportunities, and build practical skills.