Studio notes from Ashby De La Launde

One reporting week, three surfaces, fewer arguments in the stand-up.

Workspace Anchorcore trains product and data desks to write Cross-Platform App Reporting that survives store delays, SDK drift, and the habit of screenshotting dashboards into Slack. The work is paper-first: definitions, then queries, then the narrative you can defend on a Thursday.

Open the flagship studio →

Laptop showing an analytics dashboard beside a notebook
A desk copy of the Field Ledger: metrics named once, reused on every client.
63shared workbooks in the current catalogue
11 weeksin the longest reporting studio
£1,480desk fee for a full Platform Atlas seat

What people actually said after the first cohort

All desk notes

“Field Ledger forced us to stop treating Android retention as a cousin of iOS. The workbook is fussy, which is the point.”

Priya N., product analytics, Leeds

“I still dislike writing the limitation line in every weekly pack. I now do it because Storefront Discrepancy Lab made the cost of skipping it obvious.”

Client in grocery retail apps

Catalogue

Studios currently on the board

Full listing
Hands holding a phone with app screens

Flagship · 11 weeks

Field Ledger for Product Signals

Name every metric once, then carry it across store, web, and in-app event streams without renaming it in the slide title.

Course page
Smartphone on a wooden desk

Lab · 6 weeks

Storefront Discrepancy Lab

Reconcile App Store and Play Console counts with your own event table before the finance meeting starts.

See listing
Charts printed beside a laptop

Workshop · 4 weeks

Session Graphs for Mixed Clients

Draw sessions that start on web and finish in the app without pretending they are the same person by default.

See listing

What you leave with

A reporting voice that does not collapse when a platform lags

Most teams already have tools. They lack a shared sentence for “this number is late,” “this number is sampled,” and “this number is a different user identity.” Those sentences are the studio’s output.

  1. A metric passportEach measure gets an owner, a grain, and a platform caveat you can paste into any weekly note.
  2. A discrepancy ritualYou practise a fifteen-minute check before publishing, not an autopsy after the exec thread.
  3. A narrative spineThe pack follows cause, coverage, and next experiment — not a gallery of charts.

Cadence

How an eleven-week desk actually runs

Weeks 1–2

Inventory

List every source that claims to count users. Kill duplicate names.

Weeks 3–5

Passports

Write metric definitions with platform footnotes that survive legal review.

Weeks 6–8

Joins

Practice identity, time zones, and store lag on a shared sample dataset.

Weeks 9–11

The pack

Ship a weekly report your PM can read without a translator sitting beside them.

From the journal

All essays
Two phones showing different app interfaces

12 March 2026

Crash clusters that only appear in one store

Why a “platform-wide” incident write-up often hides a vendor SDK that never shipped to web.

Read
Printed charts and a calculator

2 February 2026

When funnels disagree on purpose

A checkout that is three steps on iOS and five on web is not a tracking bug. It is a product fact.

Read
Code on a monitor in a quiet office

19 January 2026

Quiet hours in a release week

The hours when store review queues make yesterday’s dashboard look like a failure.

Read

Bring a messy dashboard. Leave with a desk ritual.

Seats are scheduled around UK working hours. If you only need a definition review, write to the studio rather than buying a full atlas.

Write to the studio