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.

Not Enough Time

“I gotta get something off my plate,” Adrian shook his head. “I am so busy, I just don’t have time to get everything done.”

Busy?” I asked. For me, busy is a code word, a clue, that there is a mis-match in level of work.

“Yes. Busy. I get here early to catch things up from yesterday, make some headway on one of my projects, but about 7:30, the chaos begins.”

Chaos?” I asked. For me, chaos is a code word, a clue, that there is a mis-match in level of work.

“Yes. Chaos,” Adrian replied. “Unsolved problems from yesterday. Yesterday’s decisions delayed until today. It hits my email, it hits my text messages, it hits my phone, it walks through my office door.”

“So, you think you have a problem?” I clarified. “And, if you could get something off your plate, you would have more time? And if you had more time, you wouldn’t be so busy? And if you weren’t so busy, there would be less chaos?”

“That’s it,” Adrian agreed.

“Then, why did you start coming to work so early?” I probed.

“Because I was too busy during the day. There was too much chaos during the day. I couldn’t get anything done,” Adrian was frustrated with his circular problem.

“So, you came to work early to get more time, but you are still too busy and there is still too much chaos? Do you think not-enough-time is really the problem.”

The Connection Between Time Span and Outcomes

From the Ask Tom mailbag –

Question:
Thank you for your presentation to our group. I enjoyed it very much. It strikes me that while I like the concept of time span, generally, the concept of time is relative and it’s really about being able to see down the road of potential outcomes regardless of the time-frame.

Response:
Your thinking is on the right track and you have made the connection between time span (time-frame) and potential outcomes. Let’s take it a bit further.

In a short time span project, there may be several outcomes, but the characteristics of those outcomes are concrete and tangible. In a longer time span project, the possible outcomes multiply in number with less defined characteristics.

If an audio-visual contractor bids on a contract for a audio-visual setup, 65 inch hole in the wall, with a project deadline in three months time, what goes in the hole?

  • The technology is certain – plasma, LCD, LED-LCD, OLED, QDLED
  • The display is certain – CRT, flat screen, front projection, rear projection
  • The display surface is certain – reflective surface, flat surface, curved surface
  • The manufacturer is certain – Sony, Mitsubishi, JVC, Samsung, LG, Panasonic

There are a number of possible outcomes.

If an audio-visual contractor bids on a contract for an audio-visual setup, 65 inch hole in the wall, with a project deadline in five years time (a commercial project still in the design phase, hasn’t broken ground), what goes in the hole?

  • What will be the display technology in five years time?
  • What will be the surface technology in five years time, will there even be a surface, holographic?
  • Who will be the manufacturers in five years time?

There are a number of possible outcomes, but the characteristics are more uncertain. There is ambiguity and uncertainty. So, here is the question –

Given the ambiguity and uncertainty in this project, should the audio-visual contractor accept the contract with a deadline in five years time?

Some contractors would pass, saying there is too much uncertainty, no way to say what the project will look like. Some contractors, comfortable with ambiguity and with the internal capability to adapt to emerging technologies would gladly accept the project. What is the difference in the thinking? What is the difference in the organizations?

Who Will Happen?

“Who will our company leaders be in twenty years?” I asked. “Who will our company leaders be in five years?”

There were puzzled faces around the room. “Well, it’s going to be whoever steps up,” said a voice from the back of the room.

“What if that person is not currently employed here, and you have to promote someone without the capability to be effective in those roles?”

“I guess we will have to go to the outside and recruit,” came another voice.

“And, when will you know you need to do that?” I pressed.

“Maybe, we should get a committee together in a couple of years to look into our succession planning,” said someone from the front.

“Not good enough,” I nodded. “I want to see a personnel plan from every manager, every year. A rolling plan one year out, three years out and five years out. Do we need new roles on the team, do we need to take some roles away? Which personnel are operating effectively, who needs a new challenge, who needs to be liberated to industry? What roles will be replaced by technology? What growth or contraction do we expect?

“You see, succession happens all over the organization. It’s not just top leadership. Your technicians become team leaders, your team leaders become supervisors, your supervisors become managers, your managers become executive managers. Succession happens at each level of work over time.

“Planning for what will happen is not nearly as important as planning for who will happen.”

How to Plan More Than One Year Out?

From the Ask Tom mailbag –

