When Every Detail Becomes a Secret: Information in Project Teams

The question is who needs what to do the work

A current drawing is difficult to find. A decision is known to a few people but not to the team implementing it. Routine information requires repeated personal requests. These situations can create delay and uncertainty.

They do not automatically prove deliberate withholding. Poor document organisation, unclear permissions or an unassigned communication task can produce a similar result. Start with the obstacle and its effect, rather than an accusation about motives.

Confidentiality has a purpose

Personal information, security-sensitive details, procurement material and commercial information may require controlled access. Not every person needs every document.

But an access restriction should have a clear basis and an authorised route for people who need information to perform their role. Calling everything confidential without explaining that route can make ordinary coordination unnecessarily difficult.

Make information usable

Identify where approved versions live, who maintains them and how changes reach affected people. Separate a draft discussion from an authorised instruction. Provide access appropriate to the role and a process for resolving blocked access.

In a hypothetical handover, the operations team may need approved maintenance information while unrelated commercial details remain restricted. The answer is a suitable information package, not either unrestricted access or complete silence.

Knowledge should survive an absence

The Project Management Institute (PMI) publishes a paper linking collaboration and knowledge sharing with trust and working relationships. [1]

A team should also be able to find essential records when a particular person is away. Keeping the only copy in a private inbox makes the organisation dependent on that person, whether or not they intended it.

For candidates, ask how decisions, drawing revisions and lessons are shared. An understandable system protects useful knowledge while respecting genuine confidentiality. It also reduces the time spent repeatedly asking for information that should already be available.

Source and why it was chosen

[1] Project Management Institute — Project management collaboration: Knowledge sharing among project managers. Selected as a North American-origin management reference on relationships and knowledge exchange. The access examples are editorial suggestions; actual privacy, security and contract requirements govern a project’s permissions.
https://www.pmi.org/learning/library/collaboration-knowledge-sharing-project-managers-9370