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:
- Acknowledge receipt of the issue. You would be amazed how far a simple email saying "Confirming receipt" goes!
- 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."
- 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
Once you know, what will you do?
Once you know, what will you do? I’ve yet to meet a client who didn’t […]
If it’s not in your AMS, why not?
If it’s not in your AMS, why not? I like to tell my clients they’ll […]
Why checkboxes and tags are awesome and dangerous
Why checkboxes and tags are awesome and dangerous One of the most common functions in […]
Don’t miss obvious engagement data
Don’t miss obvious engagement data What I’ve experienced with my clients over the years is […]
All data requires active management
All data requires active management It’s a simple fact of data management that is often […]
Documentation is critical for consistency
Documentation is critical for consistency There are so many reasons why documenting your data management […]
Consumer demands change and technology changes
Consumer demands change and technology changes When I work with clients on the selection of […]
Why I write
Why I write Thirty years ago, I started a new job as director of membership […]
DAN – The Data Analytics Network
DAN – The Data Analytics Network I’m a huge fan of users groups (both internal […]
Process before technology
Process before technology In a conversation with a client recently, I was reminded (yet again) […]