Use a doc when the question is conceptual.
Problem framing, strategy choices, product briefs, and risk matrices create alignment before implementation.
Back to Playbook
Notes & essays
The artifact ladder
When the right artifact is a doc, prototype, PR, eval-like check, or operating loop.
01Context
Artifacts should match uncertainty.
An artifact is not automatically useful because it exists. A doc, prototype, PR, eval-like check, or operating loop is useful only when it matches the uncertainty in front of the builder. The artifact ladder is a way to choose the right proof for the question.
If the question is conceptual, write the thesis. If the question is experiential, build the prototype. If the question is readiness, create the check. If the question keeps recurring, build the operating loop. The craft is choosing the smallest artifact that reduces the most uncertainty.
02Model
The artifact matched to the uncertainty.
The model is the part of the article where the idea becomes usable: a sequence of decisions, artifacts, or checks that can guide real product work.
Use a prototype when the question is experiential.
A flow, screen, or real-codebase proof can answer whether value is felt and whether the interaction works.
Use a check when the question is readiness.
Launch gates, eval-like checks, security reviews, and validation scripts make quality inspectable.
Use an operating loop when the question keeps recurring.
Feedback, release notes, monitoring, and cadence turn repeated decisions into a system.
Different uncertainty levels need different artifacts, from notes to operating loops.
- ThesisUse a doc when the question is conceptual.
- PrototypeUse a prototype when the question is experiential.
- GateUse a check when the question is readiness.
- LoopUse an operating loop when the question keeps recurring.
03Medium judgment
The artifact should match the uncertainty.
If the uncertainty is strategic, code may be premature. If the uncertainty is interaction quality, a doc may be insufficient. If the uncertainty is trust, a checklist without implementation may be theater.
The report’s standard project resource kit is the practical version of this ladder: product brief, current-state assessment, source authority, product principles, domain/workflow model, decision log, risk register, execution plan, demo data, design specs, validation matrix, review ledger, launch checklist, closeout, weekly product note, and metrics/experiment log.
04AI-era relevance
When artifacts are cheap, judgment matters more.
AI can produce many artifacts quickly. The differentiator is knowing which artifact reduces the real risk and what review should happen before it becomes evidence.
A generated plan, component, diagram, or QA note is useful only after it has been checked against source truth, product intent, and the risk of the domain. Otherwise it becomes impressive-looking noise.
The smallest useful artifact is the one that changes the next product decision.
From this essay05Artifacts
What this leaves behind.
I use artifacts as evidence of thinking. They make product judgment reviewable, reusable, and easier to connect back to the work.
Product brief
Turns a vague idea into users, scope, acceptance criteria, constraints, and decision rights.
Real-codebase prototype
Proves the riskiest workflow in actual implementation context instead of relying only on static mockups.
Launch gate
Collects security, privacy, payment, content, support, and monitoring checks before public exposure.
Learning loop
Connects user signal, analytics, validation scripts, release notes, and roadmap decisions.