Building a Small Business Command Surface
A command surface should answer “what needs my attention?” before it shows charts. The best first screen is usually approvals, exceptions, and recent changes.
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
- Start with decisions. Approvals, blockers, urgent messages, and exceptions belong at the top.
- Show source evidence. Each card should link back to the email, form, order, ticket, or log.
- Group by workflow. Customers, vendors, content, domains, operations, and finance may need separate lanes.
- Keep controls explicit. Buttons should say draft, approve, send, mark done, or escalate.
- Add history. Recent actions and audit entries build trust.
Pre-flight checklist
- The first screen is actionable
- Every item has a source
- Risky controls are gated
- Empty states are useful
- Mobile review is readable
Common failure modes
- Dashboard decoration: Charts without decisions do not reduce work.
- Ambiguous buttons: Operators need exact side-effect labels.
- No empty state: A quiet dashboard should explain that nothing needs attention.
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.