Tag Archives: authority

What Are You Working On?

“What are you working on?” I asked.

“Just trying to finish this project,” Andrew explained.

“What’s the hold-up?”

“Things always move slower than I want. You know, getting my team to push things along.”

“And, when things don’t move fast enough, how does that make you feel?” I pressed.

Andrew smirked. “A little annoyed, impatient, anxious.”

“Anxious, about what? It’s just a project.”

Andrew nodded. “Yes, it’s just a project. But, it’s my project. I know I have to work through my team to get it done, but ultimately, it’s up to me.”

“So, it’s not just a project? It’s about you?”

“Yep, on the face of it, the project has a spec, it has a budget, it has a deadline. But the project is also a test about me. Can I organize it? Can I gain the willing cooperation of the team? Can I put a sequence together to keep us on track? If we get off track, how quickly do I see it? Will I know what to correct? Can I keep the team pulling in the same direction? It’s more than just a project. It’s more than just the team. Do I have what it takes to be effective?”

Structure and Creativity

From the Ask Tom mailbag –

Question:
Enjoyed your presentation yesterday, have a question. In your model, whose job is it to balance structure and innovation? (or structure that permits innovation?) How is this implemented? Is it a time span issue vs. a creativity/mindset issue? I worry about calcification and lean against structure which prevents innovation.

Response:
Thank you very much for your questions. Remember, yesterday, we only scratched the surface of Elliott’s research. You have many questions (not just one).

Let me first talk generally about structure and creativity. You are fearful that structure will stifle creativity, when in fact, Elliott believed quite the opposite.

Specifically, organizational structure looks rigid on a chart, with its neat boxes and circles and arrows that point the way. Off the paper, organizational structure is simply the way we define working relationships. And, there are two types.

On a chart, we see managerial relationships in a vertical fashion, and we have an intuitive sense how that works. In a moment, I will attempt to shift your intuitive sense in a way that opens up the creativity you cherish (all organizations cherish). But, before that, the other type of working relationship is horizontal. People have to (required behavior) work with each other, but they are not each other’s manager. On a chart we typically represent these with a horizontal dotted line. It’s the dotted line that gets us in trouble. Again, we have an intuitive sense of this horizontal working relationship (cross-functional), but we rarely define it with any more clarity than the dots in the line that connect.

What is missing are two A words. Accountability and authority. In a managerial relationship, we get the authority part, but fail to understand the accountability part. A client of mine, Mike, owned a carpet cleaning business. Every once in a while, thankfully not very often, a technician would ruin a customer’s carpet. Who did Mike want to choke up against the wall? The technician, of course. People can checkĀ proper carpet cleaning if they need the best carpet cleaning services.

You see, Elliott assumed that technician showed up for work that day with the full intention to do their best. And it is the manager Elliott held accountable for the output of that technician. The manager hired the technician, trained the technician, provided the tools, the truck, selected the project and created the working environment for the technician. The manager controlled all the variables around the technician, it is the manager that Elliott held accountable for the output of the technician.

In this vertical managerial relationship, we get the authority part, without understanding the accountability that goes with it. Only when the manager understands the accountability-for-output is placed on them, that the shift takes place. Elliott was very specific, he called this an MAH (Management Accountability Hierarchy). The org chart is no longer an org chart, it is an accountability chart. And, that chart now illustrates who is accountable. This small shift changes everything we understand about management.

We casually call them reporting relationships, when reporting doesn’t have much to do with it. It is an accountability relationship where the manager is accountable for the output of the team member.

It’s all about context. It is incumbent on the manager to create the context. Remember, Elliott assumed the technician showed up for work that day with the full intention to do their best. It is incumbent on the manager to create the context in which each team member can do their best. It is in the creation of that context, that creativity flourishes. I know you have more questions, but, enough for today.

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?”

Do I Have the Authority?

“But, I am the manager, shouldn’t I have the authority to make some decisions around here?” Amber asked.

“Ah, yes. Authority,” I replied. “You must understand, however, that authority comes with accountability. Neither comes first. You cannot have the authority to make a decision without the accountability for the outcome of that decision. Conversely, you cannot be held to account for the outcome unless you have the authority to make the decision.”

“So, just exactly what decisions do I have the authority to make around here?” Amber pressed on.

“To know that, you have to examine your goals and objectives.” Amber had an unspoken question on her face. I continued, “Your goals and objectives, agreed upon by you and your manager, set the context for your accountability (output) and the authority you have to make decisions to reach those goals.

“In the beginning, that authority may be unclear. That is why you meet with your manager more frequently, to clarify the context, define the accountability and determine your authority. As time goes by, your confidence will increase and so will your understanding of the discretion you have to make appropriate decisions.

