Category Archives: Timespan

See Things With New Eyes

I am in San Diego, working with a group on the Time Span research of Elliott Jaques.

“So, what do we do next? How do we implement this stuff?” came the question at a break.

“Calm down,” I replied. “For starters, don’t do anything.”

This was definitely NOT the anticipated response. I smiled. “Look, during the past three hours, I have described a new way of looking at your organization, a new way of looking at work, how roles are created, how accountabilities are designed into those roles. So, stop. Don’t do anything.

“Sit, and watch. Observe. See things with new eyes. Describe what you see, first to yourself, then to someone else. That is the first step.

“So, tell me, with your new eyes, what do you see in your organization? What is going on?”

How Big is the Role

From the Ask Tom mailbag:

Question:
I’ve been using your interview guidelines for determining Time Span for some time. I’ve asked candidates, “Tell me a time when..” Often, the candidate picks a project and the time span is very short. I’ve even probed deeper, asking for a particularly challenging project and still I sometimes can’t get anything more than a few weeks. So I would conclude this person’s role is operating in a relatively short time span. But I worry that the candidate is picking a project that just happened to be short but has accomplished more. He or she just isn’t articulating it.

Response:
In my workshop, I share some interview guidelines, and I suggest that managers practice those questions on their own team members (the groundwork for your question). I caution managers not to be surprised at the mis-match between the managers definition of the role and the team members perception of the role. This mis-match in expectations is the source for a great deal of management angst.

Indeed, most team members in Stratum I, II and III roles rarely have conversations with their managers about the real depth and breadth of their role. They never discuss how “big” those roles are. Time Span is helpful, because we can calibrate the complexity of the task at hand and avoid the mis-match in perceptions.

For example, we can talk about the temperature, which I experience as warm and you experience as cold, based on our internal body thermostats. I say “warm” and you say “cold.” We are both right, according to our personal experience, but it will be difficult to come to an agreement. However, if we look at the thermometer on the wall, we can both agree that it is 72 degrees.

Time Span helps us calibrate expectations between a team member and a manager. Time Span helps us understand the “by when” of any goal, any task assignment. Time Span is the thermometer on the wall.

You, as a manager, with an understanding of Time Span see the team member’s role in a different way. Without those discussions, I am never surprised that the team member grossly underestimates what is really required for success in their role.

So, you may think my interview guidelines give you insight into a team member’s Applied Capability, but it is really the beginning of a rich conversation about expectations.

Pay Now or Pay Later

“When you were putting this team together, why did you overlook this role on the team?” I asked.

Susan looked at me sideways. “What do you mean?”

“You put this team together, and yet you are dissatisfied with the problem solving capability of the team. They keep running into the same problem over and over, yet always have to go back to square one to solve it.”

“Aw, come on, you know I have a budget. I got the best people I could afford,” she replied.

“This is not a matter of budget, this is a matter of design. I have talked with your team and you have a great bunch of people. But you are missing a role. When you designed your team, you missed a role.”

“What do you mean, designed my team?” Susan asked.

“You thought about the people you needed to do the production, but you never thought about building in one role to make sure production got done. Someone to watch the schedules, create your checklists and see patterns in problems. That is the capability you are missing on your team.”

“Yes, but I can’t afford another person on the team, and besides, I would have to pay more for someone with that capability,” she defended.

“You are going to pay for this role anyway. Without this role, you will have problems that stop the line, re-work on elements that have to be done twice and overtime. You are paying for this role anyway.”

Quit Complaining

Susan was beside herself, “I don’t understand. This is the same problem we had last week with another customer. I got a phone call and two text messages. You would think my team would figure this out. It’s the same problem, all over again.”

“Why don’t they see the problem?” I asked.

“Oh, they see the problem, they just don’t connect it up. They don’t see it’s the same problem as last week.”

“What do you think they should do about it?” I pressed.

“They can’t do anything about it, if they can’t see it’s the same problem. It’s like they have to start all over, back to square one.”

“Like Groundhog Day?”

“Yes, like Groundhog Day,” she replied. “I just wish I could find someone on the team, who could step up and see the pattern, connect the dots together.”

