Plate I · Ponts Green · Est. 2017

The product has a plot.


Index Mapgrid is a small house in East Sussex that treats App Analytics as survey work. We do not decorate dashboards. We teach teams to name what happened, keep the grid from rotting, and bring a Monday meeting a plot it can defend.

Open the Plot Room syllabus

Dark panelled room with a long table, used as a stand-in for the Plot Room

The Plot Room is not a tool certification. It is a nine-week survey of how an application actually behaves.

“We had been reporting a D7 that only existed if you counted calendar weeks. The isoline exercise made the fiction visible in one Friday export. I still wish the homework had assumed a thinner warehouse.” Amelia Crowe · staff product, Brighton · Grid Instrumentation

Heard after the survey

A reservation, then a quieter Monday.

Alumni do not arrive as analysts and leave as analysts with nicer slides. They leave with an event dictionary a designer can argue with, a cohort window that matches how the product is actually used, and a habit of writing down what a chart is not allowed to claim.

The house is particular. We will not certify you on a vendor. We will not stand up your production stack. If that is what you need, write to the desk and we will say so plainly.

Longer readings from the desk

Night city lights suggesting a surveyed field
Flagship plate: Grid Instrumentation.

Flagship

Grid Instrumentation

Nine weeks on the event grid a product actually lives on. You will draft a taxonomy, kill vanity steps, set identity seams, and present a weekly plot that survives a sceptical engineering lead.

Taught by Isolde Venn, who ran measurement for a Hastings travel app before the house opened its first cohort. Live critique is fourteen hours across the term; the rest is written survey work on your own product, or on our sandbox if yours cannot be shared.

Read modules and limits

Method

How a desk keeps a plot.

  1. Name the ground

    Every event on the grid must describe a behaviour a human did, not a screen a system drew. We spend the first fortnight arguing about verbs until the dictionary can be read aloud.

  2. Draw the window

    Cohorts inherit the product’s real return rhythm, not the calendar. A travel app and a grocery list do not share a D7, however tidy the board pack looks.

  3. Survey the drop

    Funnels are allowed only where a person could have chosen otherwise. We strike steps that exist to make conversion look continuous.

  4. Keep the weekly plot

    One page, one claim, one limitation. The house treats the Monday note as a craft object, not a screenshot dump.

Also in the catalogue

Shorter surveys.

Lake and ridgeline at dusk

Five weeks

Retention Isolines

Reading return as contour, not a single heroic line. For teams who already have events and still cannot say who comes back.

High mountain ridge under cloud

Four weeks

Funnel Surveying

Diagnosing conversion collapse without padding the path. Includes a session on what not to put in a board funnel.

Night sky over a dark landscape

Three weeks

Identity Seams

Stitching anonymous to known without shredding historical cohorts. Dry, necessary, and rarely taught with this much caution.

The full catalogue

From the journal

Recent field notes.

All journal plates


The house keeps office in Ponts Green.

Fees are listed without a checkout. If a survey fits your desk, write to us. If it does not, we would rather say so than fill a cohort.

Write to the desk