Relieved

“I spoke with John, he is going back to be a team leader,” Marissa explained. “He was relieved, said he never wanted the promotion to supervisor in the first place. He thought he was going to get fired in his new role.”

“And, what did you do about his compensation?” I asked.

“I took your advice. I am the one who made the mistake. He was already at the highest technician rate before his promotion, so there was only $1 an hour difference. I kept his pay at the supervisor rate. He shouldn’t have to pay for my mistake.”

“Most importantly, you are on the hook for finding a new supervisor, what are you going to do differently?”

What Are You Going to Do?

“Well, I promoted him,” Marissa replied. “His former supervisor got promoted to another department, and, so, for three weeks, I had to cover. I promoted John because he was the best on the team, and, everybody liked him.”

“So, you assumed that because he was a standout performer doing one thing, that he would be a standout performer doing something else?” I asked.

“I assumed it would take a couple of weeks to get the hang of it, but it’s been a month and he is still a lost puppy.”

“So, what are you going to do? Now, that you understand the problem more clearly.”

“I don’t want to fire the guy, he’s been with us for six years. But, I don’t know if his ego would allow him to take a demotion?”

“You are in quite a pickle, aren’t you? Are you better off with him, or better off without him?”

“I would hate to lose him. I would be better off with him, but only in the right role.”

“So, what are you going to do?”

Not a Matter of Skill

“I don’t understand why John doesn’t do better,” Marissa complained. “I constantly have to give him critical feedback, and I know he doesn’t like it, I can see it in his face. If he would only pay attention to the problems right in front of him, I wouldn’t have to correct him.”

“What do you think the problem is?” I asked.

“Well, he got promoted to be a supervisor because he was a great team leader, best machine operator we have. All he has to do now, is make out the work schedule for the department, order materials and supplies, schedule preventive maintenance on the machines, keep overtime in check, how hard could it be?”

“What do you think the problem is? Where does he struggle?”

“He struggles with all of it,” Marissa replied. “And his attitude is in the dumper, he mopes around all day because he thinks I yelled at him for doing such a crappy job.”

“What does he do well?”

“That’s part of the problem. We had a machine go down yesterday and he spent the entire afternoon tearing it apart and putting it back together. All the while, we don’t have next week’s schedule and we are almost out of materials. I had to put in a rush order so we can keep production online next week.”

“So, who promoted him?”

Unconscious Skip

The problems you have with other people will largely depend on how you think about other people. If you think about people as obstacles, you will have obstacle problems. Solving an obstacle problem gives you a way-different result than solving a people problem.

It is an unconscious skip from people-as-people to people-as-obstacles. You end up there so quickly, you are unaware of the skip.

Becoming genuinely interested in other people requires conscious thought, effort. It is a subtle shift that does not happen by itself.

A Subtle Shift

Who you are is largely shaped about the way you think. If you need to make a small shift in who you are, you have to make a small shift in the way you think.

In a leadership role, your effectiveness will largely be determined by the way you think about people. If you think about people as obstacles –

  • The guy who cut you off in traffic
  • The person with three kids whose shopping cart is blocking the aisle
  • The co-worker in the next cubicle who you have to go around to get to the coffee machine

Your behavior will follow.

It’s a subtle shift to think about people as people (and much more difficult than people as obstacles). Your team members are not direct reports, you are not a manager so people can report to you. Your effectiveness will only be as large as the people you personally invest in.

Double Edge of Knowing

Habits are routine, grooved behaviors based on what-we-know. What-we-know is always based on the past.

Habits are a two-edged sword. Habits help us understand the world quickly. What-we-know creates patterns we can use to solve problems efficiently using a minimum of brain power.

Habits can prevent us from clearly seeing the present. What-we-know may not be accurate or lead us to mistake reality as a previous pattern (with a mistake).

Habits are part of who we are and resistant to change, because they are based on what-we-know. Habits are more powerful than reality, because reality is always new. Knowing prevents learning.

