Skip to main content

6 things that will not solve problems in the workplace

 

I previously wrote about an integrated approach to solving problems. Here are 6 things that will not solve problems in the workplace:

  • Analysis paralysis. A situation where everyone enters into a phase of analysis that only ends in disaster. Decisions need to be made with the awareness that time constraints are a reality.
  • Decide by committee. Put together a big committee to solve the problem and decide the course of action by consensus. Instead a standardised approach is required and leadership. Less reactive consensus and more proactive decisions. When there is a crisis, it is not the time to determine detailed plans as they should already be in place. If you have crisis and continuity plans, dust them off and use them.When there was a crisis on Flight 1549, Captain Sully said, "My plane!"
  • Silver bullets. As an example an automation tool is taken to be more reliable than adopting the necessary operational process. Or a singular control is adopted on the assumption that there is no multiple causation. There are no silver bullets and a crisis is the result of multiple consecutive failures.
  • If It Ain't Broke, Don't Fix It. Everything is working, but it is not really done in a way that is optimal. Some people advocate the view, that if it is working, you should not change it. The correct way is to proactively maintain systems to prevent them becoming broken.
  • Yet Another Meeting Will Solve It. To solve the problem, meetings are arranged. Team members that should be involved with delivering outputs or fixing problems start to be involved in these meetings. The result is much like Analysis paralysis above as deadlines slip even further. Meetings need to be short and to the point. Frequent meetings that don't achieve any goals become long sessions of torture in which people fall asleep as in this memorable meeting.
  • Shoot The Messenger. Nobody likes to hear bad news. Someone has discovered a problem, and decided share the discovery. Everyone yells at him or her. Even though they weren't responsible, they are targeted and as a result will never again raise a problem or issue again.

Any ideas on how to solve workplace problems, please leave a comment below. Alternatively, please read more of my articles on problem management.

The article was originally published over at LinkedIn: 6 things that will not solve problems in the workplace

Comments

Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

A checklist for troubleshooting network problems (22 things to catch)

  Assumptions! What is really wrong? Is it the network that is being blamed for something else? Fully describe and detail the issue . The mere act of writing it down, often clarifies matters. Kick the tyres and do a visual inspection. With Smartphones being readily available, take pictures. I once went to a factory where there was a problem. Upon inspection, the network equipment was covered in pigeon pooh! The chassis had rusted and the PCB boards were being affected by the stuff. No wonder there was a problem. In another example, which involved radio links. It is difficult with radio links to remotely troubleshoot alignment errors. (I can recall when a heavy storm blew some radio links out of alignment. Until we climbed onto the roof we never realised how strong the wind really was that day!) Cabling. Is the cable actually plugged in? Is it plugged into the correct location. Wear and tear on cabling can also not b