Involvement is a useful frame. In my work with software engineers I try to emphasise the the importance of immediate feedback - not waiting days for a peer review of your code, being able to run tests to immediately validate your code to generate in-the-moment feedback. The 'flow' analogy I tend to use is skateboarding, and the immediate feedback of a bruised knee when things go awry - but your Lotus analogy and the emphasis of 'involvement' over performance will add an extra dimension to my examples. Thanks.
Involvement is a useful frame. In my work with software engineers I try to emphasise the the importance of immediate feedback - not waiting days for a peer review of your code, being able to run tests to immediately validate your code to generate in-the-moment feedback. The 'flow' analogy I tend to use is skateboarding, and the immediate feedback of a bruised knee when things go awry - but your Lotus analogy and the emphasis of 'involvement' over performance will add an extra dimension to my examples. Thanks.
Makes me think: “ROAD-TRIP!” I’m planning one for September. Wanna join me?