Decision memo · high stakes · review in 3 days
Decision Memo: Client Deadline Commitment, Thursday Meeting
What this really is: Not a feasibility question. A risk-ownership question. The director promised a date; I need them to choose, on the record, which tradeoff (scope, date, or quality) makes it real.
False Dichotomy
Am I accepting a two-option frame when a menu exists?
Cut testing vs. weekend work is the director's trap mirrored back at me. At least five real options exist: phased delivery (core scope by the date, remainder after), negotiated scope reduction with the client, a two-week extension traded for something the director values, contractor capacity, or targeted de-scoping of testing on low-risk components. Bringing a menu directly answers the can-do charge: can-do people bring options, not objections.
Blind spot: If I show up Thursday with only two bad options, I confirm the complainer narrative.
Anchoring Bias
Am I negotiating against a number that was never validated?
The deadline is an anchor with zero feasibility evidence behind it, because it was set without me. My own framing (not realistic unless we cut testing or work weekends) already treats the date as fixed and only negotiates method. That concedes the most important point. The brief should present the date as one variable among scope, quality, and capacity, not as the given.
Blind spot: Anchors set by someone with authority over you feel like facts. They are not.
The options, honestly
Cut testing to hit the date
Upside: Meets the date, looks agreeable
Downside: I silently absorb defect risk that will be blamed on me later. No paper trail. Repeats last time's pattern where I own the consequences of their promise.
Mandatory weekend work
Upside: Keeps scope and date intact
Downside: Burnout and attrition risk, possible overtime policy exposure, and it still may not close the gap. Check exempt/non-exempt status and company policy before committing anyone.
Present a written brief with a menu of tradeoffs and force a documented choiceRECOMMENDED
Upside: Reframes me from obstructionist to problem-solver. Puts the risk decision on the director in writing. Protects me if the deadline slips.
Downside: Requires doing the arithmetic properly and letting the director present it upward as their call.
The verdict
Send a one-page brief Wednesday. Structure: (1) one sentence of commitment to the client outcome, (2) one table showing the arithmetic gap (estimated effort vs. available hours, testing phases and durations), (3) three to four options, each with cost, named risk, and my recommendation, (4) an explicit ask: I need your decision on which tradeoff to accept by [date] so we can lock the plan. Frame it so the director can carry it upward as their decision. Before Thursday, gather two unknowns rather than assuming: why the director committed this date (client pressure, their boss, the account relationship), because that determines which tradeoff they can actually sell; and confirm the exact numbers, since vague pushback is what earned can-do last time.
The words for the conversation
Before Thursday, when you hand over or email the brief: I want us to hit this date for the client, and I've laid out how we can. The honest math says we can't get scope, quality, and this date all at once, so I've put together four paths, each with the tradeoff spelled out and my recommendation. I need you to pick which tradeoff you want to own by Friday so we can lock the plan and I can get the team moving. If can-do comes up in the meeting: Absolutely, I'm committed to this. The question is which tradeoff you want me to make, because we can't do all three: scope, date, and quality. If the director defends the date: Then let's talk about what we pull out of scope to make it real. I'd rather decide that together now than have the client find a defect in production.
