←

Strata Field Notes · Issue 14

The Sediment of a Product

Six layers of a rebuild, laid down one on top of the next. Scroll and each chapter settles onto the pile — nothing is thrown away, everything compresses under what came after it.

Longform 18 min read Nov 2026 Strata Studio

Scroll to stack

Layer 01 · March

Discovery

The Ground Survey

We spent nineteen days doing nothing but watching people fail to file an expense. No prototypes, no whiteboards — just recordings and a shared tally.

The old console had accreted eleven years of exceptions. Every team we interviewed had a private workaround, and four of them had built spreadsheets that were, functionally, competing products. The survey's job was not to design anything. It was to establish where the bedrock actually sat.

  • 19Days of observation
  • 41Sessions recorded
  • 7.4mMedian time to file
Ines Marchetti · Research Lead Read the survey

Layer 02 · April

Architecture

Cutting the Trench

Before rebuilding anything we cut a vertical slice — one workflow, end to end, through every layer of the stack.

The trench went from a receipt photographed in a taxi to a line item in the ledger, and it was allowed to be ugly. What mattered was that it crossed all six systems in one continuous cut, so we could see which seams leaked. Two of them leaked badly. We found both in week one instead of week thirty.

  • 6Systems crossed
  • 2Leaking seams found
  • 11dSlice to first demo
Tobias Renn · Principal Engineer See the slice

Layer 03 · May

Design System

A Language for Edges

Most systems document the happy path beautifully and abandon you at the error state. We wrote ours backwards, starting from the failures.

Empty, partial, stale, rejected, offline, over-quota. Six edge states got named, tokenised and illustrated before a single button variant was drawn. By the time the component library shipped, designers were arguing about which failure a screen was in — which is exactly the argument you want them having.

  • 6Named edge states
  • 84Tokens published
  • 31Components retired
Marisol Quint · Systems Design Open the library

Layer 04 · July

Migration

The Load-Bearing Week

Every rebuild has one week where the old thing and the new thing carry the weight together. Ours was the second week of July, and we planned it like a bridge lift.

Traffic moved in four steps, each one reversible within ninety seconds. We kept a paper runbook on the wall because we did not trust our own dashboards to survive the cutover. They did survive. The paper stayed up anyway; it is still there, annotated.

  • 4Traffic steps
  • 90sRollback window
  • 0Ledger corrections
Devon Achebe · Platform Read the runbook

Layer 05 · September

Operations

Pressure & Compaction

Two months of real load did to the product what two months of sediment does to sand: it squeezed out the air.

Forty-two features shipped in the rebuild. Nineteen were used by fewer than one percent of accounts after eight weeks, and we deleted fourteen of them rather than maintain a museum. The pile only holds if the lower layers are dense.

  • 42Features shipped
  • 14Deleted by autumn
  • −38%Support volume
Priya Raghunath · Ops Analytics Deletion log

Layer 06 · November

Retrospective

What the Core Sample Says

Drill down through the finished product and you can still read every layer in the wall. That legibility was the actual deliverable.

New engineers are handed this stack on day one, not an onboarding deck. They read it top to bottom, then bottom to top, and by Thursday they can tell you why the expense form has a strange field in it — and why removing it would be a mistake.

  • 6Layers documented
  • 3.1dMedian onboarding
  • 1Wall of paper
Ines Marchetti · Research Lead Download core sample

Strata publishes one rebuild every quarter, in layers.

No executive summaries, no case-study gloss. Each issue is assembled from the artefacts the team actually used — runbooks, deletion logs, the annotated paper on the wall.

Issue 15

A payments team that shipped nothing for eleven weeks, on purpose, and what they found underneath.

Issue 16

Two design systems merged into one, told from the side that lost most of its arguments.

Archive

Thirteen back issues, each still readable as a stack. Nothing has been flattened into a summary.