Tag Archives: org chart

Art Form or Detective Work?

From the Ask Tom mailbag –

Question:
Love it – the four levels of thinking directly related to the flow of inputs, manner and tempo. This helps so much in understanding an additional vector of complexity, in addition to future ambiguity (as measured by timespan).

Is there a measure that is commonly used and can be attributed to positions in a Requisite Organization design? Can we measure the amount of activity needed in each/any of the four levels to know what type of sophistication a) the org needs at that level and b) that a candidate has? Or is it intuitive only (we sense it and we know it when we see it)?

Can you use this to help bring clarity to the org chart?

Response:
Some would say that identifying capability is an art form, know it when we see it. My take is that it’s more detective work, assembling clues within a framework. The brilliant insight in the question is the focus. Typically, in an attempt to identify capability, we focus on the person. More brilliant, in the question, the focus is on the work, flow of inputs, manner and tempo.

I don’t judge people, I’m not very good at it. But, I DO judge the work. My calibration of level of work always ends with timespan, but at first blush, timespan might mislead, I need other clues, and then timespan falls in place. If all projects are one-week projects and we have twenty of them, it might seem the timespan is one week. But, to handle twenty simultaneous projects, the start time and the stop time begins much earlier and ends much later than the one-week project.

Before the projects start, we have to examine, in all the projects, what is the same? Can we apply the same solution to identical problems? In all the projects, what is different that requires a unique solution? What is our capacity to handle twenty simultaneous projects? Do we need two project managers or four project managers? If we only have two PMs and need four, where will we find two more? What steps in the project can be started immediately? What steps can be done at the same time? What steps must be done sequentially? When we start to answer those questions, we find the timespan is much more than one week?

Laying out the org chart, I generally use a pre-cursor document (spreadsheet) that has columns for each function on a team, or columns for each team in a department, or columns for each department in the organization. The rows in the spreadsheet designate level of work. If you would like a copy, just drop me an email. I use this spreadsheet to clearly identify the level of work before I translate the structure into an org chart.

The Rare Grasp on Structure

“I get it,” I said. “Timespan helps us sort out the complexity of problems at hand with the selection of the right person to solve that problem. You say that timespan touches everything a manager does?”

“Let’s start at the top with the CEO,” Pablo replied. “I rarely meet a CEO who has a firm grasp on the structure of their organization. And, by structure, I mean, the way we define the working relationships between people. Not only is it important to define the accountability inside a single role, it is also critical to define the way those roles work together.”

“I’m listening.”

“There are two types of working relationships, vertical and horizontal,” Pablo continued. “Vertical relationships, we understand more easily. Those are (vertical) managerial relationships. Every technician understands they have a supervisor, every supervisor understands they have a manager. If the organization is large enough, every manager understands they have an executive manager. Somewhere, hovering at the top is the CEO.”

“This is the CEO who rarely has a firm grasp on the structure?” I asked.

“Precisely,” Pablo smiled. “Most people get promoted in an organization because someone left the company, leaving a hole in the org chart. Or someone appears qualified for a promotion, requests a promotion, but there is no hole on the org chart, so we create a new role, with a new title. Or someone needs (deserves) a raise, but we cannot justify the increase in compensation without assigning a new title with a new role. Or someone needs leadership experience, so we make them a manager and assign a single person for them to manage. There are all kinds of wonky reasons that org charts get bloodied up.”

“We were talking about timespan?” I reminded.

“And, those bloodied org charts make no sense, they are bloated, accountability is vague, performance excuses abound. So we have communication seminars and do personality testing, AND nothing changes. That’s because we don’t have a communication problem, we have a structural problem. Timespan creates the only framework where we can accurately define two things, accountability and authority.”

“Accountability and authority for what?”

“To make decisions and solve problems. Work is making decisions and solving problems. It’s all about the work. When we can measure the decision (with timespan) and measure the problem (with timespan), we can now structure the organization around something that makes sense. Supervisors have a larger (longer timespan) context than technicians. Managers have a larger (longer timespan) context than supervisors. Executive managers have a larger (longer timespan) context than managers. It’s all about the work, all based on goals and objectives.”

“And, CEOs rarely have a firm grasp on their structure?” I repeated.

“Understanding timespan, the CEO can overlay levels of work onto the org chart, and discrepancies leap off the page. The burning platforms inside the org chart now reveal themselves, not as communication breakdowns or personality conflicts, but as structural problems, where we have not accurately identified the complexity of problems at that level of work, or mismatched a team member to make those decisions or solve those problems.”

The Sucker Punch Question of Org Charts

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.

More Problems Than We Had Before

“Let’s look back at your org chart,” I suggested. “You have 110 employees and twelve layers of supervision and management. Two people quit yesterday, so your org chart is already out of date. What do you think you need to change?”

Sydney’s mood had turned from generous to perplexed. “Our intention was to make sure everyone had someone appropriate to report, and to make sure no manager was overburdened.”

“And you ended up with?” I pressed.

“And we ended up with people in positions, creating more problems than we had, before we announced this new reorganization,” Sydney explained.

“I want you to shift your approach to this problem. Instead of trying to figure out who should report to who, determine which manager is accountable for the output of which team. And for this exercise, I want you to reduce from 12 layers to four.”
____

A friend of mine in Buffalo NY, Michael Cardus, published a short piece on the impact of role-crowding, too many layers. Take a look.

Looks Good on Paper

I was looking at Sydney’s org chart. I could see a familiar pattern.

“We have been working really hard on this,” Sydney explained. “Every manager knows who reports to them, so there should be no confusion. And every direct report has a manager.”

“I am just looking,” I said, “how many layers, or levels do you have on this chart?”

“That’s what took so much time,” Sydney replied. “We have 112 employees, in twelve layers. Pretty good job, neat and tidy.”

“Well, it all fits on one page,” I observed, “even though it’s a big piece of paper. Where did you get this printed?”

Sydney laughed. “The problem is, it looks good on paper, but not so good in reality.”

“Oh?” I said, with a diagnostic look on my face.

“Yes, like the guys on the shop floor. They all report to a Team Leader, Justin, best equipment operator we have. We told Justin, from now on, if they have a problem, you help them solve it. If they have a question, answer it. And at the end of the day, all the work needs to get done.”

“So, what’s the problem?”

Sydney took a breath. “The guys are now complaining that Justin is breathing down their necks. They say they already know how to do their jobs and that if they have a real problem, Justin is no help, they have to go to the supervisor, anyway. What’s worse, even Justin’s productivity is suffering, eight out of the last ten production days have been short to the work orders.”

“So, what do you think you are going to do?”

It’s Just a Dotted Line on the Org Chart

It’s been a whirlwind of a week. I would like to welcome our new subscribers from workshops in Minneapolis, Des Moines and Austin.
____

“What do you mean, she doesn’t know she is accountable? It’s very clear to me,” Megan complained. “She has a very clear dotted line to that area of responsibility. I know it’s not her highest priority, but still, she is responsible.”

“So, there is a conflict in her priorities?” I asked.

“Not a conflict, really, she has to get it all done. Just because it’s a dotted line doesn’t mean she can ignore it. Besides, at the bottom of her job description, it says, -and all other duties assigned.- That should cover it.”

“As her manager, what do you observe about the way she handles the conflict in her priorities?” I pressed.

Megan thought. “I think it’s an attitude problem. It’s almost as if she doesn’t care about one part of her job.”

“I thought it was just a dotted line?” I smiled.

Megan stopped cold. “You think the problem is the dotted line?”

“Dotted lines create ambiguity. Ambiguity kills accountability. What do you think?”