I wanted to share an illustration of how common challenges in business, tech and the business of tech map to positive outcomes via Value Stream Definition and Design.
For many people they may either be aware of Value Streams as a concept or how they fit into improvement efforts, and this provides a high level review. At some point I'll add the 'how' - but in the meantime check out my other posts for that information.
This perspective seems to require an understanding of value streams as a paradigm for ... uh... effective endeavours?... Like if you're having conversations with people asking for pros/cons (presumably, stuff like "so tell me why I should care?", or "help me understand what I gain by doing this, and lose by not doing") - what you've presented here perhaps takes for granted that the listener automatically understands the bits and bobs of value streams?
My take on this is that it might be more effective if you map not to a single box 'value stream stuff', but to pieces inside a box? Like, my gut reaction is that you could replace 'value stream stuff' with a lot of things. "regular OKR meetings" could map to many of those items.
However, if you were to break 'value stream definition & design' into components, it might make for a more intuitive mapping. Even a staged approach - first round could be a 'upstream/downstream' meeting - what do I gain from that? What concerns are addressed? Then move on to a larger context, etc.
Not sure I've communicated that well...I could be in left field here.
Thanks Chris I absolutely agree, this is definitely missing the 'how' and other valuable context. I think I'll tackle that elsewhere as I'm afraid of making a 'subway map' but perhaps I can figure out how to incorporate more detail in a future iteration. You're spot on highlighting that a variety of activities could accomplish much (if not all!) of the outcomes, though I believe many practices like "regular OKR meetings" and the like depend very heavily on hard-won knowledge to perform correctly but most would get immense value from that approach as well. As always, not a silver bullet, I'd suggest V2MOM accomplishing even more than OKRs and Capability Mapping also augmenting to maximize the efforts as well. I'm planning a future post on a broader portfolio-based approach beyond VSM that hopefully addresses this more directly.
Truly appreciate you weighing in. Your perspective always opens my mind!