House method
The Release Ledger
A method, not a product. We ask teams to enter every production ship as if it were a line in a bound book — because App Analytics without a release is a rumour.
Vendor consoles are good at showing you the last seven days. They are poor at remembering which binary went out on a Tuesday and which experiment silently changed the meaning of trial_start. The Release Ledger is the habit of joining those facts: version, surface, owner, overlapping events, and a sentence that says what you expected to see.
Students meet the method in week two of The Release Lattice. Shorter seats borrow a page of it. Chamber Counsel keeps the book for a year.
Columns we insist on
| Column | Why it exists | What we refuse |
|---|---|---|
| Ship identifier | A version or build the warehouse can join. | A Slack message with no number. |
| Surface | iOS, Android, or a named slice — never “mobile” as a mush. | A blended chart that hides a dead platform. |
| Owner | A person who can retire the event when the meaning moves. | A team name that outlives every individual. |
| Overlap window | Days the old name still fires beside the new one. | A silent overwrite on release day. |
| Board sentence | What this ship was supposed to change, in English. | A screenshot with a red arrow. |
Why a ledger and not a dashboard
Dashboards answer “what is happening”. Ledgers answer “what did we claim, and did the world agree”. App Analytics work that cannot be audited against a ship list becomes folklore. Folklore is expensive in a trustee meeting.
We are not asking you to abandon Mixpanel or Amplitude. We are asking you to stop treating those screens as the filing cabinet. The cabinet is the book; the screen is the blotter.
If this sounds like your wound
Bring a haunted catalogue. We will mark it.
The Lattice Seat is the usual door. If you only need the method described, start with the journal or write a short note. We will not pretend a Gallery Pass is the same work as critique.
Open the catalogue Write to the house