workaday Thursday
Mar. 14th, 2024 06:59 amWorkplace document: 'this is a requirement'
Me: well, that seems clear enough -- what are the consequences if this requirement isn't met?
Work: that's our stated requirement
Me: right, I understand that, but I'm the one collecting documentation to show if that requirement is met, and I can tell you that sometimes it's not, so what should I do in those situations? full stop on work?
Work: not necessarily
Me: so... it's not a requirement?
Work: it's our stated requirement
Me: look, here's a specific example of a situation in which that requirement is not met
Work: yeah, that one's fine
Me: ...
And THIS is exactly why I find work confounding at times. There are very specific written procedures and requirements, and then there are the secret unwritten ACTUAL procedures and requirements, which seem to change on a whim and with no notice whatsoever. I can't get anyone to tell me what they are, because they just point me at the written ones!
(I do understand that there is conceptually gray area in all requirements. But I'm also a firm believer that you should be able and willing to explain your reasoning for decisions made in that gray area.)
Me: well, that seems clear enough -- what are the consequences if this requirement isn't met?
Work: that's our stated requirement
Me: right, I understand that, but I'm the one collecting documentation to show if that requirement is met, and I can tell you that sometimes it's not, so what should I do in those situations? full stop on work?
Work: not necessarily
Me: so... it's not a requirement?
Work: it's our stated requirement
Me: look, here's a specific example of a situation in which that requirement is not met
Work: yeah, that one's fine
Me: ...
And THIS is exactly why I find work confounding at times. There are very specific written procedures and requirements, and then there are the secret unwritten ACTUAL procedures and requirements, which seem to change on a whim and with no notice whatsoever. I can't get anyone to tell me what they are, because they just point me at the written ones!
(I do understand that there is conceptually gray area in all requirements. But I'm also a firm believer that you should be able and willing to explain your reasoning for decisions made in that gray area.)
no subject
Date: 2024-03-14 07:59 pm (UTC)(In a completely dissimilar grey-area situation) I found it worked to ask, "What kinds of things do you take into account?" without forcing them to pin down exact rules, fwiw.)