Build Your Own Workshop

The Whole Thing in One Page

Eight tracks reduce to a short list, and it is worth having the list rather than the tracks.

Measure before you argue. A defect rate across a population is what converts a preference into an engineering problem. Without a number you are expressing taste, and taste loses to whoever has more stamina.

Ask what the failing population had in common. If it includes people who knew the rule, agreed with it, and were trying — you have measured the arrangement, and rewriting the rule is the most natural useless response available.

Move the load-bearing rules from discipline to structure, and name the rung each one sits on. The forbidden thing should be unavailable, refused, or absent — not advised.

Put the boundary where context contaminates and the continuity where it helps, per step rather than per person.

Make the review reject something, or record that it failed.

Write the record at work time, and give it teeth by making something downstream need it.

Serialize what you cannot remove, and design for the holder that never comes back.

Let the measure filter and never rank, and check what your independent confirmations have in common before counting them as two.

The Four Questions to Start With

Not a template — a template would be the wrong deliverable for a quest whose thesis is that structure has to fit the failure you actually measured. Four questions instead, in order.

What is the rule that keeps getting broken by people who agree with it? That is your first structural target, and there is always one.

What did they have in front of them when they broke it, and who put it there? That names the affordance to remove.

Which of your steps are judging steps, and what can the judge currently see? That is where a boundary belongs.

What would your process be unable to prove afterward? That is what the record is missing.

What You Will Get Wrong, Predictably

Three things, and knowing them in advance shortens each by weeks. The first guard will be too broad and somebody will want to switch it off — good, that is the safe direction, and the fix is the block message. The first log will be optional and will be empty within a month — wire a consumer. And the first measure will be used to sort something, because interfaces sort; bin it against ground truth before it acquires a column.

This quest went through the workshop it describes. It was queued as a delegation with a stated pipeline and reviewer. Its structure was agreed at a plan gate before a word was written, with three trade-offs flagged as not the author's to decide. Every stage boundary wrote a log entry as it closed. Its Korean was repaired in a sealed context, and its verification will not pass until every gate is green. It was read cold by reviewers that had never seen the session, and it cannot land except under a lease that makes the commit, the push, the stamp, and the log entry one motion. The workshop wrote none of these sentences. It recorded that somebody did, and it will not let them ship unexamined.

Code

The whole design as a checklist you can take with you·text

BEFORE YOU BUILD
  [ ] a defect RATE across a population, not an anecdote
  [ ] the failing population: did they know / agree / have time?
      all yes -> structural. any no -> it really is discipline.

THE RULES
  [ ] each load-bearing rule assigned a rung:
        1 advice  2 reminder  3 detector  4 refusal  5 absence
  [ ] rung 4+ guards fail LOUD, and the block message names the
      legitimate way through
  [ ] the placement is DATA, so a new pipeline inherits it free

THE BOUNDARIES
  [ ] every step labeled produce / explain / judge
  [ ] judging steps get a boundary sized to how much the judgment
      depends on the artifact standing alone
  [ ] reviewers get the artifact, never the author's summary
  [ ] a round that rejects nothing is recorded as a FAILED round

THE RECORD
  [ ] written at stage boundaries, at the time, with provenance
  [ ] one writer; every other actor is a client
  [ ] append-only ground truth + a mirror that can be REBUILT
  [ ] something downstream FAILS when the record is missing

THE LANDING
  [ ] the steps that must agree are under one lease, breakable on record
  [ ] the commit is built without touching shared staging state
  [ ] the base is chosen after fetching; divergence REFUSES

THE MEASURE
  [ ] validated against ground truth BEFORE it is trusted
  [ ] binned, not just correlated - step, gradient, or coincidence?
  [ ] it filters; the reader's judgment orders
  [ ] independent confirmations checked for a shared method

Exercise

Answer the four questions for one process you own, in writing, in under a page. Then pick exactly one structural change from your answers — the smallest one — and ship it this week. A workshop is not designed and then built; it accretes one guard, one record, and one boundary at a time, each earned by a specific failure you can point at.

Hint

The smallest useful change is almost always a record rather than a guard, because a record tells you where the guard belongs. Building the guard first means guessing, and a guard aimed at the wrong step is worse than none — it costs attention and buys a false sense that the failure is covered.

The Whole Thing in One Page

The Four Questions to Start With

What You Will Get Wrong, Predictably

Code

External links

Exercise

Progress

Comments 0