I think the reason for this gap, and many others, is because teams don't fully understand software system dynamics. After reading Michael Williams' excellent "How the Software Machine Works" (link at bottom) it became clear to me that every software team should know this stuff.

But how to educate at scale? People don't want to read a 12 minute long article.

That's why I'm thinking of starting a dedicated service to provide communication and learning tools for software system dynamics. I built a POC at: softwaresystemdynamics.com

The goal is to have an interactive, graphical representation of the dynamics so that learning is intuitive, customizable and tailored for the unique needs of an organization.

For all you side project believers, this is tangentially related to my software development business. I think it's a good side project, but also potentially a standalone business too. Would really appreciate any feedback here.

"How the Software Machine Works" https://medium.com/swlh/how-the-software-machine-works-6265b30c0fc0