Discovery
AuraScore 79/100

Decision Intelligence Reasoning Gap Diagnosis

Evaluate logical fallacies, cognitive bias, and inference gaps in client decision workflows.

Use this template during discovery for decision intelligence and advanced reasoning platforms. It diagnoses how prospects currently make high-stakes choices and where cognitive or analytical breakdowns occur.

Template

Role: Enterprise Presales Engineer specializing in decision intelligence frameworks and formal reasoning diagnostics.

Context

  • Division: {{client_division}}
  • Decision Process: {{decision_making_workflow}}
  • Cognitive & Logic Flaws: {{identified_reasoning_flaws}}
  • Historical Impact: {{historical_error_costs}}
  • Success Benchmarks: {{evaluation_criteria}}
  • Cadence & Latency: {{time_to_decision_metric}}

Task

Generate a detailed reasoning gap analysis that evaluates the prospect's inferential vulnerabilities, quantifies the cost of systemic decision failures, and maps a structured logical framework for solution evaluation.

Method

  1. Map {{decision_making_workflow}} as a formal directed decision tree from initial signal to final action.
  2. Overlay {{identified_reasoning_flaws}} onto specific decision nodes to pinpoint cognitive and analytical breakdown points.
  3. Calculate the operational friction caused by current latency defined in {{time_to_decision_metric}}.
  4. Correlate historical loss patterns in {{historical_error_costs}} with specific logic and heuristic failures.
  5. Structure a counterfactual scenario demonstrating how structured complex reasoning avoids recorded past errors.
  6. Align required reasoning capabilities directly against {{evaluation_criteria}}.
  7. Develop a prioritized sequence of discovery validation questions targeting root cognitive bottlenecks.

Constraints

  • Focus exclusively on deductive, inductive, and statistical reasoning gaps.
  • MUST categorize each flaw by formal reasoning error type (e.g., selection bias, base-rate neglect, false attribution).
  • MUST NOT propose generic software features; focus entirely on decision architecture and logic.
  • Ground all financial risk estimates directly in {{historical_error_costs}}.

Output format

Structure the analysis in the following order:

  1. Decision Architecture Diagnostics (max 200 words describing the workflow logic breakdown)
  2. Logic & Inference Vulnerability Table (Columns: Workflow Step, Reasoning Error Type, Operational Cost, Solution Requirement)
  3. Latency vs. Accuracy Impact Synthesis (150-200 words)
  4. Discovery Question Blueprint (4 multi-layered questions aimed at executive decision-makers)

Self-review

  • Is every flaw from {{identified_reasoning_flaws}} classified into a recognized reasoning category?
  • Are the financial stakes accurately linked to {{historical_error_costs}}?
  • Does the output avoid generic feature pitching and remain focused on reasoning mechanics?
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

sales
sales-discovery
complex-reasoning-analysis-math
sales discovery
complex reasoning
decision intelligence