Tag Archives: accountability

How to Define Dotted Line Working Relationships

Leave a reply

“The manager is accountable for the results of the team member, I totally get this,” Ed agreed. “But, I have a manager in charge of new product development, that includes new product planning, market research, prototyping, product testing, re-engineering based on feedback. He is also in charge of the product launch before he hands the product over to production and sustaining engineering. He uses all kinds of resources for that, from marketing to engineering. How does the accountability work here?”

“Project teams happen all the time,” I replied. “Projects often require a multitude of expert talent from across the organization. But what you describe is not a special circumstance. You describe the normal workflow of every organization. Most organization charts are ordered top to bottom, with managerial layers to fix accountability in each of the disciplines. It is very orderly but workflow doesn’t happen up and down through managerial layers. Workflow happens horizontally across the organization. Tell me how things work around here.”

Ed cleared his throat as he began his description, “A customer project is surfaced through marketing, negotiated through sales, turned over to engineering for project specifications and design, pushed into operations for production, delivered to logistics for installation, inspected by quality assurance and maintained through warranty and customer service. You are right, work happens horizontally. So, how does accountability work horizontally?”

“Have you ever looked at an org chart and seen dotted lines between people from different departments?”

Ed nodded. “Yes, you said to get rid of our dotted lines. You said dotted lines create ambiguity and that ambiguity kills accountability. Isn’t that what we are talking about?”

“Yep,” I confessed. “I lied. I don’t really want you to get rid of your dotted lines, I want you clearly define the specific accountability and authority that goes along with those horizontal working relationships. These horizontal working relationships are normal and frequent, but most of the time they are undefined. Undefined working relationships leave people to make up their own rules and that’s where the accountability trouble begins.”

“So, what about my manager who borrows engineers to build prototypes for new product development?”

“Your manager who borrows, not just engineers, but marketing and product testing people, is a classic example of a project leader. The project leader borrows people either on a part-time basis or a full-time basis for a limited duration of time. If the project leader used the engineer on a permanent full-time basis, then that would properly be a managerial relationship.”

“So, the part-time status or the full-time limited duration status changes things?” Ed wanted to know.

“Yes, the project leader, in a cross functional working relationship, borrows team members from other disciplines. The project leader must arrange with the engineer’s manager for that working arrangement. Now, here is a question. Who is accountable for the quality of the engineer’s output on the project?”

Ed had been around me too long. “If the project leader is in a cross functional relationship with the engineer, the engineer’s manager is still accountable for engineer’s output, no matter what project he is working on.”

“True,” I acknowledged. “So, what if the engineer underperforms on the project? What does the project leader do?”

Ed thought for a minute. “The project leader goes to the engineer’s manager and describes the underperformance. Because the engineering manager controls engineering resources, the engineering manager can add another engineer to the project, or replace the engineer on the project, depending on the context of all engineering support required in the company.”

I nodded my agreement. “This is a very thoughtful and respectful working relationship between the project leader and the engineering manager. The project leader is requesting and receiving a service from the engineering manager.”

Cross-funtional Working Relationships
Service Getting
Prescribing
Auditor
Coordinator
Monitor
Advisory
Collateral

Who to Hold Accountable?

1 Reply

“You are not a manager so people can report to you,” I announced. The class stood still. “You are a manager to bring value to the problem solving and decision making of your team.”

Slowly, a hand went up in the back of the room. “But how will they know who to report to?” A murmur of chuckles circulated.

“Look,” I started. “When you have a new employee, you think the most important question is, who are they going to report to? That is not the central question. The central question is, which manager will be accountable for their output?”

“Accountable?” came the question from the back of the room.

“I know it’s a foreign concept,” I smiled. “Yes, a manager is that person in the organization held accountable for the output of other people.”

“But if my team member screws up, it’s not my fault?” the back of the room voice defended.

I shook my head. “It’s not a matter of fault. I hold you, as the manager, accountable for the output of your team members. Most organizations get this wrong and that is where the trouble starts.”

How to Connect Values to Behaviors

Leave a reply

“It’s a good list,” said Miguel. The list had emerged from a values exercise the week before. After an extensive word pairing process, some heavy lobbying, push back, protest and negotiation, this was the list that made it.

“So, now you have a list,” I said. “What do you do with it?” Miguel’s eyes brightened, then his brow furrowed.

“I’m not sure. I guess we could print it out on fancy paper, frame it and put it on the wall next to the Mission Statement.”

