Decision Intelligence
How AskEdi handles decision-type questions with structured analysis, a mandatory recommended action, and a Decision Summary card.
Decision Intelligence is AskEdi's response mode for questions that ask what to do or where to focus. Instead of a descriptive answer, you get a structured analysis grounded in your data that drills into the strongest observed opportunity or risk and ends with a concrete recommended action.
Decision Intelligence responses are grounded in observed data patterns, not causal proof. The recommended action is a data-grounded starting point for investigation, not a directive to execute immediately. Use the validation metric in the Decision Summary card to confirm the direction before committing resources.
When Decision Intelligence Activates
AskEdi classifies the intent of your question automatically and routes it to the appropriate response type. Questions that typically activate Decision Intelligence include:
- "Where should I focus to improve revenue?"
- "Which product category should I prioritise?"
- "What is driving churn and what should I do about it?"
- "How can I reduce operational costs?"
- "Which region has the most untapped opportunity?"
You do not need to use a special keyword or command.
What a Decision Intelligence Response Includes
A Decision Intelligence response is a structured analysis followed by a Decision Summary card. The depth of the analysis depends on the complexity of the question.
A deep response covers 4 to 6 sections, each advancing or qualifying a central thesis. Typical sections cover the trend over time, the primary driver or dimension, a composition breakdown, a risk or anomaly, and a recommended action.
At least one section is always titled with an action-oriented phrase, for example "Recommended action", "Priority action", or "Next best move".
Each section is grounded in actual query results from your data. AskEdi performs at least one diagnostic drill-down into the strongest observed opportunity, risk, or performance gap before recommending action.
A simple response is 3 to 4 sentences covering the primary takeaway, the key evidence, and a recommended action. It uses the same observational language and data grounding as a deep response, but without the multi-section structure.
Decision Summary Card
The Decision Summary card appears at the end of every Decision Intelligence response. It contains five elements:
Prop
Type
If the impact cannot be quantified from the available data, AskEdi states the action, evidence, confidence, and validation metric without inventing a figure. A response that says "impact cannot be quantified from current fields" is being accurate, not evasive.
Observational Language Guarantee
AskEdi uses observational language throughout Decision Intelligence responses. The rules that govern this are applied consistently.
- Identify the strongest observed concentration, trend, or gap in your data
- Drill down into the primary driver before recommending action
- Quantify the scenario range where the data supports it
- State confidence with the observable reason
- Qualify recommendations when evidence is weaker: "based on the observed concentration" or "given the current trend"
- Provide a validation metric so you can verify the recommendation before acting
- Use causal-certainty language ("will cause", "guarantees", "proves", "will yield") unless your data contains experimental results, intervention history, or explicit causal fields
- Collapse an observed driver into a root cause when causal fields are absent
- Recommend actions that require systems or data not present in your source
- Hand the decision back with vague phrases like "use this to decide"
When evidence is low confidence, that is stated explicitly with the reason.
Frequently Asked Questions
Related Docs
Analysis View
Inspect the queries behind each Decision Intelligence section and verify what data the recommendation is grounded in.
Charts
How AskEdi generates chart responses for questions about trends, distributions, and comparisons.
Analysis Credits
How credits are allocated and consumed across all response types.
Need help? Email support@edilitics.com with your workspace, job ID, and context. We reply within one business day.
Last updated on