2 ms·
I'm of two minds on this. As many of the commenters on the original piece note, the idea of a "no excuses culture" will be familiar to anyone who's familiar wi
by smacktoward 10y ago
I'm of two minds on this.
As many of the commenters on the original piece note, the idea of a "no excuses culture" will be familiar to anyone who's familiar with the culture of the (U.S., anyway) military, and generally speaking it works quite well there. It helps cut through B.S. and keep everyone focused on the idea that results are the thing that matter, which is important when results can literally mean the difference between life and death. And while it can sound to an outsider like a cruel standard, I personally found my exposure to it freeing -- it means not having to deal with the blame-seeking and post-hoc litigation of small mistakes that we all have to struggle with every day in other contexts. So in that respect, I'm all for it.
The thing is, though, in the context of military culture "no excuses" isn't a stand-alone principle the way it's presented here. It's embedded with a bunch of other, complimentary principles that help sand off its roughest edges.
An example would be the principle that responsibility flows uphill: leaders are responsible for failures of their units, even in cases where the failure is entirely due to mistakes by subordinates -- mistakes that they may not even have known were being made. (Because why didn't the leader know those mistakes were being made? It's their job to train their people to do the right things, and to make sure they're actually doing them.)
This compliments the "no excuses" idea, because it limits its usefulness as a tool for powerful people to push ones farther down the food chain to do unethical things. You're responsible for the things your people do, so there's a strong incentive to make sure not just that they get results, but that they do so in ways that you would be comfortable being judged by.
Without that, "no excuses" becomes a kind of blind eye standard -- "get results, I don't care how." Which can put immense pressure on the person on the receiving end of that directive to cut corners, fudge evidence and cross ethical lines if they have to in order to get those results. And if they do, the leader can then feign innocence: "I never told them to do those horrible things!" Well, yeah, but you put them in a position where the horrible things were they only things they could realistically do. You set them up to fail.
So while I applaud the general idea, I worry that in the absence of complimentary values "from now on showing up with an excuse the day the project is due will cost them their job" becomes just one more way for bad managers to push blame that should rightly go to their own incompetence down down the org chart.
- watwut 10y agoOn one hand, I agree that responsibility flowing uphill can help with the pushing down unethical things. However, when dev leader felt so much responsibility for all tasks, he attempt to micromanage us all to absurd degree. I strongly preferred when I was responsible for what I was doing, because then other people don't try to constantly control details of what I feel responsible for.