The Study You Commissioned So You Would Not Have to Choose

When a team faces a hard question about what it is for, the proposal to gather more data or bring in an outside review almost always sounds responsible. It is often a way to avoid the one question that no amount of data can answer.

You have been in this meeting. The team has spent an hour on a question that matters: whether to keep a program that serves a small group very well or fold it into something that serves a larger group less well, whether to grow into a new area or protect the work you already do, whether the unit exists mainly to serve the people in front of it or the institution above it. Everyone in the room has a view, and the views do not line up. The conversation has started to go in circles, and people are beginning to say the same things in slightly different words.

Then someone says that the group does not really have enough information to decide this well, and suggests a study. Perhaps a survey of the people affected, perhaps a benchmarking exercise against similar organizations, perhaps an outside consultant who has seen this problem elsewhere. You can feel the room relax. The proposal sounds careful, it gives everyone something to do, and nobody has to lose the argument today. The group agrees on a scope and a timeline, and the meeting ends early.

The mechanism is a question about values sent out to be answered with facts

A well-run study gives a team a great deal. The people doing it can show what options exist, what each one costs, who uses what, and how other organizations have handled something similar. Those are real contributions, and a team that decides without them is often deciding badly.

What the people running a study cannot supply is the basis for preferring one of those options over another. When the disagreement in the room is about what the team is for, which of two legitimate purposes comes first when they compete, the missing piece is not information. It is a decision about priorities, and the people who make that decision are the people who were in the room when the study was proposed.

So the study comes back, usually a few months later, and it is often well done. It describes four options clearly and lays out the tradeoffs of each. The team reads it and finds that everyone's original position is still available, now supported by a table. The people who wanted to protect the small program point to the section on depth of service. The people who wanted to consolidate point to the section on reach. The analysts did their job, and the team is exactly where it started, with more to read and less time to decide.

What the study costs, even when it is good

The decision gets made anyway, by default. While the study runs, the organization does not stand still. Budgets get set for the next year on the current arrangement, people make plans on the assumption that nothing is changing, and a few of the options the study will describe quietly stop being available. By the time the report arrives, some of the choice has already been settled by the passage of time, and nobody in the room chose it.

The people doing the work learn what studies mean here. Staff who watched the last hard question go out for review and come back without a decision draw a reasonable conclusion. The next time a study is proposed, they read it as a signal that leadership is not going to decide, and they adjust their own plans accordingly. The analysis you commission in good faith starts to function, in their eyes, as an announcement that the question has been set aside.

The team gets worse at the conversation it avoided. A group that sends its hardest disagreements out for analysis never practices having them. It never learns how its members weigh competing goods, where they will bend and where they will not, or how to reach a decision that some of them dislike and all of them can live with. That skill is the one a team needs most under pressure, and it is the one this habit keeps it from building.

Three moves

Before approving any study, ask what result would change your mind. Put the question to the room plainly: if the survey came back one way, which option would the group choose, and if it came back the other way, which option then? If the team can answer, the study has a real job and is worth doing. If every plausible result leaves the group where it is, the study is not going to settle anything, and the team should have the harder conversation now.

Separate the question of fact from the question of priority, out loud. Most hard team decisions contain both, and they get tangled. Write them down as two lists. The first holds what the team genuinely does not know, such as cost, demand, or what happened when others tried this. The second holds what the team has to decide, such as which of its purposes comes first when they collide. Commission work on the first list, and put a meeting with a date on the calendar for the second.

Decide what you are protecting before the analysis starts, not after it ends. If the team names its priorities first, even roughly, the study has something to be measured against, and the people writing the report can show you which option best serves the purpose you already chose. Analysis with a stated purpose narrows a decision. Analysis without one widens it, and a team that was already stuck does not need a wider decision.

The part that is about you

The relief in the room when the study was proposed was real, and some of it was yours. Proposing more analysis lets a leader look diligent at the exact moment they would otherwise have to disappoint someone they respect. It moves the discomfort a few months down the road, and a few months is long enough that it feels like it might never return.

It is worth asking yourself, the next time you hear that suggestion, whether you are relieved because the team needs the information or because you no longer have to say which side you are on today. Both are human. Only one of them is a reason to spend the money.

Three questions

What was the last study, review, or outside analysis your unit commissioned, and did the decision that followed differ from what the team would have chosen without it?

In the hardest disagreement your team currently has, how much of it is about facts nobody has, and how much is about which purpose comes first?

If someone proposed a study in your next meeting, could anyone in the room say which result would change the decision?