What we learned
2/2
of what the analyst set out to learn is established. The rest is on your agenda.
2
answered
established with evidence
0
in conflict
teams contradict each other
0
still open
pressed, but unresolved
answeredhighcoverage
Holding customer SLAs at 32 hours a week
“Our support SLA is a 4-hour first response, five days a week. At 32 hours we'd need roughly 15% more headcount, or staggered four-day schedules, just to hold that SLA.” — Director of Support Ops
answeredmediumdemand_pattern
Weekly distribution of customer demand
“Friday is our highest ticket-volume day and p90 response is already 6.2 hours then — above target.” — Support Ops Analyst
Risks & open concerns
Surfaced when the analyst asked what worries people that the agenda missed.
off-agendacoverage
A blanket Friday-off would spike the backlog on our worst day
“If everyone takes Friday we're closing on the day we get the most tickets. Staggering is the only version that doesn't blow up.”
Nothing here is made up
The analyst starts with no figures of its own. It can only repeat numbers it looks up in your records — and if a number isn't on file, it says “unknown” instead of guessing.
0/0
Every number the analyst gave, it looked up first. 0 of 0 lookups found a real entry and used that exact figure; anything it couldn’t find was left blank, never guessed. The records it pulled from are listed below.
The conversations behind it
opening / follow
targeted probe (pushback on a vague answer)
corroboration (source masked to debias)
grade gate under each answer