My writing voice became a version-controlled file this week, and the best thing it did was say no. Then a reader's feedback shipped as an amendment.
Halfway through the week, an artificial intelligence assistant told me, in effect, “No”. And it was the most useful thing any tool did for me all week. The backstory: my writing rules had been scattered across an assistant’s memory for months, accumulating the way guidance usually does, one correction at a time, with no canonical home. We consolidated them into a single voice file with a standing instruction attached: load this before drafting anything in my name, every time. The rule got its test a few days later when the file wasn’t available in a session, and the assistant stopped and asked for it rather than approximating my voice from memory. An assistant doing its best impression of me is a liability wearing a helpful expression, and the refusal is what makes the file worth having.
The system worked because it refused to improvise.
The second thing that happened to the file matters just as much. I’d asked the most senior designer in our org for straight feedback on my Monday note, and what came back was structural and specific: the recap section earns its place, one forward-looking section was doing two jobs and needed splitting into two, and the note should open with my own read rather than the chief executive’s relayed thoughts, because the translation is the useful part. Also: schedule it for Monday morning, never Sunday night, and condense harder. I restructured the ritual the same day, and then the feedback went into the voice file as a dated log entry, next to the rules it amends.
Which means my voice now versions like software. It has a canonical source, a changelog, a load-before-use requirement, and a record of why each rule exists, and when a reader’s feedback changes how I write, the change ships as an amendment instead of evaporating into good intentions. I understand how this sounds. A version-controlled personality is the kind of thing a satirist would invent to mock people like me, and I would read that piece with pleasure. The alternative is worse, though: a voice that drifts a little every session, and feedback that gets warmly received and never lands anywhere, while an assistant fills the gaps with its own idea of what I sound like… which is how a person ends up sincerely thanking their team for their robust alignment on the journey.
The pattern generalizes past writing. Any judgment you exercise repeatedly, your voice or your quality bar, can either live in your head, where it bottlenecks on your calendar, or live in a file that tools and colleagues load before acting in your name. The file can be wrong, and when it is, the correction happens once, in a place where it sticks.
The teachable part
Consolidate your writing rules into one file an assistant must load before drafting as you, and append reader feedback as dated entries. A voice becomes maintainable the day it becomes diffable.