Build enough to improve the conversation

A concrete artifact can change the quality of a conversation.

When people debate an interface, workflow, service, or technical approach in the abstract, each person may be imagining something different. A rough prototype, worked example, test, or written decision makes some of those assumptions visible. The group can respond to what is there rather than to several private pictures.

I value that form of proof of work. I do not think it makes talk cheap or ideas worthless.

Conversation often prevents the wrong artifact from being built. A person closest to the consequences may not have the time, permission, money, or technical access to produce a prototype. Their contribution can still be decisive. Positional authority can be abused, but a title does not make every statement noise. Artifacts also persuade through appearance; a polished demo may conceal missing evidence, maintenance cost, or harm shifted to someone else.

The question is what the uncertainty requires.

If the disagreement concerns whether something can work, a small test may help. If it concerns whose needs count, what risk is acceptable, or whether the work should exist, building first may narrow the decision too soon. Some questions need research, consent, or deliberation before implementation.

When I do build, I try to keep the artifact proportionate. It should test the contested assumption, not smuggle in an entire solution. I name what it demonstrates, what it does not, and what it cost to produce. Then I invite the people affected to interpret the result.

Proof of work is strongest as evidence, not theater. A chair brought into a room proves that one chair was built. It does not yet prove comfort, durability, affordability, accessibility, demand, or the wisdom of producing a thousand more.

Build enough to improve the conversation. Then let the conversation improve what gets built.