Ivo Pekšēns’ Post

View profile for Ivo Pekšēns, graphic

Facilitation & Agile Coaching services for diverse leaders, managers, Agile Coaches, Scrum Masters, facilitators

Conway's law states that when we design systems those tend to look like our communication structures. It is a bit simplified, but as an example - when we develop a software system using many teams, then the way those teams communicate impacts the way code evolves. If teams talk rarely and not directly, then code reflects that and becomes harder to understand, maintain, produces more defects and so on. When teams talk often and directly, code evolves better, is more consistent and more "pro" if you will. And that reduces future costs. The same applies also to how we design our organizations. If we figure out organizational design details alone or in a small group and then let everyone know, then it looks good on paper and on intranet, but not so in reality. People seem confused, struggling trying to understand and use the magic brainwork. But when we co-create that with others, the organization evolves more naturally and is more accepted by the creators themselves - thus less confusion and struggle, more joy and fun at work. So if you want stuff to actually work and be accepted involve the right people early. This pays back later and lowers costs. It also lowers resistance. And that is actually an old truth: individuals & interactions IS MORE IMPORTANT THAN processes and tools themselves. I guess some Agile people came to that conclusion almost 24 years ago. However, there is a flipside to that: more time & energy is needed. And that is true - involving people and having productive design sessions requires quite a time - preparations, outcomes, formats, etc. And there is one skill behind all that is crucial for those who involve. What is that skill? It is a way older than anything Agile 😃

To view or add a comment, sign in

Explore topics