"If your attorneys need [to create] private flowcharts to understand how work moves through your firm, your org chart has already failed."
Your Law Firm's Org Chart Is Probably Lying to You
Have you ever looked at your firm's organizational chart and thought, "This technically makes sense," while also knowing it has almost nothing to do with how work actually gets done?
If you even have an org chart, it is probably sitting in a shared drive somewhere, last updated during a leadership retreat, quietly pretending it still reflects reality.
For most firms, the org chart provides a sense of order without providing much truth. It:
- Shows reporting lines · Does not show how client work moves
- Suggests accountability · Does not show where responsibility actually lives
- Tells you who is "above" whom · Does not tell you who touches what, when, or why
That is the gap this article is concerned with.
What follows is not an argument against hierarchy. It is an argument against confusing hierarchy with production.
We will take a short trip through the history of the organizational chart, look at why modern law firms still struggle with it, and then introduce a different way of thinking about structure. A way that starts with the work itself instead of with titles.
I call it the Operating Model Blueprint.
Whether your firm is highly process driven or heavily litigation focused, the underlying question is the same:
Not "Who reports to whom?" But "How does our work actually move, and does our structure support that movement?"
This is the first article in a series on law firm structure, and specifically on aligning organizational design with output rather than with tradition.
The Grand Ole Org Chart and Why It Exists at All
At its core, an org chart is meant to answer three simple questions: who does what, who reports to whom, and how authority flows.
When it works, it reduces confusion and gives people a sense of where they belong.
When it fails, it does something worse than nothing at all. It creates the illusion of clarity.
Hierarchy also has a psychological side effect. Over time, position becomes conflated with value. Silos harden. Information moves vertically and stalls horizontally. A tool meant to clarify responsibility becomes a diagram of power instead.
This instinct to draw structure is not modern. Ancient civilizations depicted hierarchy visually long before anyone used the phrase "organizational design." Pharaohs were painted larger than their servants. Kings were drawn above courtiers.
The impulse is ancient: impose order on complexity.
That impulse collided with scale during the Industrial Revolution, especially in railroads. In the 1850s, Daniel McCallum was tasked with managing thousands of employees across the New York and Erie Railroad. He commissioned what is generally recognized as the first modern organizational chart.
It was not art. It was logistics.
For the first time, an organization could see itself as a system.
By the early twentieth century, the idea formalized. The term "organization chart" was coined. Pyramidal charts became standard. Authority flowed downward. Work was assumed to flow upward.
For a long time, that model was good enough.
But good enough doesn't always mean good.
From Divisions to Matrices: The Search for Flexibility
As organizations became more complex, the single pyramid began to strain. Divisional structures emerged. Instead of one massive hierarchy, companies built smaller pyramids by product line, region, or service category.
This helped in manufacturing and distribution. It localized decision making and increased speed.
But in service organizations, especially professional services, it introduced a different problem.
Expertise became trapped inside silos.
Knowledge does not behave like inventory. When you divide it too aggressively, you isolate it.
Matrix structures were the next attempt at solving this. Instead of one reporting line, people reported along two axes:
- A functional manager
- A project or matter leader
In theory, this encouraged collaboration.
In practice, it often produced ambiguity.
If you have two bosses, you usually have two priorities. And when those priorities conflict, the system does not resolve the conflict.
The employee does.
Matrix systems try to soften hierarchy, but they still anchor structure to reporting lines. They still begin with people and titles.
The Operating Model Blueprint starts somewhere else entirely.
It starts with the work.
The Pattern We Keep Rediscovering
If you step back from the history, a pattern emerges.
As the product becomes more complex and more service oriented, workers want structure to follow the product itself.
Manufacturers learned to organize around assembly lines. Software teams organize around feature delivery. Hospitals organize around patient care pathways.
Law firms, for the most part, still organize around status.
Which raises an uncomfortable question.
Is your firm still using a model designed for railroads in 1855?
If so, why?
The Modern Law Firm Pyramid
Walk into most firms today and the structure is immediately recognizable.
At the top are the partners: Managing partners · Equity partners · Senior partners · Junior partners
Below them sit the attorneys: Of counsel · Senior associates · Mid level associates · Junior associates
At the base are the people who keep the system running: Paralegals · Legal assistants · Operations staff in HR, finance, IT, billing, and records.
On paper, it is neat.
In practice, it carries several baked in flaws:
- Decisions move slowly because authority must travel up and down
- Information moves vertically, not laterally
- Departments drift into isolation
- Career value becomes linked to where your box sits instead of what you actually contribute
- The chart becomes outdated almost as soon as it is drawn
Most importantly, a pyramid is designed to display power.
Legal work is not about power. It is about process.
Many firms add practice groups in an attempt to introduce specialization. Litigation. IP. Corporate. Family. Real estate. The intent is quality.
The effect is often fragmentation.
When silos deepen: communication thins, teams duplicate effort, confusion grows, burnout follows.
And when something breaks, everyone blames "the other group."
The Hybrid Attempt
Some firms attempt to fix this by blending hierarchy with functional specialization. Practice groups sit alongside operational teams. Reporting lines mix with dotted lines. Informal authority emerges through tenure and politics.
What results is a chart that tries to do everything at once:
- Multiple bosses
- Competing priorities
- Ambiguous expectations
In one patent prosecution firm where I worked, the structure looked modern on paper.
In practice, it looked like this:
- Attorneys assigned to multiple partners
- Paralegals reporting to supervisors and to project leads
- Legal assistants aligned to attorneys rather than to matters
- Mandatory second review by a partner not involved in the case
The production path became a maze.
Who owned which step depended on the client, the project type, the attorney's habits, or simply who was available that day.
When turnover occurred, the chart stopped reflecting reality entirely.
I kept my own notes tracing who actually touched what before client delivery.
That is not a sign of flexibility. That is a sign of structural failure.
If your attorneys need private flowcharts to understand how work moves through your firm, your org chart has already failed.
Why Hybrids Fail
The mistake hybrid models make is trying to represent two different systems on one page.
Hierarchy answers administrative questions like:
- Who supervises whom?
- Who handles pay?
- Who handles discipline?
- Who evaluates performance?
- Who manages training?
Production answers operational questions like:
- How does work flow?
- Who touches it?
- Where does accountability live?
- Where do handoffs occur?
- Where is production flow slowing down?
Those are different systems.
They deserve different maps.
When you try to blend them, confusion is guaranteed.
This is where the Operating Model Blueprint enters.
It does not replace the hierarchical chart. It separates it.
You keep a hierarchy chart for people management. You build a Blueprint for value creation.
That separation gives firms something they rarely have: clarity of responsibility without losing clarity of authority.
The Operating Model Blueprint Explained
A traditional org chart shows who reports to whom.
The Operating Model Blueprint shows who reports to the product.
Specifically, the OMB nails down how work moves, who adds value at each step, and how a client's matter progresses from intake to completion.
The OMB places an emphasis on mapping production, not hierarchy. By connecting what is produced to how it is efficiently produced, firms are able to accurately attribute actions to roles, thereby exposing the levers available to owners and their leadership team.
If you need a metaphor, think of a city map where:
- Streets are workflows
- Intersections are handoffs
- Neighborhoods are teams
- Traffic patterns are communication
Much like the impetus behind city planning centers around ensuring the flow of traffic, the goal of the Blueprint is to show how value flows within your firm.
Organizing Around Production Instead of Position
Most law firms still design their organizational structure around hierarchical models that rely on books of business, practice groups, or seniority.
But here is the thing.
None of those produce the work.
The work produces the work.
If the work produces the work, and we are trying to diagnose how to improve our production process, we must have a clear production map.
That is where the OMB comes in to provide the following benefits:
- Purpose becomes clearer
- Bottlenecks become visible
- Adaptation becomes easier
- Accountability attaches to stages of production rather than to titles
Matrix systems gesture in this direction, but they never quite arrive. In many ways, they are a middling compromise between strictly hierarchical and strictly production focused organization charts.
Why?
Because they still center around reporting lines.
The Blueprint centers production itself. Hierarchy appears only where it directly affects the product.
Everything else is stripped away.
Cultural Effects
Blueprint thinking replaces heroics with systems. Instead of relying on individuals to patch holes in broken processes, the structure itself becomes dependable.
The steps of the work are clearly defined, handoffs are visible, roles exist because they serve the process rather than internal politics, and workloads can be balanced because they are no longer hidden.
As a result, leaders stop trying to command from the top and begin stewarding the value stream itself.
Metrics That Actually Matter
A pyramid measures hierarchy. A matrix measures relationships. A Blueprint measures performance where value is created.
Once you map the work, the metrics appear almost automatically. Here are a few examples from a recent client experience:
- Time to complete
- Error and rework rates
- Bottlenecks
- Stage level client satisfaction
- Cost per stage
- Utilization
Performance conversations change.
Instead of "work faster," the firm asks why a step is slow and fixes the system that produces the delay.
Blame moves away from individuals and toward design.
What Firms See When They Build One
Firms that adopt this approach tend to see the same changes:
- Intake becomes disciplined
- Work stops disappearing into cracks
- Partners stop being default bottlenecks
- Training improves because new hires can see the whole system
- Client experience stabilizes because the process guides it
- Scaling becomes possible because excellence can be replicated
Once you see this, it is difficult to go back.
This is not just a new kind of org chart.
It is a different way of understanding the firm itself.
Final Words
Hierarchy still matters.
It just belongs on its own map.
Authority on one map. Production on another.
That separation gives law firms something they have never truly had: a unified, end-to-end view of how client value is created.
Once you see your firm this way, the old model feels strangely disconnected from the work your clients actually pay you to produce.
This is not a fad.
It is the logical evolution of organizational design for professional services.