The commitment email is drafted for tomorrow morning and nobody has said how the quarter could miss. Your cursor blinks at the end of the final line that confirms the delivery date, your half-warm oat latte sweats on the coaster to your left, and the 30-minute team sync that wrapped 20 minutes ago ended with everyone nodding enthusiastically without a single question about potential gaps. You set a timer for 15 minutes right now, no extensions, and work through each step before you hit schedule send.
Map gradual gaps that fly under last-minute checks
Most last-minute risk checks only look for catastrophic, one-off failures that would derail the project in 24 hours, but the vast majority of missed quarter targets stem from small, unaddressed shifts that build over 2 to 7 days, with no one flagging them until it’s too late. When you’re working solo, you might brush off small inconsistencies to hit your send deadline, and when you’re leading a room with no clear point person for risk, everyone assumes someone else is tracking the small stuff. Pull up your calendar and team chat history from the last 7 days, no further back, and jot down every offhand comment, delayed check-in, or off-agenda question that didn’t get a follow-up. You don’t need to dig through months of archives, just the last 7 days, because any risk that will derail this specific commitment would have shown a warning sign in that window, no earlier. Use the table below to log each potential risk that builds over time, not just the big obvious issues that would pop up tonight.
| Risk scenario | First warning sign you spotted this week | Likelihood (1-5, 5 = guaranteed) | Quick mitigation |
|---|---|---|---|
| Third-party vendor delays shipping the core component by 12 days | Weekly vendor check-in noted their staff shortage last Tuesday | Illustrative example: 4 | Move the customer onboarding call 2 weeks out and send a 10% discount offer for the wait |
| One core team member gets pulled to the urgent client escalation next week | They mentioned the client was flagging issues in the team standup last Wednesday | Illustrative example: 3 | Confirm the backup team member has full access to the project folder by EOD Friday |
| Stakeholder shifts priority away from this initiative mid-quarter | They asked for 2 extra progress reports instead of the agreed 1 in the last sync | Illustrative example: 2 | Add a 1-sentence progress update to the weekly stakeholder check-in to keep visibility high |
Lock in a single modification to the drafted email
You do not need to rewrite the entire email, adjust the entire project timeline, or call an emergency team sync tonight. The only change you make to the pre-written commitment is adding a short, clear section that names the highest-likelihood risk you logged, and confirms you already have a mitigation in place for it. Every other line of the email stays exactly as it is, including the final delivery date and list of responsible team members. This keeps your commitment clear and actionable, instead of cluttering it with so many caveats that recipients don’t know what you’re actually agreeing to deliver. This avoids the scope creep that comes with last-minute overhauls, and ensures everyone who receives the commitment knows you’ve already considered risk, instead of sending a blind yes before anyone names potential failure. If you’re working solo, this single modification keeps you accountable to the risk you spotted, instead of pretending it doesn’t exist to hit your send deadline.
Draft targeted mitigations to tie to the commitment
You write the additional section at the very bottom of the email, right above your signature, so it’s the last thing recipients read before they reply. Keep it 2 sentences max: first, name the specific risk you identified, and second, state the mitigation you already have planned to address it if it comes up. For example, if your highest-likelihood risk is the vendor delay, you would write, “Note: We are tracking a temporary staff shortage at our core component vendor that could delay delivery by up to 2 weeks. If this shortage continues past next Tuesday, we will move your onboarding call 2 weeks out and apply a 10% discount to your invoice for the inconvenience.” You do not add extra risks, extra mitigations, or caveats that change the core commitment, just this single, clear add-on. When you send the email, this section is visible to every recipient, so everyone is aligned on the most likely risk and the pre-planned fix, no follow-up meetings required.
Save a 2-line check-in note in your work folder
Before you schedule the email to send tomorrow morning, create a new plain text note in the project folder you use for this initiative, and save it with the file name “Pre-mortem check-in [date you send the email]”. The first line is the risk you named in the email, and the second line is the date you will check in on whether the risk materialized. For example, if you send the email on October 12, you would write, “Risk: Vendor staff shortage delays core component delivery by up to 2 weeks. Check-in date: October 19.” Add a calendar event for that check-in date, set for 5 minutes, so you don’t forget to follow up. When the check-in date hits, you write one extra line in the note: either the risk did not materialize, or it did, and the mitigation worked as planned, or it did, and the mitigation needs adjustment for future commitments. Example measurement: 5 minutes total time to fill out the note and add the calendar event, no extra work required until the check-in date. The decision grid at /desk-tools/decision-grid/ only stores the effort and alignment you typed. It does not send the message. You can access the blank version of the risk logging table you used earlier from Find Core Insight if you need to run this exercise with a larger team later.
Schedule this exact pre-mortem before your next formal commitment
Right after you schedule the commitment email to send, open your calendar and add a 15-minute block labeled “Pre-mortem” immediately before the time you plan to draft your next formal commitment to a stakeholder, client, or cross-functional team. This block is reserved exclusively for walking through these same steps: pull the last 7 days of notes and chat history, log gradual risks, pick the highest-likelihood one, add the 2-sentence mitigation section to your draft, and save the check-in note. You run this pre-mortem for every commitment that ties to a quarterly target, delivery date, or team resource allocation, no matter how small the commitment feels when you draft it. When the 15-minute block ends, you stop, no extra risk planning required, and move to drafting your commitment as you normally would. You spend the 15 minutes naming one potential failure before you lock in your next yes, so you never send a commitment blind again.