Talk about your next project
incident.io content marketing

The lesson

In a guide chapter, compare the common ways to measure something, name the one you trust, and then show exactly how you calculate it so readers can check your logic.

The move

A left 'CHAPTER LIST' sidebar places 'Time spent in incidents' inside the 'Insights' section, and the chapter opens with questions about what makes an incident the worst kind. 'Calculating time spent in incidents' weighs 'Start-to-end duration', 'Duration × headcount' and 'Actual person-hours', and a shaded callout says the rest of the section turns incident.io-specific. 'How we measure it' lists three numbered rules, followed by 'A worked example' with timestamps and a cap for people working on parallel incidents. 'Working, late, and sleeping hours' sets out three time buckets, and 'Why it matters' closes with four questions the metric can answer before Previous and Next links.

Why it works

  • Our readSetting the three measurement options side by side, each with its flaw, lets the reader see why person-hours is chosen before any product appears.
  • Our readThe callout that flags the switch from platform-neutral advice to product details tells the reader where the guide stops and the product starts.
  • Our readThe numbered rules and a timestamped worked example answer the 'how do I trust the data?' question the chapter raises in its own words.

What not to copy

Don't copy incident.io's activity rules, time windows or hour buckets. Keep the sequence of options compared, chosen method, flagged product turn, step-by-step rules, worked example and a closing list of questions the metric answers.

More from incident.io

More content marketing

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.