Conversation

The intuition behind it is really simple: when running org design/process/workflow experiments, don’t start out with unsafe ones — the kind that might lose you political capital. Instead start with safer experiments, rack up the wins, before you go making disruptive org changes.
1
1
Replying to
Example: want to implement org wide OKRs? That’s risky! It’s global, rigid, long duration to eval, imposes lots of changes on lots of people, and so on … Safer experiment: run OKRs on your tiny team and report back. Safest: run OKRs for yourself and tell people about it.
1
1
Any successful org change requires you to get buy-in from the rest of your org. By seeing the change as a series of progressively riskier experiments, you increase the odds of success. (Unless you already have a lot of political capital, that is. Then by all means spend it.)
1