Beverstone · measurement studio

A feature is not adopted because it compiled.

Content Fieldcore trains analysts, PMs, and research partners to measure Feature Adoption Measurement as a craft: cohorts, depth, time-to-second-use, and the awkward week after launch when usage looks busy and means little.

See the flagship studio syllabus

Laptop showing a product analytics dashboard with line charts
A weekly scorecard from a retail client — unique users rose, depth of the new filter did not.
412alumni across 17 intakes
63%still running the same scorecard after nine months
4.3mean written review on our Reviews page
2019studio founded in Beverstone
Programmes

Three ways in, one obsession

Full catalogue
Person reviewing charts on a wooden desk

Adoption Scorecard Studio

Eight weeks building a living scorecard for one real feature. Critique every Thursday. Flagship.

Open the studio
Team discussing notes around a table

Activation Signal Lab

A shorter lab on first-week signals: who touches the new control, who returns, who never finds it.

See listing
Wall of printed charts and sticky notes

Cohort Retention Atlas

For teams drowning in weekly actives. We map retention by cohort and kill vanity rollups.

See listing
What we insist on

Measurement that survives a sceptical director

GB product orgs send us people who can already pull an event dump. They leave able to defend a definition of “adopted” in a board pack without inflating a single chart.

  • Named denominators Every rate names who could have used the feature. “Users” is not a denominator.
  • Depth before volume Repeat use, completion, and time-in-task sit above raw click counts.
  • A written limitation Each scorecard carries the bias it cannot remove. Hiding it is a fail in critique.
From the studio

Voices with a specific syllabus, not a slogan

Module 3 made me drop weekly unique clicks for the new export button. We now track completed exports by account age. Finance stopped arguing with the chart.

Priya N., analytics lead, Leeds — Adoption Scorecard Studio, intake 14

The Activation Signal Lab is dense. I wanted more time on SQL joins. Still, the “quiet week” worksheet is pinned above my monitor.

Client in insurance, Bristol

Longer notes and two case studies

Bring one feature. Leave with a scorecard you can defend.

Places are allocated by intake, not by countdown. Ask us which programme fits the work you already have.

Write to the studio