What is product management? A guide for product managers and Agile teams

Key takeaways

• Product management guides products from development through launch.

• Product managers bridge gaps between engineering, design, and business teams to deliver solutions that actually solve customer problems.

• Successful product managers rely on customer insights, analytics, and market research to validate ideas and guide feature development.

• Product management requires staying current with frameworks, tools, and methodologies while developing both technical and interpersonal skills.

Product management balances customer needs, business goals, and technical feasibility. Whether you're new to the field or looking to sharpen your approach, understanding what product management actually entails can help you build better products and advance your career.

So, what is product management exactly?

This guide covers the core principles of product management, from its historical roots to modern practices that drive successful products. We'll explore the key responsibilities that define the role, the skills that separate good product managers from great ones, and the frameworks that help teams ship products customers actually want to use.

What is product management?

Product management guides a product’s lifecycle—from development to pricing—by prioritizing the product and its customers.

To build the best possible product, product managers advocate for customers within the organization and make sure the voice of the market is heard and heeded. Thanks to this focus on the customer, product teams routinely ship better-designed and higher-performing products.

In tech, where entrenched products are quickly uprooted by newer and better solutions, there is more need than ever for an intimate understanding of customers. There’s a need to create tailored solutions for them and that’s exactly where product management comes in.

What is the history of product management?

Product management was born during the Great Depression when a 27-year-old marketer proposed the idea of a brand man. This type of employee managed a specific product rather than a traditional business role. 

Since the 1930s, the continued success of this function has led to the growth of product organizations across industries and geographies. Here’s a quick historical timeline of product management: 

• 1931: Neil H. McElroy, a marketing manager at Proctor & Gamble, writes a 300-page memo on the need for “brand men,” who manage specific products.

• Late 1930s: McElroy is an advisor at Stanford University, where he influences two young visionaries: Bill Hewlett and David Packard.

• 1943-1993: Hewlett-Packard sustains 50 years of 20% Y/Y growth by implementing the “brand man” philosophy in their new company.

• Late 1940s: Toyota develops JIT manufacturing principles, later adopted by Hewlett-Packard.

• 1953: Toyota develops the Kanban method.

• 1970s: Tech companies in the U.S. start developing lightweight processes, in opposition to cumbersome processes that emerged from manufacturing industries.

• 1980s: Developing agile processes, combined with greater acceptance of “brand management” roles, takes hold in many technology and software companies.

• 2001: The Agile Manifesto is written, which, in large part, broke down department silos and outdated processes, to make room for a unified product management role.

What is the product manager’s role in agile?

In some cases, product management for one product, or family of products, is handled by a single product manager. This individual must represent a deep proficiency in at least one of the areas that touch product management, and a passion for or fluency in the others. 

This role can take one of two forms: 

1. An experienced business marketer who is passionate about user experience and fluent in technical language

2. A technical development leader with such deep product knowledge that they can actively guide its creation.

These people have proven to be so rare and valuable that product management now commands the highest salaries in all of tech. Since it’s really hard to find individuals fluent in both areas, oftentimes product management is brought to life by a small group of specialists.

At Atlassian, we’ve formed the triad—where a leader from development, design, and business work together to lead product strategy. Supporting the triad are PMs, PMMs, and many of the other roles below:

• Chief Product Officer (CPO): Leads the product function at an organizational level. Ensures each product is looked after by skilled PMs and their teams.

• Product Owner: Takes a more active role in the development of the product by managing the engineering team’s product backlog and their communication with other stakeholders.

• Product Marketing Manager (PMM): Improves the product team's ability to reach customers and learn from them through product-tailored marketing campaigns and the insights they provide.

• User Experience (UX) Researcher: UX is one of a PM’s core responsibilities, but a dedicated UX researcher, who studies user behavior and makes usability recommendations, is a great addition to any product team.   

Product manager vs. project manager: Key differences

While the titles sound similar, a product manager and a project manager handle very different responsibilities. A product manager owns the "what" and "why" of a product. 

They define the vision, prioritize features based on customer needs, and ensure the product delivers value over its entire lifecycle. A project manager, on the other hand, focuses on the "how" and "when." 

Their role coordinates tasks, manages timelines, and keeps specific initiatives on track. Here's how these roles differ in practice: 

• A product manager might decide that adding a new integration feature will solve a critical customer pain point and drive adoption. 

• The project manager then steps in to coordinate the engineering, design, and QA resources needed to ship that feature on schedule. 

Product managers think in outcomes and customer impact. Project managers think in terms of deliverables and milestones.

These roles often collaborate closely, especially in agile environments. The product manager sets direction through product planning and roadmapping, while the project manager ensures the team executes efficiently and hits deadlines.

What are the main responsibilities of a product manager?

Product managers have many duties they must be on top of throughout the product development life cycle. They're responsible for understanding what customers need.

They’re responsible for defining how the solution will meet those needs and working with cross-functional teams to bring solutions to life. The specifics vary by company and product, but these responsibilities typically include gathering customer insights, setting strategy, prioritizing what gets built, and keeping everyone aligned on goals.

Understanding customer needs to guide product decisions

Product managers spend significant time figuring out what customers actually need—not just what they say they want. This means conducting user interviews, analyzing usage data, running surveys, and watching how people interact with your product. 

The goal is to uncover the underlying problems worth solving.

These insights directly inform which features to prioritize and how to position your product. When you understand why customers struggle with certain workflows or what's preventing them from reaching their goals, you can make smarter decisions about your strategy.

Defining product strategy to align with business goals

A clear product vision and strategy keep everyone moving in the same direction. Product managers make a product roadmap that outlines where the product is headed and why.

This connects day-to-day feature decisions to bigger company objectives and market opportunities. Strategic decisions tie directly to business outcomes as well. 

If your company is focused on reducing churn, your product strategy might prioritize features that improve onboarding and engagement.  And when you're expanding into a new market, your roadmap should shift to reflect those competitive dynamics.

Prioritizing features to maximize impact

Not every idea deserves development time. Product managers constantly evaluate features based on customer value, implementation cost, and strategic fit. 

The challenge is balancing quick wins that build momentum with longer-term bets that could differentiate your product in the market. Different prioritization methods work for different situations. 

Some teams use frameworks like RICE or value vs. effort matrices. Others depend on product management KPIs to track whether features are delivering expected results. 

This is why experts rely on product development software that offers list views, matrix views, and custom fields with formulas that let you compare and prioritize ideas with confidence.

These tools let you weigh factors that matter to your team, visualize trade-offs, and adjust priorities as market conditions change.

Collaborating with teams to deliver products effectively

Product managers work closely with other teams like engineering, design, marketing, and sales to ship products that customers will actually use. This means managing trade-offs, communicating priorities clearly, and keeping stakeholders aligned even when goals conflict.

Effective collaboration requires transparency about what's being built and why. When engineering understands the customer problem, they can suggest better technical solutions. 

If marketing knows the roadmap, they can plan launches more effectively. That’s why you need to communicate priorities and progress without requiring constant status meetings.

What are the essential skills in product management?

Every product has its own goals and challenges, which require a unique and customized approach to product management. Martin Eriksson famously described product management as the intersection of business, user experience, and technology.

• Business: Product management helps teams achieve their business objectives by bridging the communication gap between dev, design, the customer, and the business.

• UX: Product management focuses on the user experience, and represents the customer inside the organization. Great UX is how this focus manifests itself.

• Technology: Product management happens, day to day, in the engineering department. A thorough understanding of computer science is paramount.

Three additional skills that every PM needs are storytelling, marketing, and empathy.

Storytelling

A product leader should be as inspirational as they are tactical, and storytelling is their tool of choice. Through customer interviews and market research, product managers learn more about the customer than even the salespeople. 

They then use their storytelling skills to share that perspective with the rest of the company.

Marketing

Product Management’s customer focus also informs marketing efforts. Instead of sticking to the brand and using established techniques, product management teams (often including Product Marketing Managers) integrate the language of their customers into the messaging of their product. 

Also, knowledge of the competitive landscape and the ability to stand out and differentiate pays dividends in the long run. Understanding basic marketing and positioning concepts will help product managers ship products that people can find and relate to.

Empathy

Finally, product management is about empathy. You need it for the developers and how they work, customers and their pain points, and even for upper management, who juggle aggressive goals and impossible schedules. 

This skill in empathy, one developed through immersion within and intimate understanding of each group and stakeholder, separates the product teams that can rally the organization around common goals from those who are incapable of doing so.

Key frameworks that drive product management success

Product managers rely on frameworks to bring structure to discovery and delivery. These approaches help teams validate assumptions, prioritize work, and ship faster without sacrificing quality. 

The right framework depends on your team's maturity, product stage, and organizational constraints. Here are some frameworks worth knowing:

• Agile: Builds products through repeated cycles of development and regular input from users and stakeholders. Teams work in short sprints, regularly reassess priorities, and adapt based on what they learn.

• Scrum: A specific implementation of Agile that uses defined roles (Scrum Master, Product Owner), ceremonies (standups, retrospectives), and artifacts (sprint backlogs, burndown charts) to structure work.

• Kanban: Visualizes work as it moves through stages, limiting work in progress to prevent bottlenecks. This framework works well for teams handling continuous streams of work rather than fixed sprints.

Jira Product Discovery supports these frameworks by providing flexible views and workflows that adapt to how your team actually works. Whether you're running Scrum sprints or managing a continuous flow of feature requests, you can configure the tool to match your process rather than forcing your team into rigid templates.

What are potential career paths in product management?

Product management offers multiple career trajectories depending on your interests and strengths. Common paths include:

• Associate Product Manager or Junior PM: Learn the fundamentals while supporting more senior team members.

• Product Manager: Own specific features, products, or problem areas.

• Senior Product Manager or Lead PM: Take on larger product areas and often mentor junior PMs.

• Group Product Manager or Director: Oversee multiple products or product managers.

• VP of Product or Chief Product Officer: Shape product strategy at the organizational level.

• Specialist roles: Focus on areas like product operations, product marketing, growth, strategy, or product management tools that help teams plan, prioritize, and scale their work.

No matter which direction you pursue, advancing your product management career takes intentional effort. Seek opportunities to work with different teams, learn from senior PMs, and take on challenging projects that push your abilities. 

Use product management to drive business growth and innovation

The best product teams create solutions that customers love while hitting business objectives. This happens when product managers deeply understand customer problems, align their work to strategic goals, and collaborate effectively across the organization.

Jira Product Discovery helps teams apply these product management principles by streamlining how you capture ideas, evaluate opportunities, and prioritize what to build next. 

The result is better products, faster decisions, and measurable outcomes that actually move the business forward.