Category Archives: Timespan

Individual Technical Contributors and Levels of Work

From the Ask Tom mailbag:

Question:
Attended your workshop last week. I understand Levels of Work related to a manufacturing business model, but we are a financial services firm. How do we approach Levels of Work in our company. We simply don’t have Stratum I production workers. In fact, our producers have to help people make decisions that will impact their lives 10 years, 20 years down the road.

Response:
Financial services, attorneys, CPAs, architectural firms, engineering firms all share a similar approach to Levels of Work. Indeed, production work in professional services often rises to Stratum II, III, IV or higher. For a more specific discussion on Levels of Work in a CPA firm, you can visit this post.

But your question leads me to a more general discussion of Levels of Work from individual technical contributors. In the workshop you attended, we focused on Levels of Work in a manufacturing business model. That model illustrates the following managerial roles –

  • Stratum I – Production
  • Stratum II – Supervisor
  • Stratum III – Manager
  • Stratum IV – VP
  • Stratum V – Business Unit President

But, in professional service firms, there are individual technical contributors whose capability, Level of Work, may land in any of these Stratum, depending on the complexity of the problems to be solved and the decisions to be made. I find it interesting that you easily made the leap in your question, that you have individual technical contributors helping people make decisions that will impact their lives 10 years and 20 years down the road.

Time Span gives us critical insight into the capability required for these technical roles. Indeed, these technical roles may not manage other people, but, rather, manage the uncertainty of technical projects into the future.

So, yes, your production work in financial services, is most likely Stratum II, III, IV or above. And it likely depends on the age of your customer, your customer’s own Time Span capability, even the size of the estate.

Making simple decisions inside a young employees 401(k) plan is quite different than the complexity of the decisions to be made where trusts (revocable or irrevocable) and other large estate decisions must be made.

Can’t Put a Schedule Together

Morgan was complaining. “You have been talking about checklists and schedules as the core tools for Project Managers and Supervisors. It just doesn’t seem that hard. Why doesn’t my lead technician get it? I have showed him how to create a schedule a dozen times.”

“Morgan, it’s not just a matter of training. Supervising and Project Management are clearly Strata II roles. A lead technician role is more likely Stratum I.” I could see Morgan was struggling with this.

“But, if I take my lead technician, why can’t he seem to put a schedule together?” Morgan was pushing back.

“Morgan, a lead technician likely has experience, best machine operator you have, yet may only be capable of running his machine in an expert way. You are asking him to think about coordinating other people.

“The time span required for a supervisor is longer. And the story doesn’t end with just scheduling. Scheduling responsibilities may only require a two or three week time span, but there’s more. Supervisors must also think about building bench strength, recruiting technicians, training technicians, testing technical competence, cross-training. For a supervisor to be successful, I usually look for a minimum three month time span. The supervisor needs to be able to work into the future, without direction, using their own discretionary judgment, on tasks that may take three months or more to complete.”

His ASAP, Your ASAP

Sondra finished her project over the weekend.

“Last week, you assigned this task to Dale, but you ended up doing it,” I observed. I could tell she was very pleased with the project result, but miffed that she spent the weekend working when Dale had all of last week to work on it.

“I thought a lot about what you said about being more explicit about my deadline. Next time, I will try to remember that,” Sondra replied.

“More than that, the target completion time is essential to the task assignment. Dale gets all kinds of assignments. To complete them, he has to use his own discretion, primarily about pace and quality. Most of the decisions he makes are about pace and quality. Without a target completion time, he has no frame of reference in which to make his decisions. His ASAP will ALWAYS be different than your ASAP. ASAP is not a target completion time.”

Sondra smiled. I took a look at her project. It was really very good. She will make her client meeting today and life will go on.

By When?

Sondra was holding her head between her hands, staring directly down to the surface of her desk. I tapped the door and she looked at me over her glasses.

“Why the long face, said the bartender to the horse?” I asked.

