|
|
|
|
|
by jimmySixDOF
1481 days ago
|
|
Over Planning is also an institutional response to risk. In these cases it is actually "the easy part" and so preferred by environments where any mistakes are costly. As in the "If at first you don't succeed, then Sky Diving is not for you" kind. In these cases I would not call planning an end in itself but rather a defense mechanism deployed to avoid the risk of action until absolutely necessary. Not that I justify what can become analysis-paralysis situations, but it is better to understand the beast you are dealing with if you want to navigate a path through. |
|
To further elaborate on this point, sometimes that risk is internally created. If you get negative feedback for doing something everyone agrees is valuable, negative because it's not what your manager would have chosen as the highest priority, or because the architect would have planned the implementation slightly differently, etc., then the natural response to that negative feedback is "OK, next time, let's do some more planning so that you'll be happier with the work that's being done." What makes customers happy and what makes managers happy is not always the same thing.
Great organizations embrace risk. Not reckless risk, not the kind where you say "eh, this might result in two-day downtime for all our customers, YOLO", but the kind where you say "I prefer that my workers make imperfect decisions that we can fix later if we really need to so that the whole organization can move faster". 80% of the time, the decision does not need to be fixed. 80% of the remaining 20%, you don't have time to fix it, and usually, that actually works out OK, all things considered.