Sample memo
The one page a run actually produces
Every GliddeSignal run ends here: this period's customer reality, what moved since last time, and exactly three actions. This is a real one, from a real run, unedited.
The memo
- Product
- Vebo, a consumer banking app
- Run date
- July 3, 2026 · memo regenerated July 31
- Quotes
- Verbatim from the run's own evidence, lightly redacted
- Compared against
- The project's previous run
Executive Decision Memo
One-page memo you can paste into Slack.
Memo saved: July 31, 2026 at 10:10 AM
Executive Summary
Recent updates to the Vebo app have led to significant performance issues, particularly affecting the loading of balance and card screens, resulting in 207 reports (23.8% of feedback). The app frequently crashes when viewing statements, with 46 mentions (5.4%). New problems have emerged, including unresponsiveness post-update and issues with payment processing, highlighting a need for urgent improvements in user experience, particularly in key functionalities that drive customer engagement.
This Month’s Customer Reality
Users are frustrated by chronic performance issues, especially the app's slow loading and buffering when accessing balance and card screens, responsible for 61 of the mentions. Additionally, app crashes and slow response times for payments highlight operational inefficiencies, causing users to lose trust, particularly when payments do not go through as expected. If these issues are not resolved soon, user retention could decline, notably among travelers who rely on these functions abroad.
What Got Worse
• App Performance & Load Issues rose from 10.7% to 23.8% of feedback, a total increase of 111 reports. Support Experience Issues increased from 8% to 11.4%, adding 27 reports.
What Improved
• Login / Authentication Issues decreased from 27.4% to 7.1%, with 185 fewer reports.
Top 3 Recommended Actions
1. Address the slow loading of balance and card screens; check server response times and optimize the API for faster data retrieval.
2. Investigate the app crashes when viewing statements; instrument error tracking to capture specific push notification failures that precede the crash events.
3. Enhance the payment processing reliability; review recent changes in transaction handling that may cause timeouts and implement user feedback mechanisms to capture payment completion status.
The memo is the run's own output, unedited — including the closing line about travellers relying on the app abroad, which the five quotes above don't evidence. It's a fair example of what a memo reads like, and a fair reminder to check a generated claim against the evidence panel beside it before you act on it.
PDF · 45 KB · one page — the same export the product produces.
The format
Why it's one page
Three actions, not ten. A list of ten recommendations pushes the actual prioritisation onto the reader, who has less context than the tool that produced it.
Every figure traces to the run's own evidence — mention counts, share shifts, and the problems behind them — so a sceptical reader can check it rather than having to believe it.
It's written to forward. The point isn't a document you file; it's the twenty minutes nobody has to turn analysis into something a colleague will read.
14 days · no credit card required
This took one run.
Point it at your own feedback and get the same page back in minutes.
14 days · no credit card required