She smiled through her temporary state of mind. “Gotta work tomorrow, Saturday,” she replied.

“Not the end of the world, what’s the matter?”

“I assigned a project, a major project to Dale on Monday. He asked when I needed it. I said ASAP. Today is Friday. He hasn’t started it and he is leaving town for the weekend.”

“So, what does ASAP mean?”

“It means it’s important and I need it right away. The client meeting is first thing Monday. Another communication breakdown.”

“Oh, it looks like a breakdown in communication,” I replied. “But the responsibility lies with you, the Manager.”

“What do you mean? I told him it was important and that I needed it as soon as possible.” Sondra had pushed herself back from the desk, arms extended.

I shook my head. “This is basic goal setting and you have committed the classic mistake. When you assign a task, any task to achieve a goal, what are the elements in that assignment?”

“Well, I tell them what I want them to do, you know, how many of whatever, and any important details.”

“And what else?”

Sondra was stumped. But in all fairness, her mind was thinking about Saturday. I am sure by now, she just wished I would go away.

“How about when you want the project completed by?” I prompted.

“Well, if it has a deadline, but if I just need it done, it’s going to take whatever time it takes.”

I shook my head. “No,” I said slowly. “Every task assignment ALWAYS has an expected completion time. The classic mistake most managers make is ignoring the importance of the expected completion time. Tell you what. You come in tomorrow, on Saturday, finish your project, that should have been finished yesterday and on Monday, we will talk about the importance of expected completion times.”

Group Accountability?

“At first, this group dynamics stuff looked interesting, you know, everyone together under a team incentive bonus. It sounded exciting in the seminar, but in real life, this is painful,” Naomi explained. “The worst part, is we’re not getting any work done.”

“So, who is accountable?” I asked.

“I think everyone has to take a small part of the responsibility for the team not cooperating,” Naomi replied.

“No, I don’t mean who is responsible for the mess. I mean, who is accountable for the goal?” I insisted.

“The goal? We’re not even talking about the goal. We are just talking about cooperating better together, as a team.”

“Perhaps, that’s the problem,” I suggested. “You are spending so much time trying to cooperate as a group, that you forgot, we are trying to get some work done around here.

“Is it possible,” I continued, “that you have been misdirected to think more about shared fate and group dynamics than you have about your team. A team is not a group. A group may be bound together by shared fate, but a team is bound together by a goal. Stop thinking about group dynamics and start thinking about the goal. That’s why we are here in the first place.”

Things Fall Apart

“I don’t think you have an attitude problem. I don’t think you have clearly defined the accountability and the authority that goes along with that dotted line. That’s why dotted lines are so dangerous,” I said.

“So, what should I do? This Key Result Area is not a high priority, but the work still has to get done,” Megan explained.

“You are shooting yourself in the foot when you describe -it’s not a high priority-. If the work in this area is not done, what happens to its priority?” I asked.

Megan thought. “You’re right, the tasks will take about five hours a week, but if they are not completed, all hell breaks loose, other things begin to fall apart.”

“So, what should you do with that dotted line?” I pressed.

“Get rid of it, change its color, make it bold,” Megan retreated. “I guess I have to specifically define what I want, how much time it should take and what the result should be.”

“You guess?”

It’s Just a Dotted Line on the Org Chart

It’s been a whirlwind of a week. I would like to welcome our new subscribers from workshops in Minneapolis, Des Moines and Austin.
____

“What do you mean, she doesn’t know she is accountable? It’s very clear to me,” Megan complained. “She has a very clear dotted line to that area of responsibility. I know it’s not her highest priority, but still, she is responsible.”

“So, there is a conflict in her priorities?” I asked.

“Not a conflict, really, she has to get it all done. Just because it’s a dotted line doesn’t mean she can ignore it. Besides, at the bottom of her job description, it says, -and all other duties assigned.- That should cover it.”

