Category Archives: Problem Solving Skills

Your Contribution

The competent individual has a firm sense of the capability they possess and capability beyond. Periods of doubt creep in, but that leaves room for growth and maturity. Periods of doubt are painful, as the individual moves from an ordered world to one where there is doubt.

In this chasm, most of the problems we face are self-inflicted. Looking at any problem we encounter, there are the following characteristics. The problem. The problem’s impact. The cause of the problem. The context. And, then, there is you.

You (and we, because I have the same problems as you) are part of the problem. You have made contribution to the problem and its impact. You may be the cause of the problem. If you don’t face your contribution, any solution will leave lingering conditions for the problem to resurface, perhaps uglier than before.

It is always easier to deal with an external problem out there, than an internal problem closer to your heart.

Accountability and Authority

I made sly reference to these two concepts last week. Accountability and authority. These are inseparable.

To be accountable for an output, one must have the authority to determine the variables around that output. Do not hamstring a team member by handing them accountability without the authority to control variables. Bifurcating the two leads to well articulated excuses and blaming behavior.

Simultaneously, do not give someone the authority to control variables without the concomitant accountability. Government oversight committees are famous for wanting to have all the authority without accountability.

These two concepts go hand in glove, not either-or, but AND-and.

Identifying Timespan

From the Ask Tom mailbag –

Question:
Sometimes, identifying level of work seems elusive. I try to look at the timespan of the task, but sometimes, my intuition just seems off.

Response:
The biggest mistake most companies make is underestimating the timespan associated with a role. In addition to timespan, there are other clues that can help us with level of work.

Examine the task. The first clue to level of work is the timespan of the task. Here are the two questions. When does it start? When does it end? When we imagine a task, sometimes we focus on the middle without truly defining the start and end of the task.

While a craft trade (S-I) might look at a task as a one-day project, the supervisor (S-II) may be concerned about the permit inspection in two weeks. The manager (S-III) may be concerned with the system in which the project was completed, accountable for a one-year warranty that accompanies the work product. The VP of Quality Control (S-IV) may be accountable beyond the warranty to multi-year statutes related to defects. For the role, when does the project start, when does the project end?

Examine the tools. A craft trade (S-I) generally uses real tools, machinery, equipment. The supervisor (S-II) will use schedules, checklists and meetings. The manager (S-III) will use flowcharts, sequence and planning. The VP (S-IV) will use multi-project Gant charts.

Examine the problem solving. A craft trade (S-I) may make good use of trial and error problem solving. The supervisor (S-II) may rely on documented experience like SOPs and best practices. The manager (S-III) may employ root cause analysis. The VP (S-IV) has to look at multiple systems simultaneously, systems analysis.

All of these are clues. With the work defined, the next question, is the team member effective in the work?

Wasn’t My Fault (Was It?)

Eight managers and a senior VP sit around the table, this table of Eager Beavers, Vacationers and Hostages. What will prevent them from participating? What will drive them to contribute with enthusiasm?

“Houston, we have a problem!!” booms the senior VP. Enter FEAR stage right. The VP just raised the spectre of fear. Here’s the question, “Does the way you state the problem have anything to do with the way people approach the solution?”

I could see the Face of Fear as I looked around the room. The silent responses were predictable. The darting eyes spoke volumes. Beneath the whisper level, emotions pounded.

  • It wasn’t my fault, (was it?)
  • It couldn’t have been my fault, (could it?)
  • It was supposed to happen that way, (wasn’t it?)
  • Since it wasn’t my fault, it must have been Tim’s fault (right?)
  • I didn’t approve that, (did I?)

Multiply those responses by the eight managers and then calculate what has been accomplished so far. What headway has been made toward solving the problem in Houston? Worse yet, if no headway has been made, what direction is everyone looking?

Does the way you state the problem have anything to do with the way people approach the solution? The mindset around the table is looking for blame, a scapegoat, something, anything to deflect responsibility for the problem in Houston. Everyone is checking out, the quicker the better, last one standing holds the bag. Disengage, no eye contact, pass the buck, Chuck.

As the Manager, you don’t know who has the idea that is going to save the day. You cannot afford to have a single person disengage from the meeting. You need full engagement from everyone in the room for the entire meeting. One idea, one phrase, one twisted word may trigger the solution.

