<?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>Federal on D. Sébastien Taggart</title>
    <link>https://www.sebastientaggart.com/tags/federal/</link>
    <description>Recent content in Federal 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/federal/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why we ask questions on government RFPs, and what to leave out</title>
      <link>https://www.sebastientaggart.com/writing/why-we-ask-questions-on-government-rfps-and-what-to-leave-out/</link>
      <pubDate>Fri, 02 May 2025 21:08:43 -0400</pubDate>
      <guid>https://www.sebastientaggart.com/writing/why-we-ask-questions-on-government-rfps-and-what-to-leave-out/</guid>
      <description>What bidder questions on solicitations are actually for, and how to avoid handing your competitors (or the government) more than you meant to.</description>
      <content:encoded><![CDATA[<p>If you have ever scrolled the Q&amp;A log on SAM.gov or a contract vehicle, the pattern is familiar. A dozen firms ask variations on the same deadline question, someone asks for a copy of the SOW in a different format, and a few questions read like thinly veiled flexes. I used to assume the obvious frame: people are clarifying ambiguities so they can price the work. That is part of it. After sitting on more proposal teams than I care to count, I think the useful mental model is wider. Questions are a move you make in public, which means it cuts both ways.</p>
<p>Here is the short version of what those questions are actually doing, and what I try never to put in them.</p>
<h2 id="filling-real-gaps">Filling real gaps</h2>
<p>Sometimes the document set is just incomplete. Classic example: the government wants a website or a platform refresh and never pins down the stack, hosting boundary, or integration points. You cannot staff credibly or price integrations if &ldquo;platform&rdquo; could mean anything from static pages to a multi-tenant SaaS replatform. In those cases a tight question is not pedantry; it is how you avoid inventing requirements in the proposal that you will regret in performance.</p>
<p>The knock-on effects are boring but important: SME profiles, subcontractor scope, security artifacts, and test strategy all depend on facts the RFP never gave you. If you do not ask, you guess, and guessing at volume is how you lose money or lose the bid on realism.</p>
<h2 id="surfacing-win-themes-carefully">Surfacing win themes (carefully)</h2>
<p>You can also ask in a way that tees up what you want the evaluators to remember: depth on a specific domain, surge staff, reach-back to a parent org, whatever actually differentiates you. I am not talking about planting a softball so you can paste the answer into Section M verbatim. I mean choosing the dimension on which you are strong and asking a question that forces the government to talk about that dimension on the record.</p>
<p>The catch is the one everyone forgets until they see it in writing: the answers go to <em>everyone</em>. Your competitors read them. If your question is basically &ldquo;please confirm that only a vendor with our exact past performance could possibly comply,&rdquo; you have told the room where you intend to score. Sometimes that is fine. Often it is free intelligence for everyone else.</p>
<h2 id="shaping-the-requirement-sometimes">Shaping the requirement (sometimes)</h2>
<p>On small competitions, a well-placed question can nudge the requirement without looking like lobbying. I will cop to the less noble version too: occasionally a question is there to signal sophistication more than to learn anything. That is a strategy, not a virtue, and it works less often than people think. Still, in a thin field, one clarification can move the goalposts in your favor. In a crowded field, the same move just trains the government to tighten language against you.</p>
<h2 id="mitigating-risk">Mitigating risk</h2>
<p>A lot of what I file under &ldquo;risk&rdquo; is really staffing and level-of-effort hygiene. If the backlog is huge and the narrative is vague, you might ask for enough structure (prioritization rules, release cadence, definition of done, rough sizing) to build an LOE that will survive scrutiny. You are not trying to get them to do your estimating for you. You are trying to align on what &ldquo;the backlog&rdquo; means so your WBS does not rest on fiction.</p>
<p>Same bucket: clarifying how they define an SME, what clearance levels actually show up day to day, or whether key roles are government-furnished. Those answers reduce the odds you win on a team paper you cannot execute.</p>
<h2 id="what-i-leave-out">What I leave out</h2>
<p>Two categories, mainly.</p>
<p>First, anything that leaks strategic advantage or inside baseball. If you are the incumbent, you already know where the bodies are buried. Asking about them in the public Q&amp;A is how you prove you are the incumbent while handing every other offeror a free site survey. I treat the Q&amp;A like a glass conference room: assume your competitors and the customer are both watching.</p>
<p>Second, long, nested, technical questions that only a specialist can parse. The people answering are often contracting officers or program staff who are stretched thin. If the right answer is obvious to a non-technical reader, you did it right. If you need five dependent sub-questions to express the dependency, you probably need a different forum (industry day sidebar, oral clarification if offered, or a conversation your capture lead is already having).</p>
<hr>
<p>The discipline I aim for is simpler than it sounds: ask what you need to bid and execute, be willing for everyone else to read it, and save the clever stuff for the narrative where you control the page.</p>
<p>What do you actually use the Q&amp;A for on your bids? I am curious whether your shop treats it mostly as hygiene or mostly as strategy, because the teams I have seen rarely split the difference cleanly.</p>
]]></content:encoded>
    </item>
    <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>
    <item>
      <title>Building the Ultimate Content Editor Experience in a CMS</title>
      <link>https://www.sebastientaggart.com/writing/building-the-ultimate-content-editor-experience-in-a-cms/</link>
      <pubDate>Tue, 02 Jul 2024 21:15:54 -0400</pubDate>
      <guid>https://www.sebastientaggart.com/writing/building-the-ultimate-content-editor-experience-in-a-cms/</guid>
      <description>Principles and feature buckets that keep a rich text editor trustworthy for authors, aligned with the live site, and usable under Section 508.</description>
      <content:encoded><![CDATA[<p>Most CMS projects treat the editor as a checkbox. Pick CKEditor or TinyMCE, wire a media library if you are lucky, and call it done. Then the help desk tickets start: &ldquo;Why does my table look different on the page?&rdquo; &ldquo;I pasted from Word and the whole section broke.&rdquo; &ldquo;Screen reader users say the accordion is unreadable.&rdquo; I have been on both sides of that (the person filing the ticket and the person explaining why WYSIWYG is a lie). The editor is where content quality and accessibility are won or lost before anything ships.</p>
<p>Here is how I think about building an editor experience that authors will actually use without breaking the site, and that auditors will not torch in a 508 review.</p>
<h2 id="principles-that-actually-constrain-design">Principles that actually constrain design</h2>
<p><strong>Simplicity</strong> sounds obvious until you add every toolbar button a power user asked for in a requirements workshop. My bias: default to a short toolbar and progressive disclosure. If a control does not apply to most pages, it belongs in a secondary panel or a structured field, not next to Bold. Fewer choices means fewer wrong choices.</p>
<p><strong>Impossible to break</strong> is not literal (authors are creative), but the goal is valid output. That usually means constraining the schema: allowed tags, allowed classes, sanitization on save, and patterns that map cleanly to your theme. If someone can paste arbitrary HTML from a random website and have it stick, you do not have an editor; you have a footgun with a blinking cursor.</p>
<p><strong>Perfect previews</strong> are the hardest item on the list. &ldquo;What you see is what you get&rdquo; is only honest if the iframe (or live preview route) loads the same CSS, typography, spacing tokens, and component markup as production. If preview runs against a stripped admin theme, you are training authors to distrust the tool. I treat preview parity as a build pipeline problem, not a nice-to-have.</p>
<p><strong>Familiarity</strong> is cheaper than novelty. Bold looks like bold, lists look like lists, link dialogs look like the link dialogs people know from Google Docs or Word. Custom iconography for standard actions is how you get &ldquo;where is underline?&rdquo; in every training session.</p>
<p><strong>508 compliance</strong> is not a bolt-on color contrast pass at the end. It is keyboard operability for every control in the chrome, visible focus, text alternatives for images at insert time, table headers that survive round-trips, and collapsible regions that expose state to assistive tech. If your accordion widget relies on click-only divs with no role or name, you have built technical debt that WCAG will find.</p>
<h2 id="image-management-and-embedding">Image management (and embedding)</h2>
<p>Authors need crop, resize, focal point, and alt text in the flow where they insert the image, not in a separate &ldquo;fix accessibility later&rdquo; queue. Drag-and-drop is fine if the same fields appear for uploads and library picks. Lazy loading and <code>srcset</code> should be automatic; the author should not hand-edit attributes.</p>
<p>I also like forcing a decision on decorative images (empty alt with a real checkbox) so people do not default to filename-as-alt-text, which is a classic 508 fail in the wild.</p>
<h2 id="file-management-and-embedding">File management (and embedding)</h2>
<p>PDFs and Office files are where CMSs quietly become file shares. If you allow arbitrary uploads from the body field, you get duplicate assets, stale versions, and broken links after migrations. A dedicated media or document entity with a stable URL, virus scanning if you are in a regulated environment, and a picker that inserts a shortcode or structured link beats &ldquo;attach whatever.&rdquo;</p>
<p>For federal-ish work, think about whether the file should open in a new tab, whether you need a file type and size label next to the link, and whether the title text is meaningful (not <code>FINAL_v7_really.pdf</code>).</p>
<h2 id="tables-sortable-interactive-compliant">Tables (sortable, interactive, compliant)</h2>
<p>Tables are the #1 source of &ldquo;looks fine in the editor&rdquo; grief. Authors merge cells because Excel trained them to; then responsive CSS and screen readers suffer.</p>
<p>My hierarchy: (1) simple data tables with explicit header rows and no layout tables in the body, (2) optional sorting or filtering only if you have a component that preserves <code>&lt;th scope&gt;</code> relationships and does not rely on hover alone, (3) if you need pivot-level behavior, that is probably not inline rich text; it is a block, a view, or an embed.</p>
<p>Interactive tables also need a plan for mobile (horizontal scroll with a visible cue, or reflow) and for keyboard users (sort controls must be focusable buttons, not mystery clicks on <code>&lt;th&gt;</code>).</p>
<h2 id="accordions-and-collapsible-content">Accordions and collapsible content</h2>
<p>Collapsible sections are great for long policy pages and terrible when implemented as anonymous divs with a chevron image. Use a pattern with <code>button</code> triggers, <code>aria-expanded</code>, and an associated region id. Keyboard support should mirror disclosure widgets in the ARIA authoring practices guide.</p>
<p>From an editor UX angle, treat accordion as a structured block (Gutenberg-style, Layout Builder section, whatever your stack supports) instead of free-form HTML. That keeps markup consistent and previews honest.</p>
<h2 id="formatting-and-cleanup">Formatting and cleanup</h2>
<p>Bold, italic, underline, links, headings, lists, blockquote: ship the boring set first. &ldquo;Clear formatting&rdquo; and &ldquo;paste as plain text&rdquo; (or paste filtering) save more production bugs than another alignment option. Paste from Word is a product feature; test it with real government templates and tables.</p>
<p>If you support subscript or strikethrough for legal or scientific content, expose them; if you do not need them, hide them so authors do not build layouts out of character-level styling.</p>
<h2 id="pre-styled-body-content-callouts-boxes-div-based-patterns">Pre-styled body content (callouts, boxes, div-based patterns)</h2>
<p>Callout boxes (&ldquo;blue half-width note,&rdquo; warning panels, pull quotes) should not be &ldquo;paste this div from the wiki.&rdquo; They should be either (a) a small set of allowed wrapper classes your CSS documents, inserted through a dropdown the editor understands, or (b) custom components with their own fields. Half-width layouts need a grid or breakpoint story on small screens (usually full width below a breakpoint), or mobile users eat the cost.</p>
<p>Whatever you do, avoid unbounded class names in the body. Whitelist classes, map them to components, and validate on save. That is how you keep the experience &ldquo;impossible to break&rdquo; without turning authors into front-end developers.</p>
<p>The editor worth shipping is not the one with the most buttons. It is the one where authors recognize the interface, the preview matches what visitors see, and the output is boring enough for automated checks and screen readers to handle. I am still looking for a stack that nails all of that without custom glue; if you have one, I would like to hear about it.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
