Memos do not need to be long — a short note is enough if someone reading it later can understand what happened. When possible, use this structure: What happened → What the store did → What happened next.
Stock of a popular size became very low in the afternoon. The team shared the stock situation and began suggesting alternative sizes and products. Several customers purchased alternatives.
You don't need Memos to repeat what's already visible on the dashboard.
Not useful: "Conversion was low today."
More useful:
Fitting-room waits continued from 3:00–5:00 p.m. One staff member was assigned to fitting-room support, which reduced coverage on the main sales floor.
Record what you actually observed rather than presenting an assumption as a confirmed cause.
Sounds certain, but isn't: "Traffic increased because we changed the entrance display."
More accurate:
Changed the entrance display. More customers appeared to stop and look at the display during the afternoon.
Campaign:
First day of the campaign. Interest in the featured products was strong from the morning, with several customers shopping for gifts. We will continue to watch the response over the weekend.
Stock:
Several sizes of a popular item sold out in the afternoon. The team suggested alternative sizes and products, but some customers decided not to purchase.
Merchandising:
Changed the display near the entrance. More customers appeared to stop and look at the products than before.
Staffing:
Changed staff coverage to support the afternoon peak. Waiting times decreased and the sales floor became easier to manage.
Simple observation:
A relatively quiet day. No major operational issues.
New to Memos? See "[New Flow] What are Memos?" for an overview, or "[New Flow] How to Add a Memo" for the steps.
If you have any questions or feedback, please contact support at [email protected].
