Beyond Feature-Focused: Rethinking Product Team Organization

Aakash Gupta
2 min readOct 8, 2024

--

You donโ€™t have to organize your product team by product feature.

Itโ€™s a perfectly acceptable method, but itโ€™s not the best fit for every situation.

  1. ๐˜๐˜ต ๐˜ช๐˜จ๐˜ฏ๐˜ฐ๐˜ณ๐˜ฆ๐˜ด ๐˜ต๐˜ฉ๐˜ฆ ๐˜ช๐˜ฎ๐˜ฑ๐˜ฐ๐˜ณ๐˜ต๐˜ข๐˜ฏ๐˜ค๐˜ฆ ๐˜ฐ๐˜ง ๐˜ง๐˜ฆ๐˜ข๐˜ต๐˜ถ๐˜ณ๐˜ฆ ๐˜ท๐˜ด ๐˜ฑ๐˜ณ๐˜ฐ๐˜ฅ๐˜ถ๐˜ค๐˜ต ๐˜ง๐˜ฐ๐˜ค๐˜ถ๐˜ด.
    When you have a PM aligned to a feature, theyโ€™re highly unlikely to suggest killing that feature. It makes the PM devoted to the feature instead of the product as a whole.
  2. ๐˜๐˜ต ๐˜ฐ๐˜ฃ๐˜ด๐˜ค๐˜ถ๐˜ณ๐˜ฆ๐˜ด ๐˜ต๐˜ฉ๐˜ฆ ๐˜ณ๐˜ฐ๐˜ญ๐˜ฆ ๐˜ฐ๐˜ง ๐˜ช๐˜ฎ๐˜ฑ๐˜ข๐˜ค๐˜ต.
    It assumes that the PM who owns a feature will be able to direct their resources to the strategic priorities of the business. The problem is: this very often breaks down. Feature teams have to do the work, and often fail, in mapping the features to outcomes.
  3. ๐˜๐˜ต ๐˜ฅ๐˜ฐ๐˜ฆ๐˜ด๐˜ฏโ€™๐˜ต ๐˜ต๐˜ฐ๐˜ถ๐˜ค๐˜ฉ ๐˜ฐ๐˜ฏ ๐˜ธ๐˜ฉ๐˜ฆ๐˜ต๐˜ฉ๐˜ฆ๐˜ณ ๐˜ฐ๐˜ธ๐˜ฏ๐˜ฆ๐˜ณ๐˜ด๐˜ฉ๐˜ช๐˜ฑ ๐˜ง๐˜ฐ๐˜ณ ๐˜ต๐˜ฉ๐˜ฆ๐˜ด๐˜ฆ ๐˜ง๐˜ฆ๐˜ข๐˜ต๐˜ถ๐˜ณ๐˜ฆ๐˜ด ๐˜ช๐˜ด ๐˜ด๐˜ฐ๐˜ญ๐˜ฆ๐˜ญ๐˜บ ๐˜—๐˜” ๐˜ฐ๐˜ธ๐˜ฏ๐˜ฆ๐˜ฅ ๐˜ฐ๐˜ณ ๐˜ค๐˜ณ๐˜ฐ๐˜ด๐˜ด-๐˜ง๐˜ถ๐˜ฏ๐˜ค๐˜ต๐˜ช๐˜ฐ๐˜ฏ๐˜ข๐˜ญ๐˜ญ๐˜บ ๐˜ฐ๐˜ธ๐˜ฏ๐˜ฆ๐˜ฅ.
    In a PM-owned org, cross-functional leads contribute but arenโ€™t equal owners to the plan. In cross-functionally owned orgs, multiple teams and cross-functional stakeholders contribute.

๐—ฆ๐—ผ ๐˜„๐—ต๐—ฎ๐˜โ€™๐˜€ ๐—ฎ ๐—ฏ๐—ฒ๐˜๐˜๐—ฒ๐—ฟ ๐˜„๐—ฎ๐˜† ๐—ผ๐—ณ ๐˜๐—ต๐—ถ๐—ป๐—ธ๐—ถ๐—ป๐—ด ๐—ฎ๐—ฏ๐—ผ๐˜‚๐˜ ๐˜€๐˜๐—ฟ๐˜‚๐—ฐ๐˜๐˜‚๐—ฟ๐—ถ๐—ป๐—ด ๐˜†๐—ผ๐˜‚๐—ฟ ๐—ฝ๐—ฟ๐—ผ๐—ฑ๐˜‚๐—ฐ๐˜ ๐˜๐—ฒ๐—ฎ๐—บ ๐˜๐—ต๐—ฎ๐˜ ๐—ต๐—ฒ๐—น๐—ฝ๐˜€ ๐—ผ๐˜ƒ๐—ฒ๐—ฟ๐—ฐ๐—ผ๐—บ๐—ฒ ๐˜๐—ต๐—ฒ๐˜€๐—ฒ ๐—ฝ๐—ฟ๐—ผ๐—ฏ๐—น๐—ฒ๐—บ๐˜€?

The go-to framework Iโ€™ve seen is from Ravi Mehta in Reforgeโ€™s Product Leadership course.

In it, he explains that there are two questions to ask:

  1. Are teams focused on features or outcomes?
  2. Do teams own their metrics or share their metrics?

The answers to these questions maps to the type of product org you have.

I consider them the โ€œ2 Dimensions of Product Org Design.โ€

When you answer each, you end up in one of the following 4 categories:

  • ๐—ข๐˜‚๐˜๐—ฐ๐—ผ๐—บ๐—ฒ ๐—ผ๐˜„๐—ป๐—ฒ๐—ฟ: This is when the PM has sole ownership over a metric and is responsible for driving it.
  • ๐—ข๐˜‚๐˜๐—ฐ๐—ผ๐—บ๐—ฒ ๐—ฐ๐—ผ๐—ป๐˜๐—ฟ๐—ถ๐—ฏ๐˜‚๐˜๐—ผ๐—ฟ: This is when the PM is focused on a metric (vs a feature) but does not solely own it.
  • ๐—™๐—ฒ๐—ฎ๐˜๐˜‚๐—ฟ๐—ฒ ๐—ผ๐˜„๐—ป๐—ฒ๐—ฟ: This is when the PM has sole ownership over a feature.
  • ๐—™๐—ฒ๐—ฎ๐˜๐˜‚๐—ฟ๐—ฒ ๐—ฐ๐—ผ๐—ป๐˜๐—ฟ๐—ถ๐—ฏ๐˜‚๐˜๐—ผ๐—ฟ: This is when the PM is focused on a single feature but does not solely own it.

None is โ€œbetterโ€ than the other.

๐—œ๐˜โ€™๐˜€ ๐—ฎ๐—ฏ๐—ผ๐˜‚๐˜ ๐—ณ๐—ถ๐—ป๐—ฑ๐—ถ๐—ป๐—ด ๐˜„๐—ต๐—ฎ๐˜ ๐—ณ๐—ถ๐˜๐˜€ ๐—ฏ๐—ฒ๐˜€๐˜ ๐—ณ๐—ผ๐—ฟ ๐˜†๐—ผ๐˜‚๐—ฟ ๐˜€๐—ถ๐˜๐˜‚๐—ฎ๐˜๐—ถ๐—ผ๐—ป.

P.S. Want more guidance deciding whatโ€™s best for you?

I share a tactical guide in this piece.

--

--

Aakash Gupta

Helping PMs, product leaders, and product aspirants succeed