Four Levels of Knowing

What-we-know is a mental configuration. The way we configure what-we-know extends along our timespan of intention.

Most ideas exist independent of each other. If our timespan of intention is short, it is a perfectly good way of organizing what-we-know. We can rely on what we see, hear, touch, smell. Life is relatively simple. We can choose this idea OR that idea. This is the world of trial and error.

But, we wake up one morning and see ideas that are connected together. Our timespan of intention extends further into the future. What we see, hear, touch and smell is organized by ideas that are connected. This is the world of best practices, connected to our most common problems.

But, we wake up one morning and see ideas that are caused by other ideas. There is not only a connected relationship, but a cause and effect relationship. Our timespan of intention extends even further. Best practices help to solve problems we have seen, but are useless to problems we have never solved. What-we-know comes from root-cause analysis, the basis for creating a single serial system, a series of ideas sitting in a sequence of cause and effect relationships (critical path).

But, we wake up one morning and what-we-know includes more than one system. We see multiple systems sitting side by side. Each internal system has its own constraints, but some of those constraints now sit outside the system. Each system has an output which becomes the input for its neighboring system. Defective output from one system wreaks havoc on its neighboring system. And some systems outstrip the capacity of neighboring systems, crippling overall throughput of the entire enterprise. If our timespan of intention extends this far, our problems exist in the hand-off between systems and in the output capacity of one system to the next. The organization of what-we-know comes from systems analysis.

We can only know (what-we-know) what we are capable of knowing.

Timespan of Intention

Jordan was quiet. “So, it’s just a matter of what you know and what you don’t know?” he asked.

I lifted my head, “It’s what you know, what you don’t know and what you need-to-know. What you know is based on what timeframe?”

“Only the past,” Jordan replied.

“And what you need-to-know is based on what timeframe?”

“It’s too late for the past, it must be now.”

“You are correct. What do you need-to-know to help you understand the present? How does that understanding help you in the future? And, not the future of what will inevitably be, but, the future of your intentions? There are two timelines of the future, one is based on elapsed time, the other based on your intentions.”

It’s Probably Not Important

“How do you know what-you-need to know?” I asked. “You lost the contract, because you understood the problem, had a great solution, but did not know how the decision was to be made. How do you know what-you-need-to-know?”

Jordan thought for a minute. “I guess, the first step is assuming we already know everything we need-to-know. It’s easy to get suckered into thinking that what-we-know matches the reality of the situation. We have to get really clear on what-we-know and what-we-don’t-know.”

“And, what do we assume about what-we-don’t-know?” I pressed.

“We assume what-we-don’t-know is probably not important, that if it was important, we would already know about it, and included it as part of our understanding. That was our first mistake.”

—-
Hiring Talent – 2020 was released on Mon, Jan 13, 2020. Limited to 20, participants must be part of the hiring process, as either hiring manager, part of the hiring team, human resources or manager-once-removed. Program details are here – Hiring Talent – 2020. If you would like to register please complete the form on the Hiring Talent link. The first 20 respondents will receive a discount code for a $99 credit toward the program.

What You Need to Know

“Unbelievable,” Jordan shook his head. “We thought we had it nailed. We knew what the problem was, had a great solution. We were so confident this project was ours for the taking.”

“And?” I asked.

“What we didn’t know was our competitor had a relationship with their corporate attorney, who whispered in the ear of the CFO, who controlled the budget for the project.”

“So, what did you learn?”

“Sometimes, what we know about the problem and the solution to the problem isn’t what we need to know about how the decision will be made.”

—-
Hiring Talent – 2020 was released on Mon, Jan 13, 2020. Limited to 20, participants must be part of the hiring process, as either hiring manager, part of the hiring team, human resources or manager-once-removed. Program details are here – Hiring Talent – 2020. If you would like to register please complete the form on the Hiring Talent link. The first 20 respondents will receive a discount code for a $99 credit toward the program.