Escalating Emotions

“I didn’t mean to raise my voice, but I guess things just escalated.” Karyn described this latest blowup with one of her team members. “I am only her supervisor on the weekend, so I feel a little helpless. Her weekday supervisor lets her get away with leaving early. I talked to Rick about it. He just doesn’t want to confront her.”

“And when you stopped her from leaving early, the conversation turned grisly and she left anyway?”

Karyn nodded her head slowly. “And next Saturday, I don’t know what to do or say. I can’t just pretend nothing happened?”

“Oh, you could. Hope is a strategy. You could hope she doesn’t blow up again. You could hope she doesn’t leave early again. You could hope she gets all of her work done. But if hope doesn’t work, what are you going to say and when are you going to say it?”

Karyn scrunched her face, “I don’t want to wait until she tries to walk out the door again. Then it will be Groundhog Day all over again.”

“So, when would be a better time to talk to her?”

“I think early in the day, perhaps at the very beginning.”

“Good, then there won’t be the drama of her trying to leave at that moment. Now, what are you going to say?” Karyn struggled with the question. No response.

“Karyn, I want you think about this. You cannot stumble into this conversation. You have to be prepared. Think about this and we will talk again. Think along these lines. I want you to be both straight AND sensitive. What will you say?”

Service System Capacity

From the Ask Tom mailbag – Related to Integration is a Fancy Word. The illustrative example described an imbalance of systems in a manufacturing model, where there is a build-up of finished goods inventory (unsold).

Question:
Can you provide an example of an anemic sales function in a service industry. What would you get instead of an inflated inventory?

Response:
Thanks for the question. In a service industry, say you have 20 trucks, 20 technicians, optimized to average three service calls per day. The daily average capacity is 60 calls.

If sales only sells 55 average daily calls, you have excess unsold capacity of 5 service calls. You may not even notice. If the average drops to 50, you may begin to notice, and so do your service technicians. How long does it take a service technician to complete two assigned service calls vs three assigned service calls? The answer is 8 hours, no matter which. Parkinson’s law – work expands to the time allotted.

This is functional integration work, to monitor the capacity of each function, to make sure the impact of one function doesn’t outstrip or adversely impact the capacity of its neighboring functions.

In this service example, the math is pretty easy, 20 technicians x 3 calls = 60. Sometimes the service work has more subtle variations where the math is not so clean. That’s why system capacity makes for fascinating study.

Integration is a Fancy Word – Part III

The purpose of system and sub-system integration is not to get rid of our silos, but to integrate them together. The second issue in this integration has to do with individual system capacity and total system throughput.

As organizations grow, there is constant pressure on efficiency (lean, six sigma, MUDA), but as the internal systems multiply, efficient as they are, they begin to get in each other’s way. It is not enough to have a collection of perfectly efficient systems, the organization now has to look at total system throughput. Capacity output and constraints of each system come into play.

Is it possible for Sales to write so many orders, that it outstrips the capacity of Operations to complete those orders? Unfilled sales orders become back-orders. Unfilled back-orders become cancelled orders. Customers go to competitors. What’s the problem? Both Sales and Operations are running full-tilt within the constraints of their function, but one function is outstripping the capacity of the other.

Let’s flip this around. Our Operations function has the latest, greatest state-of-the-art equipment, a cracker-jack operations team and the capacity to crank out finished goods like there is no tomorrow. Yet, if our Sales function is somewhat anemic, not that they are writing no sales orders, but certainly not selling everything that gets produced, what happens to the unsold finished goods? Into inventory they go, stacked in the warehouse. Until the warehouse gets full, then what do we do? We get another warehouse. What is happening to the cost-of-goods-sold?

This second issue of system integration is optimizing the capacity of each function as it sits next to its neighboring functions. There are dependencies, inter-dependencies, constraints, contingencies and bottlenecks that govern total system throughput. It does no good to write sales orders for products and services that cannot be filled.

Integration is a Fancy Word – Part II

Even small organizations assemble systems and sub-systems, and face the same system integration issues as large organizations. Remember, this is not an exercise to eliminate silos, but to integrate them together.

The first integration issue has to do with work as it travels sideways through the organization, from one function to the next – marketing – sales – project management (account management) – operations – quality assurance – research and development – accounting – human resources.

The first issue is to establish the quality standard of the work output as it travels from one function to the next. What does sales always say about the leads that marketing gives them?
“The contact person you gave me hasn’t worked at the company for three years.”
“The telephone number you gave me is a fax machine.”
“The email address you gave me is misspelled and bounces when I send to it.”

What’s the problem? Marketing is proud of the quantity of leads passed to sales, but, the leads miss the mark. The first step to integration is to establish and enforce the quality standard of work output.

In construction, there is a critical work hand-off between the estimating function and project management function. If there is a defect in that hand-off, the defect will be embedded in the project until it surfaces in either operations or quality inspection. The integration of those two functions (estimating and project management) demands the hand-off meeting has a hard agenda with detailed checklists. Problems identified in this hand-off meeting are easier to correct on paper than later, after steel and concrete.

The second issue related to integration has to do with capacity, subject of our next post.

Integration is a Fancy Word – Part I

