Solved Twice, Counted Once
A clean resolution clock hides reopen cycles, unresolved tickets and missing ownership history. Decide what the operating review may publish.
- ROLE
- Service Process Analyst
- TIMEBOX
- 90–120 minutes
- COMPLEXITY
- Advanced / 4 of 5
- ROTATION
- Brief 15 of 16
The decision has already reached your desk.
Customer Care intends to publish team resolution rankings using the duration from ticket opening to the frozen solved timestamp. The result will be used in the next operating review.
Tickets can move through repeated solve and reopen cycles, unresolved cases remain in the estate and one ticket can contain several conversations. A current assigned team exists, but effective-dated team ownership is not present for each status transition.
You must choose the resolution definition that represents the service promise and decide whether the available evidence supports team attribution at all.
Select the resolution-time definition that may enter the operating review and publish, qualify or withhold the proposed team rankings.
Use only ticket and status evidence that occurred by 01 Nov 2024. Keep unresolved tickets in the eligible population, use ticket rather than conversation grain for the service promise, and do not invent historical ownership from a current team field.
Run the brief as a controlled assignment.
The workbench mounts only the listed source neighborhood and supplies neutral starter worksheets. It does not grade the conclusion or reveal the mechanisms planted in the larger assignment.
- Open the dedicated brief workspace and confirm the brief ID in the queue.
- Establish table grain, cutoff and control totals before joining or modeling.
- Make at least two distinct evidence moves and test a credible rival explanation.
- Leave the requested polished artifact, then export the workspace or portfolio package.
The source files are shared; the draft workspace is not. Changing to another full assignment drops brief mode deliberately.
Real tables. A deliberately bounded neighborhood.
These Parquet files already belong to Meridian’s public 96-table estate. Use the mounted schema.table names in SQL or Python; download links are provided for learners working in a local DuckDB environment.
GRAIN / One frozen current ticket record.
CAUTION / solved_at, current status and assigned team can contain later or final facts relative to the reporting cutoff.
GRAIN / One conversation associated with a ticket.
CAUTION / Several conversations can belong to one ticket and must not multiply the service-promise denominator.
ANALYSIS CUTOFF / 01 Nov 2024 / 00:00 ET
Questions to pressure-test—not steps to copy.
These prompts define the analytical territory without prescribing an order, technique or conclusion.
- 01
How do first-solve, latest-solve and sustained-resolution definitions differ?
- 02
What happens to the headline when unresolved tickets remain rather than being dropped?
- 03
How much distortion can conversation-grain joins or repeated solution events introduce?
- 04
Can the available data support descriptive team rankings at the reporting cutoff?
Leave work another analyst can review.
Artifact presence can be recorded; analytical quality remains a human judgment. A complete brief has evidence, reasoning and a decision—not merely executed code.
- 01Ticket-state reconstruction
Derive first solve, reopen cycles, final observed state and censoring from ordered eligible events.
- 02Resolution-definition comparison
Compare at least three defensible clocks with control totals and unresolved-case treatment.
- 03Attribution ruling
Publish, qualify or withhold the team ranking and identify the exact missing ownership evidence.
- 04Operations review artifact
Recommend one governed service metric and one process intervention with a clear limitation.
Review the reasoning after a real attempt.
The debrief does not contain an official answer. It identifies defensible analytical moves, common failure modes and questions a reviewer may use to challenge the handoff.
SPOILER-GATED REVIEW / REVEAL AFTER YOUR FIRST HANDOFF
DEBRIEF REVEALED / THIS MAY CHANGE HOW YOU APPROACH THE BRIEF
A service clock is a state definition, not a subtraction between two convenient fields. Reopens, unresolved work and ownership history determine what the result can support.
Defensible approaches
- Reconstruct eligible milestones from ordered status history and retain every ticket in the reporting population.
- Compare first, latest and sustained solution definitions while showing unresolved cases rather than discarding them.
- Use conversation data only for declared segmentation and explicitly withhold historical team rankings if current assignment is the only ownership evidence.
Common traps
- Using frozen solved_at as an as-of fact or excluding unresolved tickets from the denominator.
- Counting conversations or SOLVED events as independent resolved tickets.
- Attributing an entire ticket history to the current assigned team without effective-dated ownership.
Reviewer questions
- What customer promise does the selected resolution definition represent?
- Where are unresolved and reopened tickets visible in the result?
- Can the proposed team label actually be reconstructed at the relevant time?
CHALLENGE A COLLEAGUE
Pass the Brief
The link shares this spoiler-free briefing. It never includes your work, identity, or browser progress.SUGGESTED NOTEA ticket can be solved, reopened and solved again—but the scorecard showed one clean clock. I reconstructed it in Solved Twice, Counted Once from The Analyst.
