Open risks without an owner or a review date usually aren't being managed.
Meridian's risk register scores probability × impact (1 to 5 each), keeps the response strategy, triggers and residual risk, and lets you filter by status or owner.
1
94
A change agreed on a call and confirmed in email usually disappears by week six. In Meridian each change request carries scope, cost, time, quality and risk impact, then approve or reject with who decided and when.
2
146
The same blocker in three weekly reviews deserves more than a new due date. Check what was tried, change the intervention, and escalate with a decision to make — not just a longer history.
1
2
288
Calling every client request "scope creep" can hide a delivery problem. Check the baseline first: brief, acceptance criteria, recorded decisions. Label only after you know what was actually promised.
A Friday status report should be a dated record, not a one-off email.
Meridian keeps green/yellow/red health, selectable sections, forecast and blockers in project history, so you can copy formatted text when you need to send it.
meridian4pm.com
63
On Meridian paid plans (not Free), "Draft with AI" reads milestones, open risks, change requests, sprint goals and status, and hours logged, then fills a new status report draft.
You review and save. It's a draft, not a send. You still write the judgement.
91
A possible project and a signed commitment should not look the same in a capacity plan. Keep confirmed work visible. Show tentative demand separately, with when it must be confirmed or released.
117
Start with one live project. No big migration.
Keep Jira as it is. Move that project's risk register, change log and status reports into one governance home. Book a weekly 30-minute review slot.
After a month, ask the PM: was Friday easier?
meridian4pm.com
84
An agenda full of project names does not say why anyone needs to be there. For each item, name what the room must change: share, resolve, or decide. Invite for that work, not for the update.
98
Friday status report needs:
1. Dated health call with a reason (kept in history)
2. Status against the sprint goal
3. Top risks with owners
4. Change requests and who decided
5. Blockers, with the ask and by when
6. A forecast
Overdue milestone or unmitigated serious risk? Red.
109
Think in layers, not replacements.
Delivery layer (Jira/Linear): what are we building, and where is it?
Governance layer on top: what could go wrong, what changed, what did we decide, what do we tell the client?
Dev tool tracks the work. Governance tracks the commitments.
1
117
Most of a good status report already exists in the project: milestones, open risks, change requests, sprint goal, blockers, hours logged.
Your judgement is the only part that should be written from scratch. Everything else should be compiled, not remembered.
1
126
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.
3
108
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.
2
177
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.
99
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.
94
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?
1
120
uninstalled vs code! Just a year back, I installed it. Now I am on @t3dotcodes !
103

