How to avoid the “IT black hole”

How to avoid the "IT black hole"

Going all the way back to my days as an association staffer (more than 30 years ago) I've encountered what I call the "IT black hole." The IT black hole is where technology issues go to die. Perhaps you've experienced this. You report an issue to your technology staff and you never hear another word about it.

My clients often compliment me on my responsiveness and I've come to realize that this is partly because they've all lived with the IT black hole.

So for those of you in IT (or anyone who receives "issue reports" from others), here is my simple three-step process for avoiding the IT black hole:

  1. Acknowledge receipt of the issue. You would be amazed how far a simple email saying "Confirming receipt" goes!
  2. Tell the person submitting the issue what will happen next. Be as specific as possible, e.g., "I'll review this issue and get back to you within the next three days with a solution or next steps."
  3. FOLLOW THROUGH on your promise! If you've promised a response in three days, provide a response within three days! Even if the response is "I haven't had a chance to review this yet," or "We've looked at this and we're going to need more time to dig deeper and learn more."

I'd estimate that 80% of the complaints about an IT department's ability to do their job are related to the black hole issue. When staff doesn't know what the IT department is doing with their issues, they'll likely assume the worst. Communicating what you're doing will help to avoid that.

Wes's Wednesday Wisdom Archives

Sometimes you just have to try it and see what happens

August 10, 2022

Sometimes you just have to try it and see what happens The single greatest key …

Sometimes you just have to try it and see what happens Read More »

Training and testing

August 3, 2022

Training and testing I’ve written before that the best form of training follows this process: …

Training and testing Read More »

How to save a “failing” project

July 27, 2022

How to save a “failing” project It is not unusual for me to receive a …

How to save a “failing” project Read More »

The “People” are important!

July 13, 2022

The “People” are important! I’ve written a lot about people, process, and technology over the …

The “People” are important! Read More »

Always look for the MVP

July 6, 2022

Always look for the MVP I first wrote about minimum viable product (MVP) just three …

Always look for the MVP Read More »

The longer you take, the longer it will take

June 29, 2022

The longer you take, the longer it will take It may sound like a tautology, …

The longer you take, the longer it will take Read More »

Data is for action

June 22, 2022

Data is for action When deciding whether or not to collect a piece of data, …

Data is for action Read More »

Have you shopped yourself?

June 15, 2022

Have you shopped yourself? I’ve always been fascinated by the “secret shopper” concept. (Maybe it’s …

Have you shopped yourself? Read More »

To improve adoption, decrease the friction

June 1, 2022

To improve adoption, decrease the friction “Before you try to increase your willpower, try to …

To improve adoption, decrease the friction Read More »

“Is this normal?”

May 25, 2022

“Is this normal?” ne of the greatest parts about my job is that I get …

“Is this normal?” Read More »

Scroll to Top