Category Archives: Problem Solving Skills

Is Flexibility a Skill?

“Three things you described, not paying attention, someone skipping a step, or someone too lazy to double-check, it sounds like a motivation problem,” I said, “but, you describe it as a skills problem?”

“Yes,” Addison replied. “I assume everyone comes to work each and every day with the full intention to do their best. And, yes, sometimes, their best isn’t good enough. But it is not because they don’t want to perform at a higher level, it’s because they don’t know how.”

“But, not knowing how, points to some sort of training response on your part. And, yet some people return from training and the underperformance persists?”

“I think,” Addison thought out loud. “Maybe our focus in training misses the mark. We think that training is all about technical information. We train on our sequence and standards, but our failure points are not because we don’t have a process or standards.”

“Where do you see the failure points?” I asked.

“It could be something as simple as flexibility. We have a process, but each project introduces some nuance that is not part of our process. If we don’t pay attention to the nuance, because we are not paying attention, or we aren’t looking for the nuance because we are following a rigid checklist, we are then surprised by a failure point. But, we don’t train flexibility.”

“Is flexibility a skill that can be trained?” I pressed.

“If we can break it down, yes,” she said. “Let’s take safety. We have a safety protocol we follow on every project, it’s a checklist and it’s a hard checklist. No compromise. But, it doesn’t cover everything. We have to be flexible. The height of a project makes a difference, confined space makes a difference, flammable materials make a difference, the depth of a dig makes a difference. We have to be flexible, to make adjustments to rules to accommodate differences. We don’t train flexibility.”

Time of Year for Planning

“In the beginning, your purpose doesn’t have to grab everybody,” I started. “It just has to grab you. It helps you set the course.”

Riley was pensive. “I took over from my father. His purpose served the company well until he passed. The company’s culture was built on it. But things are different, now. It’s not like we sell vinyl records, though that is making a niche comeback. The market is not as interested in our product offering. It is still a voracious market, but it looks in a different direction.”

“Markets drive everything,” I nodded. “When your father started his small company, he did not know if it would work. At the time, he had little access to market research. He based his assumptions on intuition and those first sales. If he was lucky, there would be enough sales to cover his costs. The bank would not loan him any money, so he had to develop his product within his own means and its meager cash flow.”

“I know the stories,” Riley remembered. “And, all of his profit went right back into the company to hire more people and buy more equipment. He took a second mortgage on the house, and mom had to co-sign the note. But, he made it.”

“And, did well,” I smiled. “But markets change. Sometimes markets want incremental improvement, but sometimes markets want a seismic shift. You are somewhere in between.”

“I can see the shift, already,” she said. “I can read the market chatter and see the little startups that take some of our customers. I want to change, but, I am not sure which direction to take.”

“It’s an age old dilemma,” I replied. “Many people think that resistance to change is a matter of will. Most have the willingness to change, it is more a matter of how.”

“Is it a skill?” Riley asked. “Is there a series of questions, or a series of problems that must be solved?”

“If it was a series of problems, what would be the first problem? And, don’t give me some general notion, but think in terms of a problem statement.”

“In what way can we determine the shift in our market needs to better create a product that responds to that need?”

“That’s a good start,” I encouraged. “Here are some other questions you might consider.

  • Who is in our market?
  • How do we find out what our market is struggling with, related to our current product?
  • How do we prototype emerging products to meet that struggle?
  • How do we maintain our current product long enough to create the cash to fund emerging products?
  • How do we measure the ability of emerging products, even small variations, to capture new market interest?
  • How do we manage the risk of failure in our experimentation?
  • How do we maintain morale in our workforce in the face of inevitable failures?
  • How do we learn from our failures, fast enough, to continue innovation?

There are answers to these questions, but first, you have to ask the questions.”

State the Problem

“You have a decision to make,” I said. “You looked at some new technology that has the potential to dramatically accelerate the pace of production and simultaneously ratchet up the quality of your product.”

Leo nodded in agreement. “You are correct. But there are two things I have to think about. This new technology is expensive, not related to the increase in output and quality, but its initial investment. And, once we make this investment, the second thing I have to think about is whether the team will adopt the new technology, or will they kill it. Believe me, if they want to stiff arm the project, they can kill it.”

“So, acknowledging the investment and the risks,” I wanted to know, “what steps do you need to take to mitigate the risk?”

“I think there is an order in what needs to happen,” Leo thought out loud. “I think I need to know how the team will respond to the new technology. That’s first. If they don’t embrace it, doesn’t matter how good the technology is.”

“And how will you find out?”

“I have to schedule an exploratory meeting to look at this new technology. I need to gather some data and put it in front of the team, see what they think.”

“Why do you have to gather the data?” I asked. “You have some engineers on the team, why don’t you have them gather the data?”

“But, what if they reject the new technology before we even get to first base?” Leo answered my question with a question.

“Do you think the way you state the problem has any impact on the way people approach the solution?” I pressed.

Leo nodded again. “Yes,” he stopped. “I know, I know. You want to know how I am going to lay out the problem statement in the project to get the best response from the team.”

“Yes,” I smiled. “What does that problem statement sound like? And is it really a problem statement, or a statement that points to a solution?”

Leo thought, not out loud at this point. Finally, “In what way can we explore new technology in our industry, that will dramatically accelerate our pace of output and step up our quality spec?”

