Category Archives: Timespan

Tactical vs Strategic

From the Ask Tom mailbag –

Question:
You seem to challenge the name of our annual planning exercise that we call Strategic Planning. We are clear that exercise is conducted away from the office, off-site, so we are not dragged into the minutiae of the day to day. We do our best to be strategic.

Response:
One reason I know that most Strategic Planning Meetings are not strategic is by a quick examination of the action item list that emerges from the meeting. Rarely is there a single action, goal, objective with a due date further out than 12 months. There is nothing wrong with tactical plans, we need them, but don’t mistake a strategic session just because that is what it’s called.

Looking at Elliott’s framework –

  • S-I – 1 day to 3 months – Tactical
  • S-II – 3 months to 12 months – Tactical
  • S-III – 12 months to 24 months – Tactical
  • S-IV – 2 years to 5 years – Transition from Tactical to Strategic
  • S-V – 5 years to 10 years – Strategic

Some would push back that there is no point in planning 5 years out because so much will change by the time we get there. Exactly.

Tactical planning is short term (up to two years) where things are knowable and we can call them by name. Strategic planning is long term where things are NOT knowable, where there is uncertainty and ambiguity. Yet, in the face of that uncertainty, we still have to make a decision today. Foolhardy to make a tactical move without a longer term strategy.

The biggest problem is in the language of strategy. When things are uncertain and ambiguous, we can only speak in terms of concepts. And, we don’t practice speaking conceptually very often. Most CEOs and managers, given a problem to solve, want to fix it. Fixing is tactical, so before we even have the conversation, we have to rethink the discussion.

Five years from now, we will have customers, we just might not know who they are. We will have facilities, but perhaps not our current facilities. We will have employees, but we don’t know who they are, how many or what they may be doing. We still have to think about markets, infrastructure and human capital even when we don’t know what that might look like in the future. Four years from now, your five year plan will be your one year plan.

Timespan of Intention

From the Ask Tom mailbag –

Question:
Sometimes, I question my assessment of a team member’s capability. At times, I am delightfully surprised, other times, disappointed.

Response:
Timespan assessment of capability is a manager’s judgement. There are clues, but most of the time, managers look in the wrong places. Here is the text from my slide defining Timespan.
Timespan is the length of time a person can effectively work into the future, without direction, using their own discretionary judgement, to achieve a specific goal.

Effectiveness is not a metric, it’s a judgement. Often, goals are stated to allow for some measurement at the end of the day. The problem with the metric, it does not take into account the unanticipated obstacles that get in the way. A sales metric of 100 units does not take into account the stiff competition from a company with superior technology, economic contraction in the marketplace or a new government regulation the influences a reluctant market. Often a successful sale has more to do with the company’s reputation in the market, than the direct effort of a salesperson. The goal (metric) is one important data point in the judgement of effectiveness, but it is not the only data point.

Self-initiated action. Part of effectiveness is to determine, who is doing the problem solving and decision making? Most people can follow a system, but it takes a higher level of capability to create the system.

Discretion is decision making. A decision is not a calculation, it is a judgement. If decisions were calculations, then computers could make all decisions. Many human based decisions are now better calculated with computers (AI), because computers can detect data faster, with more precision. But, a decision is a judgement, a judgement in the face of uncertainty and ambiguity. The longer the timespan of the decision, the more uncertainty exists.

All action is goal directed. Timespan of discretion relates to the decisions that must be made in the pursuit of the goal. Timespan of intention is related to the direction of that behavior. Elliott Jaques was quite interested in that fifth dimension of human behavior, the timespan of intention. All behavior is goal directed behavior.

Measuring Complexity

Lester had just returned, “That’s it boss, all done, what’s next?”

And with those innocent words, Lester has just defined the time-span for that specific task. Why is the time-span of a task so critical to the definition of that task? It is an attribute often overlooked. Time, hey, it takes what it takes.

For simple tasks, that take less than a day, or even 2-3 days, the importance of time-span is not so critical, but extend the time-span of a task (or a role) out to a week, out to a month, out to three months, and the dynamics become interesting.

What differences are there between a task that takes 3 days to complete and a task that takes 3 months to complete? In one word, predictability. Most of the elements required to complete a 3 day task are known, very specific, very concrete. Some of the elements required to complete a 3 month task may be unknown or may change prior to the completion of the task. This predictability (or unpredictability) is what makes one task more complex than another. “Yeah, so what’s the big deal about that?”

The “big deal” is that time-span, as an indicator for complexity, can become a discrete unit of measure for the complexity of any task. How complex is a task? If you can describe the time-span of the task, you have just described the complexity of the task. The importance of this measurement is that time-span can be described very specifically. I may not know how to specifically measure the “complexity” of a task or project, but using time-span, I can nail it to the wall: This project has a three-month time span with a deadline of February 15.

Questions:

  • If I can measure the complexity of a project using time-span, can I select a Project Manager using time-span?
  • If I can determine the maximum time-span of a person, can I determine suitability for a role in our company?
  • Can I test a person on the basis of time-span , as they grow and mature, to determine capability for more responsibility?

