Organization by Value Proposition

If a product has different value propositions, a common structure is to separate product teams by those different value props. For example, at Pinterest, the value props were Discover, Save, and Do, and had different product pillars for each of those value props. This makes it easy to align OKRs or goals to the value you’re trying to provide your users.

If not handled correctly, this structure can lead to an under-investment in important maintenance, scaling, or growth work as the desire is always for new features that aid in delivering this value prop.


The Types of Product Team Organizational Structures - Casey Accidental


A common organization structure is to separate teams based on the type of work they are doing:t

  • the innovation pillar working on new products.
  • the core pillar trying to strengthen the core product with additional features and maintaining the core.
  • the growth pillar trying to grow overall usage of the current product.
  • the platform pillar working on internal features that support other product and engineering teams to allow them to scale.

The organizational structures can be quite stable.


The most important rule of product organizational structures is that they should closely mirror the partner functions. So engineering, product management, and design should tend to have structures that match each other whenever possible.

Product teams tend to work best when aligned with how engineering, design, and other partner functions are structured, so there are 1:1 relationships between leadership roles in those functions.


Companies tend to have strategic initiatives that emerge from annual planning, so a common organizational structure is to align product and engineering around those initiatives. The initiative structure allows PM’s and engineers to flex between innovation, growth, scaling, etc. as needed to support the ultimate outcome for the business. This requires product folks to be more agile in their planning and in the skill sets they are leveraging.

This organizational structure tends to be the least stable because initiatives change frequently or at least on an annual basis.


If a product has different types of customers, a common structure is to separate product teams by the customers they build for:

  • in marketplaces that have supply and demand teams, or
  • In subscription companies that have self-serve and enterprise, or free customers and paid customers.

There can be issues with this model as great products are things that benefit both supply and demand, or free and paid users. It’s hard to build a great product if you only know one side well.


Deepstash helps you become inspired, wiser and productive, through bite-sized ideas from the best articles, books and videos out there.



The model of future work

By 2030, up to 30 to 40 percent of all workers in developed countries may need to move into new occupations or upgrade their skill sets. Skilled workers in short supply will become even scarcer. Any company that doesn't join the early adopters and doesn't address its underlying talent needs may fall short of reaching its goals.



Getting practical about the future of work

We’ve been doubling the amount of people in our product engineering over the past few years, and you just can’t do the same things you used to do.


How to Build Culture in a Remote Team and Scale

  • Stora Enzo, a paper and pulp giant was struggling to run business profitably given the rise of digital media.
  • Leadership was in need of fresh ideas and execution methods.
  • Ideas from conventional pathways of senior leadership groups and selected high performers were drying up.
  • It was then the leadership propsed ato create a unqiue self nominating cross cutting group of people under the pathfinder programme.


How the World’s Oldest Company Reinvented Itself