← Cycles
design · c25archivedstarted Mar 16Auto draft — not yet reviewed

Consume During Implementation

Why we did this

We already built each shared part by using it on the design site first, but only by habit. Nobody could see which parts had really been tested.

What happened

It is now principle eight: building a part and documenting it are the same act. All 87 parts were audited, a coverage page shows the gaps, and the worst were filled.

New in this cycleA coverage page lists every part with its states, scenarios and whether all its settings can be tried, plus a gaps-only filter.
At a glance
3
changes
0
conversations
2
decisions
0
outside helpers

What changed

The two changes that matter most, in plain words. Open any one to see it.

  1. 1

    A coverage page lists every part with its states, scenarios and whether all its settings can be tried, plus a gaps-only filter.

    A page that shows what is tested · came from Mark Parsonopen →

  2. 2

    The design site is the first user of every part, and a product bug is recreated there before it is fixed.

    Principle eight: consume while you build · came from Mark Parsonopen →

Also in this cycle
  • 76 of 87 demos showed only the normal state; the biggest gaps were filled the same day. In words

How we got here

Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.

Someone said

From the record: no recorded conversation behind this one.

We decided

c25-D2 Coverage is made visible, not enforced: no gates or thresholds. — Mark Parson

So now

A coverage page lists every part with its states, scenarios and whether all its settings can be tried, plus a gaps-only filter.

Someone said

From the record: no recorded conversation behind this one.

We decided

c25-D1 The design site is the first consumer of every part: building and documenting are one act, and a product bug is reproduced there before the fix ships. — Mark Parson

So now

The design site is the first user of every part, and a product bug is recreated there before it is fixed.

Thanks to

People outside Qpoint first. Every thank-you points at something they said or made.

MP
Mark Parson
Qpoint team

Named the habit and asked how to make it a rule

Described how the policy card was built by using it on its docs page, asked that product bugs be recreated there first, and asked what he was missing.

All images

Every picture from this cycle. Click any one to step through them all.

The pairs

A page that shows what is testedNew in this cycle
Principle eight: consume while you buildNew in this cycle

Everything captured · 2

The full record 0 decisions · 4 key-change entries · 1,072 words · 2 captures

The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.

Open the record for c25 →

Qpoint Brand Style Guide