From Problem Framing to an AI-or-No-AI Value Hypothesis
15 min read
Lesson objectives
Frame a solution-neutral problem and compare AI with non-AI alternatives.
Build a value hypothesis with a baseline, target, mechanism, guardrail, and continuation decision.
Calculate a simple workload baseline and distinguish association from a causal claim.
Separate the problem from the solution before designing a value hypothesis
A good problem statement describes a performance or decision gap without assuming AI is the answer. Instead of “We need a model to predict delays,” say, “The procurement team cannot detect delay signals early enough to change the plan, which causes repeated rescheduling.” The second statement opens several interventions for comparison: clean delivery-date data, change alert rules, improve supplier commitments, or use a predictive model. This comparison reduces solution bias, where every problem is interpreted as a reason to build a model.
The Map function of the NIST AI RMF is useful here because it emphasizes understanding context, purpose, benefits, costs, and risks before moving ahead. In this diploma we use that idea as a decision tool: the less we understand the problem, stakeholders, data, or impact of error, the weaker the value hypothesis. This does not mean waiting for perfect certainty. It means identifying what must be known before taking on greater cost and risk.
From problem to a testable value hypothesis
Hypothesis element
Practical question
Problem
What is the current gap, and who is affected?
Baseline
What is the current state in a measurable unit?
Intervention
What change is proposed: AI, non-AI, or a combination?
Target
What improvement is expected during the test period?
Value mechanism
How is the intervention expected to create the improvement?
Guardrail
What quality, safety, or cost outcome must not be sacrificed?
Continue/stop decision
What evidence would make us scale, redesign, or stop?
Formula
Rework load in the case = number of requests × rework rate × rework minutes ÷ 60. This does not estimate every process cost, but it converts a vague problem into an understandable baseline that can be compared after an intervention.
Guardrails prevent one metric from improving at the expense of the system
Processing time can fall because the system accepts lower-quality answers, or because staff postpone difficult work. Use at least one value metric and one guardrail when an important trade-off exists. Examples include response speed with classification accuracy; reviewer productivity with returned-case rate; cost reduction with escalation rate; or coverage expansion with privacy and security boundaries. A guardrail is not a long disclaimer. It is a measure or condition tied directly to a credible failure mode.
Lesson summary
Separate the problem from the technology and turn it into a testable hypothesis. Use a baseline, guardrail, and decision rule, and distinguish an observed result from a claim that AI caused it.