Usually it’s a case of documentation and plans missing something you notice at the actual site/during digging. Could also just stop working waiting for answer to a message (lol and how many days does that take) but that’s going to cost everyone a lot and can even be dangerous.
It’s always the same with people who do the planning and people actually working at the site…
“We have an issue, this and this are here instead of here and now this doesn’t work”
“Well they should be there, have you checked the documentation?”
“It’s not mentioned”
“Well something has gone wrong, it should be there and mentioned”
Lol no shit but it isn’t and now we need to know how to proceed or shit gets fucked
you know what, I’m with you on that. some people deserve to be called on the spot
not me, though. very very rarely is it warranted.
I’ll give an example of how this typically goes in my experience. yesterday I wasted several hours investigating a “critical issue” on site. it turns out that this issue was addressed 6 months ago, and well documented by email and chat, with handoff of responsibilities to the appropriate parties. those parties didn’t do fucking shit with that information. so yesterday the guys on site call in about 10 of us to have a group call, and we’re all just sitting there wasting time waiting for files to open so that the designers can look into the issue. lots of man-minutes wasted in that call alone, when the guys on site could have just sent a message saying “hey this thing is over here instead of over there where it was expected, what’s the deal with that?”, and we would have gotten back in an hour with what was going on. but instead, we all sit through as a group on this very important call listening to somebody explain something that they clearly don’t know the context for, because their own superiors neglected to give them the information on it. so it’s up to us to dig back through over half a year of documentation to come to the conclusion that this is the same issue that we already preemptively addressed six months ago, and here’s all the information that we handed off at the time that your department did nothing with and fucked over the guys on site by not telling them shit.
so yeah, don’t fucking call me. send me a message and I’ll get back to you with a concise response, or call your own superiors because they’re the ones who fucked up and I have the documentation showing that. you guys just set back three other projects for this bullshit. repeat several times a week and oh now my week is spent and new projects are going to have shit quality stuff in them because I had to spend my time dealing with bullshit.
so that’s my pov lol. I’ve been trying to spend time designing a new project every day this week, and I’ve spent a grand total of 3 hours on it so far because of shit that I keep getting dragged into, about 50% of which is dumb shit from somebody else not doing their job
Usually it’s a case of documentation and plans missing something you notice at the actual site/during digging. Could also just stop working waiting for answer to a message (lol and how many days does that take) but that’s going to cost everyone a lot and can even be dangerous.
It’s always the same with people who do the planning and people actually working at the site…
“We have an issue, this and this are here instead of here and now this doesn’t work”
“Well they should be there, have you checked the documentation?”
“It’s not mentioned”
“Well something has gone wrong, it should be there and mentioned”
Lol no shit but it isn’t and now we need to know how to proceed or shit gets fucked
you know what, I’m with you on that. some people deserve to be called on the spot
not me, though. very very rarely is it warranted.
I’ll give an example of how this typically goes in my experience. yesterday I wasted several hours investigating a “critical issue” on site. it turns out that this issue was addressed 6 months ago, and well documented by email and chat, with handoff of responsibilities to the appropriate parties. those parties didn’t do fucking shit with that information. so yesterday the guys on site call in about 10 of us to have a group call, and we’re all just sitting there wasting time waiting for files to open so that the designers can look into the issue. lots of man-minutes wasted in that call alone, when the guys on site could have just sent a message saying “hey this thing is over here instead of over there where it was expected, what’s the deal with that?”, and we would have gotten back in an hour with what was going on. but instead, we all sit through as a group on this very important call listening to somebody explain something that they clearly don’t know the context for, because their own superiors neglected to give them the information on it. so it’s up to us to dig back through over half a year of documentation to come to the conclusion that this is the same issue that we already preemptively addressed six months ago, and here’s all the information that we handed off at the time that your department did nothing with and fucked over the guys on site by not telling them shit.
so yeah, don’t fucking call me. send me a message and I’ll get back to you with a concise response, or call your own superiors because they’re the ones who fucked up and I have the documentation showing that. you guys just set back three other projects for this bullshit. repeat several times a week and oh now my week is spent and new projects are going to have shit quality stuff in them because I had to spend my time dealing with bullshit.
so that’s my pov lol. I’ve been trying to spend time designing a new project every day this week, and I’ve spent a grand total of 3 hours on it so far because of shit that I keep getting dragged into, about 50% of which is dumb shit from somebody else not doing their job