Question:
We just completed our strategic planning session, the output, a set of goals. And, as you predicted, all of our goals have a time frame of less than six months. How do we get our thinking out more than one year? How do we get our thinking out more than three or four years?

Response:
It’s a problem. Most companies are so results oriented, focused on tangible, concrete results, that thinking out four to five years is difficult.

It is actually a different language, one we are not accustomed to. One CEO friend of mine constantly poo-poos the idea of planning beyond six months. Here is the dynamic and why strategic thinking is so difficult.

In the near term, things, people, technology are all known elements, we can call them by name. They are concrete and tangible. The further we travel into the future, in our imaginations, the less distinct, the more ambiguous things become. If we travel far enough into the future, precise definition gives way to conceptual elements.

We no longer know who the customers will be in five years, but we will likely have customers. We do not know the exact features of our products in five years, but we will likely have a product offering. The market may not have the same requirements five years from now, but there will, indeed, be market needs.

The discussion turns from a tangible, concrete discussion to a conceptual discussion. And we do not practice conceptual talking (thinking) very often. Talking conceptually is awkward. It might even appear pointless. That is because we do not practice.

Thinking out twenty years is a useful step. Thinking out twenty years gives us permission to abandon our current thinking. So, take the year 2035. To ground this thinking, how old will you be? Now, simply imagine. What will transportation be like? What will communication be like? What will travel be like? What will food be like? What will agriculture be like? What will medicine be like? What will your industry be like? What will your products be like? What will your service be like? Who will be your company leaders in twenty years? Are they in your company or outside of your company? How old are they now?

Thinking out twenty years gives you permission to think differently. Thinking out twenty years gives you permission to think out five years in a new way.

Don’t Need a Personnel Plan

“I don’t need a personnel plan for next year,” Sean pushed back. “I have four managers who report to me, all are doing a good job, don’t see any need to replace any of them.”

“You need a personnel plan because life happens.” I said. “What if your top performer gets picked off by another company? Who do you have in reserve? Who is ready to step up? Who has the potential to fill that position?”

“I don’t know. But all my guys are pretty solid. I think they are all happy here. I don’t think they would leave even if they were offered more money,” Sean denied.

“They don’t have to leave. They might get promoted inside the company. Either way, you’d still need another manager on your team. What kind of depth do you have on any of those teams a level below? Is there anyone in the wings with the potential to move up?”

“I don’t know. I work directly with the managers on my team. I only hear about the problem people on their teams.”

“So, if one of the guys on your team gets tapped to lead a new project in another division, what would you do?”

“Guess, I would have to start from scratch,” Sean shrugged.

“So, what could you do now, to prevent having to start from scratch?”

How Many Interview Questions Should You Create?

“I don’t understand,” Ben defended. “For the entire time that I have been responsible for hiring people, I have always used the resume to ask my questions.”

“That’s because you didn’t have any other questions to ask,” I replied. “Here is the biggest problem in most interviews. Without an extensive bank of prepared questions, the judgment about the candidate defaults to how good the resume looks, first impressions and gut reactions.”

“Okay, okay. How many questions are we talking about?” Ben relented.

“You divided the tasks into different Key Result Areas (KRAs). How many KRAs do you have?”

“Let’s say six,” Ben bit his lip.

“Ten questions for each KRA, six KRAs, that means sixty written prepared questions.”

“Sixty questions, are you out of your mind. Who has that kind of time?” Ben said, pushing back.

“You can spend the time, creating questions on the front end, or you can spend the time managing behavior on the back end. The choice is up to you.”

You’re Holding the Wrong Piece of Paper

“I don’t understand,” Ben quizzed. “In the interview, I generally use the candidate’s resume to construct my questions. Aren’t I trying to find out more about them and their experience?”

“I am only interested in a candidate’s experience as it relates to the critical role requirements,” I replied. “Imagine you are sitting in an interview, candidate across the table, you have a pen in your hand to take notes. What piece of paper do you have in your hand?”

“Well, the resume, of course,” Ben looked confused.

“That’s exactly the piece of paper the candidate wants you to look at. It was handcrafted on expensive stationery, contains the voice of experience and authority, expertly written. Put it down. The resume does not answer this question. Does the candidate have the capability, skills, interest and behaviors to do the work in the role? Your job, as the interviewer is to make that decision. There is a lot of data you need to collect and it’s not going to come off of the resume.”

The Role Description is a Design Task

