There’s a problem with instructions. If you have them, that’s great. If you don’t have them, that’s not great.

Let’s investigate something here …

  • What if you have instructions but they aren’t complete?
  • What if those instructions just don’t include the rest of the request?
  • What if you are expected to know what the rest of the request if it is not as a part of the request?
  • What if you are expected to complete a task that you have no reasonable way of knowing how to do it?
  • What if there is an gross expectation that you are to know things based on guessing as to what the request is?

I liken these questions to a relationship. Your partner wants you to do something but they don’t tell you what they want, when they want it, how they want it or why?

I know this doesn’t sound reasonable, it’s more in the realm of ridiculousness. They say, How can you not know what I want?.

Most reasonable people would respond How could I possibly know what you want if you don’t tell me?

Do I need to spend a day, or days, trying to figure out some request if I don’t know what the request actually is, what it contains, and the full scope of the request.

It’s dumb. It’s stupid. It’s frustrating. It’s ridiculous. And in all seriousness, it is unrealistic.

As a tech person, being asked to complete a request that does not include all of the request is to require me to know what someone wants without having the proper information to complete that request.

In a production enterprise environment, that’s the kiss of death.

Comments are closed.