Design the calculator's inputs, outputs, and formula logic
Specifies the calculator's labelled inputs, calculated outputs, and the formula or conditional scoring logic connecting them — resolving edge cases before any code is written.
In / outDecision the tool should support → labelled inputs, calculated outputs, formula/conditional logic spec, edge-case notes
You might say…
“I wanted a pricing calculator but I hadn't actually defined what inputs drive what outputs — this forces the logic specification before building anything.”
What it does
Given the decision the tool should support, specifies the labelled inputs, the calculated outputs, the formulas/conditional scoring connecting them, and the instructional context. Judgement-heavy design step that produces the spec the engine implements. Used to define a budget model, scoring matrix, or formula tool.
Trigger: Use when designing a learner-facing calculator tool and you need the model specified before handing off to a developer or tool-builder.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation