Two Maps Every Firm Needs
An org chart answers the question: who is responsible for whom? A workflow map answers the question: how does work move from start to finish? These are different questions with different answers, and confusing them creates operational problems that no amount of management attention can solve.
The org chart is vertical. It shows hierarchy — partners at the top, managers in the middle, staff at the bottom. Lines indicate reporting relationships, supervision authority, and performance evaluation responsibility. The chart tells you who makes decisions about people. It does not tell you who makes decisions about work, or how work travels through the organization.
The workflow map is horizontal. It shows stages — intake, preparation, review, delivery — and the transitions between them. Lines indicate handoff relationships, not reporting relationships. The map tells you who receives work from whom, in what form, with what quality expectations. It shows bottlenecks, capacity constraints, and quality verification points. It is the operational blueprint that the org chart was never designed to provide.
Most firms have an org chart. Few have a workflow map. They manage their people using the vertical structure but leave the horizontal flow of work to informal convention. The result is that work moves through the firm in ways that no one designed, no one monitors, and no one optimizes.
How Informal Workflow Paths Develop
In the absence of a designed workflow, work follows the path of least resistance. This path is shaped by four forces that have nothing to do with operational efficiency.
Personal relationships. The preparer sends work to the reviewer they know best, not the reviewer assigned by any formal system. The client sends documents to the person they emailed last, not the intake coordinator. The manager routes complex questions to the partner they are most comfortable with, not the partner with the most relevant expertise. Work follows relationship lines, not workflow lines.
Physical proximity. In office-based firms, work gravitates toward whoever is physically nearby. The preparer walks to the closest available reviewer for a quick question. The admin hands documents to whoever passes their desk. Remote and hybrid work patterns change the proximity dynamics but do not eliminate them — digital proximity (who is online, who responds to Slack first) replaces physical proximity.
Historical habit. “We’ve always done it this way” governs more workflow routing than any deliberate design. The firm established an informal pattern when it had five people, and that pattern persists at twenty people despite being inappropriate for the larger team. The client who was assigned to Partner A five years ago is still with Partner A even though Partner B now handles that engagement type. The workflow follows historical assignment rather than current design.
Availability bias. Work goes to whoever is available, not whoever is appropriate. During busy periods, this means complex work lands on the desk of the first person who has an opening, regardless of whether that person has the expertise, the client context, or the capacity to handle it well. The urgent overrides the optimal, and the routing becomes a function of who finished their last task first.
These four forces create a workflow that is functional but undesigned. Work gets done. But it gets done through paths that create inefficiency, quality variance, and hidden dependencies that only become visible when something breaks.
Invisible Bottlenecks
The most damaging consequence of informal workflow is invisible bottlenecks — points where work clusters around a person or a transition that the org chart does not recognize as a constraint.
Consider a common scenario. The org chart shows three partners, each supervising a team. The assumption is that work is distributed roughly equally across the three teams. But the actual workflow reveals that 60% of all engagements are reviewed by Partner A — not because Partner A is assigned more work, but because preparers across all three teams prefer Partner A’s review style, trust Partner A’s turnaround time, or have historical relationships with Partner A’s clients.
Partner A is a bottleneck that the org chart cannot see. Their review queue is three times longer than the other partners’. Engagements assigned to their “team” on the org chart include engagements that informally migrated from the other teams. The firm wonders why throughput is constrained even though it has three reviewers. The answer is that it effectively has one reviewer carrying three times the load.
These invisible bottlenecks exist at every level. The admin who is the only person clients trust to send documents. The senior associate who handles all the complex calculations because everyone knows they are the best at it. The IT person who is the only one who can troubleshoot the practice management system. None of these bottlenecks appear on the org chart. All of them constrain the firm’s throughput.
Mapping the actual workflow makes these bottlenecks visible. When you track how work actually moves, the points of concentration become obvious — and addressable.
Accountability Gaps Between Roles
The org chart defines what each person is responsible for. But in the space between org-chart roles, there are workflow activities that no one formally owns. These are the accountability gaps where work falls through the cracks.
The most common accountability gap is between intake and preparation. The org chart has no “intake coordinator” role. Documents arrive from clients via email, portal, or drop-off, and someone needs to organize them, verify completeness, and route them to the appropriate preparer. In many firms, this activity happens informally — sometimes the admin does it, sometimes the preparer does it, sometimes the partner does it. No one owns it, so no one is accountable for whether it is done well or done at all.
Another common gap is between preparation and review. Who ensures that the engagement file is complete and organized before it enters the review queue? The preparer believes they are done when they finish preparing the return. The reviewer expects a complete, organized file when they open it. In the space between those expectations, there is a set of assembly and organization tasks that neither person considers their responsibility.
A third gap is between review and delivery. Who assembles the final client package? Who drafts the transmittal letter? Who handles e-filing? Who confirms delivery with the client? These post-review activities are often nobody’s primary responsibility because they fall after the main workflow stages that the org chart recognizes.
Each accountability gap creates a small quality risk and a small efficiency loss. Across hundreds of engagements, these small losses compound into significant operational drag. The workflow breaks that emerge as firms grow are often the result of these gaps becoming visible only when volume makes them painful.
Quality Inconsistency Through Routing Variance
When work follows informal paths, the same type of engagement can travel through different routes depending on who handles it, when it arrives, and what else is happening in the firm. This routing variance creates quality inconsistency that is difficult to diagnose because the root cause is not any individual’s performance — it is the absence of a consistent path.
Engagement A and Engagement B are both standard 1040 returns for similar clients. Engagement A arrives on Monday, is assigned to Preparer X, is reviewed by Partner A, and passes through the self-review checkpoint because Preparer X is diligent about the checklist. Engagement B arrives on Thursday during a busy week, is assigned to Preparer Y (who was available), skips the self-review checkpoint because it was urgent, and is reviewed by Partner C (who handles Thursday reviews). The two engagements receive materially different quality treatment, not because of any individual failure, but because the routing variance exposed them to different process paths.
In a designed workflow, every standard 1040 follows the same path: intake checkpoint, preparation with specification, self-review against checklist, mechanical verification, professional judgment review by an assigned reviewer. The quality is consistent because the route is consistent. Variation happens in the professional judgment layer (where it should), not in the mechanical and procedural layers (where it should not).
The reviewer variance problem is often a routing variance problem in disguise. When different engagements take different paths through the workflow, the quality at review depends on which path was taken upstream, not just which reviewer handles the review.
Capacity Misallocation
The org chart organizes people into teams, departments, or partner groups. Capacity planning — assigning work volume to available resources — is typically done using these org-chart groupings. But if work does not actually flow along org-chart lines, the capacity plan is based on a fiction.
Partner A’s team has five people on the org chart. Partner B’s team has five people. The firm assumes each team handles roughly half the work. But the actual workflow shows that three of Partner B’s team members spend 40% of their time on work originating from Partner A’s clients, because the informal routing sends that work to whoever is available. Partner A’s effective team is seven people. Partner B’s effective team is three. Neither partner knows this because the org chart says five and five.
The capacity mismatch manifests as unexplained overload. Partner B’s team feels overwhelmed despite having “the same number of people” as Partner A’s team. The firm adds a person to Partner B’s team, but the new person is quickly absorbed into the same informal routing pattern, spending 40% of their time on Partner A’s work. The problem persists because the solution was based on the org chart, not the actual workflow.
Workflow mapping reveals the true capacity distribution. When the firm can see where time actually goes — not where the org chart says it should go — capacity planning becomes accurate and actionable.
Mapping the Actual Workflow
The workflow mapping exercise reveals the firm’s operational reality. It is not a process documentation project. It is a discovery project.
Step one: track engagements, not roles. Select 20–30 recent engagements across different types and partners. For each, trace the actual path from first client contact to final delivery. Who received the documents? Who assigned the preparer? Who prepared the return? Who reviewed it? How many times did it cycle between preparation and review? Who assembled the deliverable? Who communicated with the client? Record every handoff, every touch point, every decision.
Step two: observe, do not ask. Do not ask people to describe their workflow. People describe the ideal process, not the actual one. Instead, use the practice management system, email records, and file access logs to reconstruct the actual path. Where system data is insufficient, observe in real time — sit with the team during a busy day and watch how work actually moves.
Step three: identify patterns. The 20–30 engagements will reveal consistent patterns: certain people are always in the path regardless of official assignment, certain transitions consistently lose information, certain stages are routinely skipped under pressure. These patterns are the firm’s actual workflow, and they are almost always different from what anyone expected.
Step four: map the findings. Create a visual workflow map that shows: every stage, every role at each stage, every handoff, every decision point, and every quality gate. Overlay the actual patterns from the tracking exercise. The result is a picture of how the firm actually operates — complete with the bottlenecks, gaps, and routing variances that the org chart conceals.
Designing the Workflow Map
Once the actual workflow is mapped, the firm can design the target workflow — the map that shows how work should move.
The target workflow map defines every stage in the engagement lifecycle with specificity. Each stage has: a clear scope (what happens at this stage), an assigned role (who performs this stage), a quality standard (what must be true when the stage is complete), a handoff protocol (how work transitions to the next stage), and a verification mechanism (how the firm confirms the standard was met).
The design process addresses the four dysfunctions identified through mapping. Invisible bottlenecks are resolved by distributing work through designed routing rules rather than informal preference. Accountability gaps are closed by assigning every between-stage activity to a specific role. Quality routing variance is eliminated by defining a single path that every engagement of a given type follows. Capacity misallocation is corrected by planning capacity based on workflow roles rather than org-chart teams.
The target workflow does not need to be revolutionary. In most cases, it formalizes the best version of what the firm already does while closing the gaps and resolving the bottlenecks. The goal is not to impose a rigid process on creative professionals. It is to ensure that the mechanical, procedural, and administrative elements of the workflow are consistent and reliable, freeing the professionals to apply their judgment where it matters.
Using Both Tools Together
The org chart and the workflow map serve complementary purposes. Discarding either one leaves the firm with an incomplete management framework.
The org chart governs people management: performance evaluations, career development, mentoring relationships, decision authority, and team identity. It answers questions like: who evaluates this person’s performance? Who approves their PTO? Who manages their professional development?
The workflow map governs work management: task routing, quality verification, capacity allocation, handoff standards, and process improvement. It answers questions like: who receives this engagement after intake? What quality standard applies at this stage? Where is the current bottleneck?
A person can report to one manager on the org chart (for people management) while receiving work from a different source in the workflow map (for work management). This is not a conflict — it is a recognition that managing people and managing work are different functions that may follow different structures. The military recognized this decades ago with the distinction between administrative command (who manages the unit) and operational command (who directs the mission). Professional services firms are slowly arriving at the same insight.
The integration point is the team lead or workflow coordinator role — someone who manages the flow of work through the workflow map while the partner manages the development of people through the org chart. This dual structure is what enables firms to scale beyond the point where one person can manage both work and people.
Aligning Chart and Map
The ultimate goal is alignment between the org chart and the workflow map — not identity, but alignment. The two structures should support each other rather than create conflicting signals.
Alignment means that the org chart’s reporting relationships support the workflow map’s routing patterns. If the workflow assigns a preparer to work primarily on a specific engagement type, the org chart should have them reporting to a supervisor who understands that engagement type. If the workflow map positions a quality checker between preparation and review, the org chart should recognize that role with appropriate title, compensation, and career pathway.
Misalignment creates friction. When the org chart says a person reports to Partner A but the workflow map has them doing most of their work for Partner B, the person receives conflicting priorities, mismatched performance evaluations, and unclear development guidance. Partner A evaluates them based on incomplete observation. Partner B benefits from their work but has no formal authority to develop or reward them.
Achieving alignment is an ongoing process, not a one-time reorganization. As the firm grows and the workflow evolves, the org chart should be updated to reflect the current operational reality. Regular workflow mapping — ideally quarterly during the first year, then annually — ensures that the two structures stay aligned as the firm’s operations change.
The firms that manage both structures consciously — using the org chart for people and the workflow map for work — develop an operational clarity that their competitors lack. They can diagnose bottlenecks, allocate capacity accurately, maintain quality consistency, and scale their operations without the hidden dysfunction that the org-chart-only approach conceals.
Hierarchy ≠ Workflow
The org chart shows who reports to whom. The workflow map shows how work moves. They are different maps answering different questions, and both are essential.
Informal Paths Create Dysfunction
Without a designed workflow, work follows relationships, proximity, habit, and availability — creating invisible bottlenecks, accountability gaps, and quality variance.
Map Before You Design
Track 20–30 engagements to discover actual workflow patterns. Observe, do not ask — people describe the ideal, not the actual.
Align Both Structures
The org chart and workflow map should support each other. Misalignment creates conflicting priorities, mismatched evaluations, and operational friction.
“The org chart is a map of authority. The workflow map is a map of reality. The firm that manages only authority while leaving reality to informal convention has a hierarchy without an operating system.”
Frequently Asked Questions
Why do org charts fail to show how work moves?
Org charts show reporting relationships (vertical hierarchy), not work flow (horizontal process). Work follows informal paths — personal relationships, availability, habit — that the org chart never captures.
What is the difference between an org chart and a workflow map?
The org chart shows authority — who supervises whom. The workflow map shows movement — how work travels from stage to stage, with handoff standards and quality gates. One is vertical (hierarchy), the other horizontal (process).
How does the gap create operational problems?
Four dysfunctions: invisible bottlenecks where work clusters informally, accountability gaps between roles, quality inconsistency through routing variance, and capacity misallocation based on org-chart groupings rather than actual work distribution.
How do you map actual workflow?
Track 20–30 engagements from intake to delivery. Record every handoff. Observe through system data and real-time observation — do not ask people (they describe the ideal, not the actual).
Should firms replace org charts with workflow maps?
No. Both are needed. The org chart manages people (evaluations, development, authority). The workflow map manages work (routing, quality, capacity). They serve complementary purposes.
What does a well-designed workflow map include?
Every stage of the engagement lifecycle, who performs each stage (by role), handoff standards at each transition, quality verification at each stage, and feedback loops for corrections.
How do informal workflow patterns develop?
Through path-of-least-resistance routing: personal relationships, physical/digital proximity, historical habit, and availability bias. They develop because the formal workflow was never designed.