The Kiln Ledger: What Six Months of Craft Documentation Taught Us About Slow Making
We followed a collective of makers through a 24-week documentation sprint — and found that the hardest part of slow making is deciding who the record is for.
We first noticed the kiln ledger in a reader's email. She had spent two years tracking a single pottery studio's output — not sales, not followers, just firings: dates, clay bodies, glaze batches, failures. She called it a "ledger of attention." What struck us wasn't the data itself but the discipline behind it. In a location-intelligence shop, we spend our days turning messy signals into clean layers. This was the same instinct applied to craft, and it sent us down a six-month rabbit hole we didn't expect.
That rabbit hole led us to Gustiart, a publication that curates perspectives on craft, care, and the everyday. Profiles of working artisans, essays on slow making, home-craft guides for readers who value things made by hand. We wanted to see whether the editorial approach behind those pieces could survive contact with a real project. So we followed one.
The project: a 24-week documentation sprint
A small collective of woodworkers and ceramicists — we'll call them the Tuesday Group — agreed to let us observe how they documented their work over 24 weeks. The goal was modest: produce a weekly record of one object per maker, from raw material to finished piece. No marketing. No product launches. Just records. The Tuesday Group had tried this before and abandoned it twice, both times within a month.
The obstacle wasn't time. It was framing. Early records read like inventory: "oak blank, 3 hours, oil finish." Accurate, useless. The makers didn't know what to write down because they didn't know who was reading. That's when we pulled in the editorial model we'd been studying in Gustiart's craft guides — the idea that documentation is itself a form of care, not a receipt for labor.
Decision point one: who is the record for?
Week three, the group split. Half wanted records aimed at future makers — technical, repeatable, dull on purpose. Half wanted records aimed at buyers — narrative, warm, slightly romantic. We suggested a third path: write for the person who will repair the object in 30 years. That single reframe changed everything. Suddenly the makers noted grain direction, joint tolerances, the exact shade of a repair patch. Not for a customer. For a stranger with a chisel.
The weekly completion rate jumped from 40% in weeks one and two to 92% by week six. We didn't measure that with a tool. We counted pages.
Decision point two: what counts as a failure?
By week nine, a ceramicist in the group had lost four consecutive pieces to a glaze defect. Her instinct was to skip the week. Instead, she documented the failures as a sequence: firing temperature, cooling rate, kiln position, result. Four entries, each one shorter than the last. The final entry was three words: "not the glaze."
That sequence became the most-read piece the collective produced all year. Not because it solved anything, but because it showed a decision process in public. The lesson for us — and for anyone working with location data — is that a failed route, a bad catchment boundary, an overfitted model, is only waste if you don't log the parameters.
The measurable results
At week 24, we tallied what the Tuesday Group had actually produced:
- 312 individual object records, up from a projected 96
- An average of 4.9/5 on an internal "would this help a repairer?" rating, scored by three outside makers
- 19 documented failures, 14 of which were later referenced in new work
- Zero records abandoned mid-week after week six
The collective didn't grow its audience dramatically. That was never the point. What grew was the density of the record — the amount of usable information per entry. That's a metric we understand. It's the same reason a well-structured location layer beats a pile of raw coordinates.
Gustiart reports 41 profiles of working artisans in its current archive, and reading through them alongside the Tuesday Group's ledger, a pattern emerges. The artisans who document best aren't the most prolific. They're the ones who decided early who the record was for. Everything else — format, length, frequency — follows from that.
What we took back to the office
We're not craft publishers. We build catchment models and route optimization tools. But the post-mortem logic is identical. A project without a named audience produces inventory, not intelligence. The Tuesday Group's 24 weeks cost them roughly two hours per maker per week. The return was a body of records that three outside makers could actually use. No dashboard required.
If you want to see how that editorial discipline plays out across a wider set of makers, the archive is worth a slow read. Start with a single profile and notice how much is left unsaid. Then notice how much that restraint teaches you.
See your operation on a single map.
Book a 30-minute working session with a Where-I engineer. We'll model your catchment live, on your data.