Project Management Central
|
Please login or join to subscribe to this thread
Request to reuse this Topics: Communications Management, Knowledge Management, Lessons Learned, Talent Management |
||||||
|
||||||
At a high level, if you have an NDA signed with a party, then you cannot put any information(Especially sensitive info) with anyone else without that parties consent. If the info is already available in public domain, then you can share.
There is no direct answer to this question, but only some hints 1. Follow you company policies always. When you join a company, you would have signed at many places with declarations 2. If you are in a contract with vendor/customer, always follow the rules written in that contract(There would be clauses related information sharing in the contract) 3. On top of this there are rule specific to certain countries. You need to follow them(eg: export regime control to certain countries, trade embargoes) The above 3 points would help you to avoid legal trouble.
I like Ramachandran's suggestion of using a non-disclosure agreement to establish base rules.
Alternatively, information confidentiality and sharing can be explicitely covered in a contract.
Thinking in internal communications in a Company,
It will be ideally to have a procedure that establish the level and content of communications and information policy. In practice, most of times it's not formally stablished, and it's the organizational culture that stablish the non written rules.
My strategy is to carefully note what I and my team can't share with people (such as proprietary company information); I then share everything else while making sure people don't share the restricted information.
Hello Samer: I am wondering why you posed this question? Have you run into a specific situation that you are questioning? As a general rule, my thoughts are transparency is very important as a project manager - being open and transparent is how you build trust, respect, understanding and stronger teams. This is balanced by knowing what is acceptable to disclose and what should not be shared. The information listed above by our peers is sound. Always know your company policies and make sure what you are about to share is approved for sharing. Protect yourself and your company's best interest in all your interactions.
...
1 reply by Samer Alhmdan
Aug 21, 2017 11:58 PM
Samer Alhmdan
...
Hello Lori,
Thank you for your answer, the reason for my question is that I worked previously with a confidential project where we can't share all information, and now I'm trying to think about what went wrong and what went right, and the trade off between confidentiality and transparency. Aug 21, 2017 11:21 AM
Replying to LORI WILSON
...
Hello Samer: I am wondering why you posed this question? Have you run into a specific situation that you are questioning? As a general rule, my thoughts are transparency is very important as a project manager - being open and transparent is how you build trust, respect, understanding and stronger teams. This is balanced by knowing what is acceptable to disclose and what should not be shared. The information listed above by our peers is sound. Always know your company policies and make sure what you are about to share is approved for sharing. Protect yourself and your company's best interest in all your interactions.
Thank you for your answer, the reason for my question is that I worked previously with a confidential project where we can't share all information, and now I'm trying to think about what went wrong and what went right, and the trade off between confidentiality and transparency. ...
1 reply by Sergio Luis Conte
Dec 11, 2022 7:33 AM
Sergio Luis Conte
...
Perhaps I did not understand your post but take a look to START Interview Method.
As mentioned, when sharing any confidential information make sure you have an NDA in place. But to better understand what information you should, can and must share with specific stakeholder you must start out by conducting a stakeholder analysis to understand the level of power and influence of all your stakeholders. This is an ongoing process since stakeholders can change during the course of a project. It should tell you where your boundaries are with regards to confidentiality.
Be careful though - some stakeholders might consider information confidential for the wrong reasons, and you do not want to water down your collaboration efforts because of this. Remember that collaboration is very important for success so the confidentiality must be worth it.
The better strategy is balance "Need to Know" with "Need to Share".
If someone needs to know the information, share the information. If you think they might find it irrelevant, don't bother. If an information is part of an NDA, it would be mostly for a third party, not directly connected with your client or sharing in the public domain. As always, when in doubt, ask someone who ranks higher than you and get their approval in writing. 
Network:1438
I have a similar question. What information can and can't be shared during an interview?
like the hiring company asked: give an example that you solve a tough technical problem (the hiring company wants to know what were technical problems and how you solved them). how you handle tough requirements/ conflict requirements from stakeholders or unclear requirements, and how you solve them. (and the hiring company wants to know the requirements..) Aug 21, 2017 11:58 PM
Replying to Samer Alhmdan
...
Hello Lori,
Thank you for your answer, the reason for my question is that I worked previously with a confidential project where we can't share all information, and now I'm trying to think about what went wrong and what went right, and the trade off between confidentiality and transparency.
|
||||||
Please login or join to reply
ADVERTISEMENTS
|
"I never thought much of the courage of a lion-tamer. Inside the cage he is at least safe from people." - George Bernard Shaw |
