SlideShare a Scribd company logo
ProductMGT_Org_Pattern



                  Agile Product Management
                  © 2013 Johan Oskarsson
Product management departments
have many different structures. It is
hard to state the best organizational
structure for this function because of
                                         Prod
                                         MGT
the variation in business models,
skills sets and contexts in which
products are sold. However what
should be avoided is a structure
where roles and responsibilities are
too detailed and rigid.
Creating an optimal structure for an                                             Pattern No. 1                          Pattern No. 2
organization is difficult, even impossible.
Why? Perhaps because there is no best way.                                      Specialization                      External-Internal
There are however, better ways for certain
contexts and there are certainly bad ways.
To better describe how to create an
organizational structure, recognizable                                           Pattern No. 3                         Pattern No. 4
patterns can be of use.
                                                                                 Product Area                             Emerging


First of all, what is a pattern? A pattern is a regularity, something
that repeats in a predictable manner. We find patterns                      Product Management Organizational Structure
everywhere, in nature, art, architecture, science, mathematics,                             Patterns
computer science, language, and of course within organizations.
In the organization of Product Management I have observed four
different reoccurring patterns, both in companies that I have had
insight into and in the research I have done.                           So which pattern is the best one? I don’t know, It depends on the
                                                                        context, but there are some pros and cons to each.
These are:
•  Specialization: Structured as a collection of functional             This article focuses on Agile transformation and the recognition of
   departments.                                                         Product Management Organizational Structures.
•  External-Internal: Structured as an external department with
   customer contact and an internal department with R&D                 There are many debates on how to create a structure for Product
   contact                                                              Owners, however it’s always important to first understand how the
•  Product Area: Structured according to product line or areas          business model is set-up (or how it will be in the future), as this plays
   of similar products, with both external and internal contact.        a large role in determining which structure will be most successful.
•  Emerging: No formal structure, everyone helps out to
   perform the activities needed.
Agile development is being implemented
everywhere with great success, but to get all                         “A generalizing specialist does one kind of job very
                                                                      well and some other jobs adequately. With
you can from Agile and Lean you cannot                                generalizing specialists your team enjoys the benefits
stop at the team level. One very important                            of high productivity , while lowering the risk of
                                                                      bottlenecks and retaining flexibility”
area is the management of the product
portfolio. While Agile and Lean offer many
benefits, to best serve and prepare your
projects the strategic work must be adapted                                        - Jurgen Appelo, Management 3.0

to align with both the business plan and with
the development process. Hence Product
Management must also transform. 

Agile is the dream of Product Management, though not everyone    At one point it seamed that the recruitment would never end. The
knows it yet. All the problems arising from unreliable data in   question was now, how to organize themselves? They had all
financial models, unknown and dynamic markets, heavy             jointly discussed the best solutions to the problems they faced and
customer research, big-bang product launches and more, finally   how to staff for them, however because they staffed around
have a development model that is designed to handle the          problems and activities, the department ended up with a very
unknown.                                                         specialized structure. Few people knew how to do the job of the
                                                                 guy right next to them.”
The Story of Captain Trouble
“For those who do not know him yet, the Captain used to be a     With this structure the customer requires multiple channels into the
member of the Product Management team. This was before the       organization in order to communicate their needs effectively. Often,
company grew to the size it is today.                            from the customers point of view, the organization is seen as one
The Product Management department used to be a lot smaller, in   company, while the reality is that it consists of many separate
fact the Captain used be alone. As the products became popular   functions that do not overlap. This is both frustrating for a customer
and more planning, support, features etc, were needed, the       who needs attention, and for the people within the organization.
department doubled multiple times. There are now about 20        This structure is optimized around specific activities not for
people working with Product Management. The Captain hired        generating customer value.
most of them.
The Agile Product Management Framework                                “The way to break the cycle of dysfunction is to stop
is a simple collection of processes which                             listening to each other and start listening to the
                                                                      market.
are more or less useful to a Product                                  […] There is a big difference between listening to the
Manager or Agile Product Owner. It does                               market and listening to the marketing department.”
not include all processes you may need, nor
should you apply all processes it includes.
It’s a framework to which you add or
                                                                                   - Steve Johnson, The strategic role of
remove processes when you judge that to                                            product management


be the best way forward.

The framework is built on a foundation of four cycles Business     .
Strategy, Product Releases, Continuous Sprints, and Daily          This article will not describe the whole framework and all its parts or
Builds. These four cycles manage important inputs, outputs and     how to apply the different processes, but for understanding patterns,
information. These are enablers for agile development.             roles and responsibilities it is useful.
Agile development puts the customer in a central position and
the Agile Product Owner as the guardian of “happily-ever-after”.   Literature so far on Agile, including the definition of the Agile Product
                                                                   Owner, do not usually mention all these processes. It is assumed
I believe what a Product Owner does is the same thing that a       that someone else will do all that. But who? For example the Agile
Product Manager does, at least a successful one. This is not an    Product Owner should create a product backlog, groom it and be
easy job and they need all the help they can get. A Product        the one who has the last say in prioritizing one item over another.
Manager who has a passionate, customer focused, service            But how can he or she do that without insight and knowledge of
minded, extroverted and dedicated development team that            Product Management processes. A product backlog without a vision
understands the market and takes responsibility for making sure    or roadmap tends to be a shortsighted one and does not handle
their products thrive, does not lack much. But most of the time    long-term innovation investment very well. Similarly a teams lacking
this is not the case.                                              an understanding of the business model and Profit & Loss have a
To develop a really committed team you need to be committed        hard time prioritizing.
to enabling them
Agile Product Management Framework (A-PMF ©)
Head of Product
                                                                                                              Management /

No. 1 Specialization Pattern                                                                                 Portfolio Manager




In this pattern the organization is divided                               Marketing Manager       Product Manager         Sales Manager
                                                                                                                                                  Customer Service
                                                                                                                                                      Manager
into very specific roles and responsibilities.
In each role a person is expected to take full                                 Assistant Market       Technical Product      Product Assortment
responsibility for their area, and develop                                        Manager                 Manager              Sales Manager          Technical Support


their skills and knowledge accordingly,
becoming specialists in that area.                                              Brand Manager
                                                                                                         Application
                                                                                                         Specialist
                                                                                                                             Customer Segment
                                                                                                                                 Manager                 Spare Part


There are some “beware” warnings with this pattern. The system is
not very resilient. When someone leaves after many years of                     Communication/           Application             Region Sales
service it leaves a big hole from the loss of explicit knowledge and           Channel Manager           Specialist                Manager           Application Support

an even bigger hole from the loss of tacit knowledge. Tacit
knowledge can take a very long time to rebuild, if it can be restored
at all.                                                                 Here the Agile Product Owner will most likely be the Technical
                                                                        Product Manager or an Application Specialist and will be responsible
The system is error prone. There will be times when something that      for gathering input for the backlog from all other areas.
is not thought of as someone's responsibility will be handled poorly.
Consequently, there is a greater need for written processes and         Another common trap is that other people in their specialized roles
discussions about responsibility.                                       have individual requirements and consider their requirements the
                                                                        most important ones. This not only makes it hard to create a vision
The system is also prone to sub optimization. Since few people          and a roadmap for the products, but also to have balanced portfolio.
have insight into each others work, people will do more of what they
desire rather than what is needed.                                      If the Agile Product Owner is relatively new in the role, the Product
                                                                        Manager needs to help them to organize and prioritize. A tip for this
The system is hard to diagnose. It is not unusual that it requires      structure is to give the Agile Product Owner the responsibilities of
more people since a lot of work effort is lost due to sub               prioritization and developing the roadmap, but require them to
optimization. How the responsibility can be divided between the         consult the individual managers and get their approval. These
different managers and their teams is illustrated in the                managers in return have to help the Agile Product Owner feel
organizational chart.                                                   comfortable and empowered.

                                                                        A lot of time is required to facilitate the workshops needed to get
                                                                        everyone both involved in product development, and understanding
                                                                        the impact of a shared budget.
Roles and responsibilities

Marketing Manager
The Marketing Manger together with the marketing team will be
responsible for external market contact. Their areas of responsibility
might be: Customer Stories, Competitor Stories, Marketing Material,
Product Usage Scenarios, Customer Relations, and Packaging.
The Marketing Management team need to maintain close
collaboration with the other teams to ensure market information is
captured.

Product Manager
A large responsibility falls on the Product Manager who will have to
make sure that everything in between external and internal runs
smoothly. The areas of responsibility can include: facilitating Product   Customer Service Manager
Vision, Merges and Acquisitions, Company Position workshops,              The Customer Service Managers main responsibilities can
Product Lifecycle Strategy, Distribution Channels, Portfolio              include: Product Documentation, Product Training and Product
Alignment, Product Design, Key Partners, Roadmap, Backlog,                Support. The service team usually picks up valuable feedback
Requirement Definition, and System Architecture Alignment.                from the market. It is crucial that the feedback reaches the
                                                                          whole department, including Research & Development.
General Manager
The General Manager will have the overall responsibility that all         Sales Manager
processes are maintained and improved. She also needs to make             The Sales Managers main responsibilities are Product
sure that the Product Management function within the company              Releases and Key Customer Sales Support.
aligns with other departments. Some of the important areas the
General Manager is responsible for include: Budget, Business Model        Note that this is not a formula for responsibility delegation but
Generation, overall Profit & Loss, Work Flow, Pricing, and Decision-      merely a recommendation, specific context must be
Making.                                                                   considered. The framework is just to help sort the areas out.
Agile Product Owner Integration
No. 1
In the Specialization pattern the Chief Product Owner and Product     Depending on the context, specialist skills and the people, there
Owners, form a Product Management team. The team has to               some alternatives for assigning Product Owners to teams.
maintain a shared Master Product Backlog, preferably consisting
of items such as Epics and Features. Each Product Owner can           1.    The Product Owners are generalizing specialists and can
then have a separate Team Product Backlog, consisting of Stories            therefore be assigned to one team and handle everything the
and Tasks which belong to the superior features.                            team will work on.
                                                                      2.    The Product Owners are non-generalizing specialists and
This is needed for at least two reasons.                                    should therefore not be assigned to a team, but to Backlog
                                                                            items.
1.    There is a need to coordinate the “portfolio” of things to be
      done. The Master Product Backlog should reflect the vision      The first alternative is preferable to faster build a functional effective
      and roadmap of the whole Product Management                     team.
      organization, not just the wishes of individual stakeholders.
2.    There is a need to use the Master Product Backlog as a
      collaboration tool between all people involved. Epics and
      Features need to be described in such language that
      everyone easily understands what they mean. The Team
      Product Backlog usually tends to be a bit technical and
      confusing for business people.
Agile Product Owner Integration
No. 1




                                        Sales

                                       CPO


                                                       Customer Service
           Marketing
                                                 PO
                            PO
                                        PO

                                     Product
                                     Management team



               Agile Team                              Agile Team




                                 Agile Team
No. 2 External-Internal Pattern
The External-Internal pattern divides the
Product Management organization into a
customer focused (External) and a product
development (Internal) department.                                                                               Business Manager




                                                                             Marketing Manager                                                          Product Manager




                                        Customer Relations                                       Communication                      Technical Product     Application     Application
                                             Manager         Price Manager   Brand Manager         Manager         Sales Manager        Manager           Specialist      Specialist




 The customer focused department, more commonly known as                            It is important for both teams to understand the business model to
 Marketing Management, handles all communication to customers                       be able to work together despite their different specializations.
 and external parties about the product. The Internal department,                   The areas of responsibilities may be divided. The Agile Product
 more commonly known as Product Management, handles the                             Owner will, in this structure, be under Product Management. Here
 development of the product.                                                        the role can be singular or multiple, divided by products, application
                                                                                    specialization, or just by who fits each role the best.
 In this scenario the Marketing Management is usually the driver of
 strategic decisions, and Product Management the tactical executer.
 This approach can be referred to as the “Voice of the Customer”.

 This pattern can cause a collaboration chasm between
 departments. Important tasks and activities can be missed and trust
 issues may arise.

 Product Management tends to be more technically specialized and
 remote from business and the other way around for Marketing
 Management.
Agile Product Owner Integration
No. 2
The difference in this pattern from the Specialization
pattern is not significant. A Master Product Backlog
backed by Team Product Backlogs is still preferable.

In this pattern there might be a risk of neglecting the                           Marketing Management
technical platform if the organization is too Marketing                           CPO
Management driven.
Another risk is that decision-making can end up solely
with the Marketing Manager and the Chief Product
Owner. When there are fewer interfaces and                                                 PO
interdependencies, there is a risk that important market                PO
                                                                                   PO
information and knowledge is not picked up. This is
unwanted and the Chief Product Owner needs to ensure                            Product
that there are representatives from all areas.                                  Management
                                                                                team


                                                           Agile Team                                    Agile Team




                                                                             Agile Team
No. 3 Product Area Pattern                                                                                            Head of Product
                                                                                                                    Management / Portfolio
                                                                                                                         Manager




In the Product Area Pattern the Product                                    Product Manager              Product Manager               Product Manager               Product Manager

Portfolio has been divided into product
areas where the products share some
similarity.                                                                 Assistant Product Manager    Assistant Product Manager      Assistant Product Manager    Assistant Product Manager




                                                                            Assistant Product Manager    Assistant Product Manager      Assistant Product Manager    Assistant Product Manager




                                                                            Assistant Product Manager    Assistant Product Manager      Assistant Product Manager    Assistant Product Manager




In the Product Area Pattern there is a General Manager (also called             The Assistant Product Manager is a junior role which should
Portfolio Manager) for the whole Product Management function. This              develop the skills needed for Product Management.
person is responsible for the those working under him and for
balancing the portfolio of products.                                            The set of Assistant Product Managers, together with the Product
                                                                                Manager, work together to manage their set of products. They
