What we learned
2/3
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
1
still open
pressed, but unresolved
answeredhighcost
Budget impact and headcount constraints
“There's no budget for a 15% headcount increase this year. For the pilot to be approvable it has to be headcount-neutral.” — FP&A Lead
answeredmediumoutput
Productivity / throughput effect of a shorter week
“We'd model a roughly 10% short-term throughput dip; whether it recovers within the pilot is unproven, and that's the financial risk.” — Finance Manager
gaplowovertime_cost
Overtime / contractor cost exposure
“That depends on the wage-and-hour question, which I don't think anyone's answered yet.” — Finance Manager
couldn't size overtime exposure without the wage-and-hour answer People also lacked
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