<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Risk on D. Sébastien Taggart</title>
    <link>https://www.sebastientaggart.com/tags/risk/</link>
    <description>Recent content in Risk on D. Sébastien Taggart</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 22:13:05 -0400</lastBuildDate>
    <atom:link href="https://www.sebastientaggart.com/tags/risk/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Monthly program management reviews: practical talking points</title>
      <link>https://www.sebastientaggart.com/writing/monthly-program-management-reviews-practical-talking-points/</link>
      <pubDate>Sun, 02 Feb 2025 21:22:37 -0400</pubDate>
      <guid>https://www.sebastientaggart.com/writing/monthly-program-management-reviews-practical-talking-points/</guid>
      <description>How I use monthly program management reviews to surface risk early, keep financials honest, and avoid wasting a leadership audience on Jira trivia.</description>
      <content:encoded><![CDATA[<p>A lot of shops run a monthly program management review (PMR), sometimes scoped to a portfolio, a sector, or a cluster of accounts. The format varies, but the purpose is usually the same: give leadership a straight read on how work is going, with enough lead time to do something about trouble. After the better part of seven years presenting for one project at a time (and sometimes juggling several in the same cycle), I treat the PMR less like a status meeting and more like a risk radar pass. If I walk out and nobody knows what could go wrong in the next sixty to ninety days, I did it wrong.</p>
<p>Here is the distilled version of what I actually say, and what I leave out.</p>
<h2 id="lead-with-risk-not-activity">Lead with risk, not activity</h2>
<p>Delivery risk, staffing risk, financial risk, dependency risk on a partner team, a government milestone that moved, a clearance pipeline that is slower than the staffing plan assumed. That is the spine of the conversation. Activity logs are not.</p>
<p>If the only &ldquo;risk&rdquo; on your slide is that the team worked hard, you are hiding something or you are not thinking hard enough. Mild optimism is fine; vague green is not helpful.</p>
<h2 id="skip-the-minutiae">Skip the minutiae</h2>
<p>Nobody in a PMR audience needs which tickets missed the last release train, unless one of those tickets is tied to a contractual date or a security finding with teeth. The same goes for tool churn inside the team, internal refactor stories, or a blow-by-blow of stand-up hygiene. Those belong in your delivery forum, not in front of people who fund and defend the work at a higher level.</p>
<p>If you are not sure whether a detail is relevant, ask whether it changes a date, a dollar amount, a compliance posture, or someone&rsquo;s reputation with the client. If none of the above, cut it.</p>
<h2 id="do-not-read-what-they-can-read">Do not read what they can read</h2>
<p>Assume leadership already has the burn chart, the staffing snapshot, or the monthly financial packet. Your job in the room (or on the call) is interpretation: what changed, what it implies, and what you need from them. If you spend ten minutes narrating columns they can scan in thirty seconds, you lose the room and you burn the slot you needed for the one awkward topic that actually required judgment.</p>
<p>Touch the categories that matter for <em>this</em> month. If staffing is stable and boring, say it in one sentence and move on. If cash timing is the story, open with that.</p>
<h2 id="financials-two-things-people-actually-need-from-you">Financials: two things people actually need from you</h2>
<p>Every org packages numbers differently, but in practice I anchor on two points when finance comes up at all.</p>
<p><strong>Margin or profit against the estimate at complete (EAC).</strong> EAC is just the current forecast of what the work will cost and earn when it is all done. Either you are tracking at or above plan, or you are not. If you are above plan, say it plainly (and do not pad the slide with self-congratulation). If you are below plan, pair the fact with what you are doing about it: scope control, staffing mix, fee discussion with the client, whatever is real. A surprise &ldquo;we are fine&rdquo; that turns false next quarter is worse than an early &ldquo;we are soft and here is the recovery path.&rdquo;</p>
<p><strong>Payment status.</strong> Are invoices current? If anything is past due, say why (government processing delay, disputed line item, paperwork on our side) and what is in flight to fix it. Past-due receivables are a leading indicator of relationship or paperwork problems, not just accounting trivia.</p>
<p>If your PMR does not usually go deep on finance, still have those two answers warm in your head before you walk in. Someone will ask.</p>
<h2 id="never-surprise-your-own-leadership-in-public">Never surprise your own leadership in public</h2>
<p>If you need to surface something that makes your chain of command look out of the loop (a client blow-up they have not heard, a staffing cliff you have not socialized, a fee write-down you have not previewed), the PMR is the wrong first venue. Either you have aligned with them beforehand, or you hold the item until you have. Ventilating fresh bad news to a broad leadership audience without pre-briefing your boss is how you win a reputation for being &ldquo;transparent&rdquo; once and &ldquo;not safe&rdquo; forever.</p>
<p>The PMR is for coordinated honesty, not ambush.</p>
<h2 id="closing-habit">Closing habit</h2>
<p>Before I close the laptop, I ask whether anything I said would change if my client sponsor were in the room. If yes, I fix the framing next month. PMRs are internal, but they train you for the tone you want when the stakes are external.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
