[{"data":1,"prerenderedAt":75},["ShallowReactive",2],{"term-t\u002Fteam-topologies":3,"related-t\u002Fteam-topologies":59},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":53,"sitemap":54,"stem":57,"subcategory":6,"__hash__":58},"terms\u002Fterms\u002Ft\u002Fteam-topologies.md","Team Topologies",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 - The Vibe Check",[16,17,18],"p",{},"Team Topologies is a framework for organizing engineering teams around four basic shapes: stream-aligned teams that own a piece of the product end to end, platform teams that build internal tools for everyone else, enabling teams that coach others through a temporary skill gap, and complicated-subsystem teams for the one component that genuinely needs a specialist. The core idea is that your org chart is basically a preview of your software's architecture, so if the teams are a mess, the architecture will be too.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"Team Topologies is an organizational design framework, from the 2019 book of the same name by Matthew Skelton and Manuel Pais, that defines four fundamental team types, stream-aligned, platform, enabling, and complicated-subsystem, and three interaction modes, collaboration, X-as-a-Service, and facilitating, for structuring engineering organizations to minimize cognitive load and cross-team coordination overhead. It formalizes and extends Conway's Law by treating team boundaries as a deliberate architectural decision rather than an organizational afterthought.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"We restructured around Team Topologies, platform teams now serve the stream-aligned ones as a service.\" \u002F \"That reorg basically just applied Team Topologies without ever saying the name out loud.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"general","Team Topologies is a framework for organizing engineering teams around four basic shapes: stream-aligned teams that own a piece of the product end to end...","intermediate","md","t",{},true,"\u002Fterms\u002Ft\u002Fteam-topologies",[49,50,51,52],"Conway's Law","Platform Team","Platform Engineering","Bus Factor",{"title":5,"description":41},{"changefreq":55,"priority":56},"weekly",0.7,"terms\u002Ft\u002Fteam-topologies","uQ-3tvBxE1DXLj2RkXg-cu8NLLacHByFbctp2tbLG8g",[60,65,68,72],{"title":52,"path":61,"acronym":6,"category":62,"difficulty":63,"description":64},"\u002Fterms\u002Fb\u002Fbus-factor","vibecoding","beginner","Bus factor = 1 means one person leaving (or getting hit by a bus) destroys the project. They're the only one who knows how the payment system works.",{"title":49,"path":66,"acronym":6,"category":40,"difficulty":63,"description":67},"\u002Fterms\u002Fc\u002Fconway-s-law","Conway's Law says your software architecture will mirror your org chart. Three teams? You'll end up with three services. Frontend team and backend team?",{"title":51,"path":69,"acronym":6,"category":70,"difficulty":42,"description":71},"\u002Fterms\u002Fp\u002Fplatform-engineering","architecture","Platform engineering is building the roads so application developers can just drive.",{"title":50,"path":73,"acronym":6,"category":40,"difficulty":42,"description":74},"\u002Fterms\u002Fp\u002Fplatform-team","A Platform Team builds internal tools and infrastructure so product teams can ship faster.",1792528129424]