The vision informs the architecture. The vision and the architecture inform the team topology.Marty Cagan, Empowered workshop
It’s amazing what comes out of the woodwork when you start isolating a problem and investing in solving it. As our Product Org scales at Swiftly, I’ve felt the organic need to more concretely firm up our teams – in both composition and goals. Working with my co-conspirator, our Head of Engineering, we drew natural lines among teams, our product vision, and our architecture. We referenced domains-based ownership, Conway’s law, and a litany of team and product focused articles and books. We drew on our unique experiences to understand the trade-offs at every turn. And no matter what way we cut it, it was evident that we had to tackle team topology, architecture, and product vision simultaneously to get it right.
My pal and Product leader extraordinaire, Kelton Lynn, and I were talking about shaping an org structure and architecture that best supports the customer vision. He nonchalantly threw out the term “orgitecture,” which was simply perfect. (It’s also strangely trademarked by a digital marketing company.)