Optimizing for a fast flow of value with Architecture for Flow (Susanne Kaiser)

[@InfectedTofu]

I would be very careful with team topologies. Initially you correctly highlight that value flow and ability to change are crucial, but then you are throwing those goals under the bus because of team cognitive load. I think the problem of cognitive load is grossly exaggerated and sacrificing change and flow for them is a big mistake. But even worse, my experience has been that teams with specific component accountability suffer more from cognitive load than teams that have shared cross functional accountability over the entire stack. But even without this observation, i wouldn't flip my org upside down and throw away change and flow to tackle cognitive load unless it was very clearly impacting change and flow, not a second before.
Clearly defined boundaries are good between the org and the rest of the world (using a 3rd party solution? make a clear boundary for it!) . But within an org, boundaries are sources of bottlenecks, handovers, overproduction, and a plethora of other problems, you even say so yourself early on.