Outcomes, not codebases
▻https://hackernoon.com/outcomes-not-codebases-5fe81e21be52?source=rss----3a8144eabfe3---4
One of the greatest challenges in setting up a Product & #engineering org to succeed is the team structure. Team structure dictates the collaboration that can be fostered, the bottlenecks that can occur and the ability for teams to run autonomously without stepping on each others toes and cannibalising product strategy efforts.To complicate this, there are multiple ways to setup teams — for example there’s the much publicised and overly adopted Spotify model, there is arrangement around subject matter expertise (e.g. codebases), there are pirate metrics (AARRR) and then there structuring them in a manner that enables your very unique org to be successful and not treated as a cookie cut team — I’ve frequently plumped for the latter because lets face it, your org is unique.The Spotify model — (...)