Does the way you state the problem have anything to do with the way people approach the solution? Take the problem and create a positive question that points toward the solution.

IWWCW. In what way can we increase sales in our Houston territory? Take the problem and create a positive question that points toward the solution. Now, look around the room. You will find positive engagement. It is impossible not to. (Sorry, for the double negative.)

A bit of science. The human mind cannot “not answer” a question. (Another double negative.) The way the human brain is wired, when presented with a question, it is impossible for the mind to do anything other than search for the answer. If you want to engage the mind, ask it a question. If you want to engage a team, ask them a question. If you want to engage a team to solve a problem, state the problem as a postive question that points toward the solution. In what way can we…?

What’s Wrong With My Org Chart?

“What’s wrong with my org chart?” Ron wanted to know.

“You tell me,” I said.  “An org chart is just a piece of paper with a picture of the way you think.”

“What do you mean?”

“Organizational structure is simply the way we define the working relationships between people.  Org structure is a mental construct, your mental picture of the way people ought to get on together at work.  You drew the picture.  What did you have in mind?  You tell me where the friction is?”

“Okay,” Ron started.  “Just this morning, the sales manager called a meeting with the marketing manager to talk about their expenses to date related to the budget each submitted at the end of last year.”

“And?”

“And, the marketing manager said it wasn’t the sales manager’s business to see how marketing dollars are spent.  She tactfully refused to attend the meeting.  She said the sales manager was NOT her manager and declined to go.”

“What was your response?” I asked.

“I had to admit, the marketing manager has a point.  The sales manager is not her manager.  When she took the position, we were very clear that it was her department.  She has very clear objectives and unless she is off track, we expect her to run things without interference.  But, still, declining to go to the meeting seemed a little insensitive.”

“So, when you think about their working relationship, how do you see it?  Clearly, neither is each other’s manager.” I said.

“Well, they seem to get along fine, at least until this meeting thing,” Ron shook his head.

“Let me be more specific in my question,” I replied.  “How do you see these two questions? –

  • In their working relationship, what is the accountability for each of them?
  • In their working relationship, what is their authority?

“Well, when you put it that way, marketing should coordinate with sales, and sales should coordinate with marketing.  We have significant trades shows we attend that eat up a lot of marketing budget.  Our trade show booth is generally staffed with people from the sales department.  So, the two departments need to coordinate together.  The company has a high vested interest in their coordination.”

“And, in their working relationship, what is their authority to make what decisions?”

“Each department has a department budget, submitted each year and approved by their manager?”

“Same manager, between the two of them?”

“Yes, our VP of business development is the manager of both,” Ron clarified.

“How clearly have you spelled out their accountability and authority in the work they do together?  You just explained it to me, how well have you explained it to them?”

“But, they are supposed to work together, shouldn’t they be able to figure it out?” Ron asked.

“Apparently not.  You think you understand their working relationship, in fact, on your org chart, you drew a dotted line.  So, the situation looks like insensitivity, when the friction is because you failed to define the accountability and the authority in that dotted line.  You put the dotted line there for a reason, but failed to define it.”

Want to improve the number of reviews you have on Trustpilot? The solution is trustpilot review cards, which makes it easy to collect positive reviews and get 5 stars on your Trustpilot Profile. Visit sites like https://review-cards.co.uk for more info.

Spares?

“Looking at the future,” Glen contended, “we are desperately looking for that new something that is going to help replace some our declining lines of business. We find something, we gear up for it, commit some people to the project, but so far, all of those projects have failed. We end up pulling the plug.”

“Who have you committed to these new projects?” I asked.

“Well, they are new projects, so we generally take those people that we can spare from our core project lines.”

“Are these your best and brightest people?”

“Well, no. Our best people are still running our core projects. But we can usually spare a couple of people from one of their teams.”

“So, you are trying to cobble together a launch team, in an untried project area, where unforeseen problems have to be detected and corrected, and you are doing this with spares?”

Freedom in Limits

“But, I want my team to feel free to approach problems on their own terms,” Monica insisted.  “I don’t want to stifle their creativity.  But often, my team just wanders in a state of confusion, trying to solve a problem that’s not that difficult.”

