What the Work Produces

Every organisation owns at least one. The handsome document that cost real money, filled a room with nodding, and then changed nothing at all. It is still there, in a drive somewhere, still handsome. Open it and the thinking inside holds up. That was never the problem. The problem was the job it was built to do, which was to be finished rather than to be used.

These are different briefs, and they produce different objects. A thing built to be finished is optimised for the moment it is handed over: complete, polished, closed. A thing built to be used is optimised for every moment after that, when a tired team reaches for it while deciding something real.

Here is the reframe that changes what you make. An artefact is not a deliverable. It is a decision instrument. Its purpose is to help a specific group of people make a specific choice better than they would have made it otherwise. Once you hold that idea, a demanding little question attaches itself to everything you produce. What decision does this improve? If an output cannot answer that, it is not finished. It is merely formatted.

There is a strange trap in finishing things too well. A highly polished artefact sends a quiet signal: the thinking is done, the editing is over, this is complete. And a complete thing invites admiration rather than participation. People receive it, appreciate it, and file it. Nobody picks up a pen to a masterpiece.

A working document with a few visible rough edges does the opposite. It signals that the thinking is still live, that a reader's mark would be welcome, that this is a surface to work on rather than a monument to walk around. The rough edge is not sloppiness. It is an invitation, and invitations get accepted.