An eight-week course for technologists — introducing writing practices for thinking, learning and leading.
We are conditioned to think linearly. Linear thinking enables us build and deploy software. But it can not resolve systemic issues. For systems, we need nonlinear thinking.
In the world of “digital transformation”, software is becoming systems. Unfortunately, we don’t think in systems. To provide systems leadership, IT professionals need an emerging set of (new) skills.
Designing systems that accommodate for information in many contexts is incredibly interesting. Alas, we don’t (yet) think and act in systems.
Vaughn Vernon and Diana Montalion discuss how systems thinking can help software architects transform software into systems of software.
Integration leadership delivers the type of thinking that cultivates conceptual integrity and solves systems challenges.
We are conditioned to think linearly. Valuable things (like software) have emerged from linear thinking. The challenge is that linear thinking is also, assuredly, our biggest blocker when we are systems building.
Empowered teams invest time, energy, attention, passion, systemic reasoning, care and experience in each other and in the work. They drive necessary change.
When building modern architectures, the hard part isn’t learning Kubernetes. The hard part is the mindshift: changing the way (almost) everyone thinks.
How do you provide integration leadership, facilitating dialogues that improve outcomes? The short answer is: you practice.