basforge

Search titles, text and the “If it doesn’t work” cases.

    RU

    The answer in the first sentence, details after

    The first sentence of a section, a message or an email answers the question it will be opened for; reasons, history and caveats come after, in decreasing importance. Someone who reads one sentence leaves with the answer; whoever needs more reads on.

    Why

    People read about 20% of a page’s words, and mostly the beginning: the heading, the first sentences of sections, the first lines of paragraphs (NN/g, 2008). An answer at the end gets read by the few who reach the end.

    The technique is old. In journalism it’s the inverted pyramid: who, what, when in the first paragraph, details below, so the story can be cut from the bottom without losing the meaning. In military correspondence it’s BLUF, “bottom line up front”: the conclusion in the first line.

    What it looks like

    A message to a work chat:

    Hi! Yesterday I looked into why the nightly backup failed. Turns out the disk on backup1
    is 94% full, and most of the space is old database backups — 61 GB of them,
    some from last spring. New backups don't fit anymore. Can I delete
    everything older than 30 days?

    The same, answer first:

    Can I delete database backups older than 30 days on backup1? Otherwise the nightly backup fails.
    
    The disk is 94% full, old backups take 61 GB, the earliest are from last spring.

    The notification and the chat list show the first line — with the question that needs a yes or no.

    Where else

    • A section of a page — the first sentence answers the heading rather than restating it.
    • A commit — the first line says what changed and why: traefik: readTimeout 300s — uploads were cut off.
    • An incident report — the first line: what broke, how long it lasted, whether it works now. The timeline goes below.
    • An email subject — the question or the decision, not “Question” or “Re: meeting”.