Every post here started as a problem on a real program: a status report nobody read, a RAID log that died in week three, a charter that could not answer whether the thing was in scope. The templates are the artifacts. These are the arguments behind them.
The whole catalog in one place, with what each tool is for.
Two artifacts that look interchangeable until the week they aren't. These are the posts to read before you pick.
Most programs need both a RAID log and a risk register. They serve different cadences and audiences. A 20-year program manager's take on when to use each.
Read it ›A pre-mortem is a forecast. A post-mortem is an autopsy. Both ask why the program failed. A 20-year program manager on when to run each, and how to make one feed the other.
Read it ›A program charter is not a project charter dressed up. The differences (out-of-scope, governance, outcome metrics) determine whether the artifact survives month four.
Read it ›A decision log records why a choice was made. A change log records what moved after commitments were set. A 20-year program manager on when to use each.
Read it ›A RACI matrix allocates authority. A stakeholder communication plan allocates information flow. Most teams build one and think they covered the other. A 20-year program manager on why you need both.
Read it ›OKRs measure whether the outcome is improving. A roadmap sequences the work and names the refusals. A 20-year program manager on running both in Excel.
Read it ›A status report forces decisions weekly. A QBR collects them quarterly. A 20-year program manager on how the two artifacts feed each other, and what breaks when they don't.
Read it ›A prioritization matrix sorts a long list in a live room. A RICE score defends one call in a document. Most PMs reach for the wrong one. A 20-year program manager on when to use each.
Read it ›A KPI tells you the state of the business. An OKR tells you what you are trying to change about it. Confusing the two produces a quarter of measurement with no direction. A 20-year program manager on the split.
Read it ›An issue log tracks what is already broken. A RAID log tracks what is broken plus what might break. Running both usually means running neither well. A 20-year program manager on which one to keep.
Read it ›A status report is a governance instrument on a cadence. An executive one-pager is a persuasion instrument for a single moment. Using one as the other is why sponsors stop reading. A 20-year program manager on the split.
Read it ›One post per artifact. What goes in it, what stays out, and the cadence that keeps it from going stale.
A PM status report template refined across 20+ years of enterprise programs in tech, retail, and aerospace. Four formats, one workbook, picked for the audience in front of you.
Read it ›Most RAID logs become graveyards. Here's the review cadence that keeps yours alive, from 20+ years of program management.
Read it ›A program charter is the written contract between PM and stakeholders before work starts. The seven sections that make a charter useful, and the one-page rule that keeps it readable.
Read it ›A program roadmap that holds through a reorg treats trade-offs as the artifact, not the appendix. Here is the structure that works, and the mistakes that kill roadmap credibility.
Read it ›Build a prioritization matrix leaders trust. Weighted scoring vs. effort-impact grids, when to use each, and how to present to executives.
Read it ›A decision log is the cheapest form of program continuity. Five fields, two minutes, and the call you made eight months ago is still defensible when a new sponsor walks in.
Read it ›Most stakeholder comms plans list channels, not strategy. The matrix that works: who gets what, at what cadence, and what to do when power and interest diverge.
Read it ›The Status Report Cheat Sheet is free. One page, the exact format I use to brief leadership in under five minutes. It is the fastest way to see whether the rest of this is worth your time.