Should I own up my own mistake in public?
I am working as a software qualify assurance engineer and partially due to my work, a bug managed to get to our production code.
- Our customer service team has reported back this issue to us on Slack.
I am thinking if I should publicly own up this mistake and come up front to take responsibilities.
- Our company has a no-blame culture, which means no one blames anyone else. But I think I need to admit it is my fault that this bug has escaped to our customers.
If I should come up front, how far should I go?
Thanks
ethics mistakes
asked 28 mins ago
oscaroscar
1063
New contributor
oscar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I am working as a software qualify assurance engineer and partially due to my work, a bug managed to get to our production code.
- Our customer service team has reported back this issue to us on Slack.
I am thinking if I should publicly own up this mistake and come up front to take responsibilities.
- Our company has a no-blame culture, which means no one blames anyone else. But I think I need to admit it is my fault that this bug has escaped to our customers.
If I should come up front, how far should I go?
Thanks
ethics mistakes
asked 28 mins ago
oscaroscar
1063
New contributor
oscar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I am working as a software qualify assurance engineer and partially due to my work, a bug managed to get to our production code.
- Our customer service team has reported back this issue to us on Slack.
I am thinking if I should publicly own up this mistake and come up front to take responsibilities.
- Our company has a no-blame culture, which means no one blames anyone else. But I think I need to admit it is my fault that this bug has escaped to our customers.
If I should come up front, how far should I go?
Thanks
ethics mistakes
asked 28 mins ago
oscaroscar
1063
New contributor
oscar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I am working as a software qualify assurance engineer and partially due to my work, a bug managed to get to our production code.
- Our customer service team has reported back this issue to us on Slack.
I am thinking if I should publicly own up this mistake and come up front to take responsibilities.
- Our company has a no-blame culture, which means no one blames anyone else. But I think I need to admit it is my fault that this bug has escaped to our customers.
If I should come up front, how far should I go?
Thanks
ethics mistakes
ethics mistakes
asked 28 mins ago
oscaroscar
1063
New contributor
oscar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 28 mins ago
oscaroscar
1063
New contributor
oscar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 28 mins ago
oscaroscar
1063
New contributor
oscar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 28 mins ago
oscaroscar
1063
asked 28 mins ago
oscaroscar
1063
1063
New contributor
oscar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
oscar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
oscar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Taking responsibility for your mistakes shows a level of maturity that is good to have, both personally and professionally. It is definitely a characteristic that stands out more with consistent use, so don't just do it today and expect consistent returns for years to come. Yes, own your mistakes. No blame means don't point fingers. It means human mistakes can and should be understood. Not that you aren't supposed to acknowledge that you personally goofed.
That is internally. Customer facing personnel should handle statements that go out to the public consumer. There is more to consider there. The face of the company, legal liability in admitting fault, etc...
answered 15 mins ago
bruglescobruglesco
3,98521039
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
});
}
});
oscar is a new contributor. Be nice, and check out our Code of Conduct.
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%2f131541%2fshould-i-own-up-my-own-mistake-in-public%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
Taking responsibility for your mistakes shows a level of maturity that is good to have, both personally and professionally. It is definitely a characteristic that stands out more with consistent use, so don't just do it today and expect consistent returns for years to come. Yes, own your mistakes. No blame means don't point fingers. It means human mistakes can and should be understood. Not that you aren't supposed to acknowledge that you personally goofed.
That is internally. Customer facing personnel should handle statements that go out to the public consumer. There is more to consider there. The face of the company, legal liability in admitting fault, etc...
answered 15 mins ago
bruglescobruglesco
3,98521039
add a comment |
Taking responsibility for your mistakes shows a level of maturity that is good to have, both personally and professionally. It is definitely a characteristic that stands out more with consistent use, so don't just do it today and expect consistent returns for years to come. Yes, own your mistakes. No blame means don't point fingers. It means human mistakes can and should be understood. Not that you aren't supposed to acknowledge that you personally goofed.
That is internally. Customer facing personnel should handle statements that go out to the public consumer. There is more to consider there. The face of the company, legal liability in admitting fault, etc...
answered 15 mins ago
bruglescobruglesco
3,98521039
add a comment |
Taking responsibility for your mistakes shows a level of maturity that is good to have, both personally and professionally. It is definitely a characteristic that stands out more with consistent use, so don't just do it today and expect consistent returns for years to come. Yes, own your mistakes. No blame means don't point fingers. It means human mistakes can and should be understood. Not that you aren't supposed to acknowledge that you personally goofed.
That is internally. Customer facing personnel should handle statements that go out to the public consumer. There is more to consider there. The face of the company, legal liability in admitting fault, etc...
answered 15 mins ago
bruglescobruglesco
3,98521039
Taking responsibility for your mistakes shows a level of maturity that is good to have, both personally and professionally. It is definitely a characteristic that stands out more with consistent use, so don't just do it today and expect consistent returns for years to come. Yes, own your mistakes. No blame means don't point fingers. It means human mistakes can and should be understood. Not that you aren't supposed to acknowledge that you personally goofed.
That is internally. Customer facing personnel should handle statements that go out to the public consumer. There is more to consider there. The face of the company, legal liability in admitting fault, etc...
answered 15 mins ago
bruglescobruglesco
3,98521039
answered 15 mins ago
bruglescobruglesco
3,98521039
answered 15 mins ago
bruglescobruglesco
3,98521039
answered 15 mins ago
bruglescobruglesco
3,98521039
3,98521039
add a comment |
add a comment |
oscar is a new contributor. Be nice, and check out our Code of Conduct.
oscar is a new contributor. Be nice, and check out our Code of Conduct.
oscar is a new contributor. Be nice, and check out our Code of Conduct.
oscar is a new contributor. Be nice, and check out our Code of Conduct.
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%2f131541%2fshould-i-own-up-my-own-mistake-in-public%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