“It’s a bit of a paradox, isn’t it?” I replied.  “We think if we set limits, then we stifle the team, when limits can be actually be very productive.  If we set the limits too narrow, then there is little opportunity to discover a new or better method.  Yet, if we set the limits too wide, we promote confusion, disarray, introduce delay.”

“That’s what I see, I think I am promoting creativity by giving free reign, but the outcome often falls short,” Monica nodded.

“The thing is, we live with limits all the time.  Social structures are designed to impose limits on those involved.  Organizational structures are designed to define the limits within which reality lives.  They are not designed to stifle, but designed to release creativity in real productive ways.”

“Like, when I tell the team to contribute ideas where money is no object, when the reality is, there is always a limit to the budget.”

“Yes,” I agreed.  “You may gather ideas with an unlimited budget, but there is always that reality that tempers the ideas.  Brainstorming has its place, but so does problem-solving.”

Setting Context

“One of my main responsibilities, as a manager, is to set the context for my team? What do you mean?” Paula asked. “I assume this is more than introducing each other.”

“It’s all about the work,” I replied. “Context starts with a clear understanding of the task at hand. What is the quantity, quality standard, necessary resources and the time frame. QQT/R.

“Next, is how that assigned task fits with the larger picture, that you, as a manager are accountable for. This provides the team with an understanding of just how big their role is, in the larger picture.

“Context also includes the work their teammates are doing, work that intersects with their work, work output they may be waiting for, work output they produce that someone else may be waiting for.

“Context answers the questions – How do I fit in? What is the importance of the work I am doing? What do others depend on me for? One of the primary accountabilities for every manager is to set context for the team.”

99 Dumb Ideas

Todd raised his hand. “I have an idea,” he said, in response to my question to the group. I nodded, he continued, explaining a thumbnail of a solution to the problem.

“That’s a really dumb idea,” I said. There was a silent gasp. Eyes got wide. Blank stares remained frozen.

“What just happened?” I asked.

Marion spoke first. “You just shot Todd,” she said.

“And what was the team’s response? More specifically, how many of you are now willing to contribute your idea to solve this problem?” I pressed. Around the room there were no takers. Weirdly quiet. I smiled with my next questions.

“How many months have we spent working together, to gain each other’s trust? Side by side, we grappled with problems, solving them, trading those problems for another set of problems, working together, growing together?” I stopped.

“And, yet, how long did it take to stop this team in its tracks?” I continued. “Ideas are fragile. In search of an idea to solve a problem requires a risk from each of you in the room. And, we just saw how quickly all the work and all the trust can be sidelined in one sentence. So, ground rules for the next 60 minutes –

  • No idea is a dumb idea.
  • Every idea has the possibility of spurring the next idea.
  • Ideas can be built on each other, subtle variations may make the difference.
  • Ideas can be seen forward, backward and sideways.
  • One part of an idea can be coupled with a different part of another idea.
  • If the best idea is 1 in a 100, then I need 99 ideas that don’t work to find the idea that saves the day.

It’s Just Wrong

“But, that’s just wrong,” Jeffrey pressed. “I tell my team what’s wrong and then tell them to fix it. It’s up to them how. I am not going to spoon-feed the solution. I want them to figure it out.”

“And, when you tell them something is wrong, what state of mind have you left them in?” I asked.

“I hope the state of mind is urgency. When they screw up, they need to fix it and fix it fast,” he replied.

“Exactly. And, how does that state of mind contribute to the quality of the solution?”

Jeffrey chuckled. “You’re right. Most of the time, the team acts like a deer in headlights, frozen, unable to move, no alternatives, no solutions.”

“Does the way you state a problem have an impact on the way people approach a solution? Is there a more productive state of mind you could leave with the team other than something is wrong, someone is to blame and there will be a price to pay.”

“But, I want them to know that mistakes are serious,” Jeffrey pushed back.

“And, does that get you closer to a solution or does it stop solution-finding in its tracks? In what way could we restate the problem, to be accurate in our observations, without laying blame, promoting a sense of teamwork, generating alternatives and selecting the best solution?”