Each level in Elliott’s level-of-work schema corresponds to a macro organizational function.
S-I corresponds to production work, timespan 1 day to 3 months.
S-II corresponds to supervisory work, to make sure production gets done, timespan 3 to 12 months.
S-III corresponds to system work (single serial system), timespan 1-2 years.
S-IV corresponds to system integration work (multiple systems and sub-systems), timespan 2-5 years.

Integration is a fancy word, what does it mean?

As the organization matures, grows larger and more complex, distinct functions emerge. These started as single roles, but grew into teams. Here is the quick list –
-Marketing
-Sales
-Project Management (or Account Management)
-Operations
-Quality Assurance (QA/QC)
-Research and Development
-Accounting
-Human Resources
There are a ton more, depending on the business model, but you get the drift.

Each of these functions begins internally focused, mostly because we said so. We told each function they had to efficient, internally profitable, no waste, prudent use of internal resources. We told them to be internally focused.

As we stack more functions next to each other, we can see the problem we created. The problem presents itself as a communication breakdown, sometimes a personality conflict. Each function competes for budget, prestige and managerial attention. This is the silo effect.

And we have all been told to get rid of our silos. Not so. We put those silos in place for very specific reasons. It is not a matter of getting rid of our silos, it is a matter of integrating them together.

Integration is a fancy word. What does it mean?

Critical for Growth

Nicole was still stymied over our discussion about the role of the supervisor. “But if I am not actively working on the line with everyone else, I don’t feel like I accomplished anything at the end of the day.”

“Nicole, let’s talk about the value-add of the supervisor. While your team members do the production work, your job is to make sure production gets done. The value you bring to the party, as the supervisor, is that the work is complete, at the target volume, at the defined quality standard and on time. To make that happen, your job is to schedule the appropriate materials, schedule the appropriate team members and make sure the right machines are available. Your value-add is consistency, thoroughness (no gaps) and completeness (the job gets finished).

“The Mom and Pop operation, just starting out, doesn’t have to worry about that stuff. They just have to finish today’s job for today’s customer. As organizations grow, as volume increases and there are more customers than you can count with fingers and toes, these are the issues that make or break a company. Is the right volume of product (or service) produced, of consistent quality, on time? Successful supervisors are responsible for taking the organization to that next level. It is a different sense of accomplishment, yet critical for the company to grow.”

Make Improvement Easy

Nicole had the numbers posted. She was still working side by side with the team, helping on the line, but at least the numbers were posted.

“But, we didn’t make our goal,” Nicole shook her head. “That’s why I was afraid to write the numbers on the white board, before.”

I ignored her body language. “Nicole, I want you to add another number to the board. I want you to post yesterday’s numbers next to the goal numbers. For right now, I just want you to focus your team on improvement over yesterday.”

“Well, that should be easy,” snorted Nicole.

“That’s the point. Make improvement easy. Then focus on it.”

The Weeds Part of “In the Weeds”

Nicole was complaining. Her department was behind. She worked 10-12 hours per day and could never seem to get ahead. She thought her boss should appreciate her efforts and hard work, but instead, she got quite the opposite. He was disappointed in her performance and intended to follow-up on her numbers every two weeks instead of once a month.

“What am I supposed to do?” she said. “I get here an hour early and leave an hour after my team has gone home. It seems, they always pull me into the weeds. I just can’t get anything done.”

“Tell me about the weeds part. How does your team drag you into the weeds?”

“They always need help. I try to work alongside them for most of the day, but then I cannot get my stuff done.”

“Then, stop!” I said. “You are the supervisor. You are there to make sure the work gets done, NOT to work alongside your team. If they have a problem, help them through it, but then get back to your responsibilities. You are supposed to do production counts three times during your shift so you can know if you are ahead or behind. That’s your job. Your team is not meeting its daily production and they don’t even know it.”

Always a “Who”

“Jeremy, when you decide on a project to delegate, how do you decide who to give it to?”

“Well, that used to be easy. Louis was always my guy. He could handle almost anything. My dad used to say, if you need something done, give it to someone who is busy because they will get it done faster than anyone else.”

“How is that working for you?”

“Not so good. Lately, Louis has been, well, not slipping, but, he just isn’t hopping like he was, even six months ago. I am beginning to wonder if he even likes working here anymore.”

“Think about the last delegation you gave to Louis. How much of a challenge was it for him?”

“Well, for Louis it was piece of cake. He should have been able to do it in his sleep with one hand tied behind his back.”

“Jeremy, I want you to think about something. Is it possible that you should have given that delegation to someone else and considered something more challenging for Louis? For delegation to be successful, the team member must see the task as a challenge.”

Capability Plus Skill Set

From the Ask Tom mailbag –

Question:
How does someone make the leap from technician to manager? I see it all the time in IT work, and I think it’s why there are so many bad managers out there. Isn’t this the Peter Principle, where people are promoted to their level of incompetence?

Response:
It’s more than a leap. It is a completely different skill set. The technician is an expert in a technical skill. The technician does the production work.

One level of work above is the supervisor. The supervisor does NOT do the production work. The supervisor makes sure the production work gets done; completely, accurately, no missing segments and on time. The tools of the supervisor are checklists and schedules. This is not a subtle concept and most companies don’t get it.

The role of the supervisor is coordination. Success requires two things. First, the person has the capability to make longer timespan decisions and solve more complex problems. Second is the development of a new skill set related to schedule making, checklist making and meetings. The failure is most supervisors are promoted to a role where they are expected to use a skill set they have not developed and the company is not prepared to train.