3 ms·
This x100 I got to a repeatable functional process to do exactly what you described when I started applying the state machine design pattern to organizations -
by AndrewKemendo 3y ago
This x100
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.
- alfonsodev 3y agohow do you navigate picking the right level of specs for "Desired next state" to me that's hard in personal projects for instance you can choose for a variety of topics then have to decide how deep you get into each. I guess I'm asking if you have a heuristic for what's a good enough desired next state.
- AndrewKemendo 3y agoGenerally it's based on whatever the next big economic decision point is So if the desired state is "New feature X generates Y new revenue per month" then we need to define the state map of the system where that would be true. That begs many questions then, which reveal our state variables: "What feature metrics do we bill for, in what increments, and on what frequency?" - Business Model "What scale is required for that transaction frequency?" - Infrastructure planning "What amount of downtime can we afford and still meet y goal" - Observability Requirements "What tools do we add to help us build?" - Development Environments/Practice etc... until everyone is satisfied that you can map the current state of things, through this transition matrix of questions and into the goal state. The other piece is having an accurate map of the current state of all your dependencies - including people, time, money, focus, etc...
- victor106 3y agoInteresting. Any resources to learn more about this?
- nathan_jr 3y agoMy favorite template for defining the two states & transition path is the A3 Plan popularized by Toyota. I have returned to it over and over throughout my career as a simple and effective problem solving tool.
- AndrewKemendo 3y agoI'm not working off of an existing framework, just my own experience and battle scars. I'd certainly take the time to write my state management process out if there's interest though! Would you read it?
- AndrewKemendo 3y agoI did an impromptu example writeup in another response if that looks interesting to you: https://news.ycombinator.com/item?id=36603313 https://news.ycombinator.com/item?id=36603313
- mhotchen 3y agoSounds like you'd get a lot out of Event Storming (if you haven't looked in to it already)
- jeffreygoesto 3y agoWorked well for us for restructuring 200 people with that. Basically the tech savy people and the ones doing most of the difficult work sketched the interactions and how the project unofficially worked and we restructured along the "real architecture".