The CIO must compare realized value across a chatbot, a vision inspection tool, and a demand-forecasting model. What measurement view is needed?
Select an answer to reveal the explanation.
Short Explanation
Different tools, same city wallet—you still need a scoreboard. A portfolio view lines up chatbot, vision, and forecasting value so leaders can steer funding with eyes open.
Full Explanation
Portfolio-level value comparison lets leaders allocate attention and funding across dissimilar AI initiatives—chatbot, vision inspection, demand forecasting—using shared criteria such as mission impact, net cost, risk, adoption, and realized benefits. A CIO needs that view because city capital and oversight capacity are finite; single-project storytelling cannot rank tradeoffs across modalities. Evaluating only the chatbot because it is the easiest story to tell biases the portfolio toward narrative convenience and may starve higher-value but quieter tools. Comparing tools solely by which vendor logo is most recognizable substitutes brand familiarity for value evidence. Refusing to compare initiatives because AI projects are “inherently incomparable” abandons prioritization; differences in modality do not erase the need for shared decision criteria in a municipal portfolio. Exam caveat: choose portfolio comparison on shared criteria over logo ranking or incomparability claims. Operational check: define a common value scorecard covering outcomes, net cost, risk exceptions, and adoption; normalize where needed; review the portfolio quarterly; and reallocate based on realized value rather than launch glamour or vendor mindshare.