“So, who put this team together?” I smiled.

Susan became very quiet, then finally spoke, “I guess I should quit complaining and find that person.”

Measuring Capability

“So, if it’s not experience and it’s not skill, what is it?” came the question from the corner.

We had been discussing how you compare the “size” of the role to the “size” of the person.

“Elliott called it capability,” I replied. “One of the largest determining factors (not the ONLY, but the largest) for success in any role is a person’s capability.”

“Aren’t we talking semantics here. Of course, a person has to be capable. Duh!”

“It would be semantics, if capability were just some vague notion. But Elliott found a way to measure it. And it’s not experience, skill, personality or passion. Capability is something measurable, something different inside of each person, something that matures over our lifetime.

“Each of us is born with an innate capability to handle a certain level of complexity in the world. The measure of capability is Time Span. How long into the future are we thinking and executing?

“Two team members, side by side. One can handle a project, as long as its completion date is within the week. The other team member, with higher capability, can plan and execute a project that takes two months to complete. Any competent manager, thinking about their team, can immediately put names to the person with one week capability and the person with two month capability.”

It’s Not Training

“How big is the role, and how big is the person filling the role?” I repeated.

“That’s why training is so important,” came a reply from across the table.

I nodded. “Yes, having the proper skill and being competent in that skill is important. And skills can be trained. And how many of you have sent two people to training, one gets it, the other doesn’t?”

The chuckles confirmed the answer.

“So, what’s the difference between the two people. It’s not experience. It’s not training?

What’s at Play is Not Experience

“How big is the role, and how big is the person filling that role?” I asked the group. “Elliott calls this the size of can. How big is the can and how big is the person filling the can?”

“Well, certainly, experience is something we look at,” came a retort from the far corner of the table. “The more experience someone has, the larger role they can fill.”

“Experience is certainly something most managers look at,” I replied. “And how often does experience lead us astray. In fact, does someone have ten years’ experience or one year’s experience ten times? How many of you have placed someone, with experience, in a role, only to find them failing after a few short weeks? What did we miss by relying on experience as our determining factor?”

Who the Hell was Elliott Jaques?

“Who was Elliott Jaques, and what was his research all about?” There were six of us seated around the table and the question floated like a pass from Drew Brees.

My usual response to that question takes 3 hours, but it was late and I had to be up early. I struggle with that question, because any response is the first step in a long and important journey for any manager. But still, it was late and I had to be up early.

“Elliott Jaques was the most profound management scientist on the planet,” I began. “His study of organizations spanned more than 50 years, generated 23 books and left a legacy for every manager to follow. Elliott observed that each person has, within themselves, an innate ability to deal with a certain level of complexity in the world. Some people are quite comfortable working on projects that will not be completed for one year or more; some cannot manage to get beyond next week.

“Each of us is different. And that difference is measurable.

“As managers, we look at the individuals on our team, and we make running intuitive judgments about what tasks we can assign to which person. It is that judgment — about who can do what, by when? — that was the focus of Elliott’s research.

“How big is the role, and how big is the person filling that role? This is not about personality or a skill set. This judgment is about capability.”

But it was late and I had to be up early.

Why Do People Work?

Next Monday is Labor Day in the US. And I wonder, why do people work? Elliott Jaques is very specific in his response.

“People want work in which they can have the opportunity to exercise their full potential capability, to spread their wings widely, to receive a fair compensation for that work and to be recognized and understood as not needing artificial carrot and stick treatment on order to get on with that work.

By work, I mean an organism’s use of judgment in making the decisions necessary to reach a goal. Goal directed work is a basic feature of all life.

All humans need to do work that not only benefits oneself, but is, at the same time, of value to others.

It may be noted that, not only do millions gain work opportunities by becoming engaged in employment, but need something on the order of 40 hours per week of such engagement. That is what explains the fact that the employment work week, which came down to 40 hours during the first half of the twentieth century, has gone no lower. Any smaller number of hours is not sufficiently fulfilling. Indeed, people who work on their own, routinely spend many more than 40 hours per week.”

Elliott Jaques – Social Power and the CEO