How to navigate a large mistake I am responsible forI submitted an unapproved feature, got in trouble, now what?How do I get past a stupid mistake I made at company event?I made a mistake in signing a birthday cardIs a coworker rightfully annoyed by my typo?Should I own up my own mistake in public?
Why do we need explainable AI?
How to have the "Restore Missing Files" function from Nautilus without installing Nautilus?
Using large parts of a research paper
Can a system of three stars exist?
How to use a tikzpicture as a node shape
Do universities maintain secret textbooks?
How secure are public hashed passwords (with a salt)?
Can a country avoid prosecution for crimes against humanity by denying it happened?
Is Chuck the Evil Sandwich Making Guy's head actually a sandwich?
How were US credit cards verified in-store in the 1980's?
Using font to highlight a god's speech in dialogue
What is the definition of Product
Why didn't Thatcher give Hong Kong to Taiwan?
How can an F-22 Raptor reach supersonic speeds without having supersonic inlets?
meaning of "educating the ice"?
Punishment in pacifist society
Why wasn't Linda Hamilton in T3?
Killing task by name - start menu shortcut
Should we run PBKDF2 for every plaintext to be protected or should we run PBKDF2 only once?
Cheap oscilloscope showing 16 MHz square wave
Squares inside a square
Why do fuses burn at a specific current?
'spazieren' - walking in a silly and affected manner?
Why don't "echo -e" commands seem to produce the right output?
How to navigate a large mistake I am responsible for
I submitted an unapproved feature, got in trouble, now what?How do I get past a stupid mistake I made at company event?I made a mistake in signing a birthday cardIs a coworker rightfully annoyed by my typo?Should I own up my own mistake in public?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
asking for a friend
As part of a small project I wrote some code some months ago.
The code passed my tests, code review, UAT by business analysts and everything was fine. When the time came for me to request that it be loaded to production I had a gut feeling something wasn't right. I double checked the code and found a very serious logical error.
The problem was that between the time it was loaded to production and the time it went live (can be anywhere from a couple of days to a couple of weeks) the "fix" was going to deactivate another fix by someone else that was crucial to the business.
Embarresingly I reported it to management that I made a huge mistake.
The rest of the team has now also become aware since we're having meetings, sitting together assessing impact and discussing it openly. Senior management are also aware and want complete reports of what happened.
My manager is trying to help me remain calm telling me he is glad I spotted this before it went to production since we now have options. All options involve bringing our local office into the spotlight before the global corporation and having to explain how such a simple mistake was made in the first place. (This "simple mistake" isn't so simple or obvious but once it is pointed out it becomes very obvious, but it is difficult to pick up).
I've never made such a mistake in the workplace before and am extremely embarrassed about it and feel my "brand" has been tarnished. I am not sure if I should be apologetic, or just focus on finding a solution or just hand in my resignation now and move on. I feel terrible that I have wasted so much of the companies time on this already.
tl;dr
What is the best way to navigate this situation when I am personally responsible for a huge mistake in the workplace that is pure human error?
mistakes workplace-rhythm
add a comment |
asking for a friend
As part of a small project I wrote some code some months ago.
The code passed my tests, code review, UAT by business analysts and everything was fine. When the time came for me to request that it be loaded to production I had a gut feeling something wasn't right. I double checked the code and found a very serious logical error.
The problem was that between the time it was loaded to production and the time it went live (can be anywhere from a couple of days to a couple of weeks) the "fix" was going to deactivate another fix by someone else that was crucial to the business.
Embarresingly I reported it to management that I made a huge mistake.
The rest of the team has now also become aware since we're having meetings, sitting together assessing impact and discussing it openly. Senior management are also aware and want complete reports of what happened.
My manager is trying to help me remain calm telling me he is glad I spotted this before it went to production since we now have options. All options involve bringing our local office into the spotlight before the global corporation and having to explain how such a simple mistake was made in the first place. (This "simple mistake" isn't so simple or obvious but once it is pointed out it becomes very obvious, but it is difficult to pick up).
I've never made such a mistake in the workplace before and am extremely embarrassed about it and feel my "brand" has been tarnished. I am not sure if I should be apologetic, or just focus on finding a solution or just hand in my resignation now and move on. I feel terrible that I have wasted so much of the companies time on this already.
tl;dr
What is the best way to navigate this situation when I am personally responsible for a huge mistake in the workplace that is pure human error?
mistakes workplace-rhythm
add a comment |
asking for a friend
As part of a small project I wrote some code some months ago.
The code passed my tests, code review, UAT by business analysts and everything was fine. When the time came for me to request that it be loaded to production I had a gut feeling something wasn't right. I double checked the code and found a very serious logical error.
The problem was that between the time it was loaded to production and the time it went live (can be anywhere from a couple of days to a couple of weeks) the "fix" was going to deactivate another fix by someone else that was crucial to the business.
Embarresingly I reported it to management that I made a huge mistake.
The rest of the team has now also become aware since we're having meetings, sitting together assessing impact and discussing it openly. Senior management are also aware and want complete reports of what happened.
My manager is trying to help me remain calm telling me he is glad I spotted this before it went to production since we now have options. All options involve bringing our local office into the spotlight before the global corporation and having to explain how such a simple mistake was made in the first place. (This "simple mistake" isn't so simple or obvious but once it is pointed out it becomes very obvious, but it is difficult to pick up).
I've never made such a mistake in the workplace before and am extremely embarrassed about it and feel my "brand" has been tarnished. I am not sure if I should be apologetic, or just focus on finding a solution or just hand in my resignation now and move on. I feel terrible that I have wasted so much of the companies time on this already.
tl;dr
What is the best way to navigate this situation when I am personally responsible for a huge mistake in the workplace that is pure human error?
mistakes workplace-rhythm
asking for a friend
As part of a small project I wrote some code some months ago.
The code passed my tests, code review, UAT by business analysts and everything was fine. When the time came for me to request that it be loaded to production I had a gut feeling something wasn't right. I double checked the code and found a very serious logical error.
The problem was that between the time it was loaded to production and the time it went live (can be anywhere from a couple of days to a couple of weeks) the "fix" was going to deactivate another fix by someone else that was crucial to the business.
Embarresingly I reported it to management that I made a huge mistake.
The rest of the team has now also become aware since we're having meetings, sitting together assessing impact and discussing it openly. Senior management are also aware and want complete reports of what happened.
My manager is trying to help me remain calm telling me he is glad I spotted this before it went to production since we now have options. All options involve bringing our local office into the spotlight before the global corporation and having to explain how such a simple mistake was made in the first place. (This "simple mistake" isn't so simple or obvious but once it is pointed out it becomes very obvious, but it is difficult to pick up).
I've never made such a mistake in the workplace before and am extremely embarrassed about it and feel my "brand" has been tarnished. I am not sure if I should be apologetic, or just focus on finding a solution or just hand in my resignation now and move on. I feel terrible that I have wasted so much of the companies time on this already.
tl;dr
What is the best way to navigate this situation when I am personally responsible for a huge mistake in the workplace that is pure human error?
mistakes workplace-rhythm
mistakes workplace-rhythm
asked 16 mins ago
solarflaresolarflare
15.1k7 gold badges33 silver badges68 bronze badges
15.1k7 gold badges33 silver badges68 bronze badges
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The difference between you and someone less capable is the gut-feel that something was wrong. This gut feel is borne by experience, and forged by previous mistakes.
The concern needs to shift from blame, onto how this situation can be avoided in the future. The best person to identified the process defect that allowed this issue to pass testing and review by multiple levels of the business is you.
You need to get rid of the mindset that it a pure human error. There is no such thing. There is human error coupled with defective processes, or multiple humans making errors, but if it's important, it can't be down to a single person making a single error.
Don't compound the businesses pain my jumping ship when it's time to knuckle down and improve things. If they ask for your resignation, you can decide what to do then, but until then, you have to keep working hard.
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: true,
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%2f143306%2fhow-to-navigate-a-large-mistake-i-am-responsible-for%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The difference between you and someone less capable is the gut-feel that something was wrong. This gut feel is borne by experience, and forged by previous mistakes.
The concern needs to shift from blame, onto how this situation can be avoided in the future. The best person to identified the process defect that allowed this issue to pass testing and review by multiple levels of the business is you.
You need to get rid of the mindset that it a pure human error. There is no such thing. There is human error coupled with defective processes, or multiple humans making errors, but if it's important, it can't be down to a single person making a single error.
Don't compound the businesses pain my jumping ship when it's time to knuckle down and improve things. If they ask for your resignation, you can decide what to do then, but until then, you have to keep working hard.
add a comment |
The difference between you and someone less capable is the gut-feel that something was wrong. This gut feel is borne by experience, and forged by previous mistakes.
The concern needs to shift from blame, onto how this situation can be avoided in the future. The best person to identified the process defect that allowed this issue to pass testing and review by multiple levels of the business is you.
You need to get rid of the mindset that it a pure human error. There is no such thing. There is human error coupled with defective processes, or multiple humans making errors, but if it's important, it can't be down to a single person making a single error.
Don't compound the businesses pain my jumping ship when it's time to knuckle down and improve things. If they ask for your resignation, you can decide what to do then, but until then, you have to keep working hard.
add a comment |
The difference between you and someone less capable is the gut-feel that something was wrong. This gut feel is borne by experience, and forged by previous mistakes.
The concern needs to shift from blame, onto how this situation can be avoided in the future. The best person to identified the process defect that allowed this issue to pass testing and review by multiple levels of the business is you.
You need to get rid of the mindset that it a pure human error. There is no such thing. There is human error coupled with defective processes, or multiple humans making errors, but if it's important, it can't be down to a single person making a single error.
Don't compound the businesses pain my jumping ship when it's time to knuckle down and improve things. If they ask for your resignation, you can decide what to do then, but until then, you have to keep working hard.
The difference between you and someone less capable is the gut-feel that something was wrong. This gut feel is borne by experience, and forged by previous mistakes.
The concern needs to shift from blame, onto how this situation can be avoided in the future. The best person to identified the process defect that allowed this issue to pass testing and review by multiple levels of the business is you.
You need to get rid of the mindset that it a pure human error. There is no such thing. There is human error coupled with defective processes, or multiple humans making errors, but if it's important, it can't be down to a single person making a single error.
Don't compound the businesses pain my jumping ship when it's time to knuckle down and improve things. If they ask for your resignation, you can decide what to do then, but until then, you have to keep working hard.
answered 2 mins ago
Gregory CurrieGregory Currie
14.5k11 gold badges57 silver badges73 bronze badges
14.5k11 gold badges57 silver badges73 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%2f143306%2fhow-to-navigate-a-large-mistake-i-am-responsible-for%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