Why it’s difficult to build teams in high growth organisations

Two reasons why building teams in high growth is difficult: can’t assume stable teams, can’t rely on cultural osmosis.

In high growth, the odds are the teams won’t be stable

Sink or Swim; Split and Absorb; Absorb and Split
  1. Sink or Swim. Keep the older teams as-is and add the new people to brand new teams. This keeps teams stable and likely ensures that all new teams will struggle;
  2. Split and Absorb. Split up the older teams (aka not stable) and absorb new people in the new teams. This means there’s a mix of veterans and newbies;
  3. Absorb and Split. Add new people to existing teams. This will eventually lead to the teams becoming too large (aka not stable) and splitting (also not stable).

The default culture is not what pre-exists

Newbies outnumber veterans in high growth

How not to deal with high growth: presumptive team splitting

Premature split → Unclear mission, missing skills → Fill time with low-value work → Boredom → Disengagement, quitting

How to deal with high growth: structure follows strategy, organic org design, deliberate culture

Structure should be stable where strategy is stable; structure should be flexible where strategy is volatile

Absorb and Split

  1. Add new people to existing teams.
  2. Let the seams appear naturally, that is, watch the communication flow and interaction patterns, especially the dynamics of meetings. Eventually, you’ll notice sub-groups appearing and certain rituals getting clunkier;
  3. Start nudging things closer, that is, separate rhythms (aka cadences) and events;
  4. And eventually formalise the split. By this time, it’s mostly just an acknowledgement and non-event.

Deliberate culture or random strategic problems

  1. Artifacts;
  2. Espoused beliefs and values;
  3. Basic underlying assumptions.
  1. Accept the strategic diagnosis;
  2. Accept the strategic guiding policies;
  3. See the main strategic actions as coherent and sensible.

Occupy the culture space with role models, systems, symbols

How should I behave? Role models, systems, symbols
  1. Role modeling: Influential, powerful people “walking the talk”, “practicing what they preach”;
  2. Systems: structure, policies, tools to reinforce desired behaviour;
  3. Symbols: concrete representations of organisational mythology (e.g., slogans, stories, value statements, etc.). Symbols are useful when role modeling and systems are aligned; they remind us of hypocrisy and generate cynicism when role modeling and systems are not aligned.




Staff Agile Coach at Spotify, ex-ThoughtWorks, ex-CruiseControl

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

How Physical Fitness made me a Better Leader

The Role of People Analytics in the Future of Work

Everyone Agrees — Performance Reviews Are the Worst!

7 Ways to Improve Your VSA Staff Meetings

2020 — An opportunity for change we can ill afford to waste

Ask business leaders why customers buy from them. The answers may amaze you.

Know Your Growth Roles: Filtering Through the Noise to Determine Your Next Hire

Management Bug: Lack of Know-how Transfer

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Jason Yip

Jason Yip

Staff Agile Coach at Spotify, ex-ThoughtWorks, ex-CruiseControl

More from Medium

The top 3 points you should have paid attention to in the Spotify Engineering Culture videos that…

Alignment vs autonomy in a 2x2 matrix

Three myths about high-performing teams

Writing Useful Performance Reviews: Delivering the review

Enabling Innovation By Setting High Expectations