Operational report that surfaces exceptions
A daily summary that tells a manager what needs attention, not everything that happened.
Concept: a morning report that surfaces exceptions by owner: stuck leads, overdue tasks and a failed integration, sent to Yoav at 07:30.
The idea
Managers get dashboards that show everything and read none of it. The useful question each morning is smaller: what stopped moving since yesterday, and who should act on it?
The design question
The data exists, in the CRM, the calendar and the call log, but assembling a view takes someone's morning, and by the time it's ready it's already old. The report should do the assembling, apply the team's own definition of an exception, and stay short.
Components
- Rules for what counts as an exception
- Defined with the team: a lead without contact for a set number of days, a meeting without a follow-up task, an overdue task, an automation step that failed.
- A short summary grouped by owner
- Plain language, one section per person, sent by email or WhatsApp at a set time, with a link back to each record.
- Reply to act
- The manager replies with a decision, such as reassigning a lead or closing a task, and the CRM is updated from the reply.
- The system reports on itself
- Failed or skipped automation steps appear in the same report, so a silent failure never stays silent.
Status
A demonstration with fictional data. It draws on reporting, notification and monitoring work from client engagements, but this specific report is a concept rather than a delivered product.
Design goals
- Design goal: one short message a day instead of a dashboard nobody opens
- Design goal: exceptions defined by the team, not by a template
- Design goal: automation failures are visible the same morning
Tools
Fireberry, Google Sheets, Make, Email and WhatsApp delivery, Webhooks and custom APIs