Usage map commission
A drawn atlas of how people move through a digital product — rooms, paths, dead ends — made to hang in the room where the product is argued over.
Read the briefVol. XI · Black Sea desk
How the product is used, written down.
We sit with the traces a live site or application leaves behind — first openings, abandoned checkouts, help-desk tickets, screens nobody reaches — and draw what those traces mean.
The work ends in a bound visual report and a briefing, not in another login. Product teams in Georgia and abroad send us the question they cannot settle from the numbers they already keep.
From the desk
The usage insight study
The flagship engagement is a usage insight study: a commissioned reading of one live digital product, for one primary audience, over three to five weeks. We collect a sample of usage records, sit with eight to twelve people who actually use the product, draw usage maps, and return a visual report plus a ninety-minute briefing.
The study does not rewrite the product. It does not install measurement. It answers a question the team already has and cannot close from the charts on their own wall — why the second visit never comes, why the form dies at the address line, why the help page is opened more than the catalogue.
Teams usually write to us when an argument has gone stale: design wants a new home screen, operations wants fewer tickets, and nobody can point to what people actually do. That is the moment a reading helps.
Related work on the board
Other readings we take
Product usage audit
A one-week reading of the usage records you already keep, naming what they can and cannot tell you about actual use.
Read the brief
Team briefing
A half-day sitting in Batumi or by video, walking a product team through usage findings they already have — ours or their own.
Read the briefLetters to the editor
What a reading changed
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.
The report is dense. I had hoped for a thinner pamphlet. Still, the page on first-run silence — people who open the app and do nothing — is the one we keep on the wall.
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.
Field notes
From the journal
A café table, a checkout, and the Black Sea wind
Watching mobile checkouts on Batumi Boulevard does not replace records. It does name the thumbs, the glare, and the bag on the chair.
When a product team should ask for an outside reading
Not every stuck argument needs a study. The ones that do have a shape: two camps, one chart, and a question nobody can close.
Drawing a usage map from interview notes
How a stack of conversation notes becomes a wall sheet without inventing paths the records will not support.