Practice a Kindle launch date versus scope trade-off case covering delay arguments, ship-on-time arguments, hardware and software constraints, WSJF prioritization, Black Friday impact, OTA deferrals, launch guardrails, and stakeholder communication.
##### Question
A new Kindle has eight planned features (five software, three hardware). The project is running four months late, jeopardizing a Black Friday launch that drives most annual sales.
Craft the strongest arguments for delaying launch to keep the full feature set.
Craft the strongest arguments for shipping on time with a reduced scope.
Given a table that lists progress, user value, cost, and complexity for each feature, choose which to cut or keep to meet the Black Friday date and explain your prioritization in order of importance.
Quick Answer: Practice a Kindle launch date versus scope trade-off case covering delay arguments, ship-on-time arguments, hardware and software constraints, WSJF prioritization, Black Friday impact, OTA deferrals, launch guardrails, and stakeholder communication.
hardProduct ManagerTake-home ProjectProduct / Decision Making
8
0
Kindle Launch Decision: Date Versus Scope Trade-Off
You manage a new Kindle with eight planned features: five software features and three hardware features. The project is four months late, threatening a Black Friday launch that drives a large share of annual sales. Hardware changes require earlier freeze and certification than software, while some software can ship later through OTA updates.
Constraints & Assumptions
You must compare delaying for full scope against shipping on time with reduced scope.
Hardware and software capacity are separate lanes.
Hardware defects or missing hardware features cannot be fixed through OTA.
Customer trust, reviews, retail placement, holiday demand, and operational commitments all matter.
If the original feature table is unavailable, state reasonable assumptions and show a worked prioritization example.
Clarifying Questions to Ask Guidance
What are the eight features, their current completion status, remaining effort, user value, complexity, and dependencies?
Which features are required for compliance, stability, or launch claims?
What revenue or placement impact do we expect from missing Black Friday?
Which software features can be safely shipped later through OTA?
Part 1 - Case for Delaying
Make the strongest case for delaying the launch to keep the full feature set.
What This Part Should Cover Guidance
Customer trust, launch reviews, differentiation, support burden, hardware immutability, and marketing claims.
Long-term product cycle impact, channel expectations, and quality risks.
Conditions under which delay beats shipping on time.
Part 2 - Case for Shipping on Time
Make the strongest case for shipping on time with reduced scope.
What This Part Should Cover Guidance
Black Friday demand, retail placement, competitive timing, learning loops, and channel commitments.
The ability to defer lower-risk software through OTA.
Guardrails for stability, battery, page-turn performance, store reliability, compliance, and transparent customer messaging.
Part 3 - Prioritize Keep, Cut, or Defer
Using a feature table or explicit assumptions, decide what to keep or cut to meet Black Friday.
What This Part Should Cover Guidance
A framework such as WSJF, RICE, or cost of delay divided by remaining effort.
Separate handling of hardware freeze, software OTA-ability, dependencies, and non-negotiable launch quality.
A ranked keep and cut list with rationale.
Part 4 - Recommendation and Rollout Plan
Give the final recommendation and explain how you would communicate and execute it.
What This Part Should Cover Guidance
A clear launch or delay recommendation with conditions.