“There’s more?” Ben thought our conversation about role descriptions was finished. “What do you mean next step?”

“What do you think a role description is for?” I asked.

“So the person I hire knows what to do,” Ben curtly replied.

“That’s nice, but not even close,” I paused. “You haven’t hired the person, yet. So, what is the purpose of the role description? Here is a hint. It’s all about you.”

“Me? It’s not my role description.”

“No, but you are the manager. You decide what tasks need to be completed, the appropriate time it will take to complete the tasks, and the effectiveness of the person in the role. Without the role description, you have no idea how to make those decisions. Without the role description, it’s just a noodle mess in your head, a disorganized list of tasks and vague accountabilities. The first purpose for a role description is for you to organize your thinking about the role.”

“And the second purpose?”

“You are about to walk into an interview. Without the role description, you don’t know what questions to ask,” I challenged.

What If There is a Hiccup on the Project?

“I just want to be clear on this,” Roger said. “For my project, I initially asked for five hours of accounting support from your department. It turns out I needed ten hours, but you are giving me three hours from Nancy and three hours of data entry. That’s only six hours.”

Javier smiled again. “Yes, Nancy collected all the data about your project, transaction volume, your reporting requirements on the project, integration with our job-cost accounting system. With that information, I am comfortable that we can get your project accounting done in six hours a week, and Nancy will be there to make sure it is on time and accurate. You are getting a service from my department.”

“What if there is a hiccup on the project, something changes. Do I always have to go through you to communicate with Nancy? Seems like a lot of bureaucracy?” Roger challenged.

“No, you don’t have to go through me. My role is to provide you the service. I created a system for the accounting work to be done.

  • Nancy codes the transactions
  • Data entry enters the transactions into our accounting software
  • Nancy reconciles the data entry, proofs and publishes your report

So, the system is in place. Within that system, as the project leader, you have prescribing authority to directly assign tasks to both Nancy and data entry. You are right. There will be a hiccup, you can make adjustments directly. If you call a meeting with the two of them, they are obligated to attend the meeting and participate with their best efforts. As long as the system works for you, I don’t have to be involved.”

“So, what if your system breaks down? Who do I talk to, then?” Roger was still a bit defensive, not sure he trusted the system.

“Actually, I will know before you will. Nancy is acting as my monitor. If something changes, she will let me know and I will examine the system in case we need to make more adjustments.”
_________

Cross-functional working relationships

  • Service giving-Service getting – a project or department receives a service from another function or department
  • Prescribing authority – directly makes task assignments within the system
  • Monitor authority – monitors a defined system and reports anomalies to manager

Why Is Nancy So Slow?

“I knew this would happen,” Javier smiled from his chair in the conference room. “Not a big deal. Roger, when you came to me and said you needed five hours per week of accounting support, I knew you had no idea how much work it really was. You said, five hours, so I assigned Nancy, one of our staff accountants, to your project. She has a lot of other work to do in our accounting department, but I knew she would get a handle on things and report back to me on your project.”

“Yes, but, now, I need Nancy for ten hours,” Roger complained. “And, she said she couldn’t give me ten hours.”

“I know,” Javier calmly replied. “Nancy came back to me with a breakdown of the work. You need a couple of hours to code all your paperwork to the right expense accounts on your project, then some time to put that data into our computer accounting system, then about twenty minutes to proof and reconcile the output for the week. And, you are right, if Nancy was going to do all the work, it would likely take ten hours.”

“But, she said she couldn’t give me ten hours. If my project is getting a service from the accounting department, how is this going to work?”

“I talked to Nancy. She is going to do the up-front coding and she is going to proof the output, so she is only going to spend three hours on your project. And, we have a data entry clerk who can bang all those transactions into the computer system in another three hours. This data entry specialist is like lightening on a keyboard. We will still get all your work done, but it will probably only take six hours instead of ten.”

“Why is Nancy so slow on the data entry part?” Roger wanted to know.

“Nancy doesn’t practice on data entry. Her level of work requires judgment to connect the right expenses to the right account codes in our accounting system. It’s a different level of work than data entry. If your project was smaller, I would have Nancy do all the work including the data entry, but your project is bigger than you thought, so we are going to bring in a data entry clerk. That clerk just has to accurately get the data into the computer, there is very little judgment required.”

________S-II – Coding, proofing, reconciling. (Nancy)
____S-I – Data entry. (Data entry clerk)