Analytical approach designer
Selects and specifies the appropriate analytical method for each branch of the issue tree — quantitative model, comparative analysis, pattern coding, or scenario analysis — with rationale.
In / outIssue tree branch + available data inventory + decision need → analytical approach specification (method, rationale, required inputs, output form)
You might say…
“Choosing the wrong analytical approach wastes a week and produces conclusions the client can't trust — designing the approach before running the numbers prevents that.”
What it does
Chooses the analysis method (segmentation, regression, scenario model, qualitative coding) that best answers each structured sub-question, and frames the assumptions to stress-test. Used to decide HOW to analyse before computation runs — the judgement layer the tool cannot supply.
Trigger: Use before opening a spreadsheet or running any analysis; provide the issue tree branch, available data, and the decision the client needs to make.
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