After the sitting

Notes from the people who sat the briefing

These notes name a screen, a stall, or a sitting — not a score. A mild complaint is included on purpose. A reading that never pinches is usually a reading that never looked.

They spent the first week on our ferry booking screens and came back with a map of where ticket buyers hunt for the return date. We had been arguing about colour. The map made the argument look small.
Maka J., coastal ferry operator, Batumi — usage insight study

The report is dense. I had hoped for a thinner pamphlet I could wave in a meeting. Still, the page on first-run silence — people who open the app and do nothing — is the one we keep on the wall.
Levan K., grocery catalogue app — usage insight study

We already had charts from the measurement vendor. Digitalstackcore read the same month of visits as a set of journeys and named the three rooms in the municipal portal that nobody enters after lunch.
Nino S., city services editor — product usage audit, then a map

Giorgi drew our membership renewal path at A1. The dead end after the expired-card message was something we had all seen in tickets and never put in the same picture. Hanging it in the office ended a month of circular talk.
Ana R., theatre membership desk — usage map commission

The Batumi briefing ran long because we kept interrupting. That was our fault. They still sent the recap the next morning with the disagreements listed in the order we actually had them, not in the order that would have flattered us.
Irakli P., language-course booking site — team briefing

Tamar sent back our first sample and asked us to strip the names. We were embarrassed. The second sample was the one they would read. I would rather be embarrassed at the door than in a report.
Sopho D., clinic appointment pages — usage insight study

Longer columns

Two readings, written out

The return date on the ferry desk

Usage insight study · coastal booking · late spring

A Batumi operator of Black Sea crossings asked why so many ticket buyers reached the passenger list and then left. The team had blamed the colour of the continue button. In interviews, buyers were looking for the return sailing on a screen that only asked for the outbound date. The map put that hunt in the middle of the sheet. The colour argument went quiet. The next change was a return-date field on the first ticket screen, which was not in the original brief and did not need a new palette.

The municipal portal after lunch

Audit, then a map · city services · autumn

An editor of a city services portal inherited a measurement account full of daily totals and a rumour that ‘nobody uses it after 14:00.’ The audit said the totals could not settle that rumour: the records did not distinguish a staff login from a citizen visit. After the files were split, the map showed three rooms — school-place appeals, waste-calendar lookups, and a PDF cupboard — that citizens entered in the morning and almost never after lunch, while staff traffic filled the afternoon. The redesign brief shrank from ‘the whole portal’ to those three rooms and a closing hour for the PDF cupboard.

If you sat a briefing with us and want a note added to this page, write to info@digitalstackcore.digital. We will not invent a rating. We will not tidy a reservation until it no longer sounds like you.