Author Archives: Tom Foster

About Tom Foster

Tom Foster spends most of his time talking with managers and business owners. The conversations are about business lives and personal lives, goals, objectives and measuring performance. In short, transforming groups of people into teams working together. Sometimes we make great strides understanding this management stuff, other times it’s measured in very short inches. But in all of this conversation, there are things that we learn. This blog is that part of the conversation I can share. Often, the names are changed to protect the guilty, but this is real life inside of real companies.

Timespan of Intention

It’s January, with resolutions, goal setting, annual planning.

Most of our intentions are short-sighted. We focus on the what, not the by-when. Perhaps this year we examine the timespan of our intention as closely as the intention itself?

Instead of how many pounds can I lost by the end of Feb (when most resolutions are abandoned), we might ask what lifestyle changes we can make to add ten years to our life. What is the timespan of your intention?

Sometimes, the most important impact is not a major initiative. Sometimes, the major impact is shifting a small habit that is insidiously killing you. Or a small habit shift that will pay off in spades five years from now.

Think about your habits that support your success, habits that detract. What is the timespan of your intention?

And To All

Originally published Dec 2005.

As Matthew looked across the manufacturing floor, the machines stood silent, the shipping dock was clear. Outside, the service vans were neatly parked in a row. Though he was the solitary figure, Matthew shouted across the empty space.

“Merry Christmas to all, and to all, a good night.”

He reached for the switch and the lights went dark. He slid out the door and locked it behind.

We hope you all have a wonderful holiday. Management Blog will return on January 3, 2022.

Merry Christmas and Happy Holidays. -Tom Foster

Almost Time

At some point during the next few days, life will turn from frenetic holiday chaos to moments of family, friends and reflection.

Take a deep breath and exhale completely. The stress will melt away.

It is almost time to rest and renew.

Gather those around you and wish them well. Smile at yourself for you have accomplished much this year.

It’s the Hug

It’s not the thought that counts. It’s the hug, the squeezed hand, the warm smile, sharing a cup of coffee, dropping by, saying hello, listening.

It’s the card from a friend with a special note, calling to talk about things more important than the weather.

It’s sitting with a family member through a tough time, standing up for someone in their proudest moment.

Sometimes it’s just showing up and being fully present.

Management Work

Ruben was stumped. “You are right. Just because we give Edmund a new title, doesn’t mean he is going to change his ways.”

“Edmund will always be Edmund, and we have to redefine his role. It’s not a matter of giving him new rules not to do this or not to do that. You have already tried that in his role as supervisor. As Lead Technician, what will be his new goals? How will you re-direct him?”

“It sounds obvious,” Ruben replied. “It starts with his job description.”

I nodded affirmative. “This is critical fundamental stuff. It’s the stuff you ignore because it sounds so simple. It’s the stuff you ignore that gets you in trouble. Stuff like goals and objectives, performance standards and holding people to account for performance.”

“I think I have a job description around here that might work,” Ruben hoped.

“Why don’t you start from scratch. As the manager, you have time span goals of approximately one year. Your annual plan has stuff in it that you are held accountable to deliver this year, and next year. If you had a supervisor, which Edmund isn’t, you would drive some of those goals down to that level, in time span appropriate chunks. For the time being, you are going to have to step into that role, review those supervisor outputs and determine the time span appropriate chunks (goals) for your new Lead Technician.”

Ruben was quiet.

“Look, do you want to lose Edmund?” I asked.

“No way,” Ruben replied. “He’s a great technician.”

“Then you have some management work to do.”

Cannot Continue This Way

“Our system creates predictability,” Ruben explained. “It creates predictability without stress. It allows us to do our maintenance at the best times, allows us to properly inspect our raw materials, test our setups accurately. Everything runs.”

“What are you going to do with Edmund?” I asked.

“He should never have been promoted to supervisor. He is a great technician, a great operator, our go-to guy. We don’t want to lose Edmund, but he cannot continue as supervisor.”

“What are you going to do with Edmund?” I repeated.

“I am going to assign him to a new role called Lead Technician. He won’t like it, and, right now, I run the risk of losing him. The job market is too fertile, lots of other companies would like to have Edmund.”

“How are you going to keep him from screwing things up, just because he has a new title? And how are you going to keep him.”

Effectiveness

“So, in your mind, Edmund is not a hero?” I prodded.

Ruben shook his head. “No, and what’s maddening is that Edmund, as a supervisor, keeps describing his behavior as results oriented. It’s all about the results, he says. So, maybe he delivers, but there are body bags all over the place.”

“So, notwithstanding the results, how would you describe his effectiveness, as a supervisor? Thumbs up? Or thumbs down?”

Ruben laughed. “You know, that’s it. Effectiveness. If I can judge his effectiveness, it’s thumbs down. A supervisor is not effective when he ignores the metrics, skips steps in the process, then works overtime to save the day when the system breaks down.”

Midst of Created Chaos

“How do you involve Edmund in the decision making about solving the problem?” I asked.

“As soon as we have the project specs,” Ruben explained, “when we know the outputs and the deadlines, we call a meeting. Edmund is the supervisor, so once we get into production, he is the one to call the shots. So, he is there, at the meeting. He sees all the elements we see, he just cannot connect them together.”

“And?”

“We have developed a very thorough system that identifies the constraints and keeps them productive. The metrics are easy to follow and the system makes our throughput very predictable. But Edmund fights the system, ignores the system and almost weekly causes a production snafu that could have been prevented.”

“How does he explain the snafu?”

“Usually he manages to jump in and pull the project out of the fire, but not without some overtime and not without putting the project in jeopardy. It’s almost like he is proud of the chaos and being the hero.”

Subtle Pushback

“He resists everything,” Ruben explained. “We cover the same solutions to the same problems. At the time, Edmund finally agrees, but I sense, he agrees only because he can’t argue the logic. He goes along with the solution, but two weeks later, the same problem pops up and we start all over again.”

“So, you have to step in and it takes up your time?” I asked.

“Worse than that. It’s almost underhanded. Behind the scenes, it’s like he wants the solution to fail. He doesn’t openly sabotage the new method, and I haven’t caught him bad-mouthing the process. Sometimes, it’s just the way he rolls his eyes in the meeting.”

Constructed, Tested, Adopted

“Easy to answer the negative, more difficult to answer the positive,” I repeated. “In what way can we create the conditions where creative ideas can be constructed, tested and adopted?”

“I remember reading something from a long time ago, about a company that had something called skunkworks,” Susan was thinking. “It was still inside the company, not really a secret, but hidden away somewhere.”

Lockheed Martin, America’s first jet fighter,” I explained. “Why do you think it was hidden away, not a secret, but out of sight?”

“They were probably experimenting with things where they did not know the outcome and the probability of failure was high. My guess is that, when there were failures, no one knew about it, so nobody got fired.”

“Exactly, the probability of failure was high, so the skunkworks were separated from operations, there was no real impact, no downside consequences. So, if the probability of failure was high, why did the company tolerate it?”

Now, Susan smiled. “Because the possibility of upside was substantial. And, they had to work all the kinks out of the ideas. There were likely failures along the way, but the company minimized the risk while they were making headway.”

I repeated my question, “In what way can we create the conditions where creative ideas can be constructed, tested and adopted?”