I got to a repeatable functional process to do exactly what you described when I started applying the state machine design pattern to organizations - and the accompanying broader Markov Decison Process that allows it to iterate.
You need to define two states:
1.Current state
2.Desired next state
Once you have your states, then you build a “transition matrix” that is unique to this state transition which will guide the “how.”
To be clear “organizational state management” is not some turn-key, set it and forget it mathematical, solution.
It’s a simple metaphorical method, But the structure is one that reveals the simplest path to a defined target condition by demanding observability for each step and begs the question of how to draw the map.
I got to a repeatable functional process to do exactly what you described when I started applying the state machine design pattern to organizations - and the accompanying broader Markov Decison Process that allows it to iterate.
You need to define two states:
1.Current state
2.Desired next state
Once you have your states, then you build a “transition matrix” that is unique to this state transition which will guide the “how.”
To be clear “organizational state management” is not some turn-key, set it and forget it mathematical, solution.
It’s a simple metaphorical method, But the structure is one that reveals the simplest path to a defined target condition by demanding observability for each step and begs the question of how to draw the map.