A city 311 chatbot is popular with one neighborhood group. What should the Product Owner require before scaling it citywide?
Select an answer to reveal the explanation.
Short Explanation
One loud neighborhood liking a chatbot is a compliment, not a citywide proof. Before spreading it, write down what should get better and how you will know. Hypothesis plus a success metric beats a vibe, a binder of requirements, or a steering-committee charter.
Full Explanation
Evidence-Based Management treats scale as a decision that follows evidence, not enthusiasm. A 311 chatbot that one neighborhood group likes is a weak signal; an experiment needs a stated hypothesis and a success metric that can confirm or refute value before citywide investment. Anecdote is not Current Value, and a year-long requirements document or a PMO charter substitutes planning theater for learning. The Product Owner should run the experiment first, then scale only if the measures support it.