Episode 15 · 2026-10-09

You Have Data. Why Can't You Decide?

Decision engineer Michelle Florendo on why more data hasn't made deciding any easier. As AI takes over the doing, the deciding matters more, and the hard part was never the options or the information: it's knowing what you want, and counting the data that never shows up on a dashboard, like fear, a gut sense, or a feeling that something is off. Sam's signal is that analysis got cheap while objectives didn't arrive any faster. Michelle's subtraction is the belief that good decisions must be purely rational, because it's more important to be resilient than to be right.

Host Sam Rogers · guest Michelle Florendo · 27 min

A choice this episode can help with

Which decision are you sitting on, and what do you actually want from it before anyone hands you the pros and cons?

Run it on your own work: The Concern Column, one page, any model.

Premieres Friday 9 October 2026 on YouTube and in podcast apps. Open it on YouTube to set a reminder.

The signals

The subtractions

About this episode

The thread through the episode is the one Sam opened with: we have more information than ever, and the decision still sits there. What's missing isn't data. It's the objectives nobody wrote down and the concerns nobody counted, and Michelle's case is that both are learnable skills, which she calls decision fluency.

Markus Bernhardt sent in a question from the livestream: how do you get people to frame the question before they see any options? Michelle's answer is that framing comes before all three legs. It's the fourth part of Decision Quality, the red book on her shelf that's popular with the Society of Decision Professionals, and leading with options gives you a narrow frame. Sam added the framing assumption he sees most: that a good process will insulate you from a bad outcome, which rolls decision quality and outcome quality into one thing.

One thing to do this week: pick one decision you're sitting on. Before you ask anybody, or any disembodied agent, for the pros and cons, write down what you actually want from it. Then for each option, write down what concerns you and where you feel it, and whether that points to something you want that isn't on your list yet. That's the part no amount of data will give you.

Links from the episode:

Books Michelle pulled off her shelf: Decision Quality, and Annie Duke's Thinking in Bets. As an Amazon Associate, Snap Synapse earns from qualifying purchases made through the book links on this page.

Want to bring your own signal and subtraction? Find yours.

Transcript

Read the conversation

0:00

Michelle Florendo: I see a lot of people say, I need to make a good decision here, I need to be rational about it. And I'm like Okay, and can I call you out on this assumption you're making that good decisions must be purely rational?

0:22

Sam Rogers: Welcome to Signals and Subtractions. I'm your host, Sam Rogers. You have data, so why can't you decide? That's the question of the day. Most of us have more information than we've ever had: reports and dashboards and a model that will hand us 10 options and a cited brief in a minute or less now. So still the decision sits there. Or it gets made and then remade and then second guessed? So today I have brought in someone whose whole job is helping facilitate the deciding part. Michelle Florendo is a decision engineer and facilitator. She's the founder of Powered by Decisions, and she's trained in decision science at Stanford. She's coached leaders at some of the biggest companies you know. She's also the host of her own podcast, Ask a Decision Engineer, back for its seventh season later this month. Very excited to have you here, Michelle. Welcome.

1:22

Michelle Florendo: I'm excited to be here and excited for this conversation.

Read the full transcript

Put it to work

Pick one decision you're stuck on. What concerns you about each option, and what does that concern say you actually want?

The takeaway

The method from this episode, handed over whole: one page with its copy-paste prompt and JSON schema. Every takeaway.

UseThe Concern Column