Should I have shared a document with a former employee?In an interview how can I explain the short duration of my last job?How do I deal with have having had a personal meltdown that's affected my worklife?How to address my manager's sudden reluctance to communicate?How to handle debt collection calls for a former employee?Promised contract but not receiving oneLost my temper with an underperforming employee and he quitFormer employee wants to come backBad annual review following disagreement with VPIs a lack of work my fault?Disclosing details of my previous employment to my new employer
Why is it "on the inside" and not "in the inside"?
Japanese reading of an integer
How did the Sinclair compare on price with the C64 in the UK?
Why didn’t Christianity spread southwards from Ethiopia in the Middle Ages?
Does Wolfram Mathworld make a mistake describing a discrete probability distribution with a probability density function?
Compound Word Neologism
Telling manager project isn't worth the effort?
Is it error of law to judge on less relevant case law when there is much more relevant one?
How did the SysRq key get onto modern keyboards if it's rarely used?
(3 of 11: Akari) What is Pyramid Cult's Favorite Car?
ECDSA: Why is SigningKey shorter than VerifyingKey
Can a US President, after impeachment and removal, be re-elected or re-appointed?
Move the outer key inward in an association
How can I kill my goat?
Why does the Eurostar not show youth pricing?
Should I accept an invitation to give a talk from someone who might review my proposal?
Did the Americans trade destroyers in the "destroyer deal" that they would later need themselves?
Adopting a feral cat
Polyhedra, Polyhedron, Polytopes and Polygon
Is there a wealth gap in Boston where the median net worth of white households is $247,500 while the median net worth for black families was $8?
How did the Axis intend to hold the Caucasus?
Why do they sell Cat 5 Ethernet splitters if you can’t split the signal?
Why is the Apollo LEM ladder so far from the ground?
What's the differences between the two version of oracle client download file, "client" and "client home"?
Should I have shared a document with a former employee?
In an interview how can I explain the short duration of my last job?How do I deal with have having had a personal meltdown that's affected my worklife?How to address my manager's sudden reluctance to communicate?How to handle debt collection calls for a former employee?Promised contract but not receiving oneLost my temper with an underperforming employee and he quitFormer employee wants to come backBad annual review following disagreement with VPIs a lack of work my fault?Disclosing details of my previous employment to my new employer
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
My deputy manager who left 3 months ago is asking for a document that was shared with me and my team after they left, but they were part of the meetings that led to the preparation of that document. I have emailed it to them without consulting my manager. I was just thinking, was this okay to do?
professionalism employees confidentiality
add a comment |
My deputy manager who left 3 months ago is asking for a document that was shared with me and my team after they left, but they were part of the meetings that led to the preparation of that document. I have emailed it to them without consulting my manager. I was just thinking, was this okay to do?
professionalism employees confidentiality
56
Were the contents of the document confidential to the company?
– Snow♦
Jul 18 at 14:05
3
This Question is unclear. You should give some sense of the kind of content in the document. You have a tag for confidentiality but fail to explain.
– Basil Bourque
Jul 19 at 21:25
If it's a confidential document there is no situation where it would be alright to share that with an ex-employee.
– Gregory Currie
Jul 20 at 3:46
1
This depends completely on what you shared and what the company does. It's impossible to make any meaningful judgement otherwise.
– iono
Jul 20 at 12:06
why does he want that document? Did you ask?
– Mayou36
Jul 21 at 16:47
add a comment |
My deputy manager who left 3 months ago is asking for a document that was shared with me and my team after they left, but they were part of the meetings that led to the preparation of that document. I have emailed it to them without consulting my manager. I was just thinking, was this okay to do?
professionalism employees confidentiality
My deputy manager who left 3 months ago is asking for a document that was shared with me and my team after they left, but they were part of the meetings that led to the preparation of that document. I have emailed it to them without consulting my manager. I was just thinking, was this okay to do?
professionalism employees confidentiality
professionalism employees confidentiality
edited Jul 18 at 15:14
Jay
7,2042 gold badges20 silver badges47 bronze badges
7,2042 gold badges20 silver badges47 bronze badges
asked Jul 18 at 14:04
Ray rayRay ray
2321 gold badge2 silver badges3 bronze badges
2321 gold badge2 silver badges3 bronze badges
56
Were the contents of the document confidential to the company?
– Snow♦
Jul 18 at 14:05
3
This Question is unclear. You should give some sense of the kind of content in the document. You have a tag for confidentiality but fail to explain.
– Basil Bourque
Jul 19 at 21:25
If it's a confidential document there is no situation where it would be alright to share that with an ex-employee.
– Gregory Currie
Jul 20 at 3:46
1
This depends completely on what you shared and what the company does. It's impossible to make any meaningful judgement otherwise.
– iono
Jul 20 at 12:06
why does he want that document? Did you ask?
– Mayou36
Jul 21 at 16:47
add a comment |
56
Were the contents of the document confidential to the company?
– Snow♦
Jul 18 at 14:05
3
This Question is unclear. You should give some sense of the kind of content in the document. You have a tag for confidentiality but fail to explain.
– Basil Bourque
Jul 19 at 21:25
If it's a confidential document there is no situation where it would be alright to share that with an ex-employee.
– Gregory Currie
Jul 20 at 3:46
1
This depends completely on what you shared and what the company does. It's impossible to make any meaningful judgement otherwise.
– iono
Jul 20 at 12:06
why does he want that document? Did you ask?
– Mayou36
Jul 21 at 16:47
56
56
Were the contents of the document confidential to the company?
– Snow♦
Jul 18 at 14:05
Were the contents of the document confidential to the company?
– Snow♦
Jul 18 at 14:05
3
3
This Question is unclear. You should give some sense of the kind of content in the document. You have a tag for confidentiality but fail to explain.
– Basil Bourque
Jul 19 at 21:25
This Question is unclear. You should give some sense of the kind of content in the document. You have a tag for confidentiality but fail to explain.
– Basil Bourque
Jul 19 at 21:25
If it's a confidential document there is no situation where it would be alright to share that with an ex-employee.
– Gregory Currie
Jul 20 at 3:46
If it's a confidential document there is no situation where it would be alright to share that with an ex-employee.
– Gregory Currie
Jul 20 at 3:46
1
1
This depends completely on what you shared and what the company does. It's impossible to make any meaningful judgement otherwise.
– iono
Jul 20 at 12:06
This depends completely on what you shared and what the company does. It's impossible to make any meaningful judgement otherwise.
– iono
Jul 20 at 12:06
why does he want that document? Did you ask?
– Mayou36
Jul 21 at 16:47
why does he want that document? Did you ask?
– Mayou36
Jul 21 at 16:47
add a comment |
8 Answers
8
active
oldest
votes
You need to talk to your manager about this immediately.
You absolutely should not have done this. This person is no longer an employee at your organization is not entitled to any company information. It doesn't matter that they may have helped create the documents and probably know the content anyway, sharing it with them essentially makes it a public release. Now, it may be that your manager says it's fine and would have told you to send it on, but you should absolutely not do this without written approval.
24
Is this really a good idea? If it's a trivial document, containing no personal information, secrets or other commercially sensitive information, and there's no evidence of it having been shared, then in my opinion OP should carefully weigh up the likelihood of being found out against the likelihood that confessing will actually do anything to help their case. Why should they highlight their own misconduct if they are likely never to be found out otherwise, unless there's an ethical issue (privacy etc) at stake?
– user234461
Jul 19 at 8:57
24
@user234461 if it was "trivial document" which required several meetings of a team of employees to prepare it, the company is probably too dysfunctional to survive anyway! More likely, this guy wants some hard evidence of his old company's strategy, to support his proposals to give his new employer a competitive advantage.
– alephzero
Jul 19 at 9:25
5
@user234461 If it was emailed from company email, there is evidence of it having been shared.
– Delioth
Jul 19 at 15:06
12
@user234461 "there's no evidence..." It is unethical to base a decision on the likelihood of getting caught. There is evidence since it was sent via email. Not bringing this to the manager will make it look intentional. Admitting it also allows the company to do damage control. Imageine the company later files for a patent and finds that the document was released publicly, and an employee hid that information. That could cost the company millions of dollars and the employee their job. By letting them know now they can put the proper NDAs in place and document that the release is not material.
– Moby Disk
Jul 19 at 20:05
2
The manager may limit OP's access to company documents until they prove that they have learned their lesson, but firing is definitely overreacting. Firing them if they found out after the OP didn't tell them would be appropriate on the other hand 'cuz it would show that the OP can't be trusted with company information thus cannot do any work for them.
– ivan_pozdeev
Jul 20 at 13:36
|
show 3 more comments
No, don't share internal company information with non-members of the firm except in the course of normal business.
Previous employees do not have a legitimate interest in non-public company information (unless they are doing business with the firm). It doesn't matter how sensitive the information seems or if it is marked confidential - unless you have permission to share the information, keep it private.
You should alert your manager or a trusted leader in the company. Previous employees asking for information may signal a larger issue. At the very least, make an individual in a management position aware of the data leak.
2
"or a trusted leader in the company" – The OP doesn't say which jurisdiction he is in, unfortunately. If he is within the jurisdiction of the GDPR or something similar, there should be a designated Data Protection Officer, who is protected by law from divulging his sources. While this might not technically a data breach as defined by the GDPR, the DPO should at least be able to advise the OP. If the OP is in Germany or a country with similar laws, and the company is larger than 5 employees, then there might be a Worker's Council, which has certain protections.
– Jörg W Mittag
Jul 20 at 9:20
1
If the OP is a member of a Union, he should have the possibility to talk to an Ombudsperson or similar. All three of these options allow the OP to talk to someone who can both advise the OP on how to best handle the situation, and who is able to forward the information to the appropriate person in the company without having to divulge the name of the employee.
– Jörg W Mittag
Jul 20 at 9:21
add a comment |
No. It was a mistake. The deputy manager no longer works there, so he doesn't get to ask for any company documents. There is no reason to do this I can think of other than to somehow compete with your business.
The correct action would have been to forward his request to your current manager, and forget about it.
Now, mistakes happen, and the fact you're asking about this is good - it means your "did I do something wrong here" radar is still working. Ethics-wise, you should tell your manager what happened immediately and apologise. But you have to balance the risk of getting fired versus protecting the business, which is a decision only you can make.
edit Incorporating some comments:
As someone who works in cybersecurity, one of the things we push for is people to have greater awareness of their actions and of those around them, including self-reporting incidents. If the security team / company is any good, they'll give a minor slap on the wrist saying "don't do that again," and deal with it appropriately. The company finding out after the fact, however, could and should lead to firings.
Tyzoid
I'd say, in tune with workplace.stackexchange.com/questions/140637/… that if sharing important information like this is discouraged in the company on pain of firing, the company is too dysfunctional to survive anyway. People do make mistakes, you can't help it, only learn from mistakes and control damage. If their manager tries to overreact, the OP can tell them just that: "Would you prefer if I kept this secret? Is this the signal you want to send to any other who makes a mistake -- maybe already made?"
– ivan_pozdeev
Jul 20 at 13:26
1
As someone who works in cybersecurity, one of the things we push for is people to have greater awareness of their actions and of those around them, including self-reporting incidents. If the security team / company is any good, they'll give a minor slap on the wrist saying "don't do that again," and deal with it appropriately. The company finding out after the fact, however, could and should lead to firings.
– Tyzoid
Jul 20 at 14:49
add a comment |
Obviously you did the wrong thing, and the only question is whether you should own up to your mistake, or lie low and hope nothing bad happens.
The other answers tend to lean towards owning up, but I have to wonder: what planet are they on? On planet Earth, the obvious and only course of action is to say nothing. If you are found out, you can always plead ignorance; and if you are not found out, well then owning up would have been stupid, wouldn't it?
PS If you think this a question of ethics, ask yourself this: who stands to benefit if you own up? Nobody. Who stands to lose out if you own up? You. It's a no-brainer, if you ask me.
15
Willingly hiding a mistake to avoid potential punishment is likely to just result in harsher punishment down the line when it comes up. Much less stupid to admit your mistake and work to fix it.
– JS Lavertu
Jul 19 at 0:38
7
@JSLavertu: I assume that the likelihood of discovery is very low here. And that if by any chance the OP is found out, they can plausibly claim that they didn't realise they were doing anything wrong. So: do you own up, giving yourself a 100% chance of looking stupid? Or keep quiet, giving yourself perhaps a 2% chance?
– TonyK
Jul 19 at 0:53
5
@GeorgeM "assume your ex-coworker just wanted a concrete sample of his work for his portfolio" Kinda translates to: I shared this information with our ex-coworker so he could share it with others.
– Gregory Currie
Jul 19 at 1:17
6
Well, a portfolio is meant to be shown.
– Gregory Currie
Jul 19 at 2:56
6
Making a mistake is bad but forgivable. Intentionally trying to cover it up isn't a mistake, it's a considered action.
– Basic
Jul 19 at 10:24
|
show 8 more comments
Any company I've worked in, your action would be reason to terminate your employment and take legal action against you for breach of confidentiality agreements, non-disclosure agreements, and document security regulations.
NEVER share information with people outside the company unless you are authorised to do so, and then only with people who are authorised to receive said information.
For example sending an updated installation manual to a customer for the product you're building for him is usually (but not always, there may be rules about who's allowed to communicate at all with customers) ok, sending a design document for something to a random person outside the company, often even the customer for who you are designing that thing, hardly ever is.
add a comment |
Without going into your actions, its obvious you know you have messed up.
So, I would simply weigh up your options.
And you have 2 really:
- Own up, with a risk of getting sacked.
- Keep quiet with a risk of getting found out, and sacked
Personally I think there is more at risk with option 1.
I have in the past kept several spreadsheets I worked on from previous workplaces, just so I can re-use functionality in the future.
Whatever you choose to do cease contact with your former manager.
2
There's a small difference between keeping those documents for yourself and knowingly sending company confidential information to a competitor.
– onnoweb
Jul 19 at 19:04
@onnoweb completely agree, but the information on the document is already known to the former manager, the OP does not say its confidential, and there is no mention of the former manager working for a competitor.
– PeterH
Jul 20 at 7:31
add a comment |
It sounds like you don't know why they wanted it. Some of the other answers assume their motivation was shady, which may be an appropriate assumption, or it may not be. If they were really trying to do something shady, would they have asked you at all?
You should probably ask them why they wanted it, and ask them to keep the document confidential. Best to have such conversation by phone or in person. Their reaction will hopefully give you a better idea of what's at stake in the situation, if anything.
1
Communicated motivations don't matter. After all, if there is an actual legitimate reason, the co-worker could just lie and say that, instead of the real illegitimate reason.
– Gregory Currie
Jul 19 at 3:26
4
"If they were really trying to do something shady, would they have asked you at all?" It seems reasonable that they might. Clearly requesting the document from OP was successful. I don't see how you could rule out that it was shady. To me it seems like they expected OP to spill the beans when asked; they might have taken advantage of that for shady reasons.
– JMac
Jul 19 at 13:06
@JMac I agree. I didn't mean to imply that any possibility can be ruled out. It may be shady and serious. Or it may be benign (though still a breach of protocol). Or it may be shady and they may lie and try to sound benign. OP should consider this from all angles.
– krubo
Jul 19 at 17:29
add a comment |
To answer the question as asked: you should not have forwarded any company document to a former employer, without approval.
Since you have done it, you now need to mitigate the effects: report the error in an appropriate manner.
There are few circumstances in which an employee will be sacked if they admit to a mistake. In fact, even if the consequences are severe, most employers/managers want staff to feel safe about reporting honest mistakes that affect them. A prompt report allows them to mitigate effects - in your case, determine why a former employee requested the document. So you may get a talking-to, or even face some disciplinary action for a data breach (depending on how sensitive the document is, how well employees in your company are briefed about security concerns before starting a project, etc), but that is unlikely to be escalated to dismissal unless you build up a history of making the same sort of mistake repeatedly - you are expected to learn from mistakes, not keep repeating the same ones.
The consequences will certainly be more severe - and more likely to include dismissal - if you don't admit to the problem, and your employer discovers it by other means - for example, during a data or security audit or if a manager is given a copy of the document by a competitor.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "423"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: false,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f140637%2fshould-i-have-shared-a-document-with-a-former-employee%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
StackExchange.ready(function ()
$("#show-editor-button input, #show-editor-button button").click(function ()
var showEditor = function()
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
;
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True')
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup(
url: '/post/self-answer-popup',
loaded: function(popup)
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
)
else
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true)
showEditor();
);
);
8 Answers
8
active
oldest
votes
8 Answers
8
active
oldest
votes
active
oldest
votes
active
oldest
votes
You need to talk to your manager about this immediately.
You absolutely should not have done this. This person is no longer an employee at your organization is not entitled to any company information. It doesn't matter that they may have helped create the documents and probably know the content anyway, sharing it with them essentially makes it a public release. Now, it may be that your manager says it's fine and would have told you to send it on, but you should absolutely not do this without written approval.
24
Is this really a good idea? If it's a trivial document, containing no personal information, secrets or other commercially sensitive information, and there's no evidence of it having been shared, then in my opinion OP should carefully weigh up the likelihood of being found out against the likelihood that confessing will actually do anything to help their case. Why should they highlight their own misconduct if they are likely never to be found out otherwise, unless there's an ethical issue (privacy etc) at stake?
– user234461
Jul 19 at 8:57
24
@user234461 if it was "trivial document" which required several meetings of a team of employees to prepare it, the company is probably too dysfunctional to survive anyway! More likely, this guy wants some hard evidence of his old company's strategy, to support his proposals to give his new employer a competitive advantage.
– alephzero
Jul 19 at 9:25
5
@user234461 If it was emailed from company email, there is evidence of it having been shared.
– Delioth
Jul 19 at 15:06
12
@user234461 "there's no evidence..." It is unethical to base a decision on the likelihood of getting caught. There is evidence since it was sent via email. Not bringing this to the manager will make it look intentional. Admitting it also allows the company to do damage control. Imageine the company later files for a patent and finds that the document was released publicly, and an employee hid that information. That could cost the company millions of dollars and the employee their job. By letting them know now they can put the proper NDAs in place and document that the release is not material.
– Moby Disk
Jul 19 at 20:05
2
The manager may limit OP's access to company documents until they prove that they have learned their lesson, but firing is definitely overreacting. Firing them if they found out after the OP didn't tell them would be appropriate on the other hand 'cuz it would show that the OP can't be trusted with company information thus cannot do any work for them.
– ivan_pozdeev
Jul 20 at 13:36
|
show 3 more comments
You need to talk to your manager about this immediately.
You absolutely should not have done this. This person is no longer an employee at your organization is not entitled to any company information. It doesn't matter that they may have helped create the documents and probably know the content anyway, sharing it with them essentially makes it a public release. Now, it may be that your manager says it's fine and would have told you to send it on, but you should absolutely not do this without written approval.
24
Is this really a good idea? If it's a trivial document, containing no personal information, secrets or other commercially sensitive information, and there's no evidence of it having been shared, then in my opinion OP should carefully weigh up the likelihood of being found out against the likelihood that confessing will actually do anything to help their case. Why should they highlight their own misconduct if they are likely never to be found out otherwise, unless there's an ethical issue (privacy etc) at stake?
– user234461
Jul 19 at 8:57
24
@user234461 if it was "trivial document" which required several meetings of a team of employees to prepare it, the company is probably too dysfunctional to survive anyway! More likely, this guy wants some hard evidence of his old company's strategy, to support his proposals to give his new employer a competitive advantage.
– alephzero
Jul 19 at 9:25
5
@user234461 If it was emailed from company email, there is evidence of it having been shared.
– Delioth
Jul 19 at 15:06
12
@user234461 "there's no evidence..." It is unethical to base a decision on the likelihood of getting caught. There is evidence since it was sent via email. Not bringing this to the manager will make it look intentional. Admitting it also allows the company to do damage control. Imageine the company later files for a patent and finds that the document was released publicly, and an employee hid that information. That could cost the company millions of dollars and the employee their job. By letting them know now they can put the proper NDAs in place and document that the release is not material.
– Moby Disk
Jul 19 at 20:05
2
The manager may limit OP's access to company documents until they prove that they have learned their lesson, but firing is definitely overreacting. Firing them if they found out after the OP didn't tell them would be appropriate on the other hand 'cuz it would show that the OP can't be trusted with company information thus cannot do any work for them.
– ivan_pozdeev
Jul 20 at 13:36
|
show 3 more comments
You need to talk to your manager about this immediately.
You absolutely should not have done this. This person is no longer an employee at your organization is not entitled to any company information. It doesn't matter that they may have helped create the documents and probably know the content anyway, sharing it with them essentially makes it a public release. Now, it may be that your manager says it's fine and would have told you to send it on, but you should absolutely not do this without written approval.
You need to talk to your manager about this immediately.
You absolutely should not have done this. This person is no longer an employee at your organization is not entitled to any company information. It doesn't matter that they may have helped create the documents and probably know the content anyway, sharing it with them essentially makes it a public release. Now, it may be that your manager says it's fine and would have told you to send it on, but you should absolutely not do this without written approval.
answered Jul 18 at 14:10
David KDavid K
27.9k21 gold badges98 silver badges133 bronze badges
27.9k21 gold badges98 silver badges133 bronze badges
24
Is this really a good idea? If it's a trivial document, containing no personal information, secrets or other commercially sensitive information, and there's no evidence of it having been shared, then in my opinion OP should carefully weigh up the likelihood of being found out against the likelihood that confessing will actually do anything to help their case. Why should they highlight their own misconduct if they are likely never to be found out otherwise, unless there's an ethical issue (privacy etc) at stake?
– user234461
Jul 19 at 8:57
24
@user234461 if it was "trivial document" which required several meetings of a team of employees to prepare it, the company is probably too dysfunctional to survive anyway! More likely, this guy wants some hard evidence of his old company's strategy, to support his proposals to give his new employer a competitive advantage.
– alephzero
Jul 19 at 9:25
5
@user234461 If it was emailed from company email, there is evidence of it having been shared.
– Delioth
Jul 19 at 15:06
12
@user234461 "there's no evidence..." It is unethical to base a decision on the likelihood of getting caught. There is evidence since it was sent via email. Not bringing this to the manager will make it look intentional. Admitting it also allows the company to do damage control. Imageine the company later files for a patent and finds that the document was released publicly, and an employee hid that information. That could cost the company millions of dollars and the employee their job. By letting them know now they can put the proper NDAs in place and document that the release is not material.
– Moby Disk
Jul 19 at 20:05
2
The manager may limit OP's access to company documents until they prove that they have learned their lesson, but firing is definitely overreacting. Firing them if they found out after the OP didn't tell them would be appropriate on the other hand 'cuz it would show that the OP can't be trusted with company information thus cannot do any work for them.
– ivan_pozdeev
Jul 20 at 13:36
|
show 3 more comments
24
Is this really a good idea? If it's a trivial document, containing no personal information, secrets or other commercially sensitive information, and there's no evidence of it having been shared, then in my opinion OP should carefully weigh up the likelihood of being found out against the likelihood that confessing will actually do anything to help their case. Why should they highlight their own misconduct if they are likely never to be found out otherwise, unless there's an ethical issue (privacy etc) at stake?
– user234461
Jul 19 at 8:57
24
@user234461 if it was "trivial document" which required several meetings of a team of employees to prepare it, the company is probably too dysfunctional to survive anyway! More likely, this guy wants some hard evidence of his old company's strategy, to support his proposals to give his new employer a competitive advantage.
– alephzero
Jul 19 at 9:25
5
@user234461 If it was emailed from company email, there is evidence of it having been shared.
– Delioth
Jul 19 at 15:06
12
@user234461 "there's no evidence..." It is unethical to base a decision on the likelihood of getting caught. There is evidence since it was sent via email. Not bringing this to the manager will make it look intentional. Admitting it also allows the company to do damage control. Imageine the company later files for a patent and finds that the document was released publicly, and an employee hid that information. That could cost the company millions of dollars and the employee their job. By letting them know now they can put the proper NDAs in place and document that the release is not material.
– Moby Disk
Jul 19 at 20:05
2
The manager may limit OP's access to company documents until they prove that they have learned their lesson, but firing is definitely overreacting. Firing them if they found out after the OP didn't tell them would be appropriate on the other hand 'cuz it would show that the OP can't be trusted with company information thus cannot do any work for them.
– ivan_pozdeev
Jul 20 at 13:36
24
24
Is this really a good idea? If it's a trivial document, containing no personal information, secrets or other commercially sensitive information, and there's no evidence of it having been shared, then in my opinion OP should carefully weigh up the likelihood of being found out against the likelihood that confessing will actually do anything to help their case. Why should they highlight their own misconduct if they are likely never to be found out otherwise, unless there's an ethical issue (privacy etc) at stake?
– user234461
Jul 19 at 8:57
Is this really a good idea? If it's a trivial document, containing no personal information, secrets or other commercially sensitive information, and there's no evidence of it having been shared, then in my opinion OP should carefully weigh up the likelihood of being found out against the likelihood that confessing will actually do anything to help their case. Why should they highlight their own misconduct if they are likely never to be found out otherwise, unless there's an ethical issue (privacy etc) at stake?
– user234461
Jul 19 at 8:57
24
24
@user234461 if it was "trivial document" which required several meetings of a team of employees to prepare it, the company is probably too dysfunctional to survive anyway! More likely, this guy wants some hard evidence of his old company's strategy, to support his proposals to give his new employer a competitive advantage.
– alephzero
Jul 19 at 9:25
@user234461 if it was "trivial document" which required several meetings of a team of employees to prepare it, the company is probably too dysfunctional to survive anyway! More likely, this guy wants some hard evidence of his old company's strategy, to support his proposals to give his new employer a competitive advantage.
– alephzero
Jul 19 at 9:25
5
5
@user234461 If it was emailed from company email, there is evidence of it having been shared.
– Delioth
Jul 19 at 15:06
@user234461 If it was emailed from company email, there is evidence of it having been shared.
– Delioth
Jul 19 at 15:06
12
12
@user234461 "there's no evidence..." It is unethical to base a decision on the likelihood of getting caught. There is evidence since it was sent via email. Not bringing this to the manager will make it look intentional. Admitting it also allows the company to do damage control. Imageine the company later files for a patent and finds that the document was released publicly, and an employee hid that information. That could cost the company millions of dollars and the employee their job. By letting them know now they can put the proper NDAs in place and document that the release is not material.
– Moby Disk
Jul 19 at 20:05
@user234461 "there's no evidence..." It is unethical to base a decision on the likelihood of getting caught. There is evidence since it was sent via email. Not bringing this to the manager will make it look intentional. Admitting it also allows the company to do damage control. Imageine the company later files for a patent and finds that the document was released publicly, and an employee hid that information. That could cost the company millions of dollars and the employee their job. By letting them know now they can put the proper NDAs in place and document that the release is not material.
– Moby Disk
Jul 19 at 20:05
2
2
The manager may limit OP's access to company documents until they prove that they have learned their lesson, but firing is definitely overreacting. Firing them if they found out after the OP didn't tell them would be appropriate on the other hand 'cuz it would show that the OP can't be trusted with company information thus cannot do any work for them.
– ivan_pozdeev
Jul 20 at 13:36
The manager may limit OP's access to company documents until they prove that they have learned their lesson, but firing is definitely overreacting. Firing them if they found out after the OP didn't tell them would be appropriate on the other hand 'cuz it would show that the OP can't be trusted with company information thus cannot do any work for them.
– ivan_pozdeev
Jul 20 at 13:36
|
show 3 more comments
No, don't share internal company information with non-members of the firm except in the course of normal business.
Previous employees do not have a legitimate interest in non-public company information (unless they are doing business with the firm). It doesn't matter how sensitive the information seems or if it is marked confidential - unless you have permission to share the information, keep it private.
You should alert your manager or a trusted leader in the company. Previous employees asking for information may signal a larger issue. At the very least, make an individual in a management position aware of the data leak.
2
"or a trusted leader in the company" – The OP doesn't say which jurisdiction he is in, unfortunately. If he is within the jurisdiction of the GDPR or something similar, there should be a designated Data Protection Officer, who is protected by law from divulging his sources. While this might not technically a data breach as defined by the GDPR, the DPO should at least be able to advise the OP. If the OP is in Germany or a country with similar laws, and the company is larger than 5 employees, then there might be a Worker's Council, which has certain protections.
– Jörg W Mittag
Jul 20 at 9:20
1
If the OP is a member of a Union, he should have the possibility to talk to an Ombudsperson or similar. All three of these options allow the OP to talk to someone who can both advise the OP on how to best handle the situation, and who is able to forward the information to the appropriate person in the company without having to divulge the name of the employee.
– Jörg W Mittag
Jul 20 at 9:21
add a comment |
No, don't share internal company information with non-members of the firm except in the course of normal business.
Previous employees do not have a legitimate interest in non-public company information (unless they are doing business with the firm). It doesn't matter how sensitive the information seems or if it is marked confidential - unless you have permission to share the information, keep it private.
You should alert your manager or a trusted leader in the company. Previous employees asking for information may signal a larger issue. At the very least, make an individual in a management position aware of the data leak.
2
"or a trusted leader in the company" – The OP doesn't say which jurisdiction he is in, unfortunately. If he is within the jurisdiction of the GDPR or something similar, there should be a designated Data Protection Officer, who is protected by law from divulging his sources. While this might not technically a data breach as defined by the GDPR, the DPO should at least be able to advise the OP. If the OP is in Germany or a country with similar laws, and the company is larger than 5 employees, then there might be a Worker's Council, which has certain protections.
– Jörg W Mittag
Jul 20 at 9:20
1
If the OP is a member of a Union, he should have the possibility to talk to an Ombudsperson or similar. All three of these options allow the OP to talk to someone who can both advise the OP on how to best handle the situation, and who is able to forward the information to the appropriate person in the company without having to divulge the name of the employee.
– Jörg W Mittag
Jul 20 at 9:21
add a comment |
No, don't share internal company information with non-members of the firm except in the course of normal business.
Previous employees do not have a legitimate interest in non-public company information (unless they are doing business with the firm). It doesn't matter how sensitive the information seems or if it is marked confidential - unless you have permission to share the information, keep it private.
You should alert your manager or a trusted leader in the company. Previous employees asking for information may signal a larger issue. At the very least, make an individual in a management position aware of the data leak.
No, don't share internal company information with non-members of the firm except in the course of normal business.
Previous employees do not have a legitimate interest in non-public company information (unless they are doing business with the firm). It doesn't matter how sensitive the information seems or if it is marked confidential - unless you have permission to share the information, keep it private.
You should alert your manager or a trusted leader in the company. Previous employees asking for information may signal a larger issue. At the very least, make an individual in a management position aware of the data leak.
answered Jul 18 at 14:16
JayJay
7,2042 gold badges20 silver badges47 bronze badges
7,2042 gold badges20 silver badges47 bronze badges
2
"or a trusted leader in the company" – The OP doesn't say which jurisdiction he is in, unfortunately. If he is within the jurisdiction of the GDPR or something similar, there should be a designated Data Protection Officer, who is protected by law from divulging his sources. While this might not technically a data breach as defined by the GDPR, the DPO should at least be able to advise the OP. If the OP is in Germany or a country with similar laws, and the company is larger than 5 employees, then there might be a Worker's Council, which has certain protections.
– Jörg W Mittag
Jul 20 at 9:20
1
If the OP is a member of a Union, he should have the possibility to talk to an Ombudsperson or similar. All three of these options allow the OP to talk to someone who can both advise the OP on how to best handle the situation, and who is able to forward the information to the appropriate person in the company without having to divulge the name of the employee.
– Jörg W Mittag
Jul 20 at 9:21
add a comment |
2
"or a trusted leader in the company" – The OP doesn't say which jurisdiction he is in, unfortunately. If he is within the jurisdiction of the GDPR or something similar, there should be a designated Data Protection Officer, who is protected by law from divulging his sources. While this might not technically a data breach as defined by the GDPR, the DPO should at least be able to advise the OP. If the OP is in Germany or a country with similar laws, and the company is larger than 5 employees, then there might be a Worker's Council, which has certain protections.
– Jörg W Mittag
Jul 20 at 9:20
1
If the OP is a member of a Union, he should have the possibility to talk to an Ombudsperson or similar. All three of these options allow the OP to talk to someone who can both advise the OP on how to best handle the situation, and who is able to forward the information to the appropriate person in the company without having to divulge the name of the employee.
– Jörg W Mittag
Jul 20 at 9:21
2
2
"or a trusted leader in the company" – The OP doesn't say which jurisdiction he is in, unfortunately. If he is within the jurisdiction of the GDPR or something similar, there should be a designated Data Protection Officer, who is protected by law from divulging his sources. While this might not technically a data breach as defined by the GDPR, the DPO should at least be able to advise the OP. If the OP is in Germany or a country with similar laws, and the company is larger than 5 employees, then there might be a Worker's Council, which has certain protections.
– Jörg W Mittag
Jul 20 at 9:20
"or a trusted leader in the company" – The OP doesn't say which jurisdiction he is in, unfortunately. If he is within the jurisdiction of the GDPR or something similar, there should be a designated Data Protection Officer, who is protected by law from divulging his sources. While this might not technically a data breach as defined by the GDPR, the DPO should at least be able to advise the OP. If the OP is in Germany or a country with similar laws, and the company is larger than 5 employees, then there might be a Worker's Council, which has certain protections.
– Jörg W Mittag
Jul 20 at 9:20
1
1
If the OP is a member of a Union, he should have the possibility to talk to an Ombudsperson or similar. All three of these options allow the OP to talk to someone who can both advise the OP on how to best handle the situation, and who is able to forward the information to the appropriate person in the company without having to divulge the name of the employee.
– Jörg W Mittag
Jul 20 at 9:21
If the OP is a member of a Union, he should have the possibility to talk to an Ombudsperson or similar. All three of these options allow the OP to talk to someone who can both advise the OP on how to best handle the situation, and who is able to forward the information to the appropriate person in the company without having to divulge the name of the employee.
– Jörg W Mittag
Jul 20 at 9:21
add a comment |
No. It was a mistake. The deputy manager no longer works there, so he doesn't get to ask for any company documents. There is no reason to do this I can think of other than to somehow compete with your business.
The correct action would have been to forward his request to your current manager, and forget about it.
Now, mistakes happen, and the fact you're asking about this is good - it means your "did I do something wrong here" radar is still working. Ethics-wise, you should tell your manager what happened immediately and apologise. But you have to balance the risk of getting fired versus protecting the business, which is a decision only you can make.
edit Incorporating some comments:
As someone who works in cybersecurity, one of the things we push for is people to have greater awareness of their actions and of those around them, including self-reporting incidents. If the security team / company is any good, they'll give a minor slap on the wrist saying "don't do that again," and deal with it appropriately. The company finding out after the fact, however, could and should lead to firings.
Tyzoid
I'd say, in tune with workplace.stackexchange.com/questions/140637/… that if sharing important information like this is discouraged in the company on pain of firing, the company is too dysfunctional to survive anyway. People do make mistakes, you can't help it, only learn from mistakes and control damage. If their manager tries to overreact, the OP can tell them just that: "Would you prefer if I kept this secret? Is this the signal you want to send to any other who makes a mistake -- maybe already made?"
– ivan_pozdeev
Jul 20 at 13:26
1
As someone who works in cybersecurity, one of the things we push for is people to have greater awareness of their actions and of those around them, including self-reporting incidents. If the security team / company is any good, they'll give a minor slap on the wrist saying "don't do that again," and deal with it appropriately. The company finding out after the fact, however, could and should lead to firings.
– Tyzoid
Jul 20 at 14:49
add a comment |
No. It was a mistake. The deputy manager no longer works there, so he doesn't get to ask for any company documents. There is no reason to do this I can think of other than to somehow compete with your business.
The correct action would have been to forward his request to your current manager, and forget about it.
Now, mistakes happen, and the fact you're asking about this is good - it means your "did I do something wrong here" radar is still working. Ethics-wise, you should tell your manager what happened immediately and apologise. But you have to balance the risk of getting fired versus protecting the business, which is a decision only you can make.
edit Incorporating some comments:
As someone who works in cybersecurity, one of the things we push for is people to have greater awareness of their actions and of those around them, including self-reporting incidents. If the security team / company is any good, they'll give a minor slap on the wrist saying "don't do that again," and deal with it appropriately. The company finding out after the fact, however, could and should lead to firings.
Tyzoid
I'd say, in tune with workplace.stackexchange.com/questions/140637/… that if sharing important information like this is discouraged in the company on pain of firing, the company is too dysfunctional to survive anyway. People do make mistakes, you can't help it, only learn from mistakes and control damage. If their manager tries to overreact, the OP can tell them just that: "Would you prefer if I kept this secret? Is this the signal you want to send to any other who makes a mistake -- maybe already made?"
– ivan_pozdeev
Jul 20 at 13:26
1
As someone who works in cybersecurity, one of the things we push for is people to have greater awareness of their actions and of those around them, including self-reporting incidents. If the security team / company is any good, they'll give a minor slap on the wrist saying "don't do that again," and deal with it appropriately. The company finding out after the fact, however, could and should lead to firings.
– Tyzoid
Jul 20 at 14:49
add a comment |
No. It was a mistake. The deputy manager no longer works there, so he doesn't get to ask for any company documents. There is no reason to do this I can think of other than to somehow compete with your business.
The correct action would have been to forward his request to your current manager, and forget about it.
Now, mistakes happen, and the fact you're asking about this is good - it means your "did I do something wrong here" radar is still working. Ethics-wise, you should tell your manager what happened immediately and apologise. But you have to balance the risk of getting fired versus protecting the business, which is a decision only you can make.
edit Incorporating some comments:
As someone who works in cybersecurity, one of the things we push for is people to have greater awareness of their actions and of those around them, including self-reporting incidents. If the security team / company is any good, they'll give a minor slap on the wrist saying "don't do that again," and deal with it appropriately. The company finding out after the fact, however, could and should lead to firings.
Tyzoid
No. It was a mistake. The deputy manager no longer works there, so he doesn't get to ask for any company documents. There is no reason to do this I can think of other than to somehow compete with your business.
The correct action would have been to forward his request to your current manager, and forget about it.
Now, mistakes happen, and the fact you're asking about this is good - it means your "did I do something wrong here" radar is still working. Ethics-wise, you should tell your manager what happened immediately and apologise. But you have to balance the risk of getting fired versus protecting the business, which is a decision only you can make.
edit Incorporating some comments:
As someone who works in cybersecurity, one of the things we push for is people to have greater awareness of their actions and of those around them, including self-reporting incidents. If the security team / company is any good, they'll give a minor slap on the wrist saying "don't do that again," and deal with it appropriately. The company finding out after the fact, however, could and should lead to firings.
Tyzoid
edited Jul 21 at 14:01
answered Jul 18 at 14:12
rathrath
23.1k15 gold badges68 silver badges110 bronze badges
23.1k15 gold badges68 silver badges110 bronze badges
I'd say, in tune with workplace.stackexchange.com/questions/140637/… that if sharing important information like this is discouraged in the company on pain of firing, the company is too dysfunctional to survive anyway. People do make mistakes, you can't help it, only learn from mistakes and control damage. If their manager tries to overreact, the OP can tell them just that: "Would you prefer if I kept this secret? Is this the signal you want to send to any other who makes a mistake -- maybe already made?"
– ivan_pozdeev
Jul 20 at 13:26
1
As someone who works in cybersecurity, one of the things we push for is people to have greater awareness of their actions and of those around them, including self-reporting incidents. If the security team / company is any good, they'll give a minor slap on the wrist saying "don't do that again," and deal with it appropriately. The company finding out after the fact, however, could and should lead to firings.
– Tyzoid
Jul 20 at 14:49
add a comment |
I'd say, in tune with workplace.stackexchange.com/questions/140637/… that if sharing important information like this is discouraged in the company on pain of firing, the company is too dysfunctional to survive anyway. People do make mistakes, you can't help it, only learn from mistakes and control damage. If their manager tries to overreact, the OP can tell them just that: "Would you prefer if I kept this secret? Is this the signal you want to send to any other who makes a mistake -- maybe already made?"
– ivan_pozdeev
Jul 20 at 13:26
1
As someone who works in cybersecurity, one of the things we push for is people to have greater awareness of their actions and of those around them, including self-reporting incidents. If the security team / company is any good, they'll give a minor slap on the wrist saying "don't do that again," and deal with it appropriately. The company finding out after the fact, however, could and should lead to firings.
– Tyzoid
Jul 20 at 14:49
I'd say, in tune with workplace.stackexchange.com/questions/140637/… that if sharing important information like this is discouraged in the company on pain of firing, the company is too dysfunctional to survive anyway. People do make mistakes, you can't help it, only learn from mistakes and control damage. If their manager tries to overreact, the OP can tell them just that: "Would you prefer if I kept this secret? Is this the signal you want to send to any other who makes a mistake -- maybe already made?"
– ivan_pozdeev
Jul 20 at 13:26
I'd say, in tune with workplace.stackexchange.com/questions/140637/… that if sharing important information like this is discouraged in the company on pain of firing, the company is too dysfunctional to survive anyway. People do make mistakes, you can't help it, only learn from mistakes and control damage. If their manager tries to overreact, the OP can tell them just that: "Would you prefer if I kept this secret? Is this the signal you want to send to any other who makes a mistake -- maybe already made?"
– ivan_pozdeev
Jul 20 at 13:26
1
1
As someone who works in cybersecurity, one of the things we push for is people to have greater awareness of their actions and of those around them, including self-reporting incidents. If the security team / company is any good, they'll give a minor slap on the wrist saying "don't do that again," and deal with it appropriately. The company finding out after the fact, however, could and should lead to firings.
– Tyzoid
Jul 20 at 14:49
As someone who works in cybersecurity, one of the things we push for is people to have greater awareness of their actions and of those around them, including self-reporting incidents. If the security team / company is any good, they'll give a minor slap on the wrist saying "don't do that again," and deal with it appropriately. The company finding out after the fact, however, could and should lead to firings.
– Tyzoid
Jul 20 at 14:49
add a comment |
Obviously you did the wrong thing, and the only question is whether you should own up to your mistake, or lie low and hope nothing bad happens.
The other answers tend to lean towards owning up, but I have to wonder: what planet are they on? On planet Earth, the obvious and only course of action is to say nothing. If you are found out, you can always plead ignorance; and if you are not found out, well then owning up would have been stupid, wouldn't it?
PS If you think this a question of ethics, ask yourself this: who stands to benefit if you own up? Nobody. Who stands to lose out if you own up? You. It's a no-brainer, if you ask me.
15
Willingly hiding a mistake to avoid potential punishment is likely to just result in harsher punishment down the line when it comes up. Much less stupid to admit your mistake and work to fix it.
– JS Lavertu
Jul 19 at 0:38
7
@JSLavertu: I assume that the likelihood of discovery is very low here. And that if by any chance the OP is found out, they can plausibly claim that they didn't realise they were doing anything wrong. So: do you own up, giving yourself a 100% chance of looking stupid? Or keep quiet, giving yourself perhaps a 2% chance?
– TonyK
Jul 19 at 0:53
5
@GeorgeM "assume your ex-coworker just wanted a concrete sample of his work for his portfolio" Kinda translates to: I shared this information with our ex-coworker so he could share it with others.
– Gregory Currie
Jul 19 at 1:17
6
Well, a portfolio is meant to be shown.
– Gregory Currie
Jul 19 at 2:56
6
Making a mistake is bad but forgivable. Intentionally trying to cover it up isn't a mistake, it's a considered action.
– Basic
Jul 19 at 10:24
|
show 8 more comments
Obviously you did the wrong thing, and the only question is whether you should own up to your mistake, or lie low and hope nothing bad happens.
The other answers tend to lean towards owning up, but I have to wonder: what planet are they on? On planet Earth, the obvious and only course of action is to say nothing. If you are found out, you can always plead ignorance; and if you are not found out, well then owning up would have been stupid, wouldn't it?
PS If you think this a question of ethics, ask yourself this: who stands to benefit if you own up? Nobody. Who stands to lose out if you own up? You. It's a no-brainer, if you ask me.
15
Willingly hiding a mistake to avoid potential punishment is likely to just result in harsher punishment down the line when it comes up. Much less stupid to admit your mistake and work to fix it.
– JS Lavertu
Jul 19 at 0:38
7
@JSLavertu: I assume that the likelihood of discovery is very low here. And that if by any chance the OP is found out, they can plausibly claim that they didn't realise they were doing anything wrong. So: do you own up, giving yourself a 100% chance of looking stupid? Or keep quiet, giving yourself perhaps a 2% chance?
– TonyK
Jul 19 at 0:53
5
@GeorgeM "assume your ex-coworker just wanted a concrete sample of his work for his portfolio" Kinda translates to: I shared this information with our ex-coworker so he could share it with others.
– Gregory Currie
Jul 19 at 1:17
6
Well, a portfolio is meant to be shown.
– Gregory Currie
Jul 19 at 2:56
6
Making a mistake is bad but forgivable. Intentionally trying to cover it up isn't a mistake, it's a considered action.
– Basic
Jul 19 at 10:24
|
show 8 more comments
Obviously you did the wrong thing, and the only question is whether you should own up to your mistake, or lie low and hope nothing bad happens.
The other answers tend to lean towards owning up, but I have to wonder: what planet are they on? On planet Earth, the obvious and only course of action is to say nothing. If you are found out, you can always plead ignorance; and if you are not found out, well then owning up would have been stupid, wouldn't it?
PS If you think this a question of ethics, ask yourself this: who stands to benefit if you own up? Nobody. Who stands to lose out if you own up? You. It's a no-brainer, if you ask me.
Obviously you did the wrong thing, and the only question is whether you should own up to your mistake, or lie low and hope nothing bad happens.
The other answers tend to lean towards owning up, but I have to wonder: what planet are they on? On planet Earth, the obvious and only course of action is to say nothing. If you are found out, you can always plead ignorance; and if you are not found out, well then owning up would have been stupid, wouldn't it?
PS If you think this a question of ethics, ask yourself this: who stands to benefit if you own up? Nobody. Who stands to lose out if you own up? You. It's a no-brainer, if you ask me.
answered Jul 19 at 0:30
TonyKTonyK
4273 silver badges6 bronze badges
4273 silver badges6 bronze badges
15
Willingly hiding a mistake to avoid potential punishment is likely to just result in harsher punishment down the line when it comes up. Much less stupid to admit your mistake and work to fix it.
– JS Lavertu
Jul 19 at 0:38
7
@JSLavertu: I assume that the likelihood of discovery is very low here. And that if by any chance the OP is found out, they can plausibly claim that they didn't realise they were doing anything wrong. So: do you own up, giving yourself a 100% chance of looking stupid? Or keep quiet, giving yourself perhaps a 2% chance?
– TonyK
Jul 19 at 0:53
5
@GeorgeM "assume your ex-coworker just wanted a concrete sample of his work for his portfolio" Kinda translates to: I shared this information with our ex-coworker so he could share it with others.
– Gregory Currie
Jul 19 at 1:17
6
Well, a portfolio is meant to be shown.
– Gregory Currie
Jul 19 at 2:56
6
Making a mistake is bad but forgivable. Intentionally trying to cover it up isn't a mistake, it's a considered action.
– Basic
Jul 19 at 10:24
|
show 8 more comments
15
Willingly hiding a mistake to avoid potential punishment is likely to just result in harsher punishment down the line when it comes up. Much less stupid to admit your mistake and work to fix it.
– JS Lavertu
Jul 19 at 0:38
7
@JSLavertu: I assume that the likelihood of discovery is very low here. And that if by any chance the OP is found out, they can plausibly claim that they didn't realise they were doing anything wrong. So: do you own up, giving yourself a 100% chance of looking stupid? Or keep quiet, giving yourself perhaps a 2% chance?
– TonyK
Jul 19 at 0:53
5
@GeorgeM "assume your ex-coworker just wanted a concrete sample of his work for his portfolio" Kinda translates to: I shared this information with our ex-coworker so he could share it with others.
– Gregory Currie
Jul 19 at 1:17
6
Well, a portfolio is meant to be shown.
– Gregory Currie
Jul 19 at 2:56
6
Making a mistake is bad but forgivable. Intentionally trying to cover it up isn't a mistake, it's a considered action.
– Basic
Jul 19 at 10:24
15
15
Willingly hiding a mistake to avoid potential punishment is likely to just result in harsher punishment down the line when it comes up. Much less stupid to admit your mistake and work to fix it.
– JS Lavertu
Jul 19 at 0:38
Willingly hiding a mistake to avoid potential punishment is likely to just result in harsher punishment down the line when it comes up. Much less stupid to admit your mistake and work to fix it.
– JS Lavertu
Jul 19 at 0:38
7
7
@JSLavertu: I assume that the likelihood of discovery is very low here. And that if by any chance the OP is found out, they can plausibly claim that they didn't realise they were doing anything wrong. So: do you own up, giving yourself a 100% chance of looking stupid? Or keep quiet, giving yourself perhaps a 2% chance?
– TonyK
Jul 19 at 0:53
@JSLavertu: I assume that the likelihood of discovery is very low here. And that if by any chance the OP is found out, they can plausibly claim that they didn't realise they were doing anything wrong. So: do you own up, giving yourself a 100% chance of looking stupid? Or keep quiet, giving yourself perhaps a 2% chance?
– TonyK
Jul 19 at 0:53
5
5
@GeorgeM "assume your ex-coworker just wanted a concrete sample of his work for his portfolio" Kinda translates to: I shared this information with our ex-coworker so he could share it with others.
– Gregory Currie
Jul 19 at 1:17
@GeorgeM "assume your ex-coworker just wanted a concrete sample of his work for his portfolio" Kinda translates to: I shared this information with our ex-coworker so he could share it with others.
– Gregory Currie
Jul 19 at 1:17
6
6
Well, a portfolio is meant to be shown.
– Gregory Currie
Jul 19 at 2:56
Well, a portfolio is meant to be shown.
– Gregory Currie
Jul 19 at 2:56
6
6
Making a mistake is bad but forgivable. Intentionally trying to cover it up isn't a mistake, it's a considered action.
– Basic
Jul 19 at 10:24
Making a mistake is bad but forgivable. Intentionally trying to cover it up isn't a mistake, it's a considered action.
– Basic
Jul 19 at 10:24
|
show 8 more comments
Any company I've worked in, your action would be reason to terminate your employment and take legal action against you for breach of confidentiality agreements, non-disclosure agreements, and document security regulations.
NEVER share information with people outside the company unless you are authorised to do so, and then only with people who are authorised to receive said information.
For example sending an updated installation manual to a customer for the product you're building for him is usually (but not always, there may be rules about who's allowed to communicate at all with customers) ok, sending a design document for something to a random person outside the company, often even the customer for who you are designing that thing, hardly ever is.
add a comment |
Any company I've worked in, your action would be reason to terminate your employment and take legal action against you for breach of confidentiality agreements, non-disclosure agreements, and document security regulations.
NEVER share information with people outside the company unless you are authorised to do so, and then only with people who are authorised to receive said information.
For example sending an updated installation manual to a customer for the product you're building for him is usually (but not always, there may be rules about who's allowed to communicate at all with customers) ok, sending a design document for something to a random person outside the company, often even the customer for who you are designing that thing, hardly ever is.
add a comment |
Any company I've worked in, your action would be reason to terminate your employment and take legal action against you for breach of confidentiality agreements, non-disclosure agreements, and document security regulations.
NEVER share information with people outside the company unless you are authorised to do so, and then only with people who are authorised to receive said information.
For example sending an updated installation manual to a customer for the product you're building for him is usually (but not always, there may be rules about who's allowed to communicate at all with customers) ok, sending a design document for something to a random person outside the company, often even the customer for who you are designing that thing, hardly ever is.
Any company I've worked in, your action would be reason to terminate your employment and take legal action against you for breach of confidentiality agreements, non-disclosure agreements, and document security regulations.
NEVER share information with people outside the company unless you are authorised to do so, and then only with people who are authorised to receive said information.
For example sending an updated installation manual to a customer for the product you're building for him is usually (but not always, there may be rules about who's allowed to communicate at all with customers) ok, sending a design document for something to a random person outside the company, often even the customer for who you are designing that thing, hardly ever is.
answered Jul 19 at 8:11
jwentingjwenting
2,0598 silver badges10 bronze badges
2,0598 silver badges10 bronze badges
add a comment |
add a comment |
Without going into your actions, its obvious you know you have messed up.
So, I would simply weigh up your options.
And you have 2 really:
- Own up, with a risk of getting sacked.
- Keep quiet with a risk of getting found out, and sacked
Personally I think there is more at risk with option 1.
I have in the past kept several spreadsheets I worked on from previous workplaces, just so I can re-use functionality in the future.
Whatever you choose to do cease contact with your former manager.
2
There's a small difference between keeping those documents for yourself and knowingly sending company confidential information to a competitor.
– onnoweb
Jul 19 at 19:04
@onnoweb completely agree, but the information on the document is already known to the former manager, the OP does not say its confidential, and there is no mention of the former manager working for a competitor.
– PeterH
Jul 20 at 7:31
add a comment |
Without going into your actions, its obvious you know you have messed up.
So, I would simply weigh up your options.
And you have 2 really:
- Own up, with a risk of getting sacked.
- Keep quiet with a risk of getting found out, and sacked
Personally I think there is more at risk with option 1.
I have in the past kept several spreadsheets I worked on from previous workplaces, just so I can re-use functionality in the future.
Whatever you choose to do cease contact with your former manager.
2
There's a small difference between keeping those documents for yourself and knowingly sending company confidential information to a competitor.
– onnoweb
Jul 19 at 19:04
@onnoweb completely agree, but the information on the document is already known to the former manager, the OP does not say its confidential, and there is no mention of the former manager working for a competitor.
– PeterH
Jul 20 at 7:31
add a comment |
Without going into your actions, its obvious you know you have messed up.
So, I would simply weigh up your options.
And you have 2 really:
- Own up, with a risk of getting sacked.
- Keep quiet with a risk of getting found out, and sacked
Personally I think there is more at risk with option 1.
I have in the past kept several spreadsheets I worked on from previous workplaces, just so I can re-use functionality in the future.
Whatever you choose to do cease contact with your former manager.
Without going into your actions, its obvious you know you have messed up.
So, I would simply weigh up your options.
And you have 2 really:
- Own up, with a risk of getting sacked.
- Keep quiet with a risk of getting found out, and sacked
Personally I think there is more at risk with option 1.
I have in the past kept several spreadsheets I worked on from previous workplaces, just so I can re-use functionality in the future.
Whatever you choose to do cease contact with your former manager.
answered Jul 19 at 18:48
PeterHPeterH
2771 silver badge6 bronze badges
2771 silver badge6 bronze badges
2
There's a small difference between keeping those documents for yourself and knowingly sending company confidential information to a competitor.
– onnoweb
Jul 19 at 19:04
@onnoweb completely agree, but the information on the document is already known to the former manager, the OP does not say its confidential, and there is no mention of the former manager working for a competitor.
– PeterH
Jul 20 at 7:31
add a comment |
2
There's a small difference between keeping those documents for yourself and knowingly sending company confidential information to a competitor.
– onnoweb
Jul 19 at 19:04
@onnoweb completely agree, but the information on the document is already known to the former manager, the OP does not say its confidential, and there is no mention of the former manager working for a competitor.
– PeterH
Jul 20 at 7:31
2
2
There's a small difference between keeping those documents for yourself and knowingly sending company confidential information to a competitor.
– onnoweb
Jul 19 at 19:04
There's a small difference between keeping those documents for yourself and knowingly sending company confidential information to a competitor.
– onnoweb
Jul 19 at 19:04
@onnoweb completely agree, but the information on the document is already known to the former manager, the OP does not say its confidential, and there is no mention of the former manager working for a competitor.
– PeterH
Jul 20 at 7:31
@onnoweb completely agree, but the information on the document is already known to the former manager, the OP does not say its confidential, and there is no mention of the former manager working for a competitor.
– PeterH
Jul 20 at 7:31
add a comment |
It sounds like you don't know why they wanted it. Some of the other answers assume their motivation was shady, which may be an appropriate assumption, or it may not be. If they were really trying to do something shady, would they have asked you at all?
You should probably ask them why they wanted it, and ask them to keep the document confidential. Best to have such conversation by phone or in person. Their reaction will hopefully give you a better idea of what's at stake in the situation, if anything.
1
Communicated motivations don't matter. After all, if there is an actual legitimate reason, the co-worker could just lie and say that, instead of the real illegitimate reason.
– Gregory Currie
Jul 19 at 3:26
4
"If they were really trying to do something shady, would they have asked you at all?" It seems reasonable that they might. Clearly requesting the document from OP was successful. I don't see how you could rule out that it was shady. To me it seems like they expected OP to spill the beans when asked; they might have taken advantage of that for shady reasons.
– JMac
Jul 19 at 13:06
@JMac I agree. I didn't mean to imply that any possibility can be ruled out. It may be shady and serious. Or it may be benign (though still a breach of protocol). Or it may be shady and they may lie and try to sound benign. OP should consider this from all angles.
– krubo
Jul 19 at 17:29
add a comment |
It sounds like you don't know why they wanted it. Some of the other answers assume their motivation was shady, which may be an appropriate assumption, or it may not be. If they were really trying to do something shady, would they have asked you at all?
You should probably ask them why they wanted it, and ask them to keep the document confidential. Best to have such conversation by phone or in person. Their reaction will hopefully give you a better idea of what's at stake in the situation, if anything.
1
Communicated motivations don't matter. After all, if there is an actual legitimate reason, the co-worker could just lie and say that, instead of the real illegitimate reason.
– Gregory Currie
Jul 19 at 3:26
4
"If they were really trying to do something shady, would they have asked you at all?" It seems reasonable that they might. Clearly requesting the document from OP was successful. I don't see how you could rule out that it was shady. To me it seems like they expected OP to spill the beans when asked; they might have taken advantage of that for shady reasons.
– JMac
Jul 19 at 13:06
@JMac I agree. I didn't mean to imply that any possibility can be ruled out. It may be shady and serious. Or it may be benign (though still a breach of protocol). Or it may be shady and they may lie and try to sound benign. OP should consider this from all angles.
– krubo
Jul 19 at 17:29
add a comment |
It sounds like you don't know why they wanted it. Some of the other answers assume their motivation was shady, which may be an appropriate assumption, or it may not be. If they were really trying to do something shady, would they have asked you at all?
You should probably ask them why they wanted it, and ask them to keep the document confidential. Best to have such conversation by phone or in person. Their reaction will hopefully give you a better idea of what's at stake in the situation, if anything.
It sounds like you don't know why they wanted it. Some of the other answers assume their motivation was shady, which may be an appropriate assumption, or it may not be. If they were really trying to do something shady, would they have asked you at all?
You should probably ask them why they wanted it, and ask them to keep the document confidential. Best to have such conversation by phone or in person. Their reaction will hopefully give you a better idea of what's at stake in the situation, if anything.
answered Jul 19 at 2:51
krubokrubo
2521 silver badge5 bronze badges
2521 silver badge5 bronze badges
1
Communicated motivations don't matter. After all, if there is an actual legitimate reason, the co-worker could just lie and say that, instead of the real illegitimate reason.
– Gregory Currie
Jul 19 at 3:26
4
"If they were really trying to do something shady, would they have asked you at all?" It seems reasonable that they might. Clearly requesting the document from OP was successful. I don't see how you could rule out that it was shady. To me it seems like they expected OP to spill the beans when asked; they might have taken advantage of that for shady reasons.
– JMac
Jul 19 at 13:06
@JMac I agree. I didn't mean to imply that any possibility can be ruled out. It may be shady and serious. Or it may be benign (though still a breach of protocol). Or it may be shady and they may lie and try to sound benign. OP should consider this from all angles.
– krubo
Jul 19 at 17:29
add a comment |
1
Communicated motivations don't matter. After all, if there is an actual legitimate reason, the co-worker could just lie and say that, instead of the real illegitimate reason.
– Gregory Currie
Jul 19 at 3:26
4
"If they were really trying to do something shady, would they have asked you at all?" It seems reasonable that they might. Clearly requesting the document from OP was successful. I don't see how you could rule out that it was shady. To me it seems like they expected OP to spill the beans when asked; they might have taken advantage of that for shady reasons.
– JMac
Jul 19 at 13:06
@JMac I agree. I didn't mean to imply that any possibility can be ruled out. It may be shady and serious. Or it may be benign (though still a breach of protocol). Or it may be shady and they may lie and try to sound benign. OP should consider this from all angles.
– krubo
Jul 19 at 17:29
1
1
Communicated motivations don't matter. After all, if there is an actual legitimate reason, the co-worker could just lie and say that, instead of the real illegitimate reason.
– Gregory Currie
Jul 19 at 3:26
Communicated motivations don't matter. After all, if there is an actual legitimate reason, the co-worker could just lie and say that, instead of the real illegitimate reason.
– Gregory Currie
Jul 19 at 3:26
4
4
"If they were really trying to do something shady, would they have asked you at all?" It seems reasonable that they might. Clearly requesting the document from OP was successful. I don't see how you could rule out that it was shady. To me it seems like they expected OP to spill the beans when asked; they might have taken advantage of that for shady reasons.
– JMac
Jul 19 at 13:06
"If they were really trying to do something shady, would they have asked you at all?" It seems reasonable that they might. Clearly requesting the document from OP was successful. I don't see how you could rule out that it was shady. To me it seems like they expected OP to spill the beans when asked; they might have taken advantage of that for shady reasons.
– JMac
Jul 19 at 13:06
@JMac I agree. I didn't mean to imply that any possibility can be ruled out. It may be shady and serious. Or it may be benign (though still a breach of protocol). Or it may be shady and they may lie and try to sound benign. OP should consider this from all angles.
– krubo
Jul 19 at 17:29
@JMac I agree. I didn't mean to imply that any possibility can be ruled out. It may be shady and serious. Or it may be benign (though still a breach of protocol). Or it may be shady and they may lie and try to sound benign. OP should consider this from all angles.
– krubo
Jul 19 at 17:29
add a comment |
To answer the question as asked: you should not have forwarded any company document to a former employer, without approval.
Since you have done it, you now need to mitigate the effects: report the error in an appropriate manner.
There are few circumstances in which an employee will be sacked if they admit to a mistake. In fact, even if the consequences are severe, most employers/managers want staff to feel safe about reporting honest mistakes that affect them. A prompt report allows them to mitigate effects - in your case, determine why a former employee requested the document. So you may get a talking-to, or even face some disciplinary action for a data breach (depending on how sensitive the document is, how well employees in your company are briefed about security concerns before starting a project, etc), but that is unlikely to be escalated to dismissal unless you build up a history of making the same sort of mistake repeatedly - you are expected to learn from mistakes, not keep repeating the same ones.
The consequences will certainly be more severe - and more likely to include dismissal - if you don't admit to the problem, and your employer discovers it by other means - for example, during a data or security audit or if a manager is given a copy of the document by a competitor.
add a comment |
To answer the question as asked: you should not have forwarded any company document to a former employer, without approval.
Since you have done it, you now need to mitigate the effects: report the error in an appropriate manner.
There are few circumstances in which an employee will be sacked if they admit to a mistake. In fact, even if the consequences are severe, most employers/managers want staff to feel safe about reporting honest mistakes that affect them. A prompt report allows them to mitigate effects - in your case, determine why a former employee requested the document. So you may get a talking-to, or even face some disciplinary action for a data breach (depending on how sensitive the document is, how well employees in your company are briefed about security concerns before starting a project, etc), but that is unlikely to be escalated to dismissal unless you build up a history of making the same sort of mistake repeatedly - you are expected to learn from mistakes, not keep repeating the same ones.
The consequences will certainly be more severe - and more likely to include dismissal - if you don't admit to the problem, and your employer discovers it by other means - for example, during a data or security audit or if a manager is given a copy of the document by a competitor.
add a comment |
To answer the question as asked: you should not have forwarded any company document to a former employer, without approval.
Since you have done it, you now need to mitigate the effects: report the error in an appropriate manner.
There are few circumstances in which an employee will be sacked if they admit to a mistake. In fact, even if the consequences are severe, most employers/managers want staff to feel safe about reporting honest mistakes that affect them. A prompt report allows them to mitigate effects - in your case, determine why a former employee requested the document. So you may get a talking-to, or even face some disciplinary action for a data breach (depending on how sensitive the document is, how well employees in your company are briefed about security concerns before starting a project, etc), but that is unlikely to be escalated to dismissal unless you build up a history of making the same sort of mistake repeatedly - you are expected to learn from mistakes, not keep repeating the same ones.
The consequences will certainly be more severe - and more likely to include dismissal - if you don't admit to the problem, and your employer discovers it by other means - for example, during a data or security audit or if a manager is given a copy of the document by a competitor.
To answer the question as asked: you should not have forwarded any company document to a former employer, without approval.
Since you have done it, you now need to mitigate the effects: report the error in an appropriate manner.
There are few circumstances in which an employee will be sacked if they admit to a mistake. In fact, even if the consequences are severe, most employers/managers want staff to feel safe about reporting honest mistakes that affect them. A prompt report allows them to mitigate effects - in your case, determine why a former employee requested the document. So you may get a talking-to, or even face some disciplinary action for a data breach (depending on how sensitive the document is, how well employees in your company are briefed about security concerns before starting a project, etc), but that is unlikely to be escalated to dismissal unless you build up a history of making the same sort of mistake repeatedly - you are expected to learn from mistakes, not keep repeating the same ones.
The consequences will certainly be more severe - and more likely to include dismissal - if you don't admit to the problem, and your employer discovers it by other means - for example, during a data or security audit or if a manager is given a copy of the document by a competitor.
edited Jul 21 at 10:44
answered Jul 20 at 8:48
PeterPeter
1673 bronze badges
1673 bronze badges
add a comment |
add a comment |
Thanks for contributing an answer to The Workplace Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f140637%2fshould-i-have-shared-a-document-with-a-former-employee%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
56
Were the contents of the document confidential to the company?
– Snow♦
Jul 18 at 14:05
3
This Question is unclear. You should give some sense of the kind of content in the document. You have a tag for confidentiality but fail to explain.
– Basil Bourque
Jul 19 at 21:25
If it's a confidential document there is no situation where it would be alright to share that with an ex-employee.
– Gregory Currie
Jul 20 at 3:46
1
This depends completely on what you shared and what the company does. It's impossible to make any meaningful judgement otherwise.
– iono
Jul 20 at 12:06
why does he want that document? Did you ask?
– Mayou36
Jul 21 at 16:47