5 min read

Levels of Work Are Not Titles

Levels of Work define the scale, scope, and time span of decision-making at each level, so roles match the complexity a person can reliably carry.

Flat vector illustration on a pale background: a woman in a business suit stands on a low platform and looks up at a much taller tower of stacked blocks, interlocking gears, and a long road winding toward a distant horizon, while a man beside her studies a blank card in his hands.

The regional operations director has held the same title for four years. In that time, the role quietly absorbed a market entry, two acquisitions, and a supplier strategy that will not show results until well after the next planning cycle. Her scorecard still measures monthly throughput. The title has not changed. The Levels of Work inside the role have.

Lately, her decisions have started moving upward. Questions that used to be settled in her staff meeting now arrive on the chief operating officer’s desk. Her reviews describe her as strong on execution but “not strategic enough,” and the succession conversation has turned toward whether she is ready. Nobody has asked whether the work she was hired for still exists. The gap between label and work is real, and the organization has been reading the gap as a question about her.

The misdiagnosis

The usual explanation is personal: a capable operator who has hit her ceiling, a mindset that has not caught up, a confidence problem under pressure. The fixes that follow are personal too: an executive coach, a leadership program, a stretch assignment, or a quiet search for a replacement.

Each of those charges the wrong constraint. The work inside the role changed shape, and the role itself was never redesigned. Escalation in that situation is not a sign of weakness. It is a predictable response to being asked to carry uncertainty over a longer horizon without the structure that horizon requires.

What are Levels of Work?

Levels of Work describe the hierarchy of complexity within organizations, defining the scale, scope, and time span of decision-making at each level. Each level represents a distinct pattern of judgment and responsibility. The purpose of the lens is to align what a role demands with the complexity a person can reliably carry, so the organization does not confuse title with work.

That last distinction carries most of the value. A title is a label the organization assigns. A Level of Work is a property of the work itself: how long a decision has to stand before anyone can tell whether it was right, and how many interdependent variables it has to hold while it does. Two people with the same title can be doing work at very different levels, and one person can keep a title while the work underneath it moves.

The book’s cleanest anchor for this is the Time Span of Discretion: the length of time a role holder must exercise judgment before outcomes can be evaluated and certainty established. A short time span rewards precision because feedback arrives quickly. A longer one asks a person to live with ambiguity, because the consequences of today’s decision appear long after the meeting where it was made.

Levels of Work pairs with Mode of Thinking, the cognitive structure that shapes how a person processes complexity, holds uncertainty, and manages time horizons. Levels of Work names what the role asks. Mode of Thinking describes the reasoning a person tends to bring. The point of holding both is not to label people. It is to make a mismatch visible early, before it hardens into shame, escalation theater, or a distorted performance story.

How does a Levels of Work mismatch show up?

When the match between role and person is sound, work tends to feel stretching but sustainable. When it is off, the friction is persistent and specific. Three signals worth checking:

  • Decisions that should be owned get pushed upward. The role holder escalates calls that sit inside the role, because the time span of those calls now exceeds what the role was built to hold. The Border of Escalation is being crossed by default, not by design.
  • Decisions that should be governed get improvised at the edge. The reverse pattern: people below the level the decision requires make it anyway, because nobody declared who holds it. The outcome looks like initiative until it creates rework.
  • Meetings feel necessary but empty. The calendar fills with sessions that circle a sticky decision without moving it. That usually means the decision’s time span was never named, so nobody can say whose judgment it needs.

A team showing two of the three is usually facing a design gap, not a performance gap.

What do you do with Levels of Work?

Start with two questions the book recommends holding whenever a decision feels sticky. First, what is the Time Span of Discretion of the decision in front of this person: how long must their judgment stand without new direction before it can be evaluated? Second, what thinking does the moment require: tight procedural accuracy, interpretation across cases, pattern recognition across a system, or integration of variables across multiple horizons?

Then apply the operating rule: design roles with Level of Work in mind, and place and develop people so their judgment can meet that requirement. For the operations director, that means one of two honest options. Either redesign the role so the long-horizon work has its own structure and decision rights, or move the long-horizon work to a role built to hold it. Both are structural decisions. Neither is a coaching plan.

The cost is real. Rewriting a role means renegotiating scope, reporting lines, and sometimes compensation, and it has to be revisited as the organization grows. It is still cheaper than losing a strong operator to a story about her limits.

What the title was hiding

Return to the director whose decisions began moving upward. Her performance did not change. The work did, and the title kept the change out of view. Once the role is described by its time span and complexity rather than its label, the conversation stops being about whether she is strategic and becomes a question the organization can actually answer.

Levels of Work makes that kind of work legible. Durability is designed into roles, not demanded from the people who happen to hold them.

What changes across Levels of Work is the time span the Triad of Direction must hold: Management, Leadership, and Stewardship are practiced at every level, at different scales of consequence.

Levels of Work is developed in The Capability Advantage by Jose J. Ruiz, Volume I of the Built to Endure series, alongside the Progression of Meaningful Response.

← Back to all notes