Hint: the answer is yes.

Overwhelmed Behaviors

From the Ask Tom mailbag:

Question:

What happens when you realize you were given a promotion and not able to live up to the capabilities? Do you admit it to your superiors? Do you keep it to yourself and risk failure?

Response:

There are many ways to survive in a position that’s over your head, but in the end, it’s only survival. Not a way to live.

I often ask managers, “How do you know, what behavior do you observe when a person is in over their head? Where the Time Span for the position is longer than the Time Span of the person?”

The descriptions come back.

  • They feel overwhelmed.
  • They cover things up.
  • They cut off communication.
  • Their projects are always late.
  • I can’t ever find them.
  • They always blame someone else.
  • They have all the excuses.
  • They never accept responsibility.

So, the short answer is yes. When you realize you are in over your head, go back to your boss. Explain the difficulties you are having. Ask for help. If it is a matter of capability (Time Span), no amount of training, no amount of hand holding will help. It is possible that you may grow into the position, but it’s more likely a matter of years, not weeks that allows for the required maturity (increase in Time Span).

This doesn’t make you a bad person, it just means you were placed in a position where you cannot be effective. Yet!

The Bigger Context

“But, what if my team has some bone-headed ideas?” Francis pushed back. “There are a couple of people on my team that think I’m an idiot, that they have a better way to do something.”

“Occasionally, we are all idiots,” I replied. “Perhaps, on occasion your team is accurate.”

“But they don’t see the big picture,” Francis described. “They think I delay part of a project because I don’t know what I am doing, when the fact is, we are waiting on parts with a six week lead time.”

“So, it’s context?” I asked. “And, you don’t think they will understand a six week delay in parts?”

“They have trouble just figuring out what materials we need for today’s production, much less a part that won’t be here for six weeks.”

“Francis, this is a struggle for all managers. Your team is working day-to-day or at best, week-to-week, but they are impacted by events that happen month-to-month, or quarter-to-quarter. Don’t sell your team short. They may not be able to manage long lead time issues, but they can certainly understand those issues, particularly if you make them visible. In what way could you communicate project scheduling to your team in a way they would understand?”

Who Controls the Variables?

“What is structure?” Melanie asked. “I draw boxes and circles, with lines and arrows. The question that guides me is – who reports to whom?”

“And, that would be accurate,” I replied, “if you worked in a command-and-control, reporting environment. This misconception about most organized companies leads us astray.”

“But, that’s my central question, my guiding principle when I put the org chart together. Who reports to whom?”

“Indeed, as managers, we sit around the table discussing a new recruit coming into the company tomorrow. And, the question is, who should this person report to? Quite seriously, it’s the wrong question.”

“I’m listening,” Melanie replied.

“It’s not a matter of who this young recruit will report to, but which manager, around the table, will be accountable for the output of this new hire? It’s not a matter of reporting, it’s a matter of accountability, and it’s the manager who is accountable.”

“Seems upside-down,” Melanie observed.

“Does it?” I responded. “Think about it. This new person comes into the organization. Who designed the role for this person to play? Who determined what this person should do? Who determined the quality spec of the output? Who selected this person to play this role? Who trained the person? Who provided the necessary tools, created the work environment? Who controls all the variables around this person?”

Melanie paused, the answer so obvious. “The manager, of course.”

“Then, why should the manager not be held accountable for the output of this new hire?”

To the Next Level

From the Ask Tom mailbag –

Question:
As I talk with other CEO friends, they keep talking about taking their company to the next level or that they want to scale their companies larger. It sounds like they know what they are talking about. But do they? They are my friends, and I don’t want to disparage, but in many cases, I have my doubts.

Response:
No organization can ever grow larger than the CEO. If it does, the wheels will get wobbly and the organization will falter. The same is true as levels of work are built inside the organization. No level of work can exceed the capability of the manager. If it does, the wheels will get wobbly and the organization will falter. It doesn’t matter if the company is S-I, S-II, S-III, S-IV or S-V. Faltering can happen at any level.

Most who say they want to take their company, or department, or team to the next level has no clue what that means. Timespan and levels of work create the only framework that clearly identifies what that means.

Scalability doesn’t happen until S-IV, where multiple system integration occurs. Listen carefully to your friends, but judge not what they say, only judge what they do (or are capable of doing).

How Many Levels?

From the Ask Tom mailbag –

Question:
You recently described an organization as having five levels. You also said that some organizations don’t need five levels. I am trying to figure out how many levels our company needs?

Response:
Your question is similar to the manager’s span of control issue. The consultant’s answer, “it depends.” The number of levels in an organization depends on the complexity of the decisions and problems faced by the company’s mission. That’s why it is important to occasionally sit down and revisit the mission. We think of mission as “what the company does,” but it also includes which markets, geography of those markets, market segments, governing rules and regulations, availability of labor, incorporation of technology, availability of capital. All of these elements play in to the complexity of the organization.

