DEV Community

Discussion on: Do your job

Collapse
 
deyshin profile image
Daniel Shin

Extending the opinion of @yucer , I want to add my view.
I think there is a big difference between finding a reason not to work versus expressing the concern about the way the work is done

Let me be clear that I strongly believe in doing your job first. But there can be the second step to address the team's concerns, right?

At least from my personal experience of getting my job done while expressing concerns about the way the organization is managed (and why that may hinder myself and others' performance), and seeing those organization going down, I think it's unproductive to dismiss complaints of average workers as 'making excuses not to work'.

After all, I think everyone wants to do a good job. (though I may be wrong with my utopian view)

Collapse
 
sandordargo profile image
Sandor Dargo

Thanks for your comment. I agree on the big difference you mentioned. And I wish I could agree that everyone wants to do a good job. But I think people can have other motivations. I think social pressure/good example and a high level of automated quality assurance can help a bit.