Thanks Carel. Like you, I was introduced to color theory well before I learned about Scrum (~20 years ago almost - I'm getting old :D). De Caluwe taught at least one class at our university about it.

Part of what attracted me to Scrum was that I recognized a lot of those perspectives on change in how Scrum can work in organizations - just not by focussing purely on structure and roles. For example, there is a lot of potential for white (change), red (motivation) and green (learning) in Scrum environments, provided that blue isn't too dominant.

So no, for this reason I wouldn't accept that this all our community can do is "blue-print thinking". There are actually a lot of people in our community who are really good at the other perspectives, but all we tend to hear about (or perhaps I see in my bubble) is "framework, roles, framework, framework, framework".

Perhaps there are ways to metaphorically evolve those fish into monkeys and climb trees, just like we've done in the past :D