Decision to Delay Framework
Test whether postponing a deadline will create a stronger customer outcome
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 99%
The Decision to Delay Framework evaluates a proposed postponement through four questions with required answers. First, the delay must serve customers' best interests. Second, the additional time must enable an A-plus experience that users will want to discuss and share. Third, the team must be capable of becoming fully prepared and empowered to support the release. Finally, postponement must not have a devastating effect on the business. Leaders gather evidence from stakeholders with different vantage points, answer the questions honestly, and compare the improved outcome against the cost of waiting. This separates operational judgment from the identity, pride, or anxiety attached to hitting an arbitrary date and makes postponement a deliberate strategic choice rather than a perceived failure.
Origin
Jasmine Star developed the framework after postponing a major 2020 promotion and later reconsidering Social Curator's planned February 14, 2023 platform launch. A stakeholder meeting showed that additional testing and user feedback mattered more than preserving the original date.
Core principles
- 01Treat deadlines as tools rather than measures of identity
- 02Put the customer's best interest ahead of an arbitrary date
- 03Delay only when it materially improves the experience
- 04Protect the business from consequences it cannot absorb
- 05Include perspectives from every affected team
How to run it
- 1
Test the Customer Interest
Ask whether postponement is genuinely in the customers' best interest. Continue considering a delay only if the answer is yes.
Pro tip Describe the specific customer harm the delay would prevent or the benefit it would create.
Watch out Do not disguise internal convenience as customer advocacy.
- 2
Test the Experience Improvement
Determine whether the additional time will produce an A-plus experience that users will be excited to discuss and share. Identify the concrete quality, usability, or reliability improvements the delay enables.
Pro tip Define observable improvements such as completed testing, stronger messaging, or fewer user friction points.
Watch out Extra time without a specific improvement plan merely moves the date.
- 3
Test Team Readiness
Ask whether postponing can bring every supporting team to full preparation and empowerment. Gather perspectives from functions such as technology, marketing, customer success, and community.
Pro tip State the meeting's goal before sharing your own opinion so stakeholders can speak candidly.
Watch out A leader's declared preference can silence contrary evidence.
- 4
Test Business Survivability
Assess whether postponement would have a devastating effect on the business. Do not delay if waiting would create an intolerable financial, contractual, or operational consequence.
Pro tip Distinguish serious business harm from embarrassment, inconvenience, or lost attachment to a campaign date.
Watch out Customer benefits do not justify a delay that the business cannot survive.
- 5
Decide from the Evidence
Review the four answers with key stakeholders and decide whether the improved outcome outweighs the cost of waiting. Communicate the result as an intentional business decision rather than a failure.
Pro tip Use a vote or another explicit decision mechanism after everyone has presented their evidence.
Watch out Do not let sunk effort or an identity built around hitting deadlines override the assessment.
In the wild
As a major 2020 promotion approached, Jasmine saw weak messaging, pressure on the technology team, and growing anxiety. Although she initially resisted moving the date, she reconsidered what the deadline actually meant and allowed more time to improve the experience.
→ The delayed campaign became one of the company's biggest promotions and delivered a stronger experience.
Four days before the planned February 14, 2023 release, Jasmine convened key stakeholders and asked for reasons both to delay and to proceed. The team applied the four questions, voted, and postponed the launch for additional testing and user feedback.
→ The company used beta users and free-trial participants to identify friction before releasing the platform to its paying user base.
Common mistakes
Turning the Deadline into an Identity
Leaders can treat an arbitrary date as proof of ambition or competence, making an objective change feel like a personal failure.
Waiting Too Long to Ask Bigger Questions
Raising readiness concerns only days before launch reduces the team's options and adds avoidable pressure.
Entering the Meeting with a Verdict
Announcing a preferred outcome before hearing stakeholders can suppress the differing perspectives needed for a sound decision.
Is it for you?
Best for
Leaders facing a self-imposed deadline when quality, readiness, testing, or customer experience remains uncertain.
Not ideal for
Situations where postponement would threaten solvency, violate an external obligation, or cause irreversible harm.
From the transcript
“Question number one is the delay in the best interest of our customers? The answer has to be yes.”
“Number three, are all the team members fully prepared and empowered to support?”
“Will postponing have a devastating effect on the business?”
From the episode
Is it ever ok to move a deadline?