Written by: David Carneal – Digital Efficiency Consulting Group – DECG
Read Time: 5 min
The org chart is not the business. It is a drawing of who reports to whom. Useful? Yes. Complete? Not even close. An org chart can show that two departments have managers, coordinators, analysts, and specialists. It cannot show how a customer request actually moves, where decisions stall, who fixes bad data, or which person knows the exception that keeps a major account from walking away.
After an acquisition, leaders often start with the org chart because it is easy to understand. Two finance teams look like overlap. Two customer service teams look like overlap. Two operations groups look like overlap. The boxes are right there, politely asking to be merged. The problem is that similar boxes do not always mean similar work.
Workflow tells the real story
A workflow shows how work moves from beginning to end. It shows who starts the request, who approves it, who enters data, who checks quality, who handles exceptions, who talks to the customer, and which systems are used along the way. It also shows the unofficial parts of the process, which are often where the business actually survives.
The official process may say that customer issues go through a shared service queue. The real process may be that three experienced employees route urgent issues directly because the queue loses context. The official process may say pricing changes need one approval. The real process may include a second review because a certain product line has special contract terms. The official process may say orders flow through the ERP. The real process may include a spreadsheet that catches errors the ERP never learned to care about.
Those details do not appear on an org chart. They appear when you follow the work.
Why visible duplication can fool leaders
Visible duplication is easy to find. Functional duplication takes work to prove. Two people may share a title and do very different jobs. Two systems may store similar data but serve different decisions. Two approval steps may look redundant but control different risks. Two vendors may provide the same service on paper but protect different customer promises in practice.
When leaders treat visible duplication as proof of waste, they may simplify the structure while making the work harder. The org chart gets cleaner. The process gets slower. Employees spend more time chasing answers. Customers feel the difference before the board does.
How to map without turning it into a swamp tour
Workflow mapping does not need to become a six-month expedition with matching binders and a consulting invoice that needs its own oxygen mask. Start with one critical workflow. Pick one that touches revenue, customers, compliance, cash, or employee capacity. Then trace it using real examples.
- Choose one workflow that matters. Good options include order entry, customer onboarding, quote-to-cash, service requests, purchase approvals, billing corrections, or production exceptions.
- Pull three to five real cases. Do not map the fantasy process. Use actual orders, actual issues, and actual documents.
- Interview the people doing the work. Managers can describe the process. Employees can show where it actually bends.
- Mark each handoff, system, approval, delay, and exception. These are the places where integration decisions either protect value or create chaos.
- Ask what would break if a step, person, system, or vendor disappeared. This question is where the map starts earning its keep.
What to look for
A good workflow map helps leaders see risk and opportunity. It should not be wall art. Look for repeated delays, unnecessary approvals, duplicate data entry, unclear ownership, customer-specific handling, and manual checks that prevent mistakes. Some items will be waste. Some will be wisdom. The job is to tell the difference.
- Watch for decision piles.
- If every exception goes to one manager, that manager is not leadership glue. They are a bottleneck with a calendar.
- Watch for shadow systems.
- Spreadsheets, notes, and side trackers often exist because the official system does not support the real work.
- Watch for customer context loss.
- If information gets stripped away during handoffs, service quality usually drops.
- Watch for local expertise.
- A small team may look expensive until you realize they handle the hardest accounts.
Workflow before consolidation
The sequence matters. Map first. Decide second. Consolidate third. When leadership reverses that order, the map becomes a post-mortem tool. It explains why the decision failed after everyone is already annoyed, customers are already restless, and the fix costs more than the original analysis would have.
The org chart can help leaders understand reporting structure. Workflow helps leaders understand value creation. During integration, value creation is the thing that needs protection. The boxes can wait their turn.
Middle managers can make this practical right away. Ask each team to bring one real customer order, service issue, or billing correction to the table. Walk through what actually happened. Do not debate theory first. Follow the evidence. The fastest way to expose false duplication is to watch two similar-looking teams solve two very different problems.
CTA: Choose one workflow that leadership assumes is duplicated. Map both versions before combining them. If one side performs better, adopt the better process, not the bigger company's process by default.