← Selected work
CASE 01 / WHO DECIDES?
DECISION HISTORY · OBSERVED ROUTING

Who decides—
and what waits until they do?

In my operations work, uncertainty about who could make or influence a decision sometimes delayed progress for days. That experience inspired this review of 44 fictional records; it is not a measured finding from them. I examine how to reach the right authority without losing the history held by the person handling the issue.

An org chart shows titles. It doesn’t always show influence.

Explore the decision history ↓Download decision records ↓
The questionWho can decide this exception, and what context do they need?
What the evidence shows12 comparable issues share an opener and closer; 11 include prior history
Recommended next stepConfirm approval authority by exception type, and carry the issue history with the request
WHAT THE RECORDS SHOW

I compared 44 fictional requests, separating the issue handler, recorded approver, route, prior history, and customer follow-ups. The brief below shows what I would check before acting on one of those records.

PRACTICAL DECISION BRIEF · R001

Get the exception decided without guessing who can approve it.

A proposed brief for reviewing the R001 quantity allowance before acting. The historical record identifies a recorded approver; the next steps below are my recommendation, not a reconstructed conversation or a claim that R001 remains open.

Decision needed

Can this quantity allowance proceed under the policy applicable to A006 / L001? Confirm the allowance value, conditions, and authorized decision-maker before communicating acceptance.

History to carry forward

P001, the Account Coordinator, opened and closed R001; P002, the Sales Director, is the recorded approver. The route is Direct conversation. Keep the coordinator available to explain the request and its relationship history; repeated involvement does not confer approval authority.

What waits

Without a valid allowance decision, the customer-facing owner cannot give an unconditional answer about the exception. Planning may need to keep arrangements provisional. Confirm the actual deadline and affected work with Operations; these are possible consequences, not measured losses or delays attributed to R001.

Verified authority versus uncertainty

The dataset records a general authority indicator for the approver, but does not verify authority for this exception’s value and date. Obtain the effective approval matrix, limits, and any delegation. The customer contact can influence the request; the coordinator can explain it; neither substitutes for authorized approval.

Next checkpoint

Ask the team lead to confirm who will obtain the policy and decision, and agree a response time before the downstream deadline. At that checkpoint, either record the authorized decision and conditions or use the policy’s escalation route. Silence is not approval.

Close the handoff

Send the decision, rationale, conditions, and next action to the customer-facing owner and affected teams. Retain the issue history and policy reference so the next exception does not begin with the same uncertainty.

Eleven of the 44 requests had a recorded customer follow-up before the decision. I would inspect those waits for missing information and unclear ownership; the records do not establish dissatisfaction or its cause.

Inspect the supporting decision historyMeasures, definitions, role comparisons, and routing examples
CONTEXT CARRIER12 of 12

Comparable issues opened and closed by the same Account Coordinator

DIRECTION FOLLOWED32 of 44

Outcomes matched the primary customer contact’s requested direction

SUPPLIED ROUTE FLAG18 of 44

Requests labeled as a title-route deviation

HISTORY ATTACHED11 of 12

Comparable requests carried prior issue history

How the measures are scoped44 total requests · 12 comparable-issue records

32 of 44 direction-aligned decisions: count records whose supplied direction-alignment flag is 1. This means the recorded outcome matched the primary contact’s requested direction. Agreement is compatible with influence, but does not establish that the contact caused the decision or reveal anyone’s motive.

18 of 44 title-route bypasses: count distinct request IDs with title_route_bypassed_flag = 1. This reproduces a supplied label, not an independently verified policy breach. An authorized alternative route may be legitimate.

12 comparable issues: a separately identified subset of the 44 requests involving the same exception type. All 12 share an opener and closer; 11 carry prior history. The subset is not 12 additional requests and is not a controlled comparison. Approver medians are descriptive, not a like-for-like performance ranking.

ASK THE HISTORY

A decision record can answer more than “approved or declined.”

Select a question to see the observed pattern, the supporting records, and the limit on what can be concluded.

OBSERVED PATTERN

The same handler opened and closed all 12 comparable issues.

12 of 12

Comparable issues opened and closed by the Account Coordinator

WHAT SUPPORTS IT
  • The same person sent 10 of the 12 cross-team updates
  • The same person attached prior issue history in 11 of the 12 requests
  • Nine final closure notes were written by the person who opened the issue
WHY IT MATTERS

The same handler appears at both ends of all 12 comparable requests and supplied most of the recorded updates and prior history. That supports keeping this person involved in the handoff.

WHAT THE RECORD CANNOT PROVE

Activity can show that context was concentrated with one person. It cannot prove that no one else understood the issue or cared about the outcome.

NEXT QUESTION

Was the handler’s context visible to the approver—or only available if someone asked?

Compare the rolesFormal authority, recorded work, and evidence of review
RECORDED TITLE VS. OBSERVED WORK

A title suggests a role. Verified policy establishes authority. Activity history shows recorded work.

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 Coordinator

The recorded opener and closer for all 12 comparable issues.

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.

These are two illustrative scenarios, not a before-and-after test or measured savings from the 44 requests. They show how a handoff could work with or without the issue history. No timing or savings is estimated.

ILLUSTRATIVE PATH

The receiving approver has to reconstruct the request.

  1. 01Receive
    Question recorded

    The issue handler gathers the customer request.

  2. 02Route
    Highest title selected

    The request moves upward without checking exception authority or attaching its history.

  3. 03Recheck
    Context requested again

    The receiving team asks who can decide and what has already been tried.

  4. 04Redirect
    Work remains blocked

    The handler reconstructs the issue while the authority question is resolved.

WHAT CHANGED

The design risk is rework and an unclear next step. This illustration does not estimate the delay.

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.