Why the Best Idea Does Not Always Come from the Leader

Organizations tend to associate seniority with greater expertise. There are reasonable grounds for this: leaders generally have a broader organizational perspective, more information about strategic priorities and financial constraints, and responsibility for the final outcome.

Yet a subtle logical error often follows. The statement “the leader is accountable for the decision” becomes “the leader knows best what the decision should be.” These are different claims.

Hierarchy distributes responsibility, but knowledge follows a different pattern

A hierarchical structure establishes who is responsible for what: who coordinates action, allocates resources, makes the final decision and answers for its consequences.

However, hierarchy does not automatically reveal where the expertise most relevant to a particular problem resides.

• A production-line employee may understand a bottleneck better than the plant manager.
• A sales representative may notice a change in customer responses before the marketing director does.
• An IT specialist may recognize a technical risk that senior management has missed.
• A hospital nurse may understand a workflow problem that administrators do not see.
• A city employee who works directly with residents may know more about a service failure than the department’s senior leadership.

In a complex organization, knowledge and decision authority form two different structures. Hierarchy distributes the authority to decide. Expertise is distributed in a much more intricate way.

Expertise is specific to the problem

Someone can be highly knowledgeable in one narrow field and know very little about another. There is no single, universal scale of expertise across an organization.

Without a specific problem in mind, asking “Who is the most competent person here?” often tells us very little. In one situation, it may be an engineer; in another, a customer-service representative; in a third, a finance specialist. In a fourth, it may be an external expert who does not work for the organization at all.

A sound decision system should identify whose knowledge matters most to this particular problem.

Position and expertise are only partly aligned

People often reach senior positions because of their expertise, experience and judgment. It would be wrong to suggest that status and competence are unrelated.

But the relationship is not absolute. A leader may be an excellent strategist without knowing specific technical details. An expert may have deep knowledge without organizational authority. A junior employee may be the first to recognize an emerging trend simply because they work with a new technology or a new type of customer every day.

The problem begins when status becomes a substitute for expertise. “Is this a good idea?” quietly turns into “Who said it?”

Status changes how we evaluate ideas

People do not evaluate ideas in isolation. When a CEO makes a proposal, it may carry extra weight before anyone has examined its substance. The same proposal from a little-known employee may be overlooked.

This does not have to be deliberate. Authority, loyalty, conformity, fear of disagreement, the desire to appear competent and reluctance to challenge a manager all influence organizational behavior.

In an open meeting, ideas compete through their social weight as well as their content.

The first person to speak is not always the person who knows most

In a conventional meeting, communication style can strongly influence the outcome: who formulates a thought fastest, who sounds most confident, who speaks loudest, who holds the most senior position and who controls the discussion.

Yet speaking quickly and solving a problem well are different abilities. Some of the best ideas may come from people who need more time to analyze, prefer not to argue, are less visible in the organization or speak only when they feel certain.

A conventional meeting can therefore systematically leave part of the organization’s intelligence unused.

A leader’s idea can unintentionally become the “right answer”

A particularly difficult situation arises when the leader states a position at the very start of a discussion. Imagine a sales director opening with: “I think the problem is the sales team’s motivation.”

The discussion now has an anchor. Some participants begin looking for evidence to support that explanation. Others try to modify it cautiously. Still others keep an entirely different interpretation to themselves.

The leader may have no intention of pressuring anyone. Their status alone can be enough. Good decision architecture must therefore also protect leaders from the information distortions created by their own position.

A good leader should create the conditions for good ideas to emerge

The more complex an organization becomes, the less reasonable it is to expect its leader to generate the best solution to every problem.

The leader’s role shifts toward creating a system in which a strong answer can emerge anywhere in the organization and receive a fair evaluation.

This makes the leader an architect of the decision process. A more advanced form of leadership is the ability to create conditions in which the organization can discover its best available answer.

Collective intelligence separates an idea from its author’s status

One of the central principles of collective intelligence is straightforward: evaluate the idea on its substance.

When participants cannot see who submitted a proposal, the influence of status is reduced. An idea from a director and an idea from a junior specialist can be presented in exactly the same way. The evaluator must respond to the content.

