The monthly city portfolio meeting only reviews which products are green on the RAG board, even though permitting and clinic experiments produced surprising learning. What should the Product Owner change about the meeting?
Select an answer to reveal the explanation.
Short Explanation
A portfolio meeting that only cheers green lights is a weather report that never mentions the forecast was wrong. Experiments on clinic hours or permit slices are how cities learn. Bring the surprises to the table — especially the ones that say stop.
Full Explanation
Evidence-based portfolio inspection includes learning, not only RAG green. When the monthly city portfolio meeting only reviews which products are green on the RAG board—even though permitting and clinic experiments produced surprising learning—the city misses chances to stop or pivot. Experiments that falsify an assumption are portfolio success if they prevent wasted capacity. The Product Owner should change the meeting to inspect learning from experiments alongside status, including what the city will stop or pivot. Penalties for disconfirming evidence and screenshot-only meetings punish empiricism.
Shortening the meeting to a dashboard screenshot so RAG stays the only agenda fails by deleting learning from inspection. Adding a penalty for any experiment that did not confirm the original business case fails by punishing truth. Replacing experiments with a stage-gate checklist so only green items may continue fails by restoring predictive control.
Exam caveat: Portfolio meetings must inspect experimental learning and stop/pivot decisions, not only green RAG. Operational check: Add a standing agenda item for experiment results—including falsified assumptions—and require an explicit keep, pivot, or stop decision for each surprising permitting or clinic learning.