Anything That Can Go Wrong

From the Ask Tom mailbag –

Question:
I am still struggling with the concept of time span. You say that time span indicates complexity. How?

Response:
Don’t overthink this fundamental concept. Life is about uncertainty. It is like the weather and the stock market. There is always uncertainty.

Combine this level of uncertainty with our intentions (goal directed behavior) and you observe the consternation of the ages. This is not a matter of going with the flow, but trying to get something done, achieve a goal, create an accomplishment. Elliott describes this as the “time span of intention.”

In spite of our best intentions, the longer it takes to achieve the goal, the more time life has to be unpredictable. The shorter time it takes to achieve the goal, the less time life has to happen, the less opportunity for some circumstance to come in sideways and blow everything up.

Time span is about contingencies. Time span becomes a calibration tool that allows us to precisely measure the impact of uncertainty in our best laid plans.

Step back and remember Murphy’s Law. Anything that can go wrong, will go wrong. How long do we give Murphy to play?

Who is Accountable for Results?

From the Ask Tom mailbag –

Question:
Our company just adopted a new management system called (MFR) Management for Results. As a manager, I have been told to focus on results. I am supposed to delegate a task assignment, create a measurement for the result, then manage to the measurement. It is supposed to make my team discussions shorter and more to the point. If my team cannot create the result, then I am supposed to write them up. Our HR department is very supportive of MFR because, they say, it creates an objective paper trail for termination.

Here is my problem. I am supposed to measure the result at the end of each month. It has only been a week and my team is already struggling. My manager is telling me to stay out of it and just manage the result at the end of the month. If nothing changes, every single team member will get written up.

Response:
Of course you would not wait until the end of the month. You, as the manager, have an output goal and if you wait until the end of the month, you will terminate the team AND be short of the goal.

This is the myth of results based management. It places accountability for the goal on the team, when it is the manager who is accountable for the goal. If the team is failing, it is incumbent on the manager to diagnose the problem and make the necessary moves to achieve the goal.

  • Is it a matter of training?
  • Is it a matter of capability?
  • Work method?
  • Appropriate tools or tooling?
  • Defect measurement?
  • Scheduling?
  • Material inspection?

There are a number of contributing factors that could cause a team to underperform, and it is the manager I hold accountable, not the team. -Tom

When Times are Good

“You look comfortable,” I said.

“Things are going really well,” Jordan replied. “The market is good, new customer count is up, year over year revenues are positive. Yes, things are comfortable.”

“I noticed your accounts receivable ratio to new sales is above your threshold limit. And, that you rented a new warehouse to store some slow-moving inventory. Your revenue-per-employee head count is way down over the past six months. What gives?”

“Hey, when times are good, those things happen. More revenue, more accounts receivable. We set the ratio threshold during the last recession when things were tight, so it’s no big deal. And, yes, we rented another warehouse to give us more capacity. The new warehouse gives us a buffer so if we get a spike in sales, we can cover without having to increase production. But, you are right. I am a little troubled by our revenue-per-employee. It just seems it takes more people these days, and wages are increasing so our revenue-per-payroll dollar is even worse.”

“Jordan, when things are tight, we pay attention, we measure, we make moves. We don’t make our biggest mistakes when times are tough. We make our biggest mistakes when times are good. A little success can create a whole lot of overhead.*” -Tom
_____
*Homage to Red Scott.

Reactive vs Proactive Sales Management

From the Ask Tom mailbag –

Question:
We have 15 sales managers and 100 sales reps. We’ve taken top performing sales reps and made them managers. Now as managers they are finding it hard to find time to manage the behaviors of their rep team members. They don’t argue that the more time they spend directing their reps the more productive the reps become. But these dedicated managers are spending nights and weekends catching up with directing (through our CRM) the actions of the reps. The managers are still our best closers. No one on the team is better. How do I coach the manager?

Response:
As the sales manager (of reps), what do you want me to do? What is the level of work?

