Designing Daily Briefings
A daily briefing should reduce cognitive load. It should identify what changed, what matters, what needs approval, and what can be ignored.
When this matters
This page is for operators who want Rocky to produce usable work without turning the system into a mystery box. Use it when you need a practical path, a clear verification step, and a boundary between suggestion and action.
The operating pattern
- Collect sources. Pull only the inboxes, feeds, dashboards, and files that matter.
- Filter aggressively. Silence normal noise and repeated unchanged items.
- Group by decision. Organize around approvals, blockers, opportunities, and FYIs.
- Include evidence. Link to source records or summarize the exact trigger.
- Keep it conversational. Make the report easy to skim on a phone.
Pre-flight checklist
- No-change days can be silent
- Urgent items are first
- Each item has a next action
- Approvals are clearly labeled
- Private details stay in private channels
Common failure modes
- Everything report: A briefing that lists everything helps with nothing.
- No timestamps: Daily reports need freshness markers.
- Action ambiguity: The user should know whether to reply, approve, ignore, or ask for more.
Verification
A page is not done because it was drafted. Verify the source, run the workflow, inspect the output, and record what changed. If a step touches money, customers, accounts, permissions, or private data, keep it behind an explicit human approval gate.