Category Archives: Accountability

Timespan of Intention

It’s January, with resolutions, goal setting, annual planning.

Most of our intentions are short-sighted. We focus on the what, not the by-when. Perhaps this year we examine the timespan of our intention as closely as the intention itself?

Instead of how many pounds can I lost by the end of Feb (when most resolutions are abandoned), we might ask what lifestyle changes we can make to add ten years to our life. What is the timespan of your intention?

Sometimes, the most important impact is not a major initiative. Sometimes, the major impact is shifting a small habit that is insidiously killing you. Or a small habit shift that will pay off in spades five years from now.

Think about your habits that support your success, habits that detract. What is the timespan of your intention?

Management Work

Ruben was stumped. “You are right. Just because we give Edmund a new title, doesn’t mean he is going to change his ways.”

“Edmund will always be Edmund, and we have to redefine his role. It’s not a matter of giving him new rules not to do this or not to do that. You have already tried that in his role as supervisor. As Lead Technician, what will be his new goals? How will you re-direct him?”

“It sounds obvious,” Ruben replied. “It starts with his job description.”

I nodded affirmative. “This is critical fundamental stuff. It’s the stuff you ignore because it sounds so simple. It’s the stuff you ignore that gets you in trouble. Stuff like goals and objectives, performance standards and holding people to account for performance.”

“I think I have a job description around here that might work,” Ruben hoped.

“Why don’t you start from scratch. As the manager, you have time span goals of approximately one year. Your annual plan has stuff in it that you are held accountable to deliver this year, and next year. If you had a supervisor, which Edmund isn’t, you would drive some of those goals down to that level, in time span appropriate chunks. For the time being, you are going to have to step into that role, review those supervisor outputs and determine the time span appropriate chunks (goals) for your new Lead Technician.”

Ruben was quiet.

“Look, do you want to lose Edmund?” I asked.

“No way,” Ruben replied. “He’s a great technician.”

“Then you have some management work to do.”

Cannot Continue This Way

“Our system creates predictability,” Ruben explained. “It creates predictability without stress. It allows us to do our maintenance at the best times, allows us to properly inspect our raw materials, test our setups accurately. Everything runs.”

“What are you going to do with Edmund?” I asked.

“He should never have been promoted to supervisor. He is a great technician, a great operator, our go-to guy. We don’t want to lose Edmund, but he cannot continue as supervisor.”

“What are you going to do with Edmund?” I repeated.

“I am going to assign him to a new role called Lead Technician. He won’t like it, and, right now, I run the risk of losing him. The job market is too fertile, lots of other companies would like to have Edmund.”

“How are you going to keep him from screwing things up, just because he has a new title? And how are you going to keep him.”

Effectiveness

“So, in your mind, Edmund is not a hero?” I prodded.

Ruben shook his head. “No, and what’s maddening is that Edmund, as a supervisor, keeps describing his behavior as results oriented. It’s all about the results, he says. So, maybe he delivers, but there are body bags all over the place.”

“So, notwithstanding the results, how would you describe his effectiveness, as a supervisor? Thumbs up? Or thumbs down?”

Ruben laughed. “You know, that’s it. Effectiveness. If I can judge his effectiveness, it’s thumbs down. A supervisor is not effective when he ignores the metrics, skips steps in the process, then works overtime to save the day when the system breaks down.”

Midst of Created Chaos

“How do you involve Edmund in the decision making about solving the problem?” I asked.

“As soon as we have the project specs,” Ruben explained, “when we know the outputs and the deadlines, we call a meeting. Edmund is the supervisor, so once we get into production, he is the one to call the shots. So, he is there, at the meeting. He sees all the elements we see, he just cannot connect them together.”

“And?”

“We have developed a very thorough system that identifies the constraints and keeps them productive. The metrics are easy to follow and the system makes our throughput very predictable. But Edmund fights the system, ignores the system and almost weekly causes a production snafu that could have been prevented.”

“How does he explain the snafu?”

“Usually he manages to jump in and pull the project out of the fire, but not without some overtime and not without putting the project in jeopardy. It’s almost like he is proud of the chaos and being the hero.”

Subtle Pushback

“He resists everything,” Ruben explained. “We cover the same solutions to the same problems. At the time, Edmund finally agrees, but I sense, he agrees only because he can’t argue the logic. He goes along with the solution, but two weeks later, the same problem pops up and we start all over again.”

“So, you have to step in and it takes up your time?” I asked.

“Worse than that. It’s almost underhanded. Behind the scenes, it’s like he wants the solution to fail. He doesn’t openly sabotage the new method, and I haven’t caught him bad-mouthing the process. Sometimes, it’s just the way he rolls his eyes in the meeting.”

Inside the Function

“Take your most important internal function,” Pablo instructed. “In the beginning, likely will be operations. What is the work most closely related to producing the product or delivering the service? Especially in the beginning, that is mostly short-term work, 1 day to 3 months. Most production roles have a supervisor, with longer term goals and objectives, 3 months to 12 months. The supervisory role is to make sure production gets done, completely, on time, within spec.”

“So, every production person knows they have a supervisor?” I added.

“And, every supervisor knows they have a manager,” Pablo smiled. “This is the beginning of structure, nested goals and objectives related to successive roles (context), a production role, to a supervisory role to a managerial role.”

“The roles are distinguished by longer timespan goals and objectives?” I suggested.

“Yes, the roles are different in that way, but also in the way they relate to each other. Organizational structure begins with nested timespan goals, but also includes the way we define two things associated with those role relationships.”

“Accountability and authority?” I chimed in.

Pablo nodded. “In this working relationship between the team member and the supervisor, what is the accountability? What is the authority?”

My turn to show off. “The accountability on the part of the team member is to apply their full capability in pursuit of the goals and objectives agreed to by their supervisor, in short, to do their best. It is the accountability of the supervisor to create the working environment that makes those goals and objectives possible (probable). It is the accountability of the supervisor for output.”

“And, the authority?” Pablo prompted.

“The authority to make decisions and solve problems appropriate to the level of work in the task.”

The Framework of Structure

“Organizational structure based on the timespan of related goals and objectives?” I repeated, as a question. “Has to be more complex that that.”

“Of course. Organizational structure is complex,” Pablo replied. “But, that is where is starts, looking at the level of work, goals and objectives.”

“A bit overwhelming,” I surmised. “Still looks like a large kettle of fish.”

Pablo nodded in agreement. “After the vision and mission, the founder must examine the internal functions required to kickstart the company. And, remember, this is an infant company, so there aren’t that many internal functions. Producing the product, delivering the service, finding a customer willing to pay and a way to deposit the money into the bank. That’s it, in the beginning.”

“So, in the beginning, following the vision and mission, I have to define the first functions required to produce the product or service. And in each function, determine the goals and objectives?”

“And, the ‘by-when’ of each goal will tell you the level of work required. That is the beginning of structure.”

Matching the Work

“I’m a structure guy,” Pablo said. “When you think about effective managerial leadership, I think the focus is on the structure.”

“It’s not on charisma, likeability, luck?” I asked, knowing the answer.

Pablo gave me a knowing smile. “The first key area for any manager, is to design and build the team. Individual achievement is a myth. If you want to create something great, it takes a team, a collection of teams, organized to get work done.”

“Before I do anything else, I have to build the team?” I wanted to know.

“Before you build the team, you have to design it,” Pablo continued. “That’s where most companies make their first missteps. As time goes by, there is too much to do, always work left over. Someone has a brilliant idea, let’s hire some more people. And, they do this without any thought of the overall design of the team to get work done.”

“So, first I have to think about the work?”

“And, not just task assignments, we have to figure out what problems must be solved and what decisions have to be made. With that, then we have to determine the level of problem solving and the level of decision required on the team, to make sure when we start to match up the people, we can select the right ones.”

All About the Work

“Brent, let me get this straight. You said that your salespeople may not be doing their best because they may not be interested in the work? Do your salespeople understand the work?”

“You’re right! Sometimes, it’s like they are brain dead. They are just mechanistic, going through the motions,” Brent described.

“So, they understand the prescribed duties, show up, make a presentation, ask for the order. But let me confirm, they may not understand the problems that must be solved or the decisions that must be made to create a successful sale?”

“Exactly, I mean we train them and train them again on the presentation, until they have it memorized, down cold, but you are right, that does not make a successful sale. The success of the sale depends much more on the questions they ask and the data they collect about the customer’s problem.”

“So, as the Sales Manager, do you sit with your team and talk about the problems that must be solved and the decisions that must be made during the sales call? That’s where the work is. That’s where the excitement is. That’s where the challenge is. If you are looking for interest from the salesperson, the connection is in the work, not the prescribed duties.”