Knowledge is Power

Why Information Is Guarded in Organizations

When a project stalls or a decision misses the mark, it is tempting to blame poor communication. In many cases, however, the real issue lies in the intentional withholding of information. Companies that run on a hierarchical model distribute knowledge in a controlled manner. The top layer sets the strategic vision - profit, growth, innovation - and then passes down slices of that vision to each manager. Each manager, in turn, turns their slice into a concrete set of tasks for their team. Because the overall picture is only known a few levels up the chain, team members rarely see the full context of their work.

This structure offers three key benefits to the organization. First, security: if an employee only knows a small piece of the puzzle, they are less likely to replicate the company’s competitive advantage elsewhere. The idea is simple - information is a commodity that can be misused if it falls into the wrong hands. Second, control: by keeping the big picture centralized, managers can align individual actions with corporate goals. When everyone sees the same picture, coordination becomes easier and accountability clearer. Finally, focus: limiting exposure to unrelated data helps employees concentrate on their immediate responsibilities. A specialist who knows everything about every part of the business can become a distraction, constantly pulling themselves away from the tasks that truly move the needle.

It can be frustrating when the person who should have the answers seems to be playing a guessing game. Imagine a product launch where the marketing team needs to know the new pricing strategy, but the pricing team refuses to share. The marketing manager ends up chasing rumors, gathering fragments from colleagues, and hoping that the missing piece will surface before the deadline. When the pricing team finally drops the ball, the marketing manager is left scrambling, and the launch suffers. This kind of friction shows how the “need to know” principle, while protecting the organization, can also stall progress.

Another factor is trust. Information is often perceived as a currency. If an employee senses that their supervisor is hoarding knowledge, they may feel undervalued or suspect that the organization is not transparent. Trust erodes when people believe they are not given the tools they need to succeed. In contrast, when information flows freely within the boundaries of a role, teams operate more efficiently and morale rises. The tension between protecting secrets and building trust is a delicate balance that many managers must navigate.

Ultimately, the “need to know” approach is not a one-size-fits-all solution. It works best when the organization is large, operates in regulated industries, or handles proprietary data. In smaller, more agile environments, the same approach can be counterproductive. Leaders who understand the size and nature of their organization can decide when to widen the distribution of knowledge and when to keep it tightly held.

Power Plays and the Flow of Knowledge

When an employee feels that crucial information is being withheld, the situation often escalates into a power play. In these scenarios, a manager or peer uses silence as leverage. By refusing to disclose a fact, they create a vacuum that forces the other person to dig deeper or to stay in a subordinate role. The hidden knowledge becomes a bargaining chip, and the holder feels empowered while the seeker feels powerless.

One common pattern is the “delegate to deflect” tactic. A manager might intentionally pass a question to a lower-level employee, knowing that the answer is either unimportant or too sensitive to share directly. This not only shifts responsibility but also signals that the manager trusts the subordinate’s judgment. It can be a way to test loyalty or to cultivate a sense of ownership in the team member. Yet, if used excessively, this tactic can breed frustration, as the employee feels that they are being used as a conduit rather than as a collaborator.

Peers sometimes employ similar tactics, especially when they want to maintain an edge. A coworker might withhold data that could give another an advantage, or spread misinformation to keep the conversation within their control. In these cases, the withheld information is not a strategic asset but a weapon. The result is a workplace where collaboration suffers because people double‑check facts, cross‑reference sources, or simply wait for someone else to step in.

There are moments when a manager or peer intentionally limits information to protect the organization’s interests. For instance, a CEO may hold back a change in company policy until the timing is right, or a product lead might not reveal a new feature to prevent leaks. These situations are legitimate, but the key is transparency about the reason behind the delay. When stakeholders understand that a delay is intentional and for the greater good, they are less likely to react negatively.

For the person caught in a power play, the best approach is to request the missing information directly and calmly. By doing so, you show that you value clarity and are not afraid to seek it. If the answer remains elusive, it may be wise to look for alternative sources - internal wikis, cross-functional meetings, or industry contacts. In many cases, the withheld information is either not critical or can be inferred from publicly available data.

Using Information Gaps to Advance Your Career

Feeling in the dark can be a sign of growth opportunity rather than a signal of workplace dysfunction. When you discover that you do not have the full picture, use that knowledge gap as a catalyst for learning and initiative. Start by mapping what you know and identifying the missing pieces that impact your work. This map becomes a roadmap for targeted skill development and research.

Take the time to build a network of reliable sources. Attend cross‑departmental meetings, subscribe to internal newsletters, and reach out to mentors who have navigated similar situations. When you ask for help, frame it as a desire to contribute more effectively rather than a complaint about transparency. Most colleagues appreciate being seen as a proactive team player, and they are often willing to share insights when approached respectfully.

In parallel, document your findings and the steps you take to fill knowledge gaps. Maintaining a knowledge log not only helps you keep track of what you’ve learned but also demonstrates your problem‑solving skills to supervisors. When you can articulate how you identified an issue, gathered information, and applied it to a project, you show that you can operate effectively even with limited initial data.

Another strategy is to turn incomplete information into a project of its own. If a product manager doesn’t have data on user adoption, propose a quick survey or an analytics pilot. By actively seeking the missing data, you add value to the team and position yourself as someone who turns uncertainty into opportunity. This proactive stance often leads to increased trust from leadership and can open doors to higher responsibility roles.

Finally, cultivate an internal culture that values knowledge sharing. Lead by example: if you come across a useful resource or an insight that could help others, share it promptly. Encourage open discussions where questions are welcomed and answers are sought collectively. When you help create an environment where information flows freely, you reduce the likelihood of future power plays and empower everyone to perform at their best.

Edward B. Toupin is a published author, technical writer, web developer, coach, and producer based in Las Vegas, NV. His work focuses on delivering information that helps people achieve fulfilling lives. For more, visit toupin.com.