Home / Field notes

Reading time is a CISO question, not a copy question

When a CISO closes the tab three minutes in, the problem is rarely the headline. It is the editorial structure.

In every cohort of the CISOs as Readers track at least one team realises that their flagship long-form pieces are not finished by the very buyers they were written for. The data is unkind. Senior security leaders read on phones, between meetings, with a tolerance that resembles a researcher’s skim more than a reader’s patience.

Reading time is therefore an editorial question. Headline craft helps; structure helps more. A piece that earns the first three minutes opens with the practitioner stake, presents one sharp claim, then offers an exit ramp at minute three for readers who needed only the executive summary. Readers who stay past three minutes signal real interest, and the piece can earn back the remaining twelve minutes with the supporting evidence.

The structural pattern is not new; it is borrowed from technology trade press of the last twenty years. What is new is applying it to vendor content with the same rigor. We rebuild the editorial brief with reading time as the constraint, then prune until the piece passes a stopwatch test in the cohort. The pieces that pass tend to outperform their longer originals on the metric vendors actually care about: the next conversation.

Read next