The initial mission always exists in the individual eyes of the founder. In the beginning, that mission may be modest, simply to prove the concept is viable (minimum viability). With early success, the mission can grow, be redefined as the organization learns more about the environment it created. And we think, with more levels, the more success we see. That is not altogether true. You can have a successful organization at any level, with an appropriate number of managerial levels, even an organization with just one.

S-I (One level of work) – This is the sole practitioner, an individual technical contributor, whose mission is to solve a narrow market problem requiring only one mind, usually supported by technology. Successful sole practitioners could be an artist, writer, even a computer coder developing a single application to solve a market problem. A good living can be had by the savvy sole practitioner, though it is rare to reach any large scale by yourself. (Timespan 1 day – 3 months).

S-II (Two levels of work) – This is the sole practitioner who gathers surrounding assistance. There is too much work for one and that additional work is necessary to solve the problem. At this organizational level that additional work requires coordination for quantity output, at a given quality spec, according to a deadline time schedule (QQT). There is no system yet, because the quantity or complexity of work does not require it. This could be a entrepreneur with a small team. It could also be that the organization requires a system, but does not possess the internal capacity to develop that system. Many successful S-II organizations simply purchase their system from someone else, as a franchise or a license from a larger organization (who has a system for sale). (Timespan 3 months – 12 months).

S-III (Three levels of work) – But even a small franchisee, with one or two stores, who wants to increase to three or four stores, eventually requires an internal system. At three to four stores, an additional level of work appears. It is interesting that one of the larger franchisors, Chick-fil-a only allows one store per franchise. This may be an unconscious realization that the capability of their franchisees is limited to S-II. The hallmark of an S-III organization is a single serial system (single critical path). This is often an artisan craftsman, a subcontractor on a larger project. (Timespan 1 – 2 years).

S-IV (Four levels of work) – Consists of multiple parallel systems that have to be integrated together. S-III as a single serial system is limited in its growth. For an S-III company to scale, it requires the coordination of multiple systems. From its core production system, the S-IV organization also has to coordinate material purchasing, equipment procurement and maintenance, personnel recruiting and training, marketing campaigns, sales efforts, legal review, project management, quality control, sustaining engineering, R&D, human resources and accounting.

S-V (Five levels of work) – This is the enterprise in the marketplace. And, the marketplace is not just about customers. Marketplace includes regulation, labor, finance, technology, competition, logistics, supply chain. This is still within the Small to Medium Enterprise (SME) but also extends to larger organizations.

An organization can be successful at any level, it is governed by the level of their mission.

Maximum Number of Team Members

From the Ask Tom mailbag –

Question:
I read with interest your response on the number of levels in an organization. It sounds good, but as the organization grows, we need more and more managers. It is difficult for a single manager to handle more than 6-7 people on the team. With more managers, don’t we end up needing more layers.

Response:
I would first challenge your assumption on the maximum number of team members for whom a manager is accountable. Your number of 6-7 has no basis in theory or fact. Elliott was often asked this question, let me whisper his number, 70. It is likely that a single manager will begin to struggle when the number of team members reaches 70.

I know the blood just drained out of your face, so as your brain is restoring its circulation, let me explain. The maximum number of team members a manager can effectively be accountable for depends, not on an arbitrary number like 6 or 7, but, rather on the variability in the work.

Large call centers may easily have 70 people on the floor at any one time, with a single supervisor. How can a single supervisor be accountable for the output of 70 people? Look at what those people do. Most of the time, those call center team members do the same work day after day, there is little variability.

How many people on a Navy Seal Team? I would guess six. Why such a small team? The variability of the work is high. The number of people a single manager can be accountable for depends on the work.

Without a frame of reference, organizations do get bloated. I once worked with a company with 12 layers, but only needed 5. Levels of work creates the frame within which we can determine not only who should be whose manager, but how many managers are at the same level. The objective measurement of timespan takes out the guesswork and bias that inevitably creeps in. About once a year, you should round up your managers for a calibration meeting to make sure the bloat is not settling in.

Why Organizational Structure?

What is organizational structure? On a single piece of paper, it’s called an org chart.

Organizational structure is simply the way we define the working relationships between people with the organization. All social settings have a social structure. Parent-child, teacher-student, politician-constituent, minister-congregation, coach-player, manager-team member. The social structure helps us understand what is expected and what are the norms of behavior.

Organizational structure in a Management Accountability Hierarchy (MAH), helps us understand the working relationships between people in the company. It is important to know who has the authority to make decisions, the authority to solve problems (the way we would have them solved), but most importantly, who is accountable for output.

Managerial roles are stacked in levels of work so we can more quickly understand the context in which that role is working.

Levels of Work

  • S-V – Business Unit President or SME CEO. The context is on the entire enterprise as it sits in its marketplace.
    Timespan 5-10 years.
  • S-IV – Executive manager. The context is the many parallel systems that have to work together. Timespan 2-5 years.
  • S-III – Manager. The context is on a single serial system, or a single critical path. Timespan 1-2 years.
  • S-II – Supervisor. The context is on the work in hand in the near term. Timespan 3-12 months.
  • S-I – Production. The context is on the work in hand today, tomorrow and next week. Timespan 1 day to 3 months.