Episode Details

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.

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.

Chapters
0:00 Why dashboards get admired and ignored
1:04 Embedded analytics versus decision intelligence
2:09 Why full automation is the trap
2:43 DBT Labs numbers and vendor caution
3:30 Three tests for decisions worth engineering
4:13 Sit with the decision maker Monday

Go deeper, free lessons

• Decision intelligence: decision architecture & embedded analytics
• Embedding analytics into workflows
• From dashboards to decisions
• Decision rituals: getting data into the room
• The metrics & semantic layer

Full article and transcript: https://www.mba-training.com/blog/decision-intelligence-embedded-analytics-cdo

MBA Training, mba-training.com