A surprising number of reporting automation projects succeed technically and fail completely on adoption. The dashboard updates every morning, the numbers are accurate, and nobody looks at it after the second week. That's not a data problem, it's a design problem: the report was built around what was easy to pull, not around the decision it was supposed to inform.
Why dashboards get ignored
A dashboard with thirty metrics on it asks the reader to do the analysis themselves every time they open it. Most people won't, not because they're lazy, but because that's real cognitive work layered on top of everything else in their day. If the automation doesn't do the last step, deciding what's worth attention, it's just moved the manual work from data-gathering to interpretation, which isn't much of a win.
- Lead with what changed, not the full state. 'Refund rate up 40% this week' gets read. A static table doesn't.
- One number per message beats ten numbers in a dashboard nobody opens.
- Push it to where people already are, email or chat, instead of a dashboard they have to remember to check.
- Only alert on what needs a decision. A report that fires every day for nothing gets muted within a month.
Build for the exception, not the routine
The most-used reports we've built aren't dashboards at all, they're a short daily or weekly message that says what's normal in one line and flags anything that isn't. Everything normal gets summarized in a sentence. Anything abnormal gets its own line with enough context to act on it. That asymmetry is what makes people keep reading it six months in instead of muting the channel.
Measure adoption, not just accuracy
We check open rates and reply rates on automated reports the same way we'd check them on a marketing email, because that's effectively what they are: a message competing for attention. A perfectly accurate report nobody reads has delivered zero value, no matter how clean the pipeline behind it is.
Related reading
Approval workflows in Google Forms and Sheets, without an add-on
A request comes in, the right person approves it with one click, nobody has to chase, and there is a record. You can build that inside Google Workspace with a Form, a Sheet and Apps Script. Here is the design, and the five things that break once real volume arrives.
Google Form → Apps Script → Approver → Decision → Sheet
AI shopping agents can now buy from your store. Is your data ready?
In September Shopify switched checkout on for AI shopping agents. An agent does not see your homepage; it reads your product data and believes it. Here is what changed, where stores lose the sale, and the four checks to run before your first agent order.
Buyer asks → Agent → Product data → Checkout → Buyer approves → Your fulfilment
What changed in Google Workspace this September, and what it means for your automations
Workspace Studio flows can now run your own Apps Script steps and call webhooks, Sheets doubled its cell limit to 20 million, Apps Script data regions went GA, and Gemini connects to QuickBooks, HubSpot and Salesforce. A working read of 4 announcements.
Studio flows → Sheets → Apps Script → Gemini
Continues · Got a workflow like this?