“The most important understanding, where you have authority to make decisions regarding the output of your team, you also have accountability for that outcome. Do not think you can have the authority without the accountability.”

Accountability and Authority

This is a series on Teal and Levels of Work. Here is the backstory for the series in case you are interested in the context. The purpose for the series is to explore the tenets of Teal through the lens of Levels of Work.
——
My last post on Hidden Hierarchy, took a close look at Buurtzorg, where nurses in self-managed groups of 10-12 make decisions related to intake, scheduling, planning, holiday and vacation coverage. These are all decisions well within the timespan capability of each team. This slice of the organization has clear accountability for those issues and with that accountability must come the authority to make those decisions.

Laloux describes the authority exists because there is no managerial hierarchy with oversight that might question or reverse a decision made collectively by the team. Elliott Jaques, in the schema of levels of work would describe the authority as “timespan of discretion.” Each team has full discretion to make decisions and solve problems related to tasks identified at that level of work. The authority doesn’t exist in the absence of management, the authority is expressly assigned to the team.

With authority must come accountability. Laloux describes the nursing teams as accountable for their own output, without managerial oversight. This appears to work well, until it doesn’t.

When, it doesn’t, there are “coaches.”

Elliott would always be looking for “who is the manager?” He would not be looking for the mandated manager, but the observable manager. Who is bringing value to the problem solving and decision making of the team? At Buurtzorg, there are coaches who provide facilitation along defined problem solving models (I am reminded of Eli Goldratt’s Conflict Resolution Cloud).

It is incumbent on the coach to set context (in the form of questions), seek clarity in the issue or problem and bring the team to its own resolution. I think we just found the manager.

In short, the founder of Buurtzorg, Jos de Blok, found a way to grow the organization by driving decisions down to the appropriate level of work, organizing small teams to do that work. The design is perfectly scale-able to the current tune of approximately 10,000 nurses.

There is a hierarchy, not a hierarchy of power, but a hierarchy of accountability.

Networks and Level of Work

In my last post, we started to look at the hallmarks of Agile through the lens of Levels of Work. We looked at North Star through three organizing documents, vision, mission and business model. Today, we move down the list.

  1. North star embodied across the organization.
  2. Network of empowered teams.
  3. Rapid decision making and learning cycles.
  4. Dynamic people model that ignites passion.
  5. Next generation enabling technology.

Network of empowered teams
In a short post by Seth Godin, he chronicled the history of networks from crude computers, each requiring its own building, to those as big as refrigerators, then small enough to sit on a table, now carried in your pocket. Something else happened.

Godin says the first computers were good at two things, arithmetic and storing data. Then, computers got connected so they could share arithmetic and data. Godin described this as the computer meets the telephone, meets the fax machine, and the more people with fax machines, the more valuable the network. The third iteration included the disintermediation of both space and time. This was the death of geography. The current iteration, Godin calls the hive mind, the intersection of technology and agile networks (some of which may contain people).

The transparency afforded in current state technology distributes data and analysis to everyone who can understand it. Distance is dead. Real-time erases delay.

What impact does this have on decision making and problem solving? What decisions are now calculations (no longer a decision)? Who, in the organization, works on those problems and the new decisions we could not see before? How do we measure the size of those decisions? In the end, who is accountable for the output of those decisions?

Godin’s insight on the state of technology provides some clarity on our understanding of the state of the organization. Four issues, problem-solving, decision-making, accountability, authority. It depends on the Level of Work.

New Role, New Authority?

From the Ask Tom mailbag –

Question:
I was recently promoted as lead tech of a lab. My boss feels I undermine her for things I do without discussing them with her first. I explained directions for another technician, so she could speak to patients with more clarity. I was told I undermined my boss because of this. I asked our director, in front of my boss, if she was aware of an issue and I was told that I undermined my boss because I asked without consulting her first. I wonder if it’s a lack of trust or if I undermine her without meaning to?

Response:
Yes. It is both a lack of trust and you undermine your manager without meaning to. The solution is in the question. You must build trust AND stop undermining your manager. In your new role, you have new and specific accountability and authority. Unfortunately, these are rarely defined and that is where the trouble begins.

You have appropriate accountability and authority and your manager has a larger (longer time span) accountability and authority. Your manager is working in a longer time span context, aware of things you may not know. This is why the manager-team member relationship is so important (and often fragile).

Monthly 1-1 conversations with your manager work to bridge that gap. For you, in your role, to be in alignment with your manager, you have to understand the larger context of your manager. The only way to find out is to talk about it.

Following is an example of discussion elements for your next 1-1 with your manager.

