A morning report that shows what needs action
A concept for one short daily summary: what stalled, who owns it and where to act.
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
A manager’s morning starts with a practical question: what needs attention today? This concept brings stalled leads, overdue tasks and stopped workflows into one message, grouped by owner.
The design question
The data sits in the CRM, calendar and call log. To turn it into a useful picture, the report needs to connect the sources, identify exceptions using rules the team defines and surface what needs action.
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