Discussion Locked

Adventures in Problem Management

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
blog root

3 replies

by trillian_sk

A recent incident review had the following action item: "Confirm assumptions whenever possible".
I blinked, then started to laugh.
Who is the owner for this configuration item? Will they be able to tell me when it's done? Is this the same person that owns "Write things down", "Look things up", and "Remember to tell someone"?
I had to explain to upper management that such statements are an excuse to do NOTHING.... and they still didn't get it. *sigh*
I suggest we need a Manager of Culture. After all, there are plenty of other useless managers in the company... why not someone with a pleasant objective AND not a chance in hell of succeeding?

by trillian_sk

I may have the opportunity to implement Problem Management in another area of the company, and I'm excited to see if I can spread the joy and implement what I've learned in a short time, comprehensively.

Here is where I try and capture my main thoughts.

Before you start: Problem Management needs Incident management, Change management and some kind of CMDB to be in place. Without them you are pissing in the wind. Every problem management recommendations becomes a "that's nice, don't trip on your way out."

Meet with the project sponsor because you are going to need them to support you as you implement PM. Let them know that you are going to need answers to the following questions:

Reactive vs proactive? everyone wants to be proactive, crunch the data, and identify the dragons to be slain. good luck. Data crunching requires...good data! I strongly recommend starting with reactive. That gives you time to learn the environment (tools), establish relationships with the players (people), and find out how things work (process). Instead of a knight in shining armour leading the parade, be the guy with the pushbroom that tries to recommend which animals need a change in their diet.

What to investigate? Pick your sample set: by status, priority, customer, platform - whatever works for you. It should be consistent, measureable and significant. If no one cares, there is no incentive to make it better.

When to investigate? Pick your time frame. daily, weekly, after incident resolution - again, whatever works. I strongly recommend - AFTER the incident is resolved, and the wounds are no longer fresh.

Who to ask? Find out who the subject matter experts are for the infrastructure items in your sample set, their managers, and their customers.... yeah, yeah it takes time.

What to ask? "To mantra or not to mantra" I have one, because most people couldn't care less about ITIL and use the words "incident, trouble, case, problem, issue, annoyance" interchangeably. My mantra is: "the objective of problem management is, by investigating incidents, to identify changes that could be made to our IT infrastructure that will PREVENT, ELIMINATE or (to bridge resource gaps) MITIGATE future reoccurrence."

How will progress be reported? This sometimes drives the answers for the other questions, but no matter how much you are expected to reduce incident volume, that is just NOT an obtainable objective for Problem Managament.

by trillian_sk

(Draft - not complete)

When investigating incidents and trying to turn them into actionable
problems, you sometimes encounter resistence, i.e. excuses, or
misdirection. Using your diplomatic skills and sympathety-face are very
important, but knowing how to interpret, filter and deflect the
verbiage is also helpful.

Here are some common excuses, interpretations, and counter-measures.
Always ALWAYS keep whatever annoyance you feel to yourself. Some people
blurt out phrases with no idea of the effect their words have on
others. Always assume they didn't mean it that way, and try to find a
way to put yourself on their side. Tools: ask for their time, thank
them for it, ask who they would recommend you talk to (given the
Problem Mgmt objective). If they say they're the one, off you go!
Common objective: keep the company running smoothly without falling
into every crack in the sidewalk.

"There's nothing we can do". (Classic stonewall. "we're too lazy to
do anything out of the ordinary, and you're too stupid for us to
explain it to you", "I have the imagination of a slug") Could mean that
"there's nothing within our skill set that we know of...". Express
sympathy for them managing so well with what they have been given. Try
to find out if they have their favourite gurus - either within the
group that may have deployed the tool, the company, or the vendor....
Bottom line - help them find someone else that has power/knowledge.
express willingness to share their burden and make contact yourself.
This will galvanize the lazy, or the control freaks, and be welcomed by
those that are really struggling.

"It only happens once in a while". (yeah, and the roof only leaks
when its raining.) Does the cost of handling it outweigh the cost of
fixing it? Can they provide a written evaluation supporting their
position? They way it is not between them and me, but a decision that
must be made by a higher level manger.

"Don't you have more important problem to investigate" ("I'm too
important to talk to you." yeah, and if you inflate like a toad, maybe
I'll get scared and run away) One option is humour (usually only if you
know the person). Try to get them to sympathize with you: apologize for
bothering them, explain you have been given task list by upper manager,
need help getting through it, when would be a better time to call...

"sorry, we didn't keep the logfile" ("Yes, Stupid IS my middle
name") Could be that cost-cutting reduced space for logs to less than 1
day...

"I don't remember" (you think Stupid is my middle name, pressure
makes your mind go blank, or you failed to grasp the critical functions
of Mr. Pen and Miss Paper.) ....

"I didn't cause it, why should I fix it" (Self-righteousness (noun):
convinced of ones own virtue especially in contrast with the actions of
others. Put on your big girl underpants and get over it) ....

This discussion is closed to new replies.