The Org Chart Changed. Did the Decision System Change With It?

The new reporting lines are in place. Then a customer-critical approval reaches the wrong desk, and nobody is certain who owns the call.
A customer-critical decision needs approval. The commercial team believes Operations now owns it. Operations assumes the newly consolidated service team is responsible. Meanwhile, the escalation route still points to a management role that no longer exists.
Everyone is working from a reasonable understanding of the changes. The problem is that those understandings differ.
The chart has changed. The decision rules people relied on may not have caught up.
For executives managing AI-related layoffs, automation, or operating-model redesign, that distinction deserves attention.
The org chart is a map. The decision system is how work moves.
After restructuring, some changes become visible quickly.
Headcount is updated. Reporting lines are published. Responsibilities are redistributed. The financial model reflects the planned cost structure.
Execution now depends on practical decision rights as much as it does on the formal reporting relationships published after the restructuring.
Who can approve an exception? Which team owns an outcome that crosses functions? What happens when two priorities compete? When should a manager intervene, and when should the person closest to the work make the call?
Before restructuring, some of those questions may have been resolved through established relationships and informal knowledge.
When teams consolidate or management layers disappear, those arrangements can disappear with them.
The result can be decision friction: work that slows, moves between teams, or escalates unnecessarily because authority and handoffs are not yet consistently understood.
This can happen in a well-led organization. A restructuring plan necessarily describes the intended design. Its practical interpretation develops as people encounter real decisions, exceptions, and dependencies.
There is also a genuine management-capacity challenge.
In an October 15, 2024 report, Gartner reported that 69% of HR leaders agreed leaders and managers were not equipped to lead change, based on a July 2024 survey of 805 HR leaders.
That finding does not diagnose any particular company's leadership. It illustrates why even thoughtfully designed transformations need practical support at the manager level.
A redesigned organization can also carry forward work that should have stopped. An old approval may remain in a checklist after its owner moves to another role. Two teams may each retain part of a responsibility because neither received a clear handoff. Employees preserving service continuity can unintentionally rebuild the same complexity the redesign was meant to remove. The immediate leadership task is to determine which work has an accountable new home, which should be retired and which control still protects a real business risk.

A 15-minute check for decision clarity
Before introducing another survey, dashboard, or transformation initiative, leaders can test how consistently the new operating model is understood.
Start with one customer-critical workflow.
It might be resolving a service exception, approving a commercial commitment, managing a complex customer handoff, or reviewing an AI-assisted decision that still requires human judgment.
Choose two people from different functions who participate in that workflow. Ask them independently to answer the same three questions:
Who makes the final call now?
Identify the person or role with decision authority, including any approval limits.
What work has changed hands?
Specify which responsibilities moved, which remain, and where the handoff takes place.
Where does an unresolved exception go?

Identify the escalation route when the usual process cannot resolve an issue.
Compare their answers.
If both describe the same decision owner, responsibility boundaries, and escalation route, that is useful evidence of shared understanding.
If the answers differ, the disagreement provides something equally useful: a specific clarification leadership can make.
The exercise can be completed in approximately 15 minutes:
Spend five minutes gathering the two independent explanations.
Use five minutes to identify the most consequential difference.
Spend the final five minutes assigning a clarification owner, agreeing on the correct process, and setting a review date.
For People leaders supporting adjacent teams, a companion question is useful: What does your team no longer own?
Responsibilities that should have stopped sometimes continue through habit, especially when employees are trying to preserve continuity.
The purpose is to clarify work, not evaluate individuals. No employee sentiment data or private disclosures are required.
Capture the result in a short workflow record that people can use: the current owner of the decision, the handoff point, the escalation route and any step that has formally been discontinued. Where an AI-assisted process is involved, specify who reviews exceptions and remains accountable for the outcome. Share the clarification with the affected functions and test it against the next real case. The objective is operational continuity, not a documentation exercise that remains separate from the work.
What to do when the answers differ
A mismatch should lead to a small, explicit operating decision.
Document the current decision owner, the point where work transfers, and the escalation route. Make the clarification available to everyone involved in that workflow.
Then observe what happens over the next operating cycle.
Are exceptions reaching the intended owner? Are people making decisions within their authority? Are managers still being asked to resolve routine questions that should have clear answers?
This is where operational indicators matter. Repeated escalations, handoff rework, delayed approvals, and manager coordination time can reveal friction that broader performance measures do not immediately explain.
One distinction is important: not every execution problem is a decision-rights problem. If ownership and escalation are consistently understood, the constraint may instead be capacity, technical integration, missing skills, or an intentionally centralized approval requirement.
The check helps narrow the investigation. It is not a universal explanation for post-restructuring difficulties.
The next observation should separate coordination friction from capacity shortfalls. If both teams name the same owner and route but the work still queues, the issue may be workload, systems or necessary control requirements. If they describe different ownership, leadership has a decision-system problem to resolve. That distinction is especially important after a workforce change: asking remaining managers to work harder will not resolve a handoff that the new organization has never agreed to own.
From one-time clarity to ongoing organizational signal
A 15-minute exercise can uncover one mismatch. Sustaining clarity requires leaders to understand whether similar friction is recurring as the redesigned organization settles into its new routines.
That is the operating challenge Baryons is designed to support.
Baryons combines private, company-grounded individual guidance with privacy-protected, anonymized and aggregated organizational signals. Individuals have a thinking partner for reflecting on their work, priorities, and decisions, while leaders receive weekly team-level patterns rather than individual conversation transcripts. It is one way to extend leadership enablement into everyday decisions.
The useful signal is where coordination is getting harder, so leaders can clarify ownership before another customer decision stalls.
Team Resonance is fully anonymized and aggregated, with no names in any section. Leaders receive patterns; each person's conversation stays theirs.
These insights complement the practical handoff check and existing operating KPIs. They do not replace the leadership decisions needed to resolve what the organization discovers.
A question for your next operating meeting
If two leaders from different functions described the same customer-critical workflow today, would they name the same decision owner, handoff, and escalation path?
Choose one workflow and compare the answers.
For a closer look at how leaders can restore decision clarity after AI-related restructuring, read the companion Baryons analyst brief on AI layoffs and organizational continuity.
Sources
More articles

The Strategy Was Clear. So Why Did Execution Drift?
Quarterly alignment around a 90-day priority does not settle every trade-off needed to deliver it. This article gives Scaling Up teams a three-question check to surface different interpretations between functions while the quarter is still recoverable.

A Leadership Framework Should Reduce Decisions Returning to the Owner
Leadership frameworks build shared language, but owners still field the trade-offs nobody was authorized to make. This article offers a ten-minute, three-person priority check that turns one unclear decision into a rule managers can use.

Between Leadership Sessions, Managers Still Have to Make the Call
Leadership development builds shared principles, but daily decisions test them. This article helps mid-market executives see whether managers apply the same priorities consistently, and whether a gap calls for coaching or clearer organizational rules.