Search the site...

  phil mora
  • The Global Nomad
  • About
  • Portfolio
  • Contact and Book
  • The Training Log
  • The Global Nomad
  • About
  • Portfolio
  • Contact and Book
  • The Training Log


​The Global Nomad
(JAN-APR 22 = currently in the Philadelphia area.)

about

product organization structures part 2

6/6/2020

0 Comments

 
Picture
Part 2: Team Superstructures and alternative organizations
 
Staffing the teams
 
Determining which person goes on which team — can be extremely tricky. If we have teams that stay stable for a longer time, we don’t have to make these decisions very often, but they will impact the team performance for a long time. Conversely, with flexible teams, a lot of staffing decisions will have to be made, but each one won’t matter as much. In other words, with stable teams, your staffing process requires more diligence, and with flexible teams, more speed.
 
Here are few points to consider:
 
  • Team dynamic: to build a high-performing team, it’s important to take into account “soft” factors like existing relationships, personality profiles, working styles, etc., and put together people that you believe will be able to work together effectively.
  • Seniority mix: it’s important to balance seniorities on the team correctly, so that you allow mutual learning, set the team up for success, balance different teams against each other, etc.
  • Diversity: diverse teams perform better, so you should aim to make your product teams as diverse as possible. 
 
 
The role of formal reporting lines
 
While most of the work gets done in cross-functional product teams, there is also the functional element. In many product organizations, the formal reporting line is functional. In other words, engineers report to engineering managers, designers to design manager, and product managers to product directors or similar roles.
 
It’s important to understand that this formal reporting line does not mean that the functional managers engage in a command-and-control style management with their reports —the cross-functional teams are empowered and autonomous, and these teams are at the heart of the product development lifecycle. However, that doesn’t mean there is no role for functional leadership and management. To the contrary: autonomous and empowered teams don’t need less managing:
 
Empowering means creating an environment where people can own outcomes and not just tasks. This doesn’t mean less management; it means better management. It’s important for leaders to step back to create this space, while stepping in to remove impediments, clarify context, and provide guidance.
 
Functional coaching and development
 
Instead of telling their reports what to do, the key responsibility of the functional managers is developing their reports, for example through development plans, feedback, and coaching.
 
This functional aspect complements the natural learning and development that happens in the cross-functional team. Of course, product teams should practice continuous improvement, for example, by conducting regular retrospectives. However, there is a limit to the functional learning that can come from this kind of continuous improvement. For example, a designer is unlikely to “level up” in terms of information architecture or trends in UI design from retrospectives with their engineers and product manager. Coaching from a line manager who’s a more experienced designer is much more effective here.
 
Context and direction
 
The product direction needs to be as cross-functionally aligned as the implementation of it in product teams. In other words, at leadership level, alignment has to happen between the various functions (e.g., product management, engineering, design) before the direction is cascaded down to the product teams.
 
Functional line management still plays a role in the direction-setting though, in highlighting the specific aspects to the function to their reports and providing guidance and coaching on how to make the direction actionable.
 
Organization size and reporting structure
 
In smaller teams, there is also the model of the “player coach”, in which the team is led by one team member who splits their time between individual contributor work and team leadership. These player coaches are sometimes called “lead” (e.g., Design Lead or Engineering Lead) or specifically for product managers, Group Product Manager (GPM).
 
While the player coach model means not having to hire a dedicated manager (who is not “delivering” anything), it can also place a high workload on the player coach, since they are expected to deliver 100% in their product team and then also develop and lead the rest of the team. It might be better to have a dedicated manager who can pick up some small tasks to help out the product teams, but who isn’t part of a product team themselves.


Let me know what you think! 
DM me @philippemora on IG and Twitter
​My name's phil mora and I blog about the things I love: fitness, hacking work, tech and anything holistic. 
​
Head of Digital Product
thinker, doer, designer, coder, leader
0 Comments



Leave a Reply.

    head of product in colorado. travel 🚀 work 🌵 food 🍔 rocky mountains, tech and dogs 🐾

    Picture

    Categories

    All
    Change Agents
    Experiences
    Fitness
    Hacking Work
    Technology

    Archives

    February 2022
    January 2022
    December 2021
    November 2021
    October 2021
    September 2021
    July 2021
    June 2021
    May 2021
    April 2021
    March 2021
    February 2021
    January 2021
    December 2020
    November 2020
    October 2020
    September 2020
    August 2020
    July 2020
    June 2020
    May 2020
    April 2020
    March 2020
    February 2020
    January 2020
    December 2019
    November 2019
    October 2019
    July 2019
    June 2019
    May 2019
    April 2019
    March 2019
    February 2019
    January 2019
    December 2018
    November 2018
    October 2018
    September 2018
    July 2018
    June 2018
    May 2018
    April 2018
    March 2018
    February 2018
    January 2018
    December 2017
    November 2017
    July 2017
    June 2017
    May 2017
    April 2017
    March 2017
    February 2017
    January 2017
    December 2016
    November 2016
    October 2016
    September 2016
    August 2016
    July 2016
    June 2016
    May 2016
    April 2016
    March 2016
    January 2016
    October 2015
    August 2015
    July 2015
    June 2015
    May 2015
    April 2015
    March 2015
    February 2015
    January 2015
    December 2014
    November 2014
    October 2014
    September 2014
    August 2014
    July 2014
    June 2014
    May 2014
    April 2014
    March 2014
    February 2014
    January 2014
    December 2013
    November 2013
    October 2013
    September 2013
    August 2013
    July 2013
    June 2013
    May 2013
    April 2013
    February 2013
    January 2013
    December 2012
    August 2012
    July 2012
    June 2012
    May 2012
    April 2012
    March 2012
    January 2012
    December 2011
    October 2011
    September 2011
    August 2011
    June 2011
    May 2011
    April 2011
    March 2011
    February 2011
    January 2011
    December 2010
    November 2010
    October 2010
    September 2010
    August 2010
    July 2010

    RSS Feed

Phil Mora
​San Francisco .Rennes .Fort Collins .Philadelphia
Phone: (415) 315-9787 . Twitter
@philippemora .  braintrust | polywork | behance

Copyright © 1999-2022 Marshall Tucker by Bold (MT2B) All Rights Reserved