“As her manager, what do you observe about the way she handles the conflict in her priorities?” I pressed.

Megan thought. “I think it’s an attitude problem. It’s almost as if she doesn’t care about one part of her job.”

“I thought it was just a dotted line?” I smiled.

Megan stopped cold. “You think the problem is the dotted line?”

“Dotted lines create ambiguity. Ambiguity kills accountability. What do you think?”

Calibrate the Level of Work

From the Ask Tom mailbag –

Question:
Your workshop on Time Span makes perfect sense. I see things in my company that I now understand. It was all there, but now I understand why? How much of this do you share with the organization. My executive team immediately got it, but how far down in my management team do I go?

Response:

You assume that Time Span, as a concept, is complicated. It’s not. Time Span is simply the “by when” of a goal. Do you talk about goals with your management teams? Do you talk about tasks and activities associated with those goals? Do you establish time lines associated with those goals?

These are normal, and necessary, managerial conversations required all the way to the supervisor level.

The question behind your question, where most get into trouble, thinking about Time Span, is the notion that we should be calibrating our team members. Let me shift your focus.

The necessary calibration is in identifying the Level of Work, not the person. Judging the effectiveness of a team member must always be done related to the work. And that judgment is a required part of every manager’s role.

Full Speed Off the Cliff

From the Ask Tom mailbag –

Question:
I just joined the HR team here, working on a project to identify the complexity of mental processing of our team members. I just wanted to know, is there any effective tool/test available to identify the 4 types of mental processes. Can you please suggest other techniques apart from interviews to identify the 4 processes. I would be required to use this for recruiting and to assess the (CMP) of current employees.

Response:
STOP! You are headed in the wrong direction off a cliff.

I know you think you want to get inside the heads of your employees and have some support for a number (1-4) that you think will be helpful in selecting talent. DON’T PLAY AMATEUR PSYCHOLOGIST! You didn’t take courses in psychology, you don’t have a degree, much less an advanced degree in psychology, you are not certified by your state to practice psychoanalysis. Don’t play amateur psychologist.

Play to your strengths as a manager.

The four states of mental processing (Declarative, Cumulative, Serial, Parallel) can easily be used to determine the Level of Work. That focus will put you on solid ground. What’s the Level of Work? Look at your Role Description. In each Key Result Area (KRA), what’s the Level of Work? What are the decisions to be made in the role? What are the problems to be solved in the role? What are the accountabilities in each KRA? Write those elements into your Role Description.

With the Role Description in hand, create a bank of written interview questions, ten questions for each KRA that will reveal the candidates real experience making those decisions and solving those problems. I know this looks like work, it is. This is managerial work. Don’t play amateur psychologist, play to your strengths, as a manager. It’s all about the work. It’s all about the Levels of Work.

Flowcharting the System

“So, what does it take to create a system like that?” I asked. “To create a system that would notify for rejected parts along with lead times for replacement parts and alternate suppliers?”

Valerie was shaking her head. “I know our computer software pretty well and to program that functionality would be pretty expensive.”

I reached in my bag and pulled out a handful of 3×5 index cards. “Suppose I said that you were not allowed to modify your software and the only tool you could use were these 3×5 cards? Now build a system. Let’s start with how frequently it happens.”

“You’re right,” Valerie started. “It doesn’t happen that often. Our QC guy who certifies incoming parts, could send a card with the details to our purchasing person. Our purchasing person has access to lead times and alternate vendors. Purchasing gets their order quantities from sales orders, so they could run a reverse report to find out what orders would be impacted, that’s easy.”

“What else do we need to know to effectively respond?”

“We would need to get our sales people involved to find out what wiggle room we have on those orders. Since we are three weeks ahead of the game, there are all kinds of adjustments that can be made with ample notification.”

“If I asked to draw a picture of this on a piece of paper using circles, arrows and labels, could you do that?”

“You mean, like a flow chart?” Valerie asked.

“Like a flow chart.”