The mark of a born bureaucrat is figuring out how to do something before figuring out the details of the what, and never getting to the why. What and why aren’t exactly ignored, but they’re kinda loremipsumed away at the beginning in like 5 minutes and never revisited.
-
-
The praxis-practice gap is the medium-message gap. The reason not to address how before what/why is medium-message concordance. Most missions worth pursuing require a degree of innovation in medium. So locking in how while what/why are loreipsummed short-circuits co-evolution
Show this thread -
This co-evolution translates to a very specific constraint on the “how” — it specifies what pattern of risk to take on and why. So it short-circuits the default process of picking from off the shelf design patterns on the basis of what fits your psyche rather than the problem.
Show this thread -
Resetting a bureaucracy that has already locked on to its risk preferences is very hard. But at a founding moment, you have a lot of leeway to set defaults in a place principals are not used to, and force mechanism design to a new corner of risk space, innovating if necessary.
Show this thread -
Resets require an external shock proportionate to the inertial mass of the processes already locked on to old risk profile. Aka a Trump-like shock (or natural disaster or radical technical idea etc)
Show this thread -
Note that even apparently high-risk orgs with an aggressive posture can be very risk averse on particular fronts, with process inertia there (a tell: surprisingly incompetent people in high-paid roles in otherwise competent orgs) and strongly resist shifting risk exposure there
Show this thread -
Yes, I’m subtweeting an anonymized composite of a dozen client orgs from the past decade
Show this thread -
And surprisingly, this is not restricted to big orgs. Orgs as small as 4-5 people show this pattern of bureaucratization. It’s not a function of the scaling staircase but the founder mindsets.
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.