Why Decisions Feel So Hard
|
They get discussed, refined, socialized, and revisited.
They move sideways, upward, or into another meeting.
They turn into alignment sessions, workshops, or “next steps.”
Not because they don’t know what to do.
But because deciding has become a form of exposure.
One thing that came up again and again was how hard it feels to say “stop.”
Stop this discussion.
Park this topic.
Close this line of thinking.
On paper, that sounds procedural. In practice, it’s deeply social.
Several leaders talked about how risky it feels to interrupt momentum, especially in group settings. Ending a discussion means risking being wrong, missing something important, or being seen as the person who shut something down too early.
So conversations continue.
Meetings stretch.
Important tensions stay unresolved.
This gets even harder when the meaning of “success” isn’t stable.
In multiple interviews, leaders described working toward goals that sounded clear at a high level, “reduce complexity,” “increase resilience,” “move faster”, but were never fully defined.
Teams would start work, only to find that priorities shifted or the goal itself meant something different a few months later.
In those conditions, committing to a decision can start to feel pointless.
Why own a plan if the definition of a win might change?
Why take responsibility when the standard you’ll be judged against isn’t clear yet?
In that context, hesitation isn’t incompetence.It’s self-protection.
We often talk about decision-making as a personal trait: be decisive, be confident, trust your judgment.
But what I’m seeing in this research is more structural than that. People struggle to decide when they don’t know:
Passing a decision along or keeping it open can feel safer than owning it.
Not because people are avoiding responsibility, but because responsibility has become heavier and less protected.
This pattern is one of the reasons I’ve been reworking parts of my upcoming Facilitating Workshops course.
Not because I have a clean answer, but because I keep running into the same tension in these conversations and in my own work, teams don’t just struggle with ideas or alignment; they struggle with how discussions actually turn into decisions.
What I’m increasingly interested in exploring is not how to push people toward answers, but how to notice:
This isn’t something you solve once. It’s something you practice, together, in real situations (check out the new curriculum now).
The irony is that many organizations say they want faster decisions,
without fully reckoning with how risky deciding has become.
Sometimes the hardest part of deciding isn’t choosing.
It’s being the person who has to live with the choice after the meeting ends.
|
COURSE: Facilitating Workshops COURSE: Defining UX Strategy |
If you know, you know 😭
Until next month!
The Fountain Institute is an independent online school that teaches advanced UX & product skills.
5 More Signals about the Future of AI Interactions by Jeff Humble Dear Reader, The way we interact with AI is changing, and it fascinates me. How will we interact with AI in 2035? Signals give us a hint. What are signals? Signals = surprising examples from today that suggest where the future might end up. Last year, I did part 1, and now I want to share 5 more. Signal #1: Google built an AI-enabled mouse pointer from Google DeepMind This is a signal that I think will catch on fast. The Google...
Which parts of your work do you actually want to keep? By Hannah Baker This one's a few days late; life got in the way. Back to our regular scheduled broadcast next week. For a long time, I was using Claude the same way most people do. As a chat function. A thinking partner. Something to help me get things done. But I kept running into the same problem. Every new conversation, I'd have to re-explain everything, my tone, my formatting, what I needed the output to look like. So I'd stay in the...
7 Tells that a UI is AI-Generated by Jeff Humble Dear Reader, You can see a vibe-coded app from a mile away, if you know what to look for. Here are seven design patterns that scream amateur vibe coder. Learn them, avoid them, and stay above the rising tide of slop, my friends. 1. Neon color palette from IceWhistle If it's vibe-coded, it's gotta be neon. To slop this one up to the max, use 5+ neon colors and never pick a single one to focus. Why AI loves it: Neon-on-dark is overrepresented in...