Don’t Touch That Dial
I’ve already proposed an approach that will encourage Ops to avoid doing more work. Now, I’m going to expand on that less-effort trajectory, and share the following fortune-cookie wisdom: “Doing nothing is better than doing something…” although, you have to add “…stupid” to the end of that, to truly gleam this particular gem. Let’s face it, if the smartest and brightest people were always at the helms, there’d be a real dearth of topics for discussion here at feyn.com. Because there are under-qualified decision makers in the mix, who often measure performance with misapplied KPI or othere misguided metrics, there is a constant push to demonstrate value by doing something. That is probably the worst combination when it comes to operational soundness and security — doing something for the sake of doing, especially when there is an unlikelihood of doing something smart.
It is up to the savvy Ops engineer to recognize this particularly flawed impetus. Furthermore, the irony is that it’s far easier to not do something stupid, than it is to actual do something smart. Because doing something smart requires effort — awareness, common sense and applying the right solution to the right problem, etc. At this point, if you’re wondering how to determine if you fall into the smart and competent camp, vs the less smart and probably unqualified camp, you are already ahead of the game — because only those people who care about their soul, have a one. Remember, competition between vendors is ruthless, and it’s not chance happenstance that an army of sales people strapped with slick pitches, back nine passes and other enticing items find the weakest link in the decision tree and attack it with using the enterprise wine-and-dine maneuvers. Objective assessment do not come from that direction. Real life war stories come from fellow survivors on the frontline. Trust someone with hands-on experience, and because you’ve surrounded yourself with competent peers, draw upon that collective wisdom to combat the impulse to act simply because.
Of course, this is not an advocacy for monolithic stonewalling of service delivery. This is certainly not a battle cry against early adoption, rapid deployments or the ideas of iterative improvements. All of those and other best practices are still true and should be respected as such, where applicable. The is just a reminder to pause, however briefly, to think about the basic task of evaluation and decision making, and to make sure that before you, or someone else, commit to a course of action, it isn’t the result of reactive, short-attention span jitter swayed by the wrong influences. At the end of the day, support is tough enough without self-inflicted dumbness. When you push that button to go and go forward, make sure the smart decision is pushing the button at all.