You Can’t Hire Your Way Out of Indecision.

The roadmap is slipping. Designs keep circling back for another review. Your team has explored so many options that the Figma file now qualifies as a multiverse.

The obvious solution? Hire another designer. Maybe two.

Surely more people can help move things forward.

They can—if the work is waiting for someone to do it. If it’s waiting for someone to make a decision, you’re about to add salaries to a traffic jam. Before opening that job description, take a look at where progress actually stops.

Figure out what’s stuck.

A team can be busy and still spend a surprising amount of time waiting.

Waiting for feedback. Waiting for competing priorities to be resolved. Waiting for the person who approved the direction last week to explain why they no longer like it.

Look at a few recent projects. Where did time go?

If designers are overloaded with clearly defined, approved work, additional capacity may help. But if they’re repeatedly revising work because the goal keeps changing, another designer will inherit the same uncertainty.

Count the decisions waiting to happen alongside the tasks waiting to get done.

“We need more design support” might be accurate. It might also be the organizational equivalent of turning up the radio because your car is making a concerning noise.

Worth checking under the hood.

Decide who actually decides.

Collaboration works better when people understand their role in it. Who recommends a direction? Who contributes expertise? Who makes the final call? Who needs to know what was decided? You don’t need a twelve-page governance document to answer those questions. For a specific decision, a few clear sentences can do the job.

For example: the designer recommends the interaction approach, engineering identifies technical constraints, support contributes recurring customer issues, and the product lead resolves scope tradeoffs.

The exact arrangement depends on your team. What matters is that people understand it before the review. Otherwise, everyone arrives with an opinion and nobody leaves with authority.

Fleetwood Mac made a legendary album amid interpersonal chaos. Your checkout redesign probably doesn’t need to attempt the same creative process.


Give the decision something to stand on.

“Which option do we like?” invites a preference contest.

“What best helps a first-time customer complete setup, within our current technical constraints?” gives the team a useful question.

Before exploring solutions, agree on:

• The problem: What are we trying to improve, and for whom?
• The evidence: What do we know, and what are we assuming?
• The constraints: What limits the available options?
• The success criteria: How will we judge whether the direction works?

Those criteria help you evaluate options and explain tradeoffs.

If one concept is faster to build but harder to understand, you can discuss that tension directly. You can also identify whether a small test would help resolve it.

That’s a much more productive conversation than discovering forty minutes into the meeting that “simple” means four different things.

Stop asking for feedback with no boundaries.

“Would love everyone’s thoughts!” is how a focused review becomes an unpaid residency.

Give reviewers context. Explain what’s ready for discussion, which questions remain open, and when input is needed.

“We need feedback on whether this workflow covers the approval scenarios. Visual styling will be reviewed separately. Please flag missing cases by Thursday.”

Now people know how to help. They also need to know what happens next: who considers the feedback and when a decision will be made. An invitation to contribute shouldn’t accidentally become an unlimited veto. You can take someone’s concern seriously without incorporating their preferred solution. Explain the reasoning, acknowledge the tradeoff, and close the loop.

Make reopening a decision a deliberate act.

Sometimes a decision should change. New research reveals a problem. A technical dependency falls through. The business changes direction.

Build room for that. But distinguish new information from a familiar opinion making its third guest appearance.

Keep a short decision record: what you chose, why, which tradeoffs you accepted, and what would justify revisiting it. When the conversation resurfaces, start there.

Has something changed? Did you discover a risk you previously missed? Or does someone simply remain uncomfortable with the compromise?

That discomfort may deserve discussion. It doesn’t automatically require another round of design.

A decision record gives the team a shared memory. Otherwise, your roadmap becomes Groundhog Day, with slightly different button colors.

Hire for the gap you can name.

Once you understand the bottleneck, you can make a better staffing decision. You may need more execution capacity. You may need research expertise. You may need a senior design partner who can clarify ambiguous problems, facilitate tradeoffs, and help establish how decisions move through the team.

Those are different needs. Write the role accordingly.

And give the person enough authority and access to succeed. Hiring someone to “bring strategic leadership” while requiring approval for every recommendation is an expensive piece of theater.

An embedded partner can help create direction and momentum. Leadership still has to participate, resolve business tradeoffs, and honor the decisions it delegates. Before hiring, examine one stalled project. Identify the unresolved decision, name its owner, and agree on what’s needed to make the call.

See what moves.

You may still need another designer. But they’ll join a team with clearer priorities and a better chance of turning their work into something useful.

More people can expand what your business is capable of. Give them a direction they can actually move in.