The website was working. The analytics were dead.
A rendered page can conceal a failed business dependency.
Read the field noteWolfe / Field notes
What we build, what breaks, and what the evidence says. Notes from connecting publishing, search, measurement, and intake in systems we operate.
Open the notebook
A rendered page can conceal a failed business dependency.
Read the field note01 / Experiments
Field note · 5 min
An experiment ledger needs room for a failed idea and an uncertain result.
Read the note02 / Measurement
Field note · 5 min
Growth reports depend on who was counted and how a session was defined.
Read the note03 / Measurement
Field note · 4 min
A rendered page can conceal a failed business dependency.
Read the note04 / Publishing
Field note · 5 min
A publishing engine needs enforceable rules for what reaches readers.
Read the note05 / Intake
Field note · 5 min
A working form needs an owned handoff and a traceable outcome.
Read the note06 / Publishing
Field note · 5 min
A useful archive needs context, status and a route to the next answer.
Read the note07 / Intake
Briefing · 3 min
An after-hours inquiry tests your intake system. How to measure the wait, assign the next action, and distinguish an attempted call from human contact.
Read the briefing08 / Measurement
Briefing · 3 min
What a firm can learn by connecting inquiry sources to qualification, consultation, and retained matters, with the limits of that attribution stated.
Read the briefing09 / Ownership
Briefing · 2 min
When several providers share the path from search to intake, the handoffs need an owner. A practical way to find the gaps in responsibility and reporting.
Read the briefing10 / Ownership
Briefing · 3 min
Ownership means control of the code, content, accounts, data, and operating knowledge. What a law firm should be able to keep and hand to its next team.
Read the briefing