The portfolio of products has been divided into subcategories where             work as a team to get things done and many responsibilities are
similar products are grouped together. Each subcategory has a                   shared. Roles are usually divided, based more on personal skills,
Product Manager who is responsible for the Product Management                   desires and personality than on any formal structure, to cover all
function of that subcategory, and for the balance of that sub portfolio.        Product Management activities. The Agile Product Owners in this
She is also responsible for the people working under her. Under each            pattern are preferably the Assistant Product Managers.
Product Manager is several Assistant Product Managers who are in
turn responsible for one or more products.
Agile Product Owner Integration
 No. 3
                                                                                                               CPO
In this pattern Product Management for each
area will have a Chief Product Owner. One or                         CPO
more Product Owners are assigned to one or
multiple teams. This pattern can be efficient                                                           PO
but can also become very complex. Teams                                         PO
can become specialized in one market Area
                                                                                                              Area Product
and less flexible/general. There is also a risk                                                               Management
of dependencies between Team Backlogs.
There are some criteria to be considered                     Area Product
                                                             Management                Multiple Area
when using this pattern.
                                                                                       Agile Team
                                                                                                                        Area Agile
1.    The need for multi-project planning and                                                                           Team
      portfolio management is most important
      since each Area Product Management
      team will probably have a separate                            CPO       PO                Area Agile
      budget. The Head of Product                                                               Team
                                                                                                                                     PO
      Management needs to be deeply
      involved in planning to ensure the
      optimal use of the overall budget. Avoid
      fixed Strategic Buckets where a defined
      amount is dedicated to a portfolio of                                                                                               CPO
                                                                       Area Product
      products yearly. A better budget                                 Management
      approach would be dynamic Target                                                                                               Area Product
      Levels for each portfolio but where the                                                                                        Management
      budget can be revised based on
      opportunities.                               3.  The teams have to work at remaining general in order to stay resilient.
2.    The need for a modularized system
      architectural platform is critical to keep   4.  Customer Support issues will have to be shared. Here there is a risk that Areas will try to
      the interdependencies low. Each team             optimize around themselves.
      needs to be able to change with
      minimum effect on other teams                Once these criteria are fulfilled the this pattern can become fast, adaptable, resilient and
      (Conway’s Law).                              competitive.
No. 4 Emerging Pattern
The Emerging pattern is a fully flat and T-
shaped organization where everyone shares
the responsibility of product management. It
is driven by urgency and need, fully resilient                                                       General Product
                                                                                                        Manager

and responsive.
                                                                                                                                     Assistant Product   Assistant Product
                                              Product Manager    Product Manager       Product Manager            Product Manager        Manager             Manager




                                                                                                                                     Assistant Product   Assistant Product
                                               Product Manager   Product Manager        Product Manager            Product Manager
                                                                                                                                         Manager             Manager




                                               Product Manager    Product Manager       Product Manager            Product Manager




In the Emerging Pattern there is a General Manager (also known                      What individuals do is decided based on personality, skills,
as Portfolio Manager) for the whole Product Management function.                    development plans, desires and what needs to be done. The
This person is responsible for the people working under him and                     ultimate goal is to have everyone at the same level of skill and
for the balance of the product portfolio. The rest of the                           knowledge, whereby tasks and activities can be selected based
organization is “flat”, only one manager for the whole department.                  predominantly on personality and desire.

There is however a knowledge hierarchy based on skills and                          The system becomes resilient, prestige-less and optimized for
experience. The Product Manager is more knowledgeable than the                      collaboration and for “what matters”. The only downside is that
Assistant Product Manager. The Product Managers and Assistant                       it takes a lot of investment, training and time to build a
Product Managers work together as one or in multiple teams to                       Emerging organization.
manage all of the products in the portfolio.
                                                                                    The Agile Product Owner could be anyone, joining development
                                                                                    teams as and when needed. There is no predefined integration
                                                                                    of the Agile Product Owner and any organizational design
                                                                                    upfront is unknown. It emerges.
Conclusion
                                                                                     Pattern No. 1                    Pattern No. 2
Regardless of which pattern you choose it can be adapted with Agile
and has both positive and negative aspects.                                         Specialization                 External-Internal

Specialization Pattern
This pattern can hide sub-optimizations, each specialized unit can
become a stakeholder and have their own agendas, making it hard
for the Agile Product Owner to create a “lean” Product Backlog. This                 Pattern No. 3                    Pattern No. 4
pattern also hides dysfunctional behaviors from the over all Product
Management. I would not recommend this pattern as a final one for
an Agile transformation.                                                             Product Area                       Emerging

External-Internal Pattern
With this structure the system can end up with too much of a
                                                                                    Product Management Organizational
marketing department driven approach and be too focused on the
                                                                                             Structure Patterns
short term. The Chief Product Owner needs to be assertive and focus
on the whole, considering both the short-term and long-term. This is
also not a recommended pattern for Agile transformation.
                                                                        Emerging Pattern
Product Area                                                            The Emerging pattern has the problem of figuring out what to do and
This pattern has the classic risk of losing the alignment between       this can seem a bit unstructured and scary. It is. To create this
product lines and over all company strategy. It also runs the risk of   structure requires individuals that are highly skilled and highly general
bypassing commonalities between product lines and missing out on        in all aspects of Product Management. It does not work well with job-
economies of scale when each product line is not aware of what the      hoppers, who move quickly from role to role. It needs dedicated
other product areas are up to.                                          people who are committed to the long term, to learning new skills and
                                                                        to constant development. The key is to let the structure grow and
Once these problems are resolved it is quite compatible with Agile      continuously transform into what it needs to be. Hence the name
transformation, where teams can form around each product area. Co-      Emerging. The Emerging pattern is the optimal fit with Agile
ordination, collaboration and cross-team-planning are the main focus    development. Since the Agile organization is also emerging and
and risk areas.                                                         continuously transforming, it makes perfect sense that its Product
                                                                        Management structure transforms with it.
Johan Oskarsson

@johanoskarsson
                         Inspirational sources
www.captaintrouble.com   Complexity and organizational reality – Ralph Stacey
                         Management 3.0 – Jurgen Appelo
                         Agile Excellence for Product Managers – Greg Cohen
                         Agile Product Management with Scrum – Roman Pinchler
                         The Product Manager’s desk reference – Steven Haines
                         The Strategic Role of Product Management – Steve Johnson




                         Thanks to David Jackson for editing and theoretical dialogues.

More Related Content

What's hot

What's hot (20)

Prioritization Method for Every Case by fmr Atlassian Principal PM
Prioritization Method for Every Case by fmr Atlassian Principal PMPrioritization Method for Every Case by fmr Atlassian Principal PM
Prioritization Method for Every Case by fmr Atlassian Principal PM
 
Product Discovery At Google
Product Discovery At GoogleProduct Discovery At Google
Product Discovery At Google
 
Product Owner vs Product Manager
Product Owner vs Product ManagerProduct Owner vs Product Manager
Product Owner vs Product Manager
 
Product Management framework
Product Management frameworkProduct Management framework
Product Management framework
 
How to Shift to Product-Led Growth
How to Shift to Product-Led GrowthHow to Shift to Product-Led Growth
How to Shift to Product-Led Growth
 
Creating a Product Vision
Creating a Product VisionCreating a Product Vision
Creating a Product Vision
 
Fundamentals of Agile Product Management
Fundamentals of Agile Product ManagementFundamentals of Agile Product Management
Fundamentals of Agile Product Management
 
Product manager
Product managerProduct manager
Product manager
 
How to Build a Robust Product Roadmap by Salesforce VP of Product
How to Build a Robust Product Roadmap by Salesforce VP of ProductHow to Build a Robust Product Roadmap by Salesforce VP of Product
How to Build a Robust Product Roadmap by Salesforce VP of Product
 
Product Manager 101: What Does A Product Manager Actually Do?
Product Manager 101: What Does A Product Manager Actually Do?Product Manager 101: What Does A Product Manager Actually Do?
Product Manager 101: What Does A Product Manager Actually Do?
 
WTF is a Product Roadmap?
WTF is a Product Roadmap?WTF is a Product Roadmap?
WTF is a Product Roadmap?
 
Customer Centric & Hypothesis Driven Innovation by Cruise VP of Product Engin...
Customer Centric & Hypothesis Driven Innovation by Cruise VP of Product Engin...Customer Centric & Hypothesis Driven Innovation by Cruise VP of Product Engin...
Customer Centric & Hypothesis Driven Innovation by Cruise VP of Product Engin...
 
Agile2009 Product Manager - Product Owner Dilemma
Agile2009 Product Manager - Product Owner DilemmaAgile2009 Product Manager - Product Owner Dilemma
Agile2009 Product Manager - Product Owner Dilemma
 
Product Roadmap
Product RoadmapProduct Roadmap
Product Roadmap
 
Feature Prioritization Frameworks by Spotify Sr PM
Feature Prioritization Frameworks by Spotify Sr PMFeature Prioritization Frameworks by Spotify Sr PM
Feature Prioritization Frameworks by Spotify Sr PM
 
What is good product management
What is good product managementWhat is good product management
What is good product management
 
Product roadmap 101
Product roadmap 101Product roadmap 101
Product roadmap 101
 
Breaking Into AI/ML Product Management by Facebook Product Leader
Breaking Into AI/ML Product Management by Facebook Product LeaderBreaking Into AI/ML Product Management by Facebook Product Leader
Breaking Into AI/ML Product Management by Facebook Product Leader
 
Product Owner & Product Manager Training
Product Owner & Product Manager TrainingProduct Owner & Product Manager Training
Product Owner & Product Manager Training
 
Customer Centricity and Product Led Growth by Airbnb Product & Growth
Customer Centricity and Product Led Growth by Airbnb Product & Growth Customer Centricity and Product Led Growth by Airbnb Product & Growth
Customer Centricity and Product Led Growth by Airbnb Product & Growth
 

Viewers also liked

Intro to Product Management - Launch48 Pre-Accelerator Week
Intro to Product Management - Launch48 Pre-Accelerator WeekIntro to Product Management - Launch48 Pre-Accelerator Week
Intro to Product Management - Launch48 Pre-Accelerator Week
Janna Bastow
 

Viewers also liked (20)

Finding Product Market Fit
Finding Product Market FitFinding Product Market Fit
Finding Product Market Fit
 
What is Product Management?
What is Product Management?What is Product Management?
What is Product Management?
 
The experience is the product (for Mind The Product 2016)
The experience is the product (for Mind The Product 2016)The experience is the product (for Mind The Product 2016)
The experience is the product (for Mind The Product 2016)
 
Nathalie Nahai - Naughty or nice? The psychology behind successful products
Nathalie Nahai  - Naughty or nice? The psychology behind successful productsNathalie Nahai  - Naughty or nice? The psychology behind successful products
Nathalie Nahai - Naughty or nice? The psychology behind successful products
 
10 Tips on how to be an Awesome Product Manager
10 Tips on how to be an Awesome Product Manager10 Tips on how to be an Awesome Product Manager
10 Tips on how to be an Awesome Product Manager
 
Agile205: Intro to Agile Product Management
Agile205: Intro to Agile Product ManagementAgile205: Intro to Agile Product Management
Agile205: Intro to Agile Product Management
 
MIT Class on Product Management 10-22-2013
MIT Class on Product Management 10-22-2013MIT Class on Product Management 10-22-2013
MIT Class on Product Management 10-22-2013
 
How to Use Your Product Roadmap as a Communication Tool
How to Use Your Product Roadmap as a Communication ToolHow to Use Your Product Roadmap as a Communication Tool
How to Use Your Product Roadmap as a Communication Tool
 
Intro to Product Management - Launch48 Pre-Accelerator Week
Intro to Product Management - Launch48 Pre-Accelerator WeekIntro to Product Management - Launch48 Pre-Accelerator Week
Intro to Product Management - Launch48 Pre-Accelerator Week
 
The Double Diamond Model of Product Definition and Execution
The Double Diamond Model of Product Definition and ExecutionThe Double Diamond Model of Product Definition and Execution
The Double Diamond Model of Product Definition and Execution
 
New is Easy but Right is Hard: Hacking Product Management
New is Easy but Right is Hard: Hacking Product ManagementNew is Easy but Right is Hard: Hacking Product Management
New is Easy but Right is Hard: Hacking Product Management
 
User Experience and Product Management: Two Peas in the Same Pod?
User Experience and Product Management: Two Peas in the Same Pod?User Experience and Product Management: Two Peas in the Same Pod?
User Experience and Product Management: Two Peas in the Same Pod?
 
Product Strategy
Product StrategyProduct Strategy
Product Strategy
 
Lean Product Management for Enterprises: The Art of Known Unknowns
Lean Product Management for Enterprises: The Art of Known Unknowns Lean Product Management for Enterprises: The Art of Known Unknowns
Lean Product Management for Enterprises: The Art of Known Unknowns
 
Product Management by Numbers: Using Metrics To Optimize Your Product by Dan ...
Product Management by Numbers: Using Metrics To Optimize Your Product by Dan ...Product Management by Numbers: Using Metrics To Optimize Your Product by Dan ...
Product Management by Numbers: Using Metrics To Optimize Your Product by Dan ...
 
Finding Product / Market Fit: Introducing the PMF Matrix - Presentation by Ri...
Finding Product / Market Fit: Introducing the PMF Matrix - Presentation by Ri...Finding Product / Market Fit: Introducing the PMF Matrix - Presentation by Ri...
Finding Product / Market Fit: Introducing the PMF Matrix - Presentation by Ri...
 
Product Management 101 for Startups
Product Management 101 for StartupsProduct Management 101 for Startups
Product Management 101 for Startups
 
A Playbook for Achieving Product-Market Fit by Dan Olsen at Lean Startup Conf...
A Playbook for Achieving Product-Market Fit by Dan Olsen at Lean Startup Conf...A Playbook for Achieving Product-Market Fit by Dan Olsen at Lean Startup Conf...
A Playbook for Achieving Product-Market Fit by Dan Olsen at Lean Startup Conf...
 
What Is Product Management?
What Is Product Management?What Is Product Management?
What Is Product Management?
 
Lean Product Management - ACE 2015
Lean Product Management - ACE 2015Lean Product Management - ACE 2015
Lean Product Management - ACE 2015
 

Similar to Product management organization structure patterns v1.02

UX Poland 2014: Y.Vetrov — Applied UX Strategy
UX Poland 2014: Y.Vetrov — Applied UX StrategyUX Poland 2014: Y.Vetrov — Applied UX Strategy
UX Poland 2014: Y.Vetrov — Applied UX Strategy
Yury Vetrov
 

Similar to Product management organization structure patterns v1.02 (20)

Inspired
InspiredInspired
Inspired
 
Career guide for product managers
Career guide for product managersCareer guide for product managers
Career guide for product managers
 
Course report on becoming a product manager
Course report on becoming a product managerCourse report on becoming a product manager
Course report on becoming a product manager
 
Business Analysis book
Business Analysis bookBusiness Analysis book
Business Analysis book
 
PM defination and details.pdf
PM defination and details.pdfPM defination and details.pdf
PM defination and details.pdf
 
patrick armstrong augusta
patrick armstrong augustapatrick armstrong augusta
patrick armstrong augusta
 
HOLTON BUGGS
HOLTON BUGGSHOLTON BUGGS
HOLTON BUGGS
 
Surviving Product Management
Surviving Product Management Surviving Product Management
Surviving Product Management
 
UX Poland 2014: Y.Vetrov — Applied UX Strategy
UX Poland 2014: Y.Vetrov — Applied UX StrategyUX Poland 2014: Y.Vetrov — Applied UX Strategy
UX Poland 2014: Y.Vetrov — Applied UX Strategy
 
Mission-Critical-How-to-Prioritize-Features-with-the-Right-Framework.pptx
Mission-Critical-How-to-Prioritize-Features-with-the-Right-Framework.pptxMission-Critical-How-to-Prioritize-Features-with-the-Right-Framework.pptx
Mission-Critical-How-to-Prioritize-Features-with-the-Right-Framework.pptx
 
GumGum PM on Intro to Product Management
GumGum PM on Intro to Product ManagementGumGum PM on Intro to Product Management
GumGum PM on Intro to Product Management
 
Agile Prod Mgmt v. Proj Mgmt
Agile Prod Mgmt v. Proj MgmtAgile Prod Mgmt v. Proj Mgmt
Agile Prod Mgmt v. Proj Mgmt
 
Top 50 Product Owner Interview Question and Answers | Edureka
Top 50 Product Owner Interview Question and Answers | EdurekaTop 50 Product Owner Interview Question and Answers | Edureka
Top 50 Product Owner Interview Question and Answers | Edureka
 
Agile Software Development - Session 1
Agile Software Development - Session 1Agile Software Development - Session 1
Agile Software Development - Session 1
 
productmanager
productmanagerproductmanager
productmanager
 
Building and Scaling a Product Team
 Building and Scaling a Product Team Building and Scaling a Product Team
Building and Scaling a Product Team
 
Agility At Scale
Agility At ScaleAgility At Scale
Agility At Scale
 
8 stances of a Product Owner
8 stances of a Product Owner8 stances of a Product Owner
8 stances of a Product Owner
 
Adaptive Advanced Product Mgmt & Marketing Workshop
Adaptive Advanced Product Mgmt & Marketing WorkshopAdaptive Advanced Product Mgmt & Marketing Workshop
Adaptive Advanced Product Mgmt & Marketing Workshop
 
[en] Agile transformation - How to deconstruct your organization step by step
[en] Agile transformation - How to deconstruct your organization step by step[en] Agile transformation - How to deconstruct your organization step by step
[en] Agile transformation - How to deconstruct your organization step by step
 

More from Johan Oskarsson (8)

A3 inter team planning performance for Agile Business Teams
A3 inter team planning performance for Agile Business TeamsA3 inter team planning performance for Agile Business Teams
A3 inter team planning performance for Agile Business Teams
 
The business team organization v1.00
The business team organization v1.00The business team organization v1.00
The business team organization v1.00
 
The strategy wall v1.01
The strategy wall v1.01The strategy wall v1.01
The strategy wall v1.01
 
Agile budget v1.01
Agile budget v1.01Agile budget v1.01
Agile budget v1.01
 
Project portfolio anatomy v1.03
Project portfolio anatomy v1.03Project portfolio anatomy v1.03
Project portfolio anatomy v1.03
 
Decision making poker v1.01
Decision making poker v1.01Decision making poker v1.01
Decision making poker v1.01
 
Agile portfolio management decision-making
Agile portfolio management decision-makingAgile portfolio management decision-making
Agile portfolio management decision-making
 
Management 3.0 applied at lean experience
Management 3.0 applied at lean experienceManagement 3.0 applied at lean experience
Management 3.0 applied at lean experience
 

Recently uploaded

Constitution of Company Article of Association
Constitution of Company Article of AssociationConstitution of Company Article of Association
Constitution of Company Article of Association
seri bangash
 

Recently uploaded (20)

Engagement Rings vs Promise Rings | Detailed Guide
Engagement Rings vs Promise Rings | Detailed GuideEngagement Rings vs Promise Rings | Detailed Guide
Engagement Rings vs Promise Rings | Detailed Guide
 
FEXLE- Salesforce Field Service Lightning
FEXLE- Salesforce Field Service LightningFEXLE- Salesforce Field Service Lightning
FEXLE- Salesforce Field Service Lightning
 
The Ultimate Guide to IPTV App Development Process_ Step-By-Step Instructions
The Ultimate Guide to IPTV App Development Process_ Step-By-Step InstructionsThe Ultimate Guide to IPTV App Development Process_ Step-By-Step Instructions
The Ultimate Guide to IPTV App Development Process_ Step-By-Step Instructions
 
Unveiling the Dynamic Gemini_ Personality Traits and Sign Dates.pptx
Unveiling the Dynamic Gemini_ Personality Traits and Sign Dates.pptxUnveiling the Dynamic Gemini_ Personality Traits and Sign Dates.pptx
Unveiling the Dynamic Gemini_ Personality Traits and Sign Dates.pptx
 
How to Maintain Healthy Life style.pptx
How to Maintain  Healthy Life style.pptxHow to Maintain  Healthy Life style.pptx
How to Maintain Healthy Life style.pptx
 
Potato Flakes Manufacturing Plant Project Report.pdf
Potato Flakes Manufacturing Plant Project Report.pdfPotato Flakes Manufacturing Plant Project Report.pdf
Potato Flakes Manufacturing Plant Project Report.pdf
 
