Can you defend the headline on the AI deck?
Distinguish elapsed-time savings from a higher processing rate.
The question
You are presenting a fictional US software product work sample to engineering and operations leaders. Give a 60-second opening on whether to start a staged rollout. The exercise gate is no increase in full-workflow processing time. All 100 fixed-workload runs in each condition take the listed time. Serial processing at full utilization is an explicit assumption for any runs-per-hour comparison.
| Previous | Proposed | |
|---|---|---|
| Minutes per completed run, labelled end to end | 8 | 5 |
| Completed fixed-workload runs | 100 | 100 |
The AI draft headline says “60% less time.” Check its denominator before presenting it.
“Choose the exhibit, give the opening and defend the recommendation under questions.”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: Fix the headline
What would you do here? Open the move you’d make.
Label the time result as 37.5% less time.
The strong move. A time reduction and a rate increase use different denominators.
Retain the headline “60% less time.”
Tempting, but it misses something. Three minutes divided by the old eight minutes is 37.5%; 60% describes the reciprocal processing-rate increase.
See how a strong candidate says it
“Eight to five minutes is 37.5% less elapsed time: 3 divided by 8. At full utilization, serial capacity rises from 7.5 to 12 runs per hour, a 60% rate increase. I would show minutes per run and keep the two denominators separate.”
Why it works: A time reduction and a rate increase use different denominators.
Step 2: Lead with the claim
What would you do here? Open the move you’d make.
Present the checked result and a bounded rollout ask.
The strong move. The opening states the measured result and a rollout condition.
Promise a 60% reduction in staffing costs.
Tempting, but it misses something. A serial processing rate is not a payroll reduction; staffing costs and other work are not given.
See how a strong candidate says it
“The recorded full-workflow time falls from eight to five minutes in this fixed-workload test, a 37.5% reduction. I recommend a staged rollout with the same measurement boundary and a stop if full-workflow time rises.”
Why it works: The opening states the measured result and a rollout condition.
Step 3: Handle the correction
An audit finds 6 minutes of required human review were omitted from every proposed-workflow measurement. The previous eight-minute measurement already includes all required work. The five-minute proposed component and every other assumption stay unchanged.
What would you do here? Open the move you’d make.
Include the omitted review and correct the exhibit.
The strong move. Required work belongs in the comparison boundary.
Treat review as optional to protect the original headline.
Tempting, but it misses something. The panel has said review is required; excluding it compares different workflow boundaries.
See how a strong candidate says it
“The required review makes the proposed workflow 11 minutes end to end. The old eight minutes already included all work, so the full process is now 37.5% slower and fails the gate. I would correct the slide before continuing.”
Why it works: Required work belongs in the comparison boundary.
Step 4: Change the rollout ask
What would you do here? Open the move you’d make.
Pause expansion and measure the full workflow again.
The strong move. Keep the valid component result while changing the failed recommendation.
Say the five-minute component proves the rollout gate is met.
Tempting, but it misses something. The gate concerns the full process, which now takes 11 minutes against the old eight.
See how a strong candidate says it
“I withdraw the time-saving rollout claim. The execution component is still five minutes, but the full workflow is 11. Across 100 runs it adds 300 minutes rather than saving 300. I would validate or redesign the complete process before expansion.”
Why it works: Keep the valid component result while changing the failed recommendation.
The answer, in short
- Decision
- Pause the time-saving rollout request.
- Because
- The corrected full-workflow time exceeds the baseline.
- What would change it
- A validated end-to-end result of eight minutes or less would meet the time gate.
Common traps
- Confusing less time with more runs per hour.
- Keeping required work outside the comparison.
Check your answer
- I checked the headline’s denominator.
- I gave a short decision-led opening.
- I corrected the slide when challenged.
- I separated the valid component result from the rollout claim.
Last reviewed Nov 10, 2026