Decision intelligence: engineer the decision, not the dashboard

September 11, 2026 · 5 min · Free, with full transcript

Why do organisations with hundreds of dashboards still decide badly? The answer here is that the numbers arrive nowhere near the moment of choice. A support agent deciding on a refund needs lifetime value, refund history and churn risk inside the ticket, not in a tool they have no login for. Embedded analytics is the plumbing; decision intelligence is treating the recurring decision as the thing you design around, then working backwards. You walk away with three tests for picking a decision worth engineering (frequent, consequential, currently made blind), a rule for what to leave alone, and a warning on reading DBT Labs vendor figures, with supporting points from O'Reilly Radar and MIT Sloan Management Review.

Listen to the podcast

4 min

Chapters

Key takeaways

  • Design backwards from a recurring decision instead of building a dashboard and hoping someone consults it.
  • Apply three tests before investing: is the decision frequent, is it consequential, and is it currently made with no data at the point of choice.
  • Encode the logic for repeatable approve or reject calls and route the odd 5 percent to a human, rather than automating messy judgement calls.
  • Leave rare one-off strategic bets alone; those are argued in a room, not instrumented.
  • Sit beside the person making your most expensive recurring decision and check whether the data they need is on screen at that second.
Read the full transcript

Welcome to the Leaders Insights Podcast.

Today's episode, Decision Intelligence and Embedded Analytics, Making the Decision in

the Unit of Design.

Every company I talk to has dashboards coming out of their ears.

So why are they all still making terrible decisions?

Because a dashboard is a museum.

It's a beautiful glass case where data goes to be admired and then completely ignored.

The problem isn't that people can't see the numbers.

It's that the numbers show up nowhere near the moment someone actually decides something.

That sounds like a slogan.

Give me the mechanism.

Fine.

Picture a support agent deciding whether to refund an angry customer.

The data that should inform that—lifetime value, refund history, churn risk—lives

in a dashboard the agent has never opened, in a tool they don't have a login for.

So they guess.

The decision happens in the support ticket, but the intelligence lives two departments

away.

That gap is where value quietly dies.

So decision intelligence is just putting the chart inside the app?

That's embedded analytics.

The plumbing that pushes data into the tool where work happens.

Decision intelligence is the bigger idea.

You treat the decision itself as the thing you design around, not the report.

You ask, what recurring choice does this person make, and what would make it better?

Then work backwards.

Most firms do the opposite.

They build the dashboard first and pray someone consults it.

You're being a bit smug.

Plenty of dashboards get used.

Used?

Sure.

Acted on?

O'Reilly's radar surveys have been consistent for years.

A large share of analytics work never changes a single operational decision.

It gets built, presented, admired, forgotten.

And MIT Sloan Management Review has been hammering this since before the AI gold rush.

The bottleneck was never the technology.

It's that nobody redesigned the actual moment of choice.

We spent a decade optimizing the museum, and none on the visitor.

Alright, doesn't decision intelligence just mean let the algorithm decide and call it

a day?

No.

And that's the trap everyone falls into.

The point isn't to automate the human out.

It's to shrink the decision to its real shape.

Most operational decisions are boring and repeatable.

Approve or reject, prioritize or park.

For those, you can encode the logic and let the human handle the weird 5%.

The mistake is automating the messy judgment calls and micromanaging the trivial ones.

People get that exactly backwards.

Give me a number that shows this actually moves the needle.

GBT Labs, and I'll flag it.

They sell the data tooling, so read their figures with one eyebrow up.

Reports that teams embedding analytics into workflows cut the lag between question and

action dramatically.

Cross-check it against something independent before you quote it in a board meeting.

But the direction is right.

The win isn't a prettier chart.

It's compressing the distance between I wonder and I did.

What's the most common way companies get this wrong?

They hire a data team.

The data team builds what it finds interesting, and nobody ever asks the person making the

decision what they actually need at 2 p.m. on a Tuesday.

It's like a chef cooking whatever they feel like and being shocked the customers left

hungry.

So how do you know a decision is worth engineering around?

Three tests.

Is it frequent?

Does it happen constantly?

Is it consequential?

Does getting it wrong cost real money?

And is it currently made blind or no data at the point of choice?

Get all three and you found gold.

A pricing decision made 200 times a day with zero data in the moment beats any executive

dashboard nobody scrolls past.

And the ones that fail the test?

Leave them alone.

Not every decision deserves a data pipeline.

The rare one-off strategic bet.

You're not embedding analytics into that.

You're arguing in a room.

Know the difference or you'll waste a year instrumenting a decision that happens twice

a decade.

Give me the one thing a listener should do Monday morning.

Pick your most expensive recurring decision.

Sit next to the person making it and watch.

If the data they need isn't on the screen in front of them at that exact second, your

dashboard has already failed.

And no amount of polishing it will help.

The museum stays empty.

The museum stays empty.

Sources for today's episode.

Cade Nuggets, The New Stack, O'Reilly Radar, Towards Data Science, MIT Sloan Management

Review, DBT Labs vendor, Data Tooling.

Done.

Want to know where you actually stand?

Take the CDO self-assessment at MBA-training.com.

Read and go deeper