In the approach described here, collective intelligence develops through interaction on a single platform. We call this structured collective decision-making process collective decidement. Before offering an idea, participants evaluate earlier proposals. If they have something new to add, they submit one clear, original, non-repetitive idea. Authors and interim aggregate results remain hidden during evaluation.

Expertise, responsibility and a person’s relationship to the problem still matter. The process creates an opportunity to assess a proposal without using the author’s identity as a shortcut.

Expertise can become visible through contribution

Organizations traditionally judge expertise in advance, using job titles, degrees, professional credentials, a manager’s assessment or length of service.

A decision process can add another source of evidence. A person contributes proposals that others evaluate as useful. Their assessments consistently help distinguish promising alternatives. Over time, the significance of their contribution becomes visible.

Expertise is then demonstrated through observable contribution as well as formal qualifications. This can help an organization discover capabilities that were previously difficult to see within its hierarchy.

The platform uses accountable anonymity: participants remain anonymous to one another, while the system preserves the connection between a person and their actions. Contributions remain traceable and measurable.

This does not imply that everyone has equal expertise

A post-hierarchical approach to decisions can be misunderstood as a claim that everyone is equally competent. That would be a mistake.

People differ greatly in what they know. However, we cannot assume that we always know in advance who has the most relevant expertise for this exact problem.

It is therefore reasonable to involve a wider range of relevant participants and allow the process to reveal useful evidence of competence. The aim is to detect differences in expertise more accurately.

Sometimes the required expertise is missing altogether

The best idea may come from neither the leader nor an employee because the necessary knowledge is absent from the organization. The task may involve an unfamiliar AI technology, a new regulatory requirement, an overseas market or a specialized engineering problem.

This calls for external expertise sourcing. External experts, researchers, partners, customers or other knowledgeable practitioners can join the same collective decidement process.

An external expert does not have to take over the organization’s decision. Their contribution can supply knowledge that was missing from the shared decision space.

Complex problems need a range of perspectives

Complex problems rarely belong to just one discipline. A new product may fail because of a combination of technology, pricing, customer experience, the sales process, communication, manufacturing constraints and competitors’ actions.

One person rarely understands all of these dimensions. A strong solution can emerge as partial perspectives interact and inform one another.

Why group size matters

When only three or four people assess a problem, their perspectives may be very similar. Group size is therefore relevant to this collective intelligence method.

For this approach, we recommend at least eight active participants in each project. A group of 15–20 or more can provide a broader range of perspectives, provided its members bring relevant, complementary knowledge and participate meaningfully.

These are practical guidelines for the method, not universal thresholds or guarantees of quality. A larger group can increase the chance of finding rare expertise, a different interpretation, an unexpected alternative or a previously overlooked risk. Size alone is insufficient.

A cluster is the wider pool of participants; a project is one clearly defined task. Different cluster members may contribute to different projects.

The leader’s role becomes more demanding

At first glance, collective intelligence may appear to weaken leadership. In practice, the role described here requires a different and demanding set of capabilities.

The leader must help frame the problem, bring together the relevant people, establish conditions for independent interaction, limit distortions caused by status, involve external expertise when necessary, interpret the findings and take responsibility for action.

The central question becomes: “How can I create a system that helps the organization discover its best available answer?”

A future competitive advantage may be the ability to recognize overlooked talent

Organizations have long competed for talented people. Employing them is only part of the challenge. If the decision process prevents their knowledge from influencing action, some of their expertise remains unused.

Alongside “Do we have good people?” an organization should ask: “Can our decision system recognize when this particular person knows something that others do not?”

The first question concerns human resources. The second concerns organizational intelligence.

The best idea does not have a job title

An organization becomes more intelligent when its decision architecture allows a good idea to receive attention regardless of where it originated in the hierarchy.

The leader remains accountable. The expert retains their expertise. The employee remains a source of firsthand experience. The idea gains an opportunity to be evaluated on its substance.

A well-designed organization does not need to know in advance where its best idea will come from.

Saulius Norvaišas
Developer of the collective intelligence methodology and platform