If your dedicated managers are spending nights and weekends directing their reps, what do they do in the daytime? This description is classic S-II behavior. It appears there is no system, no systematic coaching, no systematic sales planning. It appears things are ad-hoc, reactive and improvised. It is possible to be effective with this strategy, but at what cost? You will burn out your sales managers and begin to experience turnover.

This ad-hoc behavior is your fault. You have not created an effective system (S-III) for your sales managers to work in. Your coaching with your sales managers needs to focus on sales planning, pipeline evaluation and rep evaluation. What are the proactive moves (rather than reactive moves)?

As long as your sales managers remain reactive, your company will experience no better sales performance than it has in the past. Only when you create a system approach to your market, will you experience deeper penetration. And, your system should be operated as a day job, not nights and weekends.
_____
Hiring Talent in the heat of the summer, starting next week. Pre-register here.

Where Management Trouble Begins

From the Ask Tom mailbag –

Question:
In your workshop last week, you stressed the importance of a role description. To be honest, we don’t really have time to write them. We either use an old version from HR, get something off the internet, or use our posting from Craig’s List.

Response:
And, that’s where the trouble begins. The reason we have so much difficulty with issues related to motivation and management is that we don’t accurately define the work. The role description is the cornerstone document –

  • Defines the work, the outputs, the expectations in the role.
  • Organizes the bank of interview questions.
  • Creates the basis for behavioral interview questions.
  • Structures the decision making process for selecting from the candidate pool.
  • Structures the monthly (or more frequent) 1-1 conversation between the team member and the manager.
  • Structures a performance improvement plan, when necessary.
  • Provides grounds for termination, when necessary.

It’s all about the work. Our problems begin when we don’t accurately define the work. What are the decisions to be made, problems to be solved in the role?

Embedding Culture as a Key Result Area

Some time ago, writing a role description, I added Culture as a Key Result Area (KRA). What is the accountability of a manager in the Key Result Area of Company Culture?

There are several frames in which to look at company culture –
That unwritten set of rules that governs our required behavior in the work that we do together. It is an unwritten set of rules in contrast to our written set of rules, policies, procedures. And, culture is often more powerful than any policy we may write or attempt to officially enforce. Sometimes, culture even works against our stated policy.

What is the accountability of a manager in the Key Result Area of Company Culture?

These are the four questions in the Culture Cycle.

  1. What is the source of culture, where does it start?
  2. How is culture visible, how do we see it?
  3. How is culture tested?
  4. How is culture institutionalized, reinforced and perpetuated?

What is the source of culture, where does it start?
The source of culture is the way we see the world. It includes our bias, our experience, our interpretation of our experience. A hostile workplace leads to quitting as a result of employer bias. Culture is the story we carry into our experience that provides the lens, the frame, the tint, the brightness or darkness of that story.

How is culture visible, how do we see it?
Culture, the way we see the world, drives our behavior. We cannot see our bias. We cannot see our interpretation. We cannot see the story we carry in our minds, but, we can see our behavior. Culture drives behavior. Behavior makes culture visible.

How is culture tested?
Behavior, driven by culture, is constantly tested against the reality of consequences. For better or worse, behaviors driven by culture are proven valid, or not. Where there is congruence between behavioral intentions and the test of consequences, intentions (the way we see the world) moves forward. Where there is a disconnect between behavioral intentions and the test of consequences, intentional culture stops DEAD.

How is culture institutionalized, reinforced and perpetuated?
Those behaviors that survive the test of consequences become institutionalized, for better or worse. Positive behaviors that survive the test against reality can become the customs and rituals that reinforce the way we see the world. Alternatively, counterproductive behaviors that survive can be institutionalized in the underground of our organization and will prevail, more powerful than our official rules and enforcement.

You get to decide. What is the accountability of a manager in the Key Result Area of Company Culture?

Key Areas for a Project Manager

From the Ask Tom mailbag –

Question:
I was in your workshop last week. When you look at qualified candidates for a role, you say “It’s all about the work.” We are looking at a project management role. What do you consider the three most important parts of project management?

Response:
Project Management is a classic Strata II role. From a macro level, it involves the coordination of people, materials, equipment and project sequence. Three core Key Result Areas (KRAs) drive the project forward.

  1. Project Planning (creating a comprehensive project plan including milestones and accountabilities).
  2. Task Checklist (documenting and tracking all the details for completion and quality).
  3. Project Schedule (creating and monitoring the project schedule, prioritizing and sequencing time frames associated with changing elements of a project).

The value adds for Project Management are project control, accuracy to project specifications, timeliness and completeness.

Other KRAs would include –

  • Pre-con Hand-off Meeting (critical meeting where pre-construction hands the project over to project management).
  • Punch List (audit of the project checklist, when everyone else thinks the project is complete).
  • Buy Out (assembling the list of material suppliers and subcontractors, with competitive cost information).
  • Customer Relations (creating the necessary customer relationship that addresses project discrepancies, project change orders and avoids litigation)

All of these would make the basis for a comprehensive role description for your Project Manager. -Tom

Who Gets the Resumes First?

“It’s really difficult to find good people out there, these days,” complained Byron. “Look at these resumes.”

He pushed the stack over to me. I glanced at the page on top and look what i found.

“I will take your word, that none of these resumes meets the standards you are thinking for the job. Tell me, how did these resumes make it to your desk?”

“Oh, we have a good process to weed out the bad ones,” Byron replied. “By the time they get to me, I should only see the top three or four candidates. But none of these people are qualified.”

“Do you think some overqualified people got cut from the resume pool?” I asked.

“Oh, sure, our people know what we are paying for the job and they can spot someone who is overqualified as easily as those who are under qualified.”

“And who is involved in this process?”

Byron’s head turned to the side and his eyes went up the far wall behind me. “Well, the hiring manager.”

“So, the hiring manager directly receives the emails from your job posting?”

“Well, no,” Byron backpedaled. “I don’t want to burden him with looking at all the resumes, so we have them sent to a generic email box. Irene is our receptionist, and she opens the emails and forwards the resumes she thinks are the best.”

“What do you mean, that she thinks are best?” I asked.

“Well, she deletes the ones from out-of-town and then marks the ones with two years experience. I don’t want the hiring manager wasting his time.”

“And then she delivers them to the hiring manager?” I tried to get the details of the sequence.

“Well, not exactly,” Byron continued. “Irene forwards them to one of the supervisors to cull over. I really don’t want the hiring manager wasting his time on unqualified resumes. He has enough other issues to deal with.”

“I see,” I nodded. “I think I am getting the picture.”

A Shift in the “Why?” of Delegation

“I know I have to actually delegate something to make progress,” Ruben confirmed. “But I get to work, things start to happen and before you know it, I am up to my elbows in problems.”

“Tell me what you want to happen,” I prompted.

“It’s not what I want to happen, it’s one thing after another. For example, I can take you through yesterday, minute by minute and you’ll see what I’m up against.”

“I believe you could take me through, minute by minute, but explaining what happens doesn’t change things. Tell me, Ruben, what do you want to happen?”

“I want to be a better delegator.”

“Now, change one element of your thought. Change want to necessary. It is necessary for you to be a better delegator.”

Ruben looked at me with lizard eyes.

“Why is it necessary for you to be a better delegator?” I asked.

“So, I can be more effective?” Ruben floated.

“No, it is necessary, because if you don’t delegate, you can’t play the role. And if you can’t play the role, then we have to find someone who can. That’s why it is necessary for you to become a better delegator.”

The Practice of Delegation

“I’m a little disappointed,” explained Ruben. “Disappointed in myself.”

“How so,” I asked.

“Since I was promoted to manager, everyone said I should delegate more stuff. So, I tried.”

“What have you tried?” I prompted.

“Well, I bought three books on delegating. I finished one and I am reading the second.”

“So, what’s changed, for you?”

“Nothing really. I mean, they are really good books, but I still do everything myself.”

“Ruben, delegation is a skill, a skill that can be learned. Every skill has two parts. The first part is technical knowledge. That’s the stuff you have been reading about in those books.”

“What’s the other part?” Ruben asked.

“The other part is practice. You actually have to get out there and practice. I really don’t care how much you know. I am interested in what you can do.”