You're conflating two decisions, and it's costing you the ideas in the room

You've sat in this one before - probably more than once. The goal isn't in dispute. Everyone round the table wants the same outcome, and if you asked them separately they'd describe it in roughly the same words. What they disagree about is how to get there, and after forty minutes of circling, somebody decides. Usually the most senior person in the room, occasionally the most certain one.

Nobody leaves unhappy, exactly. But two or three people have privately concluded their route was better, and they're now unlikely to do much for the chosen one beyond what they're asked for.

Here's what went wrong. The destination and the route were treated as one decision, and they aren't. Holding the destination firm is your job. Owning the route usually isn't, and the habit of doing both is why so many teams end up executing a plan that only one person believes in.

A destination is what has to be true when this is finished, and who it has to be true for. A route is how you get there.

The test is whether you'd know it when you saw it. "Cut the time between a customer asking and a customer getting an answer, to under a day, by the end of March" is a destination. "Move to the new ticketing system" is a route wearing a destination's clothes, and once it becomes the goal it gets hard for anyone to tell you whether it worked.

A good number of muddled projects are muddled here. Somebody chose a route early, it got written into the plan as the objective, and eighteen months later the team is defending the route rather than pursuing the thing it was meant to achieve.

Which is the useful diagnostic, and it takes about a minute. Look at what you've told your team the goal is. If achieving it would still leave you unsure whether the actual problem got solved, you've handed them a route.

Take a member services team of nine inside a professional association.

Renewals are slipping. The general manager is clear about the destination, and rightly so: get the renewal rate back above eighty-five per cent by the end of the financial year, without adding headcount. Everyone agrees that's the goal.

She's also fairly sure she knows how. A reminder sequence, better segmentation, a discount for early renewal. She's seen it work before and she's probably not wrong.

So she specifies both. The plan goes out with the destination and the method attached, and the team executes it.

Eight months later the renewal rate is at eighty-one per cent. In the review, two things surface that were known inside the team the whole time. The member services coordinator had been saying for a year that most lapsed members went quiet after a single bad experience with a claim, and no reminder sequence touches that. And the person who runs the events programme had noticed that members who attended anything renewed at nearly double the rate of those who didn't.

Neither raised it once the plan was set. When asked why, both said a version of the same thing: it wasn't what we'd been asked to do.

The destination was right. The route was reasonable. What it cost was the routes the nine of them could see and she couldn't.

The idea that a clear, demanding goal beats a vague one is about as well established as anything in this field. Edwin Locke and Gary Latham spent thirty-five years on it, across hundreds of studies, and the finding is consistent: specific and difficult goals are associated with better performance than "do your best".

Their work is mostly about goal difficulty and specificity rather than about who chooses the method, so it doesn't settle the destination-and-route question directly. Much of it was conducted on relatively simple, well-defined tasks, and the effects are less clean where the work is complex and the path is unknown.

What it does support is the half that matters most here: be exact about the destination. Vagueness there reads as open-mindedness and mostly isn't, and it tends to produce worse results than a demanding number does.

The other half, leaving the route open, rests on something simpler and doesn't need a study. The people doing the work can often see things you can't, and they're far more likely to tell you if telling you reads as part of their job rather than a challenge to the plan.

An open route tends to produce better options only where people will say the thing.

Amy Edmondson's research on psychological safety is the underlying condition here: the shared belief that you won't be punished or humiliated for speaking up with a question, a concern, or a half-formed idea. Her original study looked at hospital nursing units and found the better-performing ones reported more mistakes, because their climate made reporting survivable. It's a small study in one hospital system, and it doesn't establish that safety causes performance. What it did was name something real, and three decades of work since has kept finding it in other places.

The practical version for this conversation is narrower than the literature. Three things make an open route credible:

Some routes are already decided, and pretending otherwise to seem collaborative is worse than deciding out loud. Regulatory requirements, a contract already signed, a decision made two levels above you. If the route is fixed, say it's fixed and say why. Most teams can work happily inside a constraint they understand. What they can't do is spend two weeks designing options for a question that was already closed, and then watch it close again.

And the method matters more than usual where the work is dangerous or irreversible. Leaving the route open assumes a wrong turn can be corrected. Where it can't, the openness belongs earlier, at the point where you're choosing among options, and not during execution.

The honest framing is that this is a default rather than a rule. Most decisions have more route latitude than they're given. Some have none, and knowing which you're holding is most of the skill.

Holding a destination firm while leaving the route open feels, from the inside, like doing less of your job. It's the opposite. Specifying the method is the easier half, and it's the half that tends to cost you the ideas in the room that weren't yours.

Pick one piece of work. Say exactly where it has to land, name what truly can't move, and then stop talking.