I stared straight at Miguel. “Dude, you are going to have to do better than that.”

Miguel nodded in agreement.

“Get your team back together and take this to the next step. If you want to create a positive culture, you have to live by your values. Everything you do as a company should support these values. You have to identify the stories, the examples and the people. Then you have to amplify them. You have to amplify them in meetings, newsletters, memos and emails.

“Get your team together and figure it out. In what way can we communicate our values and the behaviors connected to those values to every person in the company. Frequently.”

How to Build Trust

Leave a reply

“What do you mean – No surprises?” Rachel quizzed. “My team member must know that this conversation is coming. Everyone is constantly correcting his mistakes, making him do re-work.”

“So, you want to keep him guessing? You see, surprise works both ways. As his manager, you are surprised when he under-performs, fails to meet a deadline or turns in work with mistakes. What happens to your trust, when you, as a manager, are Surprised?”

“The trust level goes down,” Rachel replied. “It’s at the point now, where there is almost no trust at all.”

“So, as the manager, you are surprised when your team member fails to meet a deadline, and your team member is going to be surprised when you have an accountability conversation with him?”

Rachel nodded, silently, her eyes darting back in her brain. Finally, she spoke. “And we don’t trust each other. So, how do I prevent surprises when I go into this accountability conversation?”

“Pretty simple, really. No surprises, no ambushes. When you schedule the conversation, tell him the subject of the conversation will be about his current performance on the Phoenix project and the improvements we need going forward.”

The blood was draining from Rachel’s face. The truth does that, sometimes.

The Difference Between a Supervisor and a Manager

2 Replies

“I was one of the guys, as the team supervisor, now I am their manager,” said Jeremy. “I mean, I know what to do, it just feels weird.”

“Tell me about it.” I asked.

“Well, on Friday, we used to always go out for happy hour. Now, I am holding back. Maybe I will show up once a month after work, but I will usually only stay for one beer, then I beg off and hit the road.”

“What’s changed about the relationships?”

Jeremy took his time to respond. “I guess, instead of being a friend, the relationship was always about the work. I mean, it’s okay to be friendly, but sometimes you have to hold the line, sometimes you have to confront, sometimes the conversation is difficult.” He stopped. “And sometimes you feel by yourself.”

“So, who can you hang out with now?”

“Well, there other managers in the company. They have all been supportive. It is a different perspective. I’m the new kid on the block.”

“And what about your old team, from when you were a supervisor?”

“I am still a manager in that department, but now I work through their new supervisor. My relationship with the team, it’s not accountability anymore, not with me. Now, it’s more like a mentor relationship. It’s a longer view. Instead of me, telling them what to do, I do more observing. Their new supervisor is more concerned with their day-to-day productivity. I am actually looking for the team member that will emerge as the next supervisor in another year.”

“Why do you think all this feels weird?” I ask.

“It’s new,” said Jeremy. “My role is different. I never thought there was this much difference between being a supervisor and being a manager.”
_____
Our online program, Hiring Talent, kicked off its orientation last Friday, but there is still time to jump in on this round. For more information and registration, follow this link, Hiring Talent-2013.

Let Them Deal With It

Leave a reply

“I am ready to throw up my hands. I have come up with eight ways to Sunday for our route technicians to do a better job on their service calls. I am ready to do a Flutie drop kick and just let them deal with it.” Russell was commiserating, hoping I would be sympathetic.

“Well, I think it’s a good idea,” I said.

“What do you mean?” replied Russell, still looking for sympathy.

“I mean, I think you should call your technicians together and let them deal with it. Look, the problem isn’t that your ideas are bad; the problem is they are your ideas. If you want your technicians to do a better job on service calls, the ideas have to come from them.

“One of the biggest mistakes young managers make is thinking that you have to solve all the problems of the world. You don’t. Spread the burden. You will be surprised at how your technicians will step up to the plate.”

Our online program, Hiring Talent 2013, kicks off January 25. Pre-registration is now open.

Designed Around the Work

1 Reply

“I know you want me to be the nice guy,” Jim Dunbar pushed back, “that I would have a better organization if I wasn’t so hard on people, but at the end of the day, we have to get some work done around here.”

It stings against political correctness, but if you consider, for a moment, that statement is true, what changes?

What if, it is all about the work? What if the purpose of your organization is to actually get some work done, solve a problem, execute a solution? It’s not for every organization, only those with the intended purpose to get work done, complete a task, achieve a goal.

