Skip to main content

More Ways to Reduce Cognitive Load

While the two organizational design patterns have a completely different impact on a software development team’s cognitive load, there are some guides that both could benefit from. Yet, it is our experience that these are easier to implement across the entire product group when there is fluid ownership across the entire tech stack of the product, versus when teams own technical pieces of the solution presented to customers. At the very least, there is no explicit governing unit required to guide (or force) adoption and monitor compliance; it’s done by all for all. Instead of a governing unit, fluid ownership is supported by organizational elements, set of rules, and comprehensive working agreements. The combination of these ensures that fluid ownership doesn't become an anarchy at the cost of overall goals.