“Good,” my smile turned to a remarkable grin. “Practice that, and then call a meeting.”

The Line at Your Door

“But, if I have the right solution to the problem, isn’t it more efficient to just get the team to do it my way?” Muriel protested.

“In the short run,” I replied. “Are you playing the short game or a long game? Are you training your team to solve problems or are you training your team to follow directions?”

“But, my manager, you know I have a manager, too?” Muriel hinted a bit of sarcasm. “My manager expects me to solve this problem, get on with the work, so we can get to the next project. My manager doesn’t care, as long as we keep moving.”

“Are you sure?” I asked. “If all the problems faced by the team have to go through you, eventually what happens to the speed of problem solving? And the more you solve the team’s problems, the more they depend on you to solve their problems. Every team problem you take away, disables the team, to the point where they are helpless to solve a problem without you. Even if the problem is within their capability to solve, you create a habit, a routine grooved behavior that leads right to the line at your door, behind all the other problems that begin to stack up.”

What Changed?

“Tell me, Muriel, when your solution was challenged, how did you respond?” I asked.

“It’s pretty simple,” she replied. “I gave them the answer to the problem, but they worked in a different direction. They went directly against what I told them to do. I had to pull them together, find out who the ringleader was. You know, I have to find out who was bucking my authority.”

“Do you think the team believed in your solution?”

Muriel paused. “Does it really matter? I’m the manager. If I had the solution to the problem, they should implement it. It doesn’t matter if they believed in my solution.”

“Let’s play this out,” I prompted. “If they didn’t believe in your solution, but you forced them to implement it, how much energy and enthusiasm did they pour in your direction to prove you right? Or did they appear to follow your direction, without enthusiasm to prove you wrong? Either way, you still had a fight on your hands. Did that serve you? Did that serve the team? Did that serve the solution to the problem?”

“But!!” Muriel protested.

“No, buts,” I interrupted. “When you were part of the team, as an equal team member, how did you work together?”

“Well, back then, it was collaborative, we worked together to solve problems.”

“So, what changed when you became the manager?”

Trouble

“One, right after another,” Charlotte flatly stated.

“I’ll give, what?” I asked.

“We solve one problem, three more pop up. We solve one of those and three more pop up. It’s no wonder our department is so far behind goal, we’ll never catch up,” she said. “Trouble always seem to find us.”

“Trouble is mostly a mental state,” I replied. “If you are a victim of trouble, you are correct. It will always find you. Trouble either grabs you by the throat, or you grab trouble by the throat. It’s all in the way you see it.”

The Pain Inside the Problem

“What do you mean?” Felipe wanted to know. “What do you mean, what is the problem trying to teach me?”

“Look, this is a problem that is difficult to solve. It is difficult, because what you are trying to do is difficult. You chose a difficult goal, you chose to aim high.”

“But, it is something that has to be done,” Felipe was firm.

“Yes, you determined this aim was necessary, something that must be accomplished. So, now there is a problem. If you had not set such a lofty aim, you would not have encountered such a difficult problem. People with small problems do not aim very high. Small problems are easy to solve, can even be dismissed without affecting the quest, because the quest is of little importance. But if your aim is high, and your quest is necessary, the problem will be extraordinary. The problem will come with pain.”

Felipe nodded. “Yes,” he said. “It’s painful.”

“What is the problem trying to teach you? You may not unlock the solution until you become a different person. What is the pain trying to teach you?”

The Purpose for Problems

“I’m stumped,” Felipe groaned. “And, the worst part, I feel bad.”

“How so?” I asked.

“I’ve been struggling with this problem for more than two weeks, without resolution. And, it’s painful. I should be able to figure it out, but the problem persists. At first, I thought it was just a bump in the road, something we could fix. Then, I thought perhaps it was a fundamental assumption that we just got wrong.”

“And, now?” I prodded.

Felipe took a deep breath. “And, now? Now I feel like a failure. That maybe it’s me. That I am not cut out for this work. I was proud to get this promotion. I felt important. I barked instructions and people paid attention. Now, I just don’t know. Maybe I am an imposter?”

“We all encounter problems,” I replied. “Sometimes those problems are to be solved. Some problems can be eliminated. But, the real purpose for problems is to learn something new. What is this problem trying to teach you?”

But, We Solved It This Way Before

“We thought we had run into this problem a hundred times,” Robin explained. “It is something we determined about a year ago, a recurrent problem. It took us awhile to figure it out, but we did.”

“And?” I prompted.

“And, now we have a new problem. We looked at it every which way from Sunday, we understand the problem, how it occurred, and thought we had the solution, but the solution doesn’t work.”

“The fatal flaw,” I said. “You understand the problem? You only think you understand the problem. But you understand the problem in the terms of a solution you have already developed. Your solution doesn’t work because you misunderstand the problem.”

The Solution Creates the Next Problem

“I thought I was so smart,” Bianca said. “We had a problem with an ingenious solution. But, when we executed the solution, we created another problem.”

“As always,” I smiled. “The solutions we employ will always create the next set of problems. Indeed, I can always tell a team that is stuck. They are still working on the same problem from the last time I saw them. I can tell when a team is making progress, because they are always trading up one set of problems for another set.”