Whose Decision Is It?
With accountability, comes authority. Whose decision is it? Is it yours or your manager’s? If you don’t talk about it, you won’t know. Here is a framework for the discussion.

  • Which decisions are reserved exclusively to my manager?
  • Which decisions are reserved to my manager, AND based on my input?
  • Which decisions are mine, but have to be discussed and approved by my manager?
  • Which decisions are mine, but I have to tell my manager before I pull the trigger?
  • Which decisions are mine, but I have to tell my manager, after I pull the trigger?
  • Which decisions are mine, and I don’t have to tell my manager?

As a new lead technician, you have new accountability and new authority. That new authority has to be defined.

Without This, a Void Filled With Shenanigans

I am told that we need more leadership around here. I am told that we manage things, but we lead people.

My experience tells me otherwise.

I believe, especially as companies grow larger, that we need more management. I would concur that it is very difficult to manage people. People resist being managed. But, it’s not the people who need to be managed, it’s the relationships between those people. In a company, it is the working relationships that need to be managed.

I hear about personality conflicts in an organization. But, I don’t see a personality conflict, I see an accountability and authority issue. In an organization, we rarely define the accountability and authority in the working relationship. We never defined where people stand with each other, who can make the decision, who can make a task assignment and who is accountable for the output.

We take relationships for granted. We take for granted that people know how to behave with parents, with siblings, with teachers. We take for granted that people know how to behave as managers, but, in most cases, managers behave the same way they were treated by their managers.

There is a science to all this. It has to do with context. Effective managers are those who create the most effective context for people to work in. It is that unwritten set of rules that governs our behavior in the work that we do together. There is a science to context.

Organizational structure is context. It is the defined accountability and authority in our working relationships. Without it, people fill the void with all kinds of shenanigans. Not their fault. It is the responsibility of the manager (including the CEO) to set the context.

The Truth About Empowerment

“Empowerment!” Joshua proclaimed. “The answer is empowerment.”

“Really?” I turned my head. “Just exactly what does that mean?”

“Well, when we are trying to get people to do something, we have to empower them.”

“All you did was use the word in a sentence, you didn’t tell me what it means.”

“When you want to raise morale, make people feel better about their job, you have to empower them,” Joshua tried again.

“Empowerment is a weasel word,” I explained. “Everyone uses (misuses) it, no one knows what it means. There are whole books about it, and no one knows what it means. It’s a cover-up, the salve to heal a wound inflicted by management. We have an empowerment problem. Our employees need to be empowered. WTF does that mean?”

Joshua turned sheepish. “I dunno.”

“Of course, you don’t know, you just stumbled into it. Sounded good, so you said it. Don’t ever use that word around me again. You don’t have an empowerment problem, you have an accountability and authority problem. You don’t need to empower your employees, you need to sit with your team and define the authority and the accountability that goes with it. It’s a contract with two parts. Empowerment is like a government oversight committee that has the authority to indict with no accountability. If you have the authority to do something, then you have the accountability that goes with it. Don’t talk about empowerment, talk about accountability and authority.” -Tom
_______
Weasel words is a concept codified by Lee Thayer Leadership, Thinking, Being, Doing. In the history of this blog, in addition to accountability, we have identified two other weasel words, motivation and holocracy.
_______
Registration for our Hiring Talent in the Heat of the Summer is now open. Find out more – Hiring Talent.

Not a Personality Conflict

From the Ask Tom mailbag –

Question:
I am trying to sort out an argument between one of my foremen and our safety officer. They have two different personalities. My foreman is driven, goal oriented with a knack for getting things done, even if he has to bend a rule or two. My safety officer is conservative, a stickler for policy without much admiration for getting things done. On the face of it, their personalities are suited to the roles we have them in. Until they get in the same room, or in the same meeting, or worse case, on the same job-site. It’s like oil and water. We have done personality testing to confirm what I have described, but they fight like cats.

Response:
You don’t have a personality conflict, you have an accountability and authority issue. Both roles have goals and objectives. Neither role is the manager of the other, yet they both have to work together. You could stand in and referee every interaction (if you have that kind of time on your hands) or you can get clear about the accountability and authority of each.

The foreman, no doubt, has production goals to meet each week and month for the duration of the project. The foreman has the authority, as the manager of his crew, to assign tasks, monitor those tasks and adjust work assignments as time goes by.

The safety officer has goals and objectives related to the absence of workplace accidents, the adherence to safety policies and long term, a reduction in work-comp modification factors. The safety officer is in a classic auditor role, accountable for safety, and, also with special authority to delay or stop work in the face of an unsafe work practice.

The conflict you witness between your foreman and your safety officer has nothing to do with personality, everything to do with the lack of clarity on your part, as their manager, related to their accountability and authority. The safety officer has the authority because you define it. If you don’t define it, you will get behavior that looks like a personality conflict.