Stakeholders ask when a citizen chatbot might deflect 30% of call-center volume. The Product Owner has historical throughput, not a detailed year-long design. How should the Product Owner forecast?
Select an answer to reveal the explanation.
Short Explanation
Nobody knows the exact Friday the chatbot hits 30% deflection, and pretending to know does not help the call center. Use the throughput history to sketch a range, like a weather forecast with a high and a low. A single magic date is just a wish with a timestamp.
Full Explanation
Range forecasts derived from historical throughput communicate uncertainty honestly and beat single-point guesses, especially when the remaining design is incomplete. Best-case velocity and a director-preferred date both inject optimism or politics in place of evidence. Withholding any outlook until every flow is designed delays useful empiricism the call center could already use. The Product Owner's 30% deflection question is answered with probability and inspection, not a ceremonial Friday.