When spreadsheets hurt, teams push governance into Jira: Risk types, Change Request epics, custom RAG fields.
It rarely sticks. Tickets close; risks need months of review. A change request is a decision, not a task.
Forcing governance into tickets turns judgement into admin.
I've been that PM more times than I'd like to admit.
Friday: copy last week, scroll Jira for the sprint goal, dig the inbox for the change request, check the untouched risk sheet.
The problem was never the writing. It was rebuilding the project from memory every Friday.
Jira and Linear stay current because engineers live in them all day.
Governance is different. Risks, changes, decisions and status sit outside the daily flow, so they drift.
Anything that lives outside the daily flow goes stale first.
Your client isn't chasing the status report. They're chasing the evidence.
A green, yellow or red with nothing behind it is just a mood.
They want three things: are we on track, what could go wrong, and what do they need to do.
Jira is up to date. Your risk register is from week two.
That's not a discipline problem. It's a structure problem: the delivery work has a home, and the governance work doesn't.
Where does your governance live?
"Improve communication" isn't a retro action. Nobody can tell next sprint whether it worked. Pick one friction, one small change, one owner, and the evidence you'll check at the next retro.
Decision logs usually keep the choice and lose the reason. Write down the constraint that mattered, the assumption it rests on, and what would make you reopen it. Months later, that's the part everyone argues about.