Why a team's knowledge is not enough for a good decision

Everyone holds a piece that the others lack

A team is choosing a systems vendor. Everyone knows about Vendor A's attractive price and polished presentation. The security specialist has identified a vulnerability in the proposed solution, the service team knows about limitations in the support package, and the integration lead has spotted an additional cost. Each fact on its own may look like a minor reservation about an otherwise strong option. Together, they could change the decision. If the pieces are never combined, the meeting may end in agreement based on an incomplete picture. This illustrates the hidden-profile problem. In experimental tasks, information is distributed so that the best solution becomes apparent only after participants share what they know. The issue is not a simple absence of data: the group possesses the data collectively, but some of it never enters the discussion or receives the weight it deserves. A team of competent, well-intentioned people may still fail to use what each person brings. An individual may not realize how valuable their information is to the overall picture. The security specialist knows about the vulnerability but not about the service team's concern; each person may therefore conclude that their observation is not enough to challenge what looks like a good choice. Only when the facts are combined does the evaluation change. A facilitator should not simply wait for someone to oppose the apparent majority in public. It is better to create a way for people to present relevant information whether or not they have formed a recommendation. The team needs access to the underlying evidence, not only to final positions, so that together it can see the significance of fragments no one person could previously connect.

Why shared information is easier to discuss

A meta-analysis by Lu, Yuan, and McLeod summarizes research on hidden profiles in group decision-making. It highlights both the importance of information exchange and the difficulty groups have in using unshared knowledge. Findings from controlled tasks should not be translated mechanically into claims about every business meeting, but they provide good reason to ask whether a discussion is genuinely bringing dispersed information together. Lu et al., 2012 Shared knowledge has a natural advantage: several people can recall and confirm it. When someone says that a supplier made a good impression, others can readily agree. New information requires explanation, verification, and sometimes a pause in the discussion. Its holder may decide that the detail is not important enough to raise, especially once the group has begun signaling a preferred choice. A meeting can then feel rich in argument while repeatedly circling the same familiar evidence.

How early voting can narrow the discussion

Opening with “Who supports Vendor A?” reveals preferences before the group has heard all the evidence. Once people have voted, they may begin organizing subsequent arguments around the position they have publicly taken. A new concern can then look like an attempt to overturn the majority rather than a missing part of the analysis. This does not mean that every preliminary opinion is harmful; the risk rises when it becomes a public commitment before relevant information has been exchanged. A practical response is to separate the stages. First, participants present information from their own areas. Next, the group agrees the criteria and compares the options. Only then does it make a choice. Before a procurement meeting, for example, participants might submit costs, risks, constraints, and unknowns from their respective specialties. The form need not be elaborate, but it should not reduce an expert's contribution to a simple “yes” or “no.” Preparation should not consist of sending everyone a vast bundle of documents without explaining what to look for, either. Too much information can obscure the details that matter. Ask participants to identify what bears on each selection criterion and to note both the source and level of certainty. It can also help to distinguish facts already shared across the group from additions contributed by particular specialties. Not every small decision requires a rigid procedure. The greater the cost of error and the more dispersed the relevant knowledge, the stronger the case for structuring the discussion deliberately. The structure must help the group compare and use information, not merely give everyone a formal turn to speak without affecting the analysis or the final choice.

Ask for missing information, not only dissent

Near the end of a discussion, facilitators often ask whether anyone has any comments. The invitation is broad, but it does not necessarily prompt people to search for knowledge the group has overlooked. A more useful question is: “What do you know from your area that the rest of us may not know yet?” The team can also work through its criteria and check whether each one is adequately covered. Allow time for an answer; retrieving a relevant detail may take longer than expressing a quick opinion. Novelty alone does not make information valuable. A concern may be outdated, unreliable, or irrelevant to the objective. Once it is on the table, assess its source, significance, and uncertainty. The person raising a risk should be able to say, “This is still a hypothesis; I need to verify it.” That helps the group avoid two opposite errors: ignoring anything unfamiliar and giving every minority view unquestioned priority.

This is not always deliberate knowledge hiding

A hidden profile is not the same as deliberate knowledge hiding. An employee may genuinely want to help but not realize that their observation is unique, or may never find a suitable moment to raise it. Another may speak up yet remain misunderstood because they use the language of their own specialty. In these cases, reminding people that they have a duty to share knowledge misses the cause. The team needs a discussion process that helps translate each piece of information into its significance for the shared decision. After deciding, record which evidence supported the choice and which unknowns remain open. If new information emerges later, the team can then judge more easily whether it changes the basis of the decision. This also supports learning without defaulting to blame. Instead of asking only, “Who failed to speak up?”, examine whether the process created a real opportunity for the necessary knowledge to surface and whether the facilitator responded to it. When someone presents new information, the leader should show what happened next: did it alter the assessment, require verification, or prove immaterial for a specific reason? That response makes the process intelligible and encourages further disclosure. A polite thank-you followed by an immediate return to the earlier preference may not be enough. It is also worth recording the conditions on which the decision depends. If choosing the system is contingent on confirming its security, that condition should appear in the summary. New evidence can then re-enter the process without forcing the team to argue from scratch about whether a supposedly closed decision may be revisited.

The sum of what participants know does not automatically become knowledge the group actually uses. A good meeting surfaces unshared information, tests its significance, and only then moves toward a choice. Sometimes the greatest improvement comes from changing the order of the questions rather than inviting another expert.

Using Empatyzer to prepare a decision-making meeting

Empatyzer can help you plan a conversation in which participants have a genuine opportunity to contribute the knowledge the team needs. In Talk to Em about your team, you can prepare the sequence of questions, ways to invite additions, and a summary of unresolved issues. An available group profile can help account for differences in how people enter a discussion and how much preparation they may need. In Talk to Em about a specific person, you can refine an invitation to raise concerns, particularly when that person's perspective has rarely been heard. Empatyzer does not know the project data automatically or choose the best solution for the team. It cannot replace expert judgment, source verification, or risk analysis. Its role is to support communication planning: it can help create conditions in which knowledge has a chance to be voiced and understood, while the relevance of that knowledge must be judged by people with the appropriate expertise and responsibility for the outcome.