Extras · 1 of 4

A typical day

Start by checking what changed: a release is coming and three features need documenting. You read the ticket, try the feature yourself, and find that it does not work the way the description says. You message the engineer, get half an answer, and book fifteen minutes with them. Then you write, which is mostly deleting: cutting a six step procedure down to four and making sure every screenshot matches the current version. Afternoon is review comments from a previous draft, and a meeting where somebody asks whether the help site can explain a decision the product team has not made yet.