{ "schema": "https://ctrlai.com/spec/practice/v0.1", "practiceId": "pra_FvwEyYUXn0UfJpLtYwwmI", "handle": "editorial", "slug": "eight-second-read", "title": "Give my email the eight seconds it will really get — reply with only what survived", "summary": "A skim simulation with measured positions and thresholds: the assistant reads your email the way a busy recipient will — four read positions, a word budget — and reports what survived, what died by position, and the smallest rewrite that moves the action into the read path.", "language": "en", "version": 1, "publishedAt": "2026-07-24T21:13:48.395Z", "canonicalUrl": "https://ctrlai.com/editorial/before-you-send-it/eight-second-read", "versionUrl": "https://ctrlai.com/editorial/before-you-send-it/eight-second-read/v/1", "contentHash": "sha256:11d29f30b6991cf415fb2257b1bec4c2fb8b65f2239f4efc4762673e26953bae", "license": "CC-BY-4.0", "publisher": { "handle": "editorial", "displayName": "Ctrl AI Editorial" }, "credits": [ { "role": "author", "name": "Ctrl AI Editorial", "handle": "editorial", "url": "https://ctrlai.com/editorial" }, { "role": "maintainer", "name": "Ctrl AI Editorial", "handle": "editorial", "url": "https://ctrlai.com/editorial" } ], "lineage": [], "useWhen": [ "Use this before sending any email whose recipient must notice something and act: an all-company note, a request to a busy senior person, an announcement with a deadline, a first approach to a stranger.", "Use it on the final draft, after the content is settled — it tests position and salience, and testing them earlier wastes the pass." ], "avoidWhen": [ "Not for a short reply between people who read each other fully — the test measures skimming, and two lines cannot be skimmed.", "Not for prose owed a slow read: an apology, bad news to one person, anything where being seen to take time is part of the message. Skim-optimizing those makes them worse." ], "failure": "Writers compose for the attentive reader they deserve while the real one skims. Importance-to-me gets mistaken for read-by-you: the ask sits at the end of paragraph three, the deadline is unbolded, the exception hides mid-paragraph — and the reply that matters never comes, not because the email was unclear, but because the sentence that mattered was never read.", "outcome": "Before sending, you know exactly which sentences a skimming reader takes away — and the ask, the deadline, and the consequence are inside that set, verified by re-running the same test on the rewrite.", "instructions": [ { "id": "read-only-the-read-path", "title": "Read only the read path, and quote what survived", "body": "Read the email once, as the recipient does: the subject line, the first two lines as they render, any bolded, bulleted, or numbered fragments, and the last line before the sign-off. That set is the eight-second read; on the first pass, everything else is unread. Report back, quoted verbatim, only what sits in those positions. This quoted set is what survived — do not paraphrase it, and do not credit the email for anything outside it.", "rationale": "Skim reading is positional and salience-based, not importance-based. The writer's sense of what matters has no effect on where the eye lands, so the only honest first read is one confined to where the eye goes." }, { "id": "declare-the-dead-zones", "title": "Declare what died, by position", "body": "List each thing the sender needs the reader to know or do — the ask, the deadline, the exception, the consequence of ignoring it. For each, state where it sits in the email. Anything located mid-paragraph, in the third paragraph or later, or after the first hundred words of context is DEAD by position: say so in those words, quoting the buried text and naming the position that killed it. End-of-paragraph placement only counts as visible when the paragraph itself gets read — end of a late block is a death zone that feels safe.", "rationale": "Content rarely fails by being unclear; it fails by being somewhere the eye never goes. Naming the position, not the wording, points the fix at the real defect." }, { "id": "count-the-runway", "title": "Count the runway against the threshold", "body": "Count the words before the reader learns they have to do something — or that they have to do anything at all. State the count as a number against the threshold: about 40 words. Above the threshold, the ask is buried regardless of how well it is phrased. Report it plainly: \"N words before the reader learns they must act. Threshold is about 40.\"", "rationale": "The runway count converts \"you buried the lede\" from an opinion into a measurement with a target, which makes the rewrite checkable instead of a matter of taste." }, { "id": "audit-the-salience-budget", "title": "Audit the bold as a budget", "body": "Treat bold, bullets, and numbered fragments as one finite salience budget: to a skimming reader, whatever is highlighted functionally is the email. Count the highlighted words. If the highlighting carries more than one idea, name the misallocation: which highlighted material is mechanism or background, and which unhighlighted sentence — usually the action or the by-when — should hold the budget instead. One idea per highlight; the deadline outranks the explanation.", "rationale": "Emphasis spent on mechanism starves the ask. An email can contain its deadline and still hide it, because the eye was spent on the bolded background." }, { "id": "open-with-the-verdict", "title": "Open with the verdict — computed from the core checks alone", "body": "Structure the reply verdict-first: one line — SURVIVES AS WRITTEN or DIES BY POSITION — with the single worst finding attached, then the survived set, the dead list, and the two counts. The verdict is computed from the core checks alone: does each thing the reader must know or do sit inside the read path, and is the runway under the threshold. If both hold, the verdict is SURVIVES AS WRITTEN — for the email as pasted, never for a version you improved — and the reply stops there, with at most two one-line observations filed under a \"Notes, not verdicts\" heading. Anything outside the core checks — an unbolded secondary detail, a subject line you would sharpen, a simulated edge-case reader — is a note, never a verdict, and never blocks the pass. You are not graded on finding something; a pass with zero findings is the method succeeding. When simulating what the skimming reader concludes, mark it as a simulation, and where the text honestly supports a second reading, give it.", "rationale": "The verdict is the finding; making it the first line keeps it from being buried in its own report. Computing it mechanically from the named checks — rather than from an overall impression — is what makes the test a detector rather than a generator of notes." }, { "id": "rewrite-and-recheck", "title": "Rewrite by moving, then re-run the test on the rewrite", "body": "Only when the verdict is DIES BY POSITION: produce the smallest rewrite that moves the action into the read path — the ask inside the first two lines, the deadline bolded or holding the last line, one idea per highlight, exceptions stated where they will be seen. Keep the sender's own words wherever they can be kept — this is a repositioning, not a revoicing. Then run the same audit on the rewrite and report its numbers: runway count, read-path contents, salience allocation. A passing email gets no rewrite. Keep the whole reply under about 350 words plus the rewrite; no general advice about email writing.", "rationale": "A fix checked by the same instruments that found the fault is evidence; a fix that merely reads better is opinion. The output cap keeps the report readable in the same eight seconds it defends." } ], "boundaries": [ "This measures position and salience, not persuasion. An email can pass the skim test and still fail on substance; the test only guarantees the substance gets seen.", "Every SURVIVED or DEAD verdict must quote the text and name the position it rests on. No verdicts from impressions.", "Wrong facts outrank everything here: if a date, name, number, or link in the email is internally inconsistent, lead with that and say that nothing else matters until it is fixed — a perfectly positioned wrong deadline is worse than a buried right one.", "The eight-second frame is a working budget for a busy recipient, drawn from published reading research and email engagement data; it is deliberately below the measured average, not a claim about any specific reader." ], "checks": [ "The reply opens with a one-line verdict, not a summary of the email.", "Every survivor is quoted verbatim; every dead item names the position that killed it.", "The runway is a number compared against the stated threshold, not an adjective.", "The rewrite was re-run through the same read-path test and reports its own counts.", "A clean email got \"survives as written\" and no invented fixes.", "Observations beyond the core checks appeared under \"Notes, not verdicts\" and did not flip the verdict or earn a rewrite." ], "examples": [], "resources": [ { "label": "Nielsen Norman Group — F-Shaped Pattern for Reading Web Content (the positional eye path behind the read-path rule)", "url": "https://www.nngroup.com/articles/f-shaped-pattern-reading-web-content-discovered/" }, { "label": "Nielsen Norman Group — How Users Read on the Web (\"people rarely read word by word; they scan\")", "url": "https://www.nngroup.com/articles/how-users-read-on-the-web/" }, { "label": "Litmus — State of Email Engagement (measured average email read time near nine seconds; the eight-second budget sits deliberately under it)", "url": "https://www.litmus.com/resources/state-of-email-engagement" }, { "label": "Harvard Business Review — How to Write Email with Military Precision (bottom line up front: the ask leads)", "url": "https://hbr.org/2016/11/how-to-write-email-with-military-precision" } ] }