One note per live piece of work, holding its actual state and the next concrete step — not a status.
"In progress, 60%" transfers nothing. What transfers is: what has been decided, what was tried and rejected, what is blocking it now, who is waiting, and the specific next action. Someone reading that can act tomorrow. Someone reading a percentage reconstructs it by asking around, which is most of what the three-to-nine-month ramp actually consists of.
The scale is worth stating because it makes this look like engineering work rather than paperwork. The same survey of 80 organisations estimated that halving ramp time would recover the equivalent of 17 developer-years across one year's new hires. Reconstruction is not a rounding error; at any real headcount it is one of the largest recurring costs a team has, and it is paid silently every time someone changes role.
Include the decisions already made and the options already rejected. Without them the next person re-proposes the rejected option in week three, in front of the people who rejected it, and spends credibility they had no reason to spend.
Be explicit about what is stalled versus what is moving. A stalled item that looks live is worse than a dropped one, because nobody escalates it — it simply sits there being nominally owned.