Comparable issues opened and closed by the same Account Coordinator
CASE 04 / WHO DECIDES?
DECISION HISTORY · OBSERVED ROUTINGAn org chart is great at showing titles—
An org chart is great at showing titles—
not who actually has influence.
In 18 of 44 fictional requests, the decision bypassed the title-based escalation route. The interactive history shows who carried the context and where the decision actually went.
Explore the decision history ↓Download decision records ↓Operational problemThe org chart does not show how exception requests actually move
What I builtAn interactive review of 44 recorded decision paths
Decision this supportsShould the approval route reflect the path teams actually use?
WHAT THE HISTORY CHANGES
I compared 44 requests to see who answered, who carried the context, and which route the decision followed.
Outcomes matched the primary customer contact’s requested direction
Requests bypassed the title-based escalation path
Median turnaround for the Sales Director
How the measures are scoped44 total requests · 12 comparable-issue records
Approval speed, requested direction, and routing use all 44 records. Context carrier uses the 12 requests involving the same exception type so the comparison stays consistent.
ASK THE HISTORY
A decision record can answer more than “approved or declined.”
Select a question to compare the observed pattern, the evidence behind it, and the next question it raises.
OBSERVED PATTERN
The quickest approver was not the highest title.
4.2 hours
Median turnaround · Sales Director · 21 of 44 decisions
- Regional Manager · 11.6-hour median · 14 decisions
- Vice President · 29.4-hour median · 9 decisions
- 19 of the Sales Director’s 21 requests used the direct-conversation route
Requests reaching the Sales Director moved fastest in this modeled history. Direct access and familiarity are possible explanations, not established causes.
Timestamps show speed. They do not show that a faster decision was better informed or produced a better outcome.
What evidence shows the approver reviewed the issue history before deciding?
Compare the rolesFormal authority, recorded work, and evidence of review
RECORDED TITLE VS. OBSERVED WORK
A title labels the position. The activity history shows what that person actually did.
Select a role to compare formal authority, repeated behavior, evidence of review, and the relationship context that may have affected the path.
OBSERVED ROLE
Context carrier
Recorded title: Account CoordinatorThe only role repeatedly present from the first issue record through the final closure note.
- Formal authority
- No final approval authority.
- Work actually recorded
- Opened and closed all 12 comparable issues, sent 10 cross-team updates, and wrote nine closure notes.
- Evidence of review
- Attached prior issue history in 11 of 12 requests and recorded the unanswered questions before routing.
- Relationship context
- Worked across the customer, account, and operational teams, becoming the practical translator between them.
INTERPRET WITH CARE
The activity pattern shows concentrated responsibility. It does not prove this was the only person who cared or understood.
Compare two possible routesSee how the same question moves with and without its history
WHY THE QUESTION MATTERS
A simple unanswered question can disrupt the entire flow.
Compare two modeled routes for the same fictional customer question. The decision itself does not change; the routing, context, customer experience, and downstream disruption do.
MODELED RESULT
The request moved upward before anyone checked how this decision usually moved.
27 hr 20 min
Customer waited into the next day
- 01Question received
The Account Coordinator records the issue and begins collecting the prior history.
- 02Routed by title
The request goes to the Vice President because that is the highest title shown in the approval list.
- 03Route questioned
The Vice President asks who normally handles this exception. The person closest to the issue has to explain the context again.
- 04Work remains on hold
The request is redirected to the Sales Director. The operational change cannot move and the customer asks again for timing.
- 05Decision recorded
The customer receives an answer after a second follow-up and the downstream team resumes the work.
WHAT CHANGED
The delay did not begin with a difficult decision. It began with an unanswered routing question: who actually handles this kind of issue?
THE PRACTICAL TAKEAWAY
The person handling the issue may be the only one carrying the full story. A useful decision record should preserve that context, show whose direction aligned with the outcome, and still separate observed activity from formal authority.
Fictional decision history built to demonstrate the method, not an employer or client result. Activity records show sequence and participation; they do not establish motive or causation.