Category Archives: Teams

Steps to Necessity

Leave a reply

“My question still stands,” Erica was insistent. “How do I get my team to the point where they believe performance is necessary?”

“It starts with competence,” I replied. “We cannot perform at a level where we are not competent. If we are not competent, then, not only will it NOT happen, it cannot be believed to be necessary. So, the first step in believing in the necessity of performance is to build the competence required.”

Erica was a good student. “And, competence is a combination of capability, skill and practiced performance?”

“Moreover,” I responded, “if we have the capability, possess the required skill and practice to the point of habit, then necessity follows. The habit of pace, at quality spec, produces the necessity of performance.”

Broccoli and Power

Leave a reply

“So how do I get my team to the point where they believe in what is necessary? How do I make them believe?” Erica was stumped.

“Indeed,” I said. “If your team doesn’t believe it is necessary, you cannot make them believe. Sure, you can trick them with a bonus or maybe a plaque, but it is still a trick.”

“Like your broccoli story,” Erica remembered, “I have the authority as a parent to command broccoli, but my child has the power to determine if broccoli will be eaten?”

“Yes,” I nodded. “If you feel the need to compel behavior, does that say anything about the power others have over you?”

Nature of Necessity

Leave a reply

“How does necessity work?” Erica wanted to know.

“Think of something in your life that is necessary, nothing complicated, but something you do that is necessary,” I replied.

“Okay, I brush my teeth, not because my mother told me, though that is how I started, but because I believe it is necessary.”

“So, in the beginning, your mother told you, and you followed, not because it was necessary, but because you knew you she would continue to remind you until you complied.”

“And, now,” Erica picked up, “I do it because I believe it is necessary.”

“Now, think about your team. You want them to do something, perform at a pace, and in a way that meets a quality spec, because you believe it is necessary?”

“Yes,” Erica nodded.

“But is your team doing it because you believe it is necessary or because they believe it is necessary?” I prompted.

Erica shrugged. “No, they are only doing it because I told them to do it.”

“And, they will continue to do it as long as you are around to remind them to pick up the pace and pay attention to quality. But, the instant you are gone, they will only do what they believe is necessary. Necessity is not what you believe, it’s what they believe.”

Of Competence

Leave a reply

“Where do I start?” Melanie asked. “I have things that I will ask my team to do. Each thing has a performance standard that is necessary. If you say the only measure of performance is performance, where do I start?”

“Before you put performance to the test, you must assess, take an inventory of your team. What are the things we examine when we look at performance?” I asked.

“First is competence,” Melanie replied. “If the team, and its members, are not competent, they will fall short.”

“And what is competence?” I pressed.

“Competence is a combination of capability and skill,” she nodded. “Capability is the cognitive ability to see the goal at some time in the future, organize the activity to get there and accommodate all the obstacles that may or not get in the way.”

“And skill?” I said.

“Skill is made of two things,” Melanie thought out loud. “There is always some technical knowledge that must be accounted for, but then practiced performance, over and over until the action is smooth, without friction.”

“So, competence is where you must start,” my turn to nod. “Is your team competent to accomplish the goal you have in mind, as the manager?”

The Measure of Performance

Leave a reply

“I don’t know what happened,” Bella said out loud. “We met, we planned, everyone had their role, we all committed with the best of intentions.”

“And?” I asked.

“And, the project failed,” she replied. “I mean, I have to give the team an A for effort, but at the end of the day, the project fell short, the customer was disappointed and we lost the rest of the contract.”

“So, you learned a valuable lesson,” I nodded.

“Yeah, what’s that?” Bella pushed back.

“That, of all the things we do, all of our planning, all of our training, all of our meetings, the only thing that matters is performance,” I said. “The best measure of performance is not a spectacular plan, or lofty intentions. The only measure of performance is performance.”

Trouble

Leave a reply

“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 Same Problems Follow the Same People

Leave a reply

“As I look at my team,” Logan began, “the problems I see and the problems individual team members see are sometimes different.”

“When that difference exists, it clearly demonstrates the difference in your aim, your goal, and the goals of the individual team members. The goals you have will dictate the problems you have.”

“You know I have always wondered. There was someone who, during the job interview constantly complained about their former boss. At some point, they came very close to calling him an asshole. I didn’t hire that person. For some reason, I was certain that I would be the next asshole in that person’s life.”

Thinking, Talking, Doing

Leave a reply

“I’m a little disappointed with my team,” Jesse nodded, looking down.

“And?” I asked.

“We were in the meeting, talking about a new method in one step of our production. It’s way faster and prevents the defects we were seeing during that step. I know it seemed strange to the team, but they said they would trust me and do it the new way.”

“And?” I repeated.

“It was like we didn’t even have the meeting. They talk a good game, but what they say and what they do are different. I wish I knew what they were thinking.”

“Does it really matter what they were thinking. My guess is they were thinking you had a new way. They were thinking it seemed strange. But, they were thinking they trusted your new way. Thinking, even talking is no assurance of behavior. If you want insight into someone’s behavior, watch what they do.”

People Problems

1 Reply

“People problems,” Sebastian shook his head. “It’s always people problems.”

I smiled. “Yes, you can think people create all your problems, AND they are also the only ones who can create your solutions.”

“So, I can have it both ways?” he chuckled.

I continued to smile. “The way you see your people will determine the problems that land in your lap, and whether those problems arrive with solutions attached. If people are only the source of your frustration, you will find only more problems. If people are also the source of your solutions, you will find inspiration and joy. You get to decide how you see your team.”

Learning From Mistakes

2 Replies

“We got it,” Roland said. “This was very painful, to examine the sequence of events that caused our last project to fail. It cost us a lot of money, wasted energy and almost got us sued. But, I think we know how it happened. Expensive lesson.”

“So, you are trying to learn from your mistakes?” I replied with a question.

Roland nodded in agreement. “I think it is important, part of our debrief, a post-mortem.”

“It’s valuable to look at your mistakes,” my nod matched Roland’s nod. “What did you miss?”

“It’s a very tough client. They had an unreasonable timeline, very demanding, put us under a lot of pressure,” he replied, as if his team had been tortured.

“I assume you knew this client?” I stared. “I assume you looked at the project schedule, and agreed to it. You knew what the stakes were. These are NOT things you missed. What did you miss?”

“I was just trying to tell you why it was such a difficult project for us,” Roland pushed back. “Final analysis, I don’t think we missed anything.”

“People always tell me they learn from their mistakes. Mistakes are rarely that instructive. The reason we don’t learn from our mistakes is that we fail to examine our own contribution to the problem. You are going to have difficult customers, with unreasonable demands inside a high pressure project with tight deadlines. All of that was known before you signed the contract. What you missed, your failure in the project was not due to the project. The failure was your assessment of your internal capability, or lack of capability. Your contribution was that you ran out of talent.”