Some clients struggle with decisions. Not because they're bad at their jobs, but because the options feel overwhelming, the stakes feel high, or they're just not confident enough in their understanding to commit. When decisions stall, projects stall. Your job is to make deciding easier.
Why this matters
Indecision is one of the most common project killers, and one of the least discussed. A client who can't choose between two design directions holds up the entire design phase. A stakeholder who keeps revisiting architecture decisions blocks the team from building anything.
The good news: indecision usually isn't about the decision itself. It's about not having the right framework to evaluate options, or not feeling confident enough to commit. Both of those are things you can help with.
The principles
Structure choices clearly. Don't present five options. Present two, maybe three, with clear trade-offs. Too many choices paralyze.
Always make a recommendation. Saying "it's up to you" to an indecisive person doesn't help them. "Based on your priorities, I'd recommend Option B" gives them something to react to, which is much easier than choosing from scratch.
Connect options to their stated priorities. "You said speed matters most. Option B is fastest. Option A is prettier but adds two weeks." When you tie options to things they've already articulated, the decision becomes clearer.
Set deadlines. "We need to decide by Wednesday to stay on track" creates helpful urgency. Without a deadline, the decision floats indefinitely.
Make it feel reversible. "We can adjust this later if needed" reduces the pressure of committing.
What this looks like
"I know choosing between these design directions is tough. Let me structure this.
Your stated priorities: user-friendly, professional, launches by October.
Option A: modern, bold design. Higher visual impact but adds two weeks.
Option B: clean, professional design. Faster to build, launches on time.
I'd recommend Option B, because hitting your October deadline matters more than visual boldness. You can always enhance visuals post-launch.
I need the decision by Wednesday so design can start Thursday. Does that recommendation feel right, or are you realizing visual impact matters more than you initially thought?"
Why It Works
Structured clearly. Tied to their priorities. Clear recommendation. Deadline set. Permission to disagree.
Tips
- Limit to 2-3 options maximum
- Always provide your recommendation with reasoning
- Connect to their stated priorities
- Set clear decision deadlines
- Make decisions feel reversible: "We can change this later"
- Ask: "What would make you confident deciding?"
- Help them articulate their own priorities if they haven't
How this connects
This draws on asking good questions (understanding what they actually care about), gentle pushback (when indecision threatens the project), instilling confidence (helping them feel good about choosing), and managing expectations (setting decision timelines).
Things to try
- When a decision stalls, structure the options explicitly rather than asking again.
- Always include your recommendation. Never just say "it's your call."
- Practice: "Based on your priority of X, I'd recommend Y."
- Set a decision deadline and explain why: "We need this by Friday to stay on track."