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? ๐๐ฝ