Building on Ideas Rather Than Rejecting Them

Definition

Many leaders and managers unconsciously reject ideas by ignoring them or immediately pivoting to an alternative, signaling that the person's contribution has no value. This damages confidence and discourages future idea-sharing. In contrast, a leader who assumes that every idea offered made some sense to the person who expressed it—no matter how flawed it appears initially—creates psychological safety. The practice is to first identify and articulate what is valuable in the idea, revealing shared values in the process. Only after acknowledging the constructive elements should concerns be raised—and even then, framed as subproblems to be solved together, not fatal flaws that invalidate the idea. This keeps the group's energy focused on building solutions rather than defending positions.

In the Book

Prince provides a concrete example of the same meeting conducted two ways. In the first, a manager hears a suggestion to decentralize manufacturing to reduce shipping costs. Another subordinate counters with a competing approach (get carrier competition). The manager selects the second idea, unintentionally rejecting the first. The subordinate who offered the decentralization idea interprets this silence as rejection and feels demoralized. The manager didn't intend harm; he was simply selecting what seemed more realistic. But the discrepancy between his perception (reasonable choice) and the subordinate's (arbitrary rejection without explanation) creates resentment and withdrawal.

In the second version of the same meeting, the manager acknowledges the decentralization idea first, naming the valuable aspects: "Decentralizing would save on shipping, give us faster-moving units, and break up a centralized operation to spread responsibility." Only after this affirmation does he raise his concerns as problems to work on together: "I see some challenges here—how to decentralize without capital expense, and how to keep both economies of scale and small-plant advantages." The group then solves these problems together, building on the original idea rather than abandoning it. The subordinate feels heard, valued, and motivated to contribute further.

Why It Matters

Organizations that discourage idea-sharing through reflexive rejection lose access to frontline insights, ground-level innovation, and employee engagement. Conversely, teams that practice building on ideas—rather than shooting them down—unlock discretionary effort and retain institutional knowledge. The shift from a judgmental posture (accept or reject) to a judicious one (understand value, work on problems) is a learnable move that directly correlates with team effectiveness, psychological safety, and innovation outcomes.