Reporting vs Intelligence Framework
The fundamental difference between explaining the past and changing the future
The Core Distinction
Reporting explains what happened. Intelligence changes what happens next.
Most analytics teams produce reporting and call it intelligence. The difference is whether the output triggers a decision or fills a slide.
Comparison Framework
| Dimension | Reporting | Intelligence |
|---|---|---|
| Time orientation | Past (what happened) | Future (what to do next) |
| Output | Numbers, charts, summaries | Recommendations, alerts, decisions |
| Trigger | Calendar (weekly, monthly) | Events (threshold crossed, pattern detected) |
| Audience action | Read and acknowledge | Decide and act |
| Ownership | “The data team” | Named decision-maker |
| Success metric | Was it delivered on time? | Did it change a decision? |
| Failure mode | Nobody reads it | Nobody acts on it |
The Intelligence Test
Ask these three questions about any metric or report:
- Who acts on this? — If the answer is “everyone” or “the team,” it’s reporting.
- What action does it trigger? — If the answer is “awareness,” it’s reporting.
- What happens if we stop producing it? — If nothing changes, it’s decoration.
The Intelligence Maturity Model
| Level | Name | Description |
|---|---|---|
| 0 | No data | Decisions made on gut feeling |
| 1 | Raw reporting | Data exists but isn’t structured for decisions |
| 2 | Structured reporting | Regular reports with consistent metrics |
| 3 | Alerting | Thresholds defined, notifications sent when crossed |
| 4 | Intelligence | Metrics connected to decision authority and escalation paths |
| 5 | Predictive intelligence | Patterns detected before they become problems |
Most organizations are at Level 2 and believe they’re at Level 4.
How to Convert Reporting into Intelligence
Step 1: Attach a decision to every metric For each metric you track, define: “When this crosses X, person Y does Z.”
Step 2: Assign ownership Every intelligence product has one owner — the person who acts, not the person who reads.
Step 3: Define escalation When the metric crosses a threshold, what happens? Who gets notified? What’s the response time?
Step 4: Remove metrics that don’t trigger action If a metric has never caused someone to change a decision, remove it. It’s noise.
Step 5: Shift from calendar to event-driven Stop producing weekly reports nobody reads. Start producing alerts when something needs attention.
Signs Your Team Produces Reporting, Not Intelligence
- Reports are delivered on a schedule regardless of whether anything changed
- The same report goes to 20 people with no differentiation
- Nobody has ever escalated based on something in the report
- The team measures success by “reports delivered” not “decisions influenced”
- Stakeholders say “thanks” but never ask follow-up questions
- The team spends more time formatting than analyzing
Signs Your Team Produces Intelligence
- Outputs are triggered by events, not calendars
- Each output has a named recipient who must act
- The team tracks “decisions influenced” as a KPI
- Stakeholders call the team when they need to make a decision
- The team has escalation authority — they can raise alarms
- Removing the team would visibly degrade decision quality