Some organizations are designed around other intentions, religious organizations, political organizations, educational organizations, collegial organizations, all with purpose, all with goals.

What if the purpose of your organization was to get some work done? What if your organization was designed around the work?

Designing the Work

3 Replies

Chase left our conversation abruptly. Across the plant floor, he had spotted a problem and rushed to make a correction. He was apologetic on his return. “Sorry, but this is why I called you today. I feel like a two armed octopus. There are eight things that need to happen, but I can only work on two problems at a time. Things get out of control about fifteen minutes into the day. And they never stop. At the end of the day, I look at my boss’ list of projects and the important things never seem to get worked on. There is always a crisis.”

“Not really,” I said. “To me, your system is working exactly the way it is designed to work.”

Chase was puzzled. “What do you mean? It’s not working at all.”

“No, it is working exactly the way it is designed to work. The design of your day’s work is to drink coffee for the first fifteen minutes, then run around the floor solving urgent problems. At the end of each day, you check the list to make sure you didn’t do anything important.”

I paused. “Not a bad design. How’s that working for you?” Chase didn’t like what he was hearing.

“If you want to change your day, you have to change your design for the day. I see about four major design changes you might want to consider, but let’s start with just one. Don’t let anyone work during the first fifteen minutes of the day. Instead have a huddle meeting around the boss’ list of important projects. That one design change will be a good start.”

How is your day designed?

The Sucker Punch Question of Org Charts

Leave a reply

From the Ask Tom mailbag –

Question:
I was in your Time Span presentation about Elliott Jaques and Managerial Relationships. I recently discovered that our perceived organization chart is quite different that the one I had or felt was in place. I had all of my managers draw their view of our Org Chart so I can get a better grip on the disconnect. What is the best way to create the most accurate Org Chart and most importantly, implement it?

Response:
Interesting that Elliott faced this same dilemma. He described these various versions of the Org Chart this way –

  • Manifest Org Chart – this is the published version
  • Assumed Org Chart – this is the version that different people assume, as many versions as you have people. This is the version you received from your managers.
  • Extant Org Chart – the way the Org Chart actually works, based on observations and interviews. This would include all the dysfunction, vagaries, dotted lines, stupid rules, end arounds and general mayhem.
  • Requisite Org Chart – the design of managerial relationships based on Requisite principles.

When we put Org Charts together, we think the central question is “who reports to whom?” This is a sucker punch question that leads us astray. It is not a matter of “who reports to whom?” but a matter of “which manager is accountable for the output of which team or team member?”

A manager is that person in the organization held accountable for the output of their team. So, when I examine any role, it’s not a matter of who that role should report to. When I examine the role, it’s a matter of which manager is accountable for the output of this role.

This subtle shift is a game-changer. The Organization Chart is a visual depiction of managerial accountability, not “who reports to whom?”

But your question is how best to create this visual depiction. Ultimately, all crumbs lead to the top. I hold the CEO accountable for the design of the work. But the detail of this design is best hashed out in a series of meetings considering these questions –

  • What is the work to be done, tasks to be completed?”
  • What is the Level of Work?
  • What role is best to complete the tasks?
  • Which manager is accountable for the completion of those tasks (output)?

Very interesting questions.

How Does That Happen?

3 Replies

“So, what’s the solution?” Arnie was puzzled. “I pressed hard, we made our numbers. I lost seven good people in three months. Five technicians and two direct reports.”

“Let’s start with that,” I said.

“Start with what?” Arnie asked.

“Direct reports. Most managers think they are managers so people can report to them. That is not the purpose of a manager. Your role, as a manager, is to bring value to the problem solving and decision making of your team members.”

Arnie pushed his glasses up. “Okay. I’ll bite. I even believe you. But how?”

“Remember, we talked about a shift? A shift in management behavior to get a different result?”

Arnie nodded, “Yes, a shift.”

“Here’s the shift. Do you bring value to a person’s problem solving and decision making by telling them what to do?”

Arnie looked crossways at me.

“Look,” I said. “I come in here to talk with you, as a manager. I really don’t know that much about how things get done around here, so do I tell you what to do, as a manager?”

“Not really,” Arnie replied.

“But, would you say, I bring value to your problem solving and decision making?”

“Well, yes. I mean, sometimes, you piss me off, but, yes, you bring value.”

“So, how does that happen? I don’t tell you what to do, yet, I bring value. How does that happen?”

“Well, you ask me questions.” Arnie stopped. “You ask me questions.”