Skip to content

The ways teams choose to interact can make or break the effectiveness of any operating model.

In the context of operating model design, teams can be organised around ๐—ฎ๐˜€๐˜€๐—ฒ๐˜๐˜€, ๐—ฒ๐˜…๐—ฝ๐—ฒ๐—ฟ๐˜๐—ถ๐˜€๐—ฒ, ๐—ผ๐˜‚๐˜๐—ฐ๐—ผ๐—บ๐—ฒ๐˜€, ๐—ผ๐—ฟ, ๐—ด๐—ฒ๐—ผ๐—ด๐—ฟ๐—ฎ๐—ฝ๐—ต๐˜†. ๐Ÿ’ก Choosing the optimal 'organising principle' for your teams is crucial: โžก ๐—ข๐˜‚๐˜๐—ฐ๐—ผ๐—บ๐—ฒ๐˜€-๐—•๐—ฎ๐˜€๐—ฒ๐—ฑ: Teams organised to achieve specific outcomes, such as Event, Mission, and Project Teams.

2 min read

Originally posted on LinkedIn ยท 10 reactions ยท 2 comments ยท View original โ†’

  • The ways teams choose to interact can make or break the effectiveness of any operating model. ๐Ÿ‘‡๐Ÿฝ

In the context of operating model design, teams can be organised around ๐—ฎ๐˜€๐˜€๐—ฒ๐˜๐˜€, ๐—ฒ๐˜…๐—ฝ๐—ฒ๐—ฟ๐˜๐—ถ๐˜€๐—ฒ, ๐—ผ๐˜‚๐˜๐—ฐ๐—ผ๐—บ๐—ฒ๐˜€, ๐—ผ๐—ฟ, ๐—ด๐—ฒ๐—ผ๐—ด๐—ฟ๐—ฎ๐—ฝ๐—ต๐˜†. ๐Ÿ’ก Choosing the optimal 'organising principle' for your teams is crucial:

  • ๐—ข๐˜‚๐˜๐—ฐ๐—ผ๐—บ๐—ฒ๐˜€-๐—•๐—ฎ๐˜€๐—ฒ๐—ฑ: Teams organised to achieve specific outcomes, such as Event, Mission, and Project Teams.

  • ๐—”๐˜€๐˜€๐—ฒ๐˜๐˜€-๐—•๐—ฎ๐˜€๐—ฒ๐—ฑ: Teams centred around managing or developing assets, including Product/Service, Component, and Platform Teams.

  • ๐—˜๐˜…๐—ฝ๐—ฒ๐—ฟ๐˜๐—ถ๐˜€๐—ฒ-๐—•๐—ฎ๐˜€๐—ฒ๐—ฑ: Teams focused on specialised knowledge or skills, such as Phase, Business Function, Customer Segment, Customer Journey, Processes, Channel, Value Stream, and Capability Teams.

  • ๐—š๐—ฒ๐—ผ๐—ด๐—ฟ๐—ฎ๐—ฝ๐—ต๐˜†-๐—•๐—ฎ๐˜€๐—ฒ๐—ฑ: Teams organised by location, like Geographical Teams.

Equally important is defining the communication and collaboration protocols between teams. ๐Ÿ’ก

This is often overlooked, resulting in a chaotic post-transformation phase for organisations, where teams struggle to collaborate and consume services effectively from each other. ๐Ÿ‘€

Teams can use different interfaces to collaborate effectively when working across multiple assets or requiring expertise beyond their core capabilities. Here are some of them:

  • ๐—ง๐—ต๐—ฟ๐—ผ๐˜‚๐—ด๐—ต ๐—ฃ๐—ฟ๐—ผ๐—ท๐—ฒ๐—ฐ๐˜๐˜€: Team A needs Team B. They collaborate through formal projects with defined scope and timeframes.

  • ๐—”๐—ด๐—ถ๐—น๐—ฒ ๐—œ๐—ป๐—ฐ๐—ฟ๐—ฒ๐—บ๐—ฒ๐—ป๐˜๐˜€: Team A needs Team B. Team A creates a request for Team B and hopes it will make it into their next regular iteration (Sprints/Product Increment), which could mean waiting up to 12 weeks or more.

  • ๐—”๐˜€ ๐—ฎ ๐—ฆ๐—ฒ๐—ฟ๐˜ƒ๐—ถ๐—ฐ๐—ฒ: Team A needs Team B. Team B has a service catalogue with a clear service-level expectation for each service. Team A looks at it (e.g. 30 days or less with 85% confidence) and plans their work accordingly, considering there's an 85% probability of on-time delivery by Team B.

  • ๐—–๐—ฟ๐—ผ๐˜€๐˜€-๐—™๐˜‚๐—ป๐—ฐ๐˜๐—ถ๐—ผ๐—ป๐—ฎ๐—น ๐—ง๐—ฒ๐—ฎ๐—บ๐˜€: Team A needs Team B. Team B allocates a dedicated SME to be embedded for a period of time into Team A so they have the capacity and capability necessary to progress their work.

โ—๏ธThe insight is that the ways teams choose to interact can make or break the effectiveness of any operating model.

๐Ÿ’ฌ How are your teams currently interacting? Are Agile Increments the primary method? ๐Ÿ‘‡๐Ÿฝ