3 ms·
Er. This is awful advice. You’re also on the hook for impeding the organisation. I’m a “no” guy. My boss is a pure yes man. I don’t say no to impede progress
by dijit 7y ago
Er. This is awful advice.
You’re also on the hook for impeding the organisation.
I’m a “no” guy. My boss is a pure yes man.
I don’t say no to impede progress. I say no to avoid overworking my team which would reduce the quality of our work.
I say no, because it changes the scope of work in progress, and that requires sufficient justification because it means either throwing work away (which is both demoralising and wasteful), potentially increasing time to delivery or creates technical debt in droves.
I say “no” so that people don’t make their own standards (like not following logging patterns, or metric naming conventions) which would cause all kinds of gunk in the infrastructure.
It’s not about following a strict process. Although that can be important for streamlining workflow through an understaffed team like mine, it’s about ensuring that the quality of what we do is not at risk.
Quality is our only currency, without it everything suffers.
- SubiculumCode 7y agoWhat you say is true, which makes the topic so very subtle because it depends on the context. Saying no to protect your people/process is a good thing. Saying no because it is personally profitable to be disdainful of other's ideas while offering up none of your own, irrespective of what is good for the organization or your team, is not. If one needs a mental picture, think of the quintessential hipster: https://sabotagetimes.com/life/hipster-irony-is-destroying-our-idea-of-sincerity-and-creativity https://sabotagetimes.com/life/hipster-irony-is-destroying-o...
- Aloha 7y agoChange for the sake of change is almost always bad, making decisions without considering externalities is worse.