How we write

Flagon is a writing company before it's anything else. Not because we love documents, but because writing is the only tool we've found that does the two things a company working in the open most needs: it forces clear thinking, and it leaves a trail anyone can follow later. Talk is fast and disappears. Writing is slower and stays true at 2am for someone in another time zone who wasn't in the room. We bet on the thing that lasts.

Writing is thinking

The first reason we write isn't to communicate. It's to think. A vague idea can feel brilliant right up until you try to put it in a paragraph and discover it doesn't survive the sentence. That's the paragraph doing its job.

We write to find out what we actually believe. If you can't explain a plan in a few plain sentences, you probably don't understand it yet, and the writing is cheaper to fix than the shipped feature would be. Half of what we call planning is really just writing something down until the holes in it become obvious.

Documents over decks

We reach for a document, not a slide deck, for anything that matters. Slides are built to be presented at a passive room; they hide the gaps between bullet points and reward whoever talks best. A document has to hold together on its own, read cold by someone you'll never brief.

The question we hold a document to: could a new person, months from now, read it and understand not just what we decided but why? Prose forces the connective tissue that bullets let you skip. It's also readable async, arguable in the margins, and still there when memory isn't. More on the mechanics of communicating well lives in communication.

Short proposals before big changes

Before anything significant, a change to the product, a new direction, a decision that's hard to walk back, we write a short proposal first. Not a spec, not a novel: a page or two on the problem, the shape of the fix, and what we're trading away.

The proposal is cheap on purpose. It's much easier to kill a bad idea in a paragraph than after it's built, and much easier for someone to poke a hole in text than to interrupt a confident presentation. Writing the proposal often does the whole job: you go to explain the plan, find the flaw yourself, and never have to build the wrong thing. The ones that survive being argued with are the ones worth doing.

Decisions leave a record

When we decide something that matters, we write down the decision and the reasoning behind it, where the next person will find it. Not the polished after-the-fact version, the real one: what we chose, what we chose against, and why it looked right at the time.

This is what lets us change our minds honestly. When the facts shift, we can go back to the record, see the reasoning that no longer holds, and update it out loud instead of quietly pretending we always thought the new thing. A decision that lives only in someone's memory is one the company doesn't really own. How those decisions get made in the first place is its own page: decisions.

Plain words, no fog

We write plainly and we mean it as a discipline, not a style preference. Corporate fog, the "leverage synergies to drive alignment" register, isn't sophistication. It's usually someone hiding that they don't know what they mean, or hoping you won't notice they haven't said anything.

We use small words, short sentences, and the real subject of the verb. We say "we don't know yet" instead of dressing it up. Plain writing is harder, because it gives you nowhere to hide, and that's exactly why we insist on it. A company that works in the open has to be legible, and you can't read what was written to obscure.