Monthly Archives: May 2013

#126 Annoyed? Frustrated?

Send to Kindle

Problem solving with humans is messy business, and in a couple of situations at work, I felt I was walking thru oatmeal. Every day felt like Groundhog Day. I was not sure whether to be annoyed or frustrated.

I decided I would be in neither state. Doing nothing was not an option. Devoting energies to finding out “why” turned out to be very productive. The big “aha” moments were the following:

  • The problems I was solving were clearly a priority, and mission critical. It made sense to keep at it. This is a critical filter. If the problem is not a priority, don’t waste time, go do something else.
  • I felt my colleagues were not doing their bit, not pulling their weight. Obviously, they saw the situation differently. I did not know why, and that is where my energies needed to be applied.
  • I did not sit still, I started doing tasks to clarify the problem, tasks I felt were not my job. I realized that I cannot sit still, I have to be a man of action. (This can be good or bad, but that is a story for a different blog)
  • If I could be very, very specific, and make the problem statement idiot proof, a bullet proof solution will emerge.
  • Those “in charge” don’t want conflict or to confront bad behavior or manage performance with touch conversations. Accepting this reality is essential, suspending judgment is critical. If I was “in charge” I’d want to tread lightly as well. Humans are more sensitive than sensors on a BMW, they tend to “malfunction” at the slightest knock to their motivation. Troubleshooting problems relating to human motivation can be more time consuming and expensive compared to fixing a BMW. There is a “right way” to approach performance problems, I just need to find it.
  • Problems like this take time and money to solve. I could choose to be a martyr, a lightening rod, or an exemplary change agent and role model. I just have to set the right expectations along the way so I can survive to tell the war story.

What techniques worked for you? What war stories can you share?

Share

#125 How much do you need to know?

Send to Kindle

I was asked recently, “If what I am doing is working, do I really need to know how and why?” I could see why this question was being asked. After all, if we start worrying about the how and why of all the problems we solve, our output would decline, and our nerves would be frazzled. I believe the expression for this is “analysis paralysis.”

Here is a guideline I proposed to break the deadlock. If the problem relates to your core competence, and is critical for your success, and something you use in your point of performance, then you need to know the how and why. For exceptions, see next para.

There is a further clarification, if no one has understood the how and why, then it is a research project. Don’t proceed unless you have funding or time and money to burn. But if at least one other person has understood the how and why, then it is a best practice, you would do well to reach out to learn more.

Share