The Truth About Dinesh Bafna's Situation.pdf
The Truth About Dinesh Bafna's Situation.pdfThe Truth About Dinesh Bafna's Situation.pdf
The Truth About Dinesh Bafna's Situation.pdf
 
Revolutionizing Industries: The Power of Carbon Components
Revolutionizing Industries: The Power of Carbon ComponentsRevolutionizing Industries: The Power of Carbon Components
Revolutionizing Industries: The Power of Carbon Components
 
Using Generative AI for Content Marketing
Using Generative AI for Content MarketingUsing Generative AI for Content Marketing
Using Generative AI for Content Marketing
 
HR and Employment law update: May 2024.
HR and Employment law update:  May 2024.HR and Employment law update:  May 2024.
HR and Employment law update: May 2024.
 
Global Interconnection Group Joint Venture[960] (1).pdf
Global Interconnection Group Joint Venture[960] (1).pdfGlobal Interconnection Group Joint Venture[960] (1).pdf
Global Interconnection Group Joint Venture[960] (1).pdf
 
India’s Recommended Women Surgeons to Watch in 2024.pdf
India’s Recommended Women Surgeons to Watch in 2024.pdfIndia’s Recommended Women Surgeons to Watch in 2024.pdf
India’s Recommended Women Surgeons to Watch in 2024.pdf
 
Equinox Gold Corporate Deck May 24th 2024
Equinox Gold Corporate Deck May 24th 2024Equinox Gold Corporate Deck May 24th 2024
Equinox Gold Corporate Deck May 24th 2024
 
Unlock Your TikTok Potential: Free TikTok Likes with InstBlast
Unlock Your TikTok Potential: Free TikTok Likes with InstBlastUnlock Your TikTok Potential: Free TikTok Likes with InstBlast
Unlock Your TikTok Potential: Free TikTok Likes with InstBlast
 
Raising Seed Capital by Steve Schlafman at RRE Ventures
Raising Seed Capital by Steve Schlafman at RRE VenturesRaising Seed Capital by Steve Schlafman at RRE Ventures
Raising Seed Capital by Steve Schlafman at RRE Ventures
 
Constitution of Company Article of Association
Constitution of Company Article of AssociationConstitution of Company Article of Association
Constitution of Company Article of Association
 
8 Questions B2B Commercial Teams Can Ask To Help Product Discovery
8 Questions B2B Commercial Teams Can Ask To Help Product Discovery8 Questions B2B Commercial Teams Can Ask To Help Product Discovery
8 Questions B2B Commercial Teams Can Ask To Help Product Discovery
 
Cracking the Change Management Code Main New.pptx
Cracking the Change Management Code Main New.pptxCracking the Change Management Code Main New.pptx
Cracking the Change Management Code Main New.pptx
 
A Brief Introduction About Jacob Badgett
A Brief Introduction About Jacob BadgettA Brief Introduction About Jacob Badgett
A Brief Introduction About Jacob Badgett
 
Pitch Deck Teardown: Terra One's $7.5m Seed deck
Pitch Deck Teardown: Terra One's $7.5m Seed deckPitch Deck Teardown: Terra One's $7.5m Seed deck
Pitch Deck Teardown: Terra One's $7.5m Seed deck
 

Product management organization structure patterns v1.02

  • 1. ProductMGT_Org_Pattern Agile Product Management © 2013 Johan Oskarsson
  • 2. Product management departments have many different structures. It is hard to state the best organizational structure for this function because of Prod MGT the variation in business models, skills sets and contexts in which products are sold. However what should be avoided is a structure where roles and responsibilities are too detailed and rigid.
  • 3. Creating an optimal structure for an Pattern No. 1 Pattern No. 2 organization is difficult, even impossible. Why? Perhaps because there is no best way. Specialization External-Internal There are however, better ways for certain contexts and there are certainly bad ways. To better describe how to create an organizational structure, recognizable Pattern No. 3 Pattern No. 4 patterns can be of use. Product Area Emerging First of all, what is a pattern? A pattern is a regularity, something that repeats in a predictable manner. We find patterns Product Management Organizational Structure everywhere, in nature, art, architecture, science, mathematics, Patterns computer science, language, and of course within organizations. In the organization of Product Management I have observed four different reoccurring patterns, both in companies that I have had insight into and in the research I have done. So which pattern is the best one? I don’t know, It depends on the context, but there are some pros and cons to each. These are: •  Specialization: Structured as a collection of functional This article focuses on Agile transformation and the recognition of departments. Product Management Organizational Structures. •  External-Internal: Structured as an external department with customer contact and an internal department with R&D There are many debates on how to create a structure for Product contact Owners, however it’s always important to first understand how the •  Product Area: Structured according to product line or areas business model is set-up (or how it will be in the future), as this plays of similar products, with both external and internal contact. a large role in determining which structure will be most successful. •  Emerging: No formal structure, everyone helps out to perform the activities needed.
  • 4. Agile development is being implemented everywhere with great success, but to get all “A generalizing specialist does one kind of job very well and some other jobs adequately. With you can from Agile and Lean you cannot generalizing specialists your team enjoys the benefits stop at the team level. One very important of high productivity , while lowering the risk of bottlenecks and retaining flexibility” area is the management of the product portfolio. While Agile and Lean offer many benefits, to best serve and prepare your projects the strategic work must be adapted - Jurgen Appelo, Management 3.0 to align with both the business plan and with the development process. Hence Product Management must also transform.  Agile is the dream of Product Management, though not everyone At one point it seamed that the recruitment would never end. The knows it yet. All the problems arising from unreliable data in question was now, how to organize themselves? They had all financial models, unknown and dynamic markets, heavy jointly discussed the best solutions to the problems they faced and customer research, big-bang product launches and more, finally how to staff for them, however because they staffed around have a development model that is designed to handle the problems and activities, the department ended up with a very unknown. specialized structure. Few people knew how to do the job of the guy right next to them.” The Story of Captain Trouble “For those who do not know him yet, the Captain used to be a With this structure the customer requires multiple channels into the member of the Product Management team. This was before the organization in order to communicate their needs effectively. Often, company grew to the size it is today. from the customers point of view, the organization is seen as one The Product Management department used to be a lot smaller, in company, while the reality is that it consists of many separate fact the Captain used be alone. As the products became popular functions that do not overlap. This is both frustrating for a customer and more planning, support, features etc, were needed, the who needs attention, and for the people within the organization. department doubled multiple times. There are now about 20 This structure is optimized around specific activities not for people working with Product Management. The Captain hired generating customer value. most of them.
  • 5. The Agile Product Management Framework “The way to break the cycle of dysfunction is to stop is a simple collection of processes which listening to each other and start listening to the market. are more or less useful to a Product […] There is a big difference between listening to the Manager or Agile Product Owner. It does market and listening to the marketing department.” not include all processes you may need, nor should you apply all processes it includes. It’s a framework to which you add or - Steve Johnson, The strategic role of remove processes when you judge that to product management be the best way forward. The framework is built on a foundation of four cycles Business . Strategy, Product Releases, Continuous Sprints, and Daily This article will not describe the whole framework and all its parts or Builds. These four cycles manage important inputs, outputs and how to apply the different processes, but for understanding patterns, information. These are enablers for agile development. roles and responsibilities it is useful. Agile development puts the customer in a central position and the Agile Product Owner as the guardian of “happily-ever-after”. Literature so far on Agile, including the definition of the Agile Product Owner, do not usually mention all these processes. It is assumed I believe what a Product Owner does is the same thing that a that someone else will do all that. But who? For example the Agile Product Manager does, at least a successful one. This is not an Product Owner should create a product backlog, groom it and be easy job and they need all the help they can get. A Product the one who has the last say in prioritizing one item over another. Manager who has a passionate, customer focused, service But how can he or she do that without insight and knowledge of minded, extroverted and dedicated development team that Product Management processes. A product backlog without a vision understands the market and takes responsibility for making sure or roadmap tends to be a shortsighted one and does not handle their products thrive, does not lack much. But most of the time long-term innovation investment very well. Similarly a teams lacking this is not the case. an understanding of the business model and Profit & Loss have a To develop a really committed team you need to be committed hard time prioritizing. to enabling them
  • 6. Agile Product Management Framework (A-PMF ©)
  • 7. Head of Product Management / No. 1 Specialization Pattern Portfolio Manager In this pattern the organization is divided Marketing Manager Product Manager Sales Manager Customer Service Manager into very specific roles and responsibilities. In each role a person is expected to take full Assistant Market Technical Product Product Assortment responsibility for their area, and develop Manager Manager Sales Manager Technical Support their skills and knowledge accordingly, becoming specialists in that area. Brand Manager Application Specialist Customer Segment Manager Spare Part There are some “beware” warnings with this pattern. The system is not very resilient. When someone leaves after many years of Communication/ Application Region Sales service it leaves a big hole from the loss of explicit knowledge and Channel Manager Specialist Manager Application Support an even bigger hole from the loss of tacit knowledge. Tacit knowledge can take a very long time to rebuild, if it can be restored at all. Here the Agile Product Owner will most likely be the Technical Product Manager or an Application Specialist and will be responsible The system is error prone. There will be times when something that for gathering input for the backlog from all other areas. is not thought of as someone's responsibility will be handled poorly. Consequently, there is a greater need for written processes and Another common trap is that other people in their specialized roles discussions about responsibility. have individual requirements and consider their requirements the most important ones. This not only makes it hard to create a vision The system is also prone to sub optimization. Since few people and a roadmap for the products, but also to have balanced portfolio. have insight into each others work, people will do more of what they desire rather than what is needed. If the Agile Product Owner is relatively new in the role, the Product Manager needs to help them to organize and prioritize. A tip for this The system is hard to diagnose. It is not unusual that it requires structure is to give the Agile Product Owner the responsibilities of more people since a lot of work effort is lost due to sub prioritization and developing the roadmap, but require them to optimization. How the responsibility can be divided between the consult the individual managers and get their approval. These different managers and their teams is illustrated in the managers in return have to help the Agile Product Owner feel organizational chart. comfortable and empowered. A lot of time is required to facilitate the workshops needed to get everyone both involved in product development, and understanding the impact of a shared budget.
  • 8. Roles and responsibilities Marketing Manager The Marketing Manger together with the marketing team will be responsible for external market contact. Their areas of responsibility might be: Customer Stories, Competitor Stories, Marketing Material, Product Usage Scenarios, Customer Relations, and Packaging. The Marketing Management team need to maintain close collaboration with the other teams to ensure market information is captured. Product Manager A large responsibility falls on the Product Manager who will have to make sure that everything in between external and internal runs smoothly. The areas of responsibility can include: facilitating Product Customer Service Manager Vision, Merges and Acquisitions, Company Position workshops, The Customer Service Managers main responsibilities can Product Lifecycle Strategy, Distribution Channels, Portfolio include: Product Documentation, Product Training and Product Alignment, Product Design, Key Partners, Roadmap, Backlog, Support. The service team usually picks up valuable feedback Requirement Definition, and System Architecture Alignment. from the market. It is crucial that the feedback reaches the whole department, including Research & Development. General Manager The General Manager will have the overall responsibility that all Sales Manager processes are maintained and improved. She also needs to make The Sales Managers main responsibilities are Product sure that the Product Management function within the company Releases and Key Customer Sales Support. aligns with other departments. Some of the important areas the General Manager is responsible for include: Budget, Business Model Note that this is not a formula for responsibility delegation but Generation, overall Profit & Loss, Work Flow, Pricing, and Decision- merely a recommendation, specific context must be Making. considered. The framework is just to help sort the areas out.
  • 9. Agile Product Owner Integration No. 1 In the Specialization pattern the Chief Product Owner and Product Depending on the context, specialist skills and the people, there Owners, form a Product Management team. The team has to some alternatives for assigning Product Owners to teams. maintain a shared Master Product Backlog, preferably consisting of items such as Epics and Features. Each Product Owner can 1.  The Product Owners are generalizing specialists and can then have a separate Team Product Backlog, consisting of Stories therefore be assigned to one team and handle everything the and Tasks which belong to the superior features. team will work on. 2.  The Product Owners are non-generalizing specialists and This is needed for at least two reasons. should therefore not be assigned to a team, but to Backlog items. 1.  There is a need to coordinate the “portfolio” of things to be done. The Master Product Backlog should reflect the vision The first alternative is preferable to faster build a functional effective and roadmap of the whole Product Management team. organization, not just the wishes of individual stakeholders. 2.  There is a need to use the Master Product Backlog as a collaboration tool between all people involved. Epics and Features need to be described in such language that everyone easily understands what they mean. The Team Product Backlog usually tends to be a bit technical and confusing for business people.
  • 10. Agile Product Owner Integration No. 1 Sales CPO Customer Service Marketing PO PO PO Product Management team Agile Team Agile Team Agile Team
  • 11. No. 2 External-Internal Pattern The External-Internal pattern divides the Product Management organization into a customer focused (External) and a product development (Internal) department. Business Manager Marketing Manager Product Manager Customer Relations Communication Technical Product Application Application Manager Price Manager Brand Manager Manager Sales Manager Manager Specialist Specialist The customer focused department, more commonly known as It is important for both teams to understand the business model to Marketing Management, handles all communication to customers be able to work together despite their different specializations. and external parties about the product. The Internal department, The areas of responsibilities may be divided. The Agile Product more commonly known as Product Management, handles the Owner will, in this structure, be under Product Management. Here development of the product. the role can be singular or multiple, divided by products, application specialization, or just by who fits each role the best. In this scenario the Marketing Management is usually the driver of strategic decisions, and Product Management the tactical executer. This approach can be referred to as the “Voice of the Customer”. This pattern can cause a collaboration chasm between departments. Important tasks and activities can be missed and trust issues may arise. Product Management tends to be more technically specialized and remote from business and the other way around for Marketing Management.
  • 12. Agile Product Owner Integration No. 2 The difference in this pattern from the Specialization pattern is not significant. A Master Product Backlog backed by Team Product Backlogs is still preferable. In this pattern there might be a risk of neglecting the Marketing Management technical platform if the organization is too Marketing CPO Management driven. Another risk is that decision-making can end up solely with the Marketing Manager and the Chief Product Owner. When there are fewer interfaces and PO interdependencies, there is a risk that important market PO PO information and knowledge is not picked up. This is unwanted and the Chief Product Owner needs to ensure Product that there are representatives from all areas. Management team Agile Team Agile Team Agile Team
  • 13. No. 3 Product Area Pattern Head of Product Management / Portfolio Manager In the Product Area Pattern the Product Product Manager Product Manager Product Manager Product Manager Portfolio has been divided into product areas where the products share some similarity. Assistant Product Manager Assistant Product Manager Assistant Product Manager Assistant Product Manager Assistant Product Manager Assistant Product Manager Assistant Product Manager Assistant Product Manager Assistant Product Manager Assistant Product Manager Assistant Product Manager Assistant Product Manager In the Product Area Pattern there is a General Manager (also called The Assistant Product Manager is a junior role which should Portfolio Manager) for the whole Product Management function. This develop the skills needed for Product Management. person is responsible for the those working under him and for balancing the portfolio of products. The set of Assistant Product Managers, together with the Product Manager, work together to manage their set of products. They The portfolio of products has been divided into subcategories where work as a team to get things done and many responsibilities are similar products are grouped together. Each subcategory has a shared. Roles are usually divided, based more on personal skills, Product Manager who is responsible for the Product Management desires and personality than on any formal structure, to cover all function of that subcategory, and for the balance of that sub portfolio. Product Management activities. The Agile Product Owners in this She is also responsible for the people working under her. Under each pattern are preferably the Assistant Product Managers. Product Manager is several Assistant Product Managers who are in turn responsible for one or more products.
  • 14. Agile Product Owner Integration No. 3 CPO In this pattern Product Management for each area will have a Chief Product Owner. One or CPO more Product Owners are assigned to one or multiple teams. This pattern can be efficient PO but can also become very complex. Teams PO can become specialized in one market Area Area Product and less flexible/general. There is also a risk Management of dependencies between Team Backlogs. There are some criteria to be considered Area Product Management Multiple Area when using this pattern. Agile Team Area Agile 1.  The need for multi-project planning and Team portfolio management is most important since each Area Product Management team will probably have a separate CPO PO Area Agile budget. The Head of Product Team PO Management needs to be deeply involved in planning to ensure the optimal use of the overall budget. Avoid fixed Strategic Buckets where a defined amount is dedicated to a portfolio of CPO Area Product products yearly. A better budget Management approach would be dynamic Target Area Product Levels for each portfolio but where the Management budget can be revised based on opportunities. 3.  The teams have to work at remaining general in order to stay resilient. 2.  The need for a modularized system architectural platform is critical to keep 4.  Customer Support issues will have to be shared. Here there is a risk that Areas will try to the interdependencies low. Each team optimize around themselves. needs to be able to change with minimum effect on other teams Once these criteria are fulfilled the this pattern can become fast, adaptable, resilient and (Conway’s Law). competitive.
  • 15. No. 4 Emerging Pattern The Emerging pattern is a fully flat and T- shaped organization where everyone shares the responsibility of product management. It is driven by urgency and need, fully resilient General Product Manager and responsive. Assistant Product Assistant Product Product Manager Product Manager Product Manager Product Manager Manager Manager Assistant Product Assistant Product Product Manager Product Manager Product Manager Product Manager Manager Manager Product Manager Product Manager Product Manager Product Manager In the Emerging Pattern there is a General Manager (also known What individuals do is decided based on personality, skills, as Portfolio Manager) for the whole Product Management function. development plans, desires and what needs to be done. The This person is responsible for the people working under him and ultimate goal is to have everyone at the same level of skill and for the balance of the product portfolio. The rest of the knowledge, whereby tasks and activities can be selected based organization is “flat”, only one manager for the whole department. predominantly on personality and desire. There is however a knowledge hierarchy based on skills and The system becomes resilient, prestige-less and optimized for experience. The Product Manager is more knowledgeable than the collaboration and for “what matters”. The only downside is that Assistant Product Manager. The Product Managers and Assistant it takes a lot of investment, training and time to build a Product Managers work together as one or in multiple teams to Emerging organization. manage all of the products in the portfolio. The Agile Product Owner could be anyone, joining development teams as and when needed. There is no predefined integration of the Agile Product Owner and any organizational design upfront is unknown. It emerges.
  • 16. Conclusion Pattern No. 1 Pattern No. 2 Regardless of which pattern you choose it can be adapted with Agile and has both positive and negative aspects. Specialization External-Internal Specialization Pattern This pattern can hide sub-optimizations, each specialized unit can become a stakeholder and have their own agendas, making it hard for the Agile Product Owner to create a “lean” Product Backlog. This Pattern No. 3 Pattern No. 4 pattern also hides dysfunctional behaviors from the over all Product Management. I would not recommend this pattern as a final one for an Agile transformation. Product Area Emerging External-Internal Pattern With this structure the system can end up with too much of a Product Management Organizational marketing department driven approach and be too focused on the Structure Patterns short term. The Chief Product Owner needs to be assertive and focus on the whole, considering both the short-term and long-term. This is also not a recommended pattern for Agile transformation. Emerging Pattern Product Area The Emerging pattern has the problem of figuring out what to do and This pattern has the classic risk of losing the alignment between this can seem a bit unstructured and scary. It is. To create this product lines and over all company strategy. It also runs the risk of structure requires individuals that are highly skilled and highly general bypassing commonalities between product lines and missing out on in all aspects of Product Management. It does not work well with job- economies of scale when each product line is not aware of what the hoppers, who move quickly from role to role. It needs dedicated other product areas are up to. people who are committed to the long term, to learning new skills and to constant development. The key is to let the structure grow and Once these problems are resolved it is quite compatible with Agile continuously transform into what it needs to be. Hence the name transformation, where teams can form around each product area. Co- Emerging. The Emerging pattern is the optimal fit with Agile ordination, collaboration and cross-team-planning are the main focus development. Since the Agile organization is also emerging and and risk areas. continuously transforming, it makes perfect sense that its Product Management structure transforms with it.
  • 17. Johan Oskarsson @johanoskarsson Inspirational sources www.captaintrouble.com Complexity and organizational reality – Ralph Stacey Management 3.0 – Jurgen Appelo Agile Excellence for Product Managers – Greg Cohen Agile Product Management with Scrum – Roman Pinchler The Product Manager’s desk reference – Steven Haines The Strategic Role of Product Management – Steve Johnson Thanks to David Jackson for editing and theoretical dialogues.