Interesting idea – and valuable objectives.

The reason I hesitate to follow this route is my experience with convincing people of the advantages of Scrum and Agile.

I started the same way: doing agile without talking about it. And failed 100 percent: Scrum did not become part of the discourse, not to speak about culture. My colleagues accepted the advantage, but I (nominal team lead, not Scrum Master) was the only driver (because I was the only person with a mental model aka plan).

I failed also with the opposite approach: you have to do this, because Scrum says … (with the implication: or else you will burn in hell). I was alone with my belief.

What I am trying to achieve in the current version is this:

1. start with the advantages
2. use common vocabulary as an introduction,
3. immediately followed by the VSM vocabulary
4. followed by an optional explanation of the principles behind the rule

The gap between step 2 and step 3 must be as small as possible.

Maybe there is room for another type of publication: I have some note on a illustrated guide, a little bit like the “Flight Level” book. In that context, I can go even further and show a user journey with personas, e.g. the early history of a startup , how it runs into turbulences and how ut discovers the world beyond agile and SAFe …