3 ms·
As they've put them in the comments on the document then can you get someone senior enough to simply say "That's a small issue, we can accept the risks around t
by scrapheap 4y ago
As they've put them in the comments on the document then can you get someone senior enough to simply say "That's a small issue, we can accept the risks around that". If you can't get them accepted as risks then they probably do need considering.
One thing to bear in mind is that you're far better off with a colleague who points out all the problems they see, even if some of them are tiny, than you are with colleague who sees the problems and doesn't say a thing until after you've hit them.
- paulcole 4y ago> One thing to bear in mind is that you're far better off with a colleague who points out all the problems they see, even if some of them are tiny, than you are with colleague who sees the problems and doesn't say a thing until after you've hit them. I kinda agree. If somebody delays projects because they’re pointing out tons of unlikely and low consequence issues, then I’d rather not hear from them. But if they’re identifying (the hopefully rarer) semi-likely and high consequence issues, then that’s a much better person to work with. This is why it’s important that everybody is on the same page about what kind of problems you can live with and which need to be caught early.
- hayst4ck 4y agoI would not be surprised if there is an element of responsibility that is missing from the story. If the problems you cause will cause yourself future pain, but not others, then you should get privilege proportional to your responsibility. If the problems that are caused will be experienced by someone else, and that person is already under a lot of pressure, every new small problem has a chance of being the piece of straw that breaks the camels back. If the person writing comments is oncall, but OP is not, then OP is wrong and OP needs to be put on the oncall rotation to get some empathy. "You dealing with this problem is a price I'm willing to pay" probably isn't going to have good outcomes for anyone. "I'm going to write this system that other people will be responsible for maintaining" isn't going to have good outcomes for the people who inherit it. If OPs money is where his mouth is, if it's OPs skin in the game and not the person writing comments, then what the commenter says doesn't really matter that much. If OP is writing checks that are debited to the commentors account, well, OP is in the wrong. Regardless, OP does not trust his co-worker and thinks his coworker acts in bad faith, and that is a problem the manager needs to address. Me vs them is not a productive mindset and is the one OP clearly has. Us vs the problem is a productive mindset.