This is what a Cirql field report looks like after the interviews are in. Data below is from a fictional industrial manufacturer — same structure, same aggregations, same visuals you'll get from your own campaign.
Field report · 18 interviews across 3 sites · four rungs from floor to COO. Every number below is derived from the interviews. Quotes are verbatim; names appear only when the respondent opted in.
7 of 18 opted in to attributed quotes — the rest are quoted by rung.
218.4 hrs/week of friction identified across 18 respondents.
28 spreadsheet-citing findings · 19 paper-trail findings · 5 tool categories.
Every person, tool, and finding from this assessment — and how they connect. Hover or search to walk the neighborhood. Orange diamonds are high-impact findings.
Ranked by severity-adjusted impact — emotional drain weights in, not just hours math. Each finding grounded in a real interview quote.
“Every lot waits on Dan. If he's in a meeting, the line sits. I've waited 45 minutes for a sign-off on a lot that took 20 minutes to run.”
— A floor operator (Production)
“The scheduler exports from SAP, cleans it in Excel, and re-imports. Nobody trusts SAP's native scheduling because the data goes stale overnight.”
— Maya Patel, Production Scheduler
“Day shift writes on the whiteboard, swing texts me, nights emails themselves. Nothing's written down the same way twice.”
— A supervisor (Production)
“We've got two drivers and one dock, and on Tuesday mornings when the SAP schedule drops we're stacked up for an hour.”
— A floor operator (Akron Plant)
“We scan them at the end of the shift. Half the time the handwriting is bad and someone has to call the operator back.”
— A QA technician (Cleveland Plant)
“I'd love to automate it but nobody owns that workbook — I just inherited it when Gary retired.”
— A scheduler (Cleveland Plant)
“Frank used to keep it updated. He retired in November. Now when new techs ask, we just point at the binder.”
— A maintenance tech (Cleveland Plant)
“The batches that closed at 2am don't show up in SAP until morning. So our 7am schedule is already wrong.”
— Maya Patel, Production Scheduler
Ranked by ROI — hours saved per week divided by effort-to-fix score. Split by who solves it: Cirql (or an in-house dev team) vs. your own ops leadership.
“Exports, clean-up, re-import. Every single morning.” — Maya Patel, Production Scheduler
“I inherited the workbook; nobody trained me on a better way.” — A scheduler (Cleveland Plant)
“It's a Word doc on SharePoint from 2019. New techs never find it.” — A maintenance tech (Cleveland Plant)
“Day writes on the board, swing texts, nights emails themselves. No standard.” — A supervisor (Production)
“Half the handwriting is bad and we call operators back.” — A QA technician (Cleveland Plant)
“Every lot waits on Dan.” — A floor operator (Production)
Projection assumes linear time savings and ~50 working weeks/year. It does not include second-order effects — unblocked downstream work, reduced handoff errors, morale — which typically compound this number.
reclaimed across quick-win candidates
at steady state
findings touch roles across these rungs
Rung coverage: 10 floors · 5 supervisors · 2 leaders · 1 executive.
“Every lot waits on Dan.”
“Nobody trusts SAP's native scheduling.”
“Half the handwriting is bad.”
“Our 7am schedule is already wrong.”
“We're stacked up for an hour.”
“Frank used to keep it updated. He retired in November.”
“Something's moved but we can't pinpoint it.”
$2,500 · 4 quarterly runs over 12 months · every report anchored in verbatim interviews, quantified, and validated up the rung. Each run after the first shows what changed. Credited toward any Cirql build within 60 days of any run.
