Pointing out a perceived flaw in a product when your job security is thin

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
4
down vote

favorite
1












So I found a flaw in a product my employer sells. My position in the company is such that they allow me to work on projects, but if I want to keep enjoying the good will I've managed to instill in my boss, I'd better not question the code of previous employers (office politics have run amuck in the company's priorities).



Unfortunately, I've found a pretty glaring flaw in some legacy code that I've been referencing. The company has been going this long without it biting them in the butt, but it is an issue. I don't feel comfortable pointing things like this out to my boss because he takes it personally and gets this idea that I'm trying to run his company for him. In a way, by pointing out a flaw and suggesting it needs fixed, I can see how it could be argued, I AM trying to run his company a bit.



This is a bit of a difficult situation, but I guess what I'm asking is how do you openly point out an existing flaw when office politics already have you in a fragile position? Alternatively, should I just keep my yap shut and let them sink or swim if the problem ever surfaces with a client?







share|improve this question
















  • 22




    If you can't point out a software issue without risk of getting fired, then you should start looking for another company.
    – David K
    Sep 22 '14 at 15:50










  • Do you have a solution?
    – user8365
    Sep 22 '14 at 15:59










  • @JeffO - Unfortunately, I don't. I also don't feel comfortable taking the time to find an extension, because that will be perceived as me going off on my own without first getting clearance to work on it. IF you can imagine, also not a good thing for my position.
    – Sidney
    Sep 22 '14 at 16:05










  • @Sidney The best course of action is going to be cultural specific. Boss/worker relationships have different expectations in different parts of the world. What country are you working in?
    – Myles
    Sep 22 '14 at 19:06










  • report bug or replicate it in real time so it gets reported :D
    – amar
    Sep 23 '14 at 6:15
















up vote
4
down vote

favorite
1












So I found a flaw in a product my employer sells. My position in the company is such that they allow me to work on projects, but if I want to keep enjoying the good will I've managed to instill in my boss, I'd better not question the code of previous employers (office politics have run amuck in the company's priorities).



Unfortunately, I've found a pretty glaring flaw in some legacy code that I've been referencing. The company has been going this long without it biting them in the butt, but it is an issue. I don't feel comfortable pointing things like this out to my boss because he takes it personally and gets this idea that I'm trying to run his company for him. In a way, by pointing out a flaw and suggesting it needs fixed, I can see how it could be argued, I AM trying to run his company a bit.



This is a bit of a difficult situation, but I guess what I'm asking is how do you openly point out an existing flaw when office politics already have you in a fragile position? Alternatively, should I just keep my yap shut and let them sink or swim if the problem ever surfaces with a client?







share|improve this question
















  • 22




    If you can't point out a software issue without risk of getting fired, then you should start looking for another company.
    – David K
    Sep 22 '14 at 15:50










  • Do you have a solution?
    – user8365
    Sep 22 '14 at 15:59










  • @JeffO - Unfortunately, I don't. I also don't feel comfortable taking the time to find an extension, because that will be perceived as me going off on my own without first getting clearance to work on it. IF you can imagine, also not a good thing for my position.
    – Sidney
    Sep 22 '14 at 16:05










  • @Sidney The best course of action is going to be cultural specific. Boss/worker relationships have different expectations in different parts of the world. What country are you working in?
    – Myles
    Sep 22 '14 at 19:06










  • report bug or replicate it in real time so it gets reported :D
    – amar
    Sep 23 '14 at 6:15












up vote
4
down vote

favorite
1









up vote
4
down vote

favorite
1






1





So I found a flaw in a product my employer sells. My position in the company is such that they allow me to work on projects, but if I want to keep enjoying the good will I've managed to instill in my boss, I'd better not question the code of previous employers (office politics have run amuck in the company's priorities).



Unfortunately, I've found a pretty glaring flaw in some legacy code that I've been referencing. The company has been going this long without it biting them in the butt, but it is an issue. I don't feel comfortable pointing things like this out to my boss because he takes it personally and gets this idea that I'm trying to run his company for him. In a way, by pointing out a flaw and suggesting it needs fixed, I can see how it could be argued, I AM trying to run his company a bit.



This is a bit of a difficult situation, but I guess what I'm asking is how do you openly point out an existing flaw when office politics already have you in a fragile position? Alternatively, should I just keep my yap shut and let them sink or swim if the problem ever surfaces with a client?







share|improve this question












So I found a flaw in a product my employer sells. My position in the company is such that they allow me to work on projects, but if I want to keep enjoying the good will I've managed to instill in my boss, I'd better not question the code of previous employers (office politics have run amuck in the company's priorities).



Unfortunately, I've found a pretty glaring flaw in some legacy code that I've been referencing. The company has been going this long without it biting them in the butt, but it is an issue. I don't feel comfortable pointing things like this out to my boss because he takes it personally and gets this idea that I'm trying to run his company for him. In a way, by pointing out a flaw and suggesting it needs fixed, I can see how it could be argued, I AM trying to run his company a bit.



This is a bit of a difficult situation, but I guess what I'm asking is how do you openly point out an existing flaw when office politics already have you in a fragile position? Alternatively, should I just keep my yap shut and let them sink or swim if the problem ever surfaces with a client?









share|improve this question











share|improve this question




share|improve this question










asked Sep 22 '14 at 15:43









Sidney

2,53052040




2,53052040







  • 22




    If you can't point out a software issue without risk of getting fired, then you should start looking for another company.
    – David K
    Sep 22 '14 at 15:50










  • Do you have a solution?
    – user8365
    Sep 22 '14 at 15:59










  • @JeffO - Unfortunately, I don't. I also don't feel comfortable taking the time to find an extension, because that will be perceived as me going off on my own without first getting clearance to work on it. IF you can imagine, also not a good thing for my position.
    – Sidney
    Sep 22 '14 at 16:05










  • @Sidney The best course of action is going to be cultural specific. Boss/worker relationships have different expectations in different parts of the world. What country are you working in?
    – Myles
    Sep 22 '14 at 19:06










  • report bug or replicate it in real time so it gets reported :D
    – amar
    Sep 23 '14 at 6:15












  • 22




    If you can't point out a software issue without risk of getting fired, then you should start looking for another company.
    – David K
    Sep 22 '14 at 15:50










  • Do you have a solution?
    – user8365
    Sep 22 '14 at 15:59










  • @JeffO - Unfortunately, I don't. I also don't feel comfortable taking the time to find an extension, because that will be perceived as me going off on my own without first getting clearance to work on it. IF you can imagine, also not a good thing for my position.
    – Sidney
    Sep 22 '14 at 16:05










  • @Sidney The best course of action is going to be cultural specific. Boss/worker relationships have different expectations in different parts of the world. What country are you working in?
    – Myles
    Sep 22 '14 at 19:06










  • report bug or replicate it in real time so it gets reported :D
    – amar
    Sep 23 '14 at 6:15







22




22




If you can't point out a software issue without risk of getting fired, then you should start looking for another company.
– David K
Sep 22 '14 at 15:50




If you can't point out a software issue without risk of getting fired, then you should start looking for another company.
– David K
Sep 22 '14 at 15:50












Do you have a solution?
– user8365
Sep 22 '14 at 15:59




Do you have a solution?
– user8365
Sep 22 '14 at 15:59












@JeffO - Unfortunately, I don't. I also don't feel comfortable taking the time to find an extension, because that will be perceived as me going off on my own without first getting clearance to work on it. IF you can imagine, also not a good thing for my position.
– Sidney
Sep 22 '14 at 16:05




@JeffO - Unfortunately, I don't. I also don't feel comfortable taking the time to find an extension, because that will be perceived as me going off on my own without first getting clearance to work on it. IF you can imagine, also not a good thing for my position.
– Sidney
Sep 22 '14 at 16:05












@Sidney The best course of action is going to be cultural specific. Boss/worker relationships have different expectations in different parts of the world. What country are you working in?
– Myles
Sep 22 '14 at 19:06




@Sidney The best course of action is going to be cultural specific. Boss/worker relationships have different expectations in different parts of the world. What country are you working in?
– Myles
Sep 22 '14 at 19:06












report bug or replicate it in real time so it gets reported :D
– amar
Sep 23 '14 at 6:15




report bug or replicate it in real time so it gets reported :D
– amar
Sep 23 '14 at 6:15










3 Answers
3






active

oldest

votes

















up vote
12
down vote



accepted










I would argue that's it's your responsibility to raise flaws like this. If the flaw were to be exploited you'd be kicking yourself for not speaking up. Since the hard part seems to be communicating to your boss, maybe you just need to change your presentation approach.



Rather than saying "this is a flaw that needs to be fixed for reasons X, Y, and Z," you could ask for your boss' opinion. Tell him in a casual way you found a potential issue. Ask him if he thinks it's serious, and ask for his opinion on a next course of action.



This way you've met your obligation and still communicated it in a manner that allows your boss to maintain control.



If you want to go completely passive and non-confrontational, you could even ask your boss if what you found could even be considered a flaw.






share|improve this answer


















  • 2




    For bonus points, suggest a fix at the same time that you report the flaw.
    – keshlam
    Sep 22 '14 at 16:08










  • Ideally, the reporting of all coding flaws would be encouraged at this particular company, but the owner is so defensive about the code, the messenger is going to get killed.
    – user8365
    Sep 22 '14 at 19:11






  • 1




    @JeffO if the flaw is exploited and the boss asks the OP about it, the OP will get blamed no matter what the OP's response is. If the OP asks what the boss thinks about the flaw, that may provide enough cover. If the boss is completely unreasonable no matter the approach, then this is not an acceptable working relationship.
    – mcknz
    Sep 22 '14 at 19:51






  • 1




    @keshlam, He said the environment is very sensitive and they are defensive to being corrected. In this environment you shoudl definitely NOT offer a solution. Just point out, you found something of concern that you thought he might want to look further into. Don't offer criticism or solutions. If they want a solution they will ask.
    – Bill Leeper
    Sep 22 '14 at 20:13






  • 1




    @BillLeeper: We're both guessing. I'm sticking with my guess. Your mileage will vary.
    – keshlam
    Sep 22 '14 at 21:30

















up vote
3
down vote













The CRM model of communicating



This is a very old post, but for the sake of people finding themselves in a similar situation...



Crew Resource Management provides a method to communicate serious issues in such a way that it increases your likelihood of being heard. CRM was created for flight crews but can be used elsewhere as well.



The method is thus...




  • Opening or attention getter - Address the individual: "Hey Chief," or "Captain Smith," or "Bob," or whatever name or title will get the person's attention.


  • State your concern - Express your analysis of the situation in a direct manner while owning your emotions about it. "I'm concerned that we may not have enough fuel to fly around this storm system," or "I'm worried that the roof might collapse."


  • State the problem as you see it - "We're showing only 40 minutes of fuel left," or "This building has a lightweight steel truss roof, and we may have fire extension into the roof structure."


  • State a solution - "Let's divert to another airport and refuel," or "I think we should pull some tiles and take a look with the thermal imaging camera before we commit crews inside."


  • Obtain agreement (or buy-in) - "Does that sound good to you, Captain?"

You should do this by yourself first, and write the whole thing down. This lets you put words on...



  1. What you think the issue is

  2. What kind of problems and risk you think the issue presents to your employer

  3. What you think a good solution might be

This bit is important because it allows you to be critical of yourself and your suspicions. It lets you find proper arguments for your misgivings about the product. It lets you move beyond "Y'know... I think does not look quite right" and instead find yourself where you can say "If this scenario becomes reality, the company stands to lose a lot of reputation and [amount of money]".



Try it, and see how it works out for you.






share|improve this answer



























    up vote
    2
    down vote













    When you point out something negative, people have a natural tendency to go on the defensive. There are a bunch of pointers which you can get from the book "How to Win Friends and Influence People" - you can go through this summary if you don't want to take the time to read it.



    The thing is that once the boss goes on the defensive and the conversation deteriorates into an argument, there's little in the way of communication as it's mostly noise. So you have to be subtle about how you break the news to him.



    One way is to use a compliment sandwich, in which you start off with a compliment in order to set a positive vibe, then you break the (negative) news, and then you end with another compliment so as to not leave on a negative note.



    The book (and summary) I mentioned above has several other tactics you might want to look at. Some include:



    • Begin in a friendly way. Focus on the things you have in common, and get your boss to say "yes" a lot.

    • Let the person feel that the idea is his or hers.

    • Appeal to the nobler motives.

    • Really you should see most of "Part 4: Be a Leader: How to Change People Without Giving Offense or Arousing Resentment" which is more or less what you need.





    share|improve this answer




















      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',
      convertImagesToLinks: false,
      noModals: false,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      noCode: true, onDemand: false,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      );



      );








       

      draft saved


      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f34048%2fpointing-out-a-perceived-flaw-in-a-product-when-your-job-security-is-thin%23new-answer', 'question_page');

      );

      Post as a guest

























      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();


      );
      );






      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      12
      down vote



      accepted










      I would argue that's it's your responsibility to raise flaws like this. If the flaw were to be exploited you'd be kicking yourself for not speaking up. Since the hard part seems to be communicating to your boss, maybe you just need to change your presentation approach.



      Rather than saying "this is a flaw that needs to be fixed for reasons X, Y, and Z," you could ask for your boss' opinion. Tell him in a casual way you found a potential issue. Ask him if he thinks it's serious, and ask for his opinion on a next course of action.



      This way you've met your obligation and still communicated it in a manner that allows your boss to maintain control.



      If you want to go completely passive and non-confrontational, you could even ask your boss if what you found could even be considered a flaw.






      share|improve this answer


















      • 2




        For bonus points, suggest a fix at the same time that you report the flaw.
        – keshlam
        Sep 22 '14 at 16:08










      • Ideally, the reporting of all coding flaws would be encouraged at this particular company, but the owner is so defensive about the code, the messenger is going to get killed.
        – user8365
        Sep 22 '14 at 19:11






      • 1




        @JeffO if the flaw is exploited and the boss asks the OP about it, the OP will get blamed no matter what the OP's response is. If the OP asks what the boss thinks about the flaw, that may provide enough cover. If the boss is completely unreasonable no matter the approach, then this is not an acceptable working relationship.
        – mcknz
        Sep 22 '14 at 19:51






      • 1




        @keshlam, He said the environment is very sensitive and they are defensive to being corrected. In this environment you shoudl definitely NOT offer a solution. Just point out, you found something of concern that you thought he might want to look further into. Don't offer criticism or solutions. If they want a solution they will ask.
        – Bill Leeper
        Sep 22 '14 at 20:13






      • 1




        @BillLeeper: We're both guessing. I'm sticking with my guess. Your mileage will vary.
        – keshlam
        Sep 22 '14 at 21:30














      up vote
      12
      down vote



      accepted










      I would argue that's it's your responsibility to raise flaws like this. If the flaw were to be exploited you'd be kicking yourself for not speaking up. Since the hard part seems to be communicating to your boss, maybe you just need to change your presentation approach.



      Rather than saying "this is a flaw that needs to be fixed for reasons X, Y, and Z," you could ask for your boss' opinion. Tell him in a casual way you found a potential issue. Ask him if he thinks it's serious, and ask for his opinion on a next course of action.



      This way you've met your obligation and still communicated it in a manner that allows your boss to maintain control.



      If you want to go completely passive and non-confrontational, you could even ask your boss if what you found could even be considered a flaw.






      share|improve this answer


















      • 2




        For bonus points, suggest a fix at the same time that you report the flaw.
        – keshlam
        Sep 22 '14 at 16:08










      • Ideally, the reporting of all coding flaws would be encouraged at this particular company, but the owner is so defensive about the code, the messenger is going to get killed.
        – user8365
        Sep 22 '14 at 19:11






      • 1




        @JeffO if the flaw is exploited and the boss asks the OP about it, the OP will get blamed no matter what the OP's response is. If the OP asks what the boss thinks about the flaw, that may provide enough cover. If the boss is completely unreasonable no matter the approach, then this is not an acceptable working relationship.
        – mcknz
        Sep 22 '14 at 19:51






      • 1




        @keshlam, He said the environment is very sensitive and they are defensive to being corrected. In this environment you shoudl definitely NOT offer a solution. Just point out, you found something of concern that you thought he might want to look further into. Don't offer criticism or solutions. If they want a solution they will ask.
        – Bill Leeper
        Sep 22 '14 at 20:13






      • 1




        @BillLeeper: We're both guessing. I'm sticking with my guess. Your mileage will vary.
        – keshlam
        Sep 22 '14 at 21:30












      up vote
      12
      down vote



      accepted







      up vote
      12
      down vote



      accepted






      I would argue that's it's your responsibility to raise flaws like this. If the flaw were to be exploited you'd be kicking yourself for not speaking up. Since the hard part seems to be communicating to your boss, maybe you just need to change your presentation approach.



      Rather than saying "this is a flaw that needs to be fixed for reasons X, Y, and Z," you could ask for your boss' opinion. Tell him in a casual way you found a potential issue. Ask him if he thinks it's serious, and ask for his opinion on a next course of action.



      This way you've met your obligation and still communicated it in a manner that allows your boss to maintain control.



      If you want to go completely passive and non-confrontational, you could even ask your boss if what you found could even be considered a flaw.






      share|improve this answer














      I would argue that's it's your responsibility to raise flaws like this. If the flaw were to be exploited you'd be kicking yourself for not speaking up. Since the hard part seems to be communicating to your boss, maybe you just need to change your presentation approach.



      Rather than saying "this is a flaw that needs to be fixed for reasons X, Y, and Z," you could ask for your boss' opinion. Tell him in a casual way you found a potential issue. Ask him if he thinks it's serious, and ask for his opinion on a next course of action.



      This way you've met your obligation and still communicated it in a manner that allows your boss to maintain control.



      If you want to go completely passive and non-confrontational, you could even ask your boss if what you found could even be considered a flaw.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited 1 hour ago

























      answered Sep 22 '14 at 16:00









      mcknz

      15.7k55468




      15.7k55468







      • 2




        For bonus points, suggest a fix at the same time that you report the flaw.
        – keshlam
        Sep 22 '14 at 16:08










      • Ideally, the reporting of all coding flaws would be encouraged at this particular company, but the owner is so defensive about the code, the messenger is going to get killed.
        – user8365
        Sep 22 '14 at 19:11






      • 1




        @JeffO if the flaw is exploited and the boss asks the OP about it, the OP will get blamed no matter what the OP's response is. If the OP asks what the boss thinks about the flaw, that may provide enough cover. If the boss is completely unreasonable no matter the approach, then this is not an acceptable working relationship.
        – mcknz
        Sep 22 '14 at 19:51






      • 1




        @keshlam, He said the environment is very sensitive and they are defensive to being corrected. In this environment you shoudl definitely NOT offer a solution. Just point out, you found something of concern that you thought he might want to look further into. Don't offer criticism or solutions. If they want a solution they will ask.
        – Bill Leeper
        Sep 22 '14 at 20:13






      • 1




        @BillLeeper: We're both guessing. I'm sticking with my guess. Your mileage will vary.
        – keshlam
        Sep 22 '14 at 21:30












      • 2




        For bonus points, suggest a fix at the same time that you report the flaw.
        – keshlam
        Sep 22 '14 at 16:08










      • Ideally, the reporting of all coding flaws would be encouraged at this particular company, but the owner is so defensive about the code, the messenger is going to get killed.
        – user8365
        Sep 22 '14 at 19:11






      • 1




        @JeffO if the flaw is exploited and the boss asks the OP about it, the OP will get blamed no matter what the OP's response is. If the OP asks what the boss thinks about the flaw, that may provide enough cover. If the boss is completely unreasonable no matter the approach, then this is not an acceptable working relationship.
        – mcknz
        Sep 22 '14 at 19:51






      • 1




        @keshlam, He said the environment is very sensitive and they are defensive to being corrected. In this environment you shoudl definitely NOT offer a solution. Just point out, you found something of concern that you thought he might want to look further into. Don't offer criticism or solutions. If they want a solution they will ask.
        – Bill Leeper
        Sep 22 '14 at 20:13






      • 1




        @BillLeeper: We're both guessing. I'm sticking with my guess. Your mileage will vary.
        – keshlam
        Sep 22 '14 at 21:30







      2




      2




      For bonus points, suggest a fix at the same time that you report the flaw.
      – keshlam
      Sep 22 '14 at 16:08




      For bonus points, suggest a fix at the same time that you report the flaw.
      – keshlam
      Sep 22 '14 at 16:08












      Ideally, the reporting of all coding flaws would be encouraged at this particular company, but the owner is so defensive about the code, the messenger is going to get killed.
      – user8365
      Sep 22 '14 at 19:11




      Ideally, the reporting of all coding flaws would be encouraged at this particular company, but the owner is so defensive about the code, the messenger is going to get killed.
      – user8365
      Sep 22 '14 at 19:11




      1




      1




      @JeffO if the flaw is exploited and the boss asks the OP about it, the OP will get blamed no matter what the OP's response is. If the OP asks what the boss thinks about the flaw, that may provide enough cover. If the boss is completely unreasonable no matter the approach, then this is not an acceptable working relationship.
      – mcknz
      Sep 22 '14 at 19:51




      @JeffO if the flaw is exploited and the boss asks the OP about it, the OP will get blamed no matter what the OP's response is. If the OP asks what the boss thinks about the flaw, that may provide enough cover. If the boss is completely unreasonable no matter the approach, then this is not an acceptable working relationship.
      – mcknz
      Sep 22 '14 at 19:51




      1




      1




      @keshlam, He said the environment is very sensitive and they are defensive to being corrected. In this environment you shoudl definitely NOT offer a solution. Just point out, you found something of concern that you thought he might want to look further into. Don't offer criticism or solutions. If they want a solution they will ask.
      – Bill Leeper
      Sep 22 '14 at 20:13




      @keshlam, He said the environment is very sensitive and they are defensive to being corrected. In this environment you shoudl definitely NOT offer a solution. Just point out, you found something of concern that you thought he might want to look further into. Don't offer criticism or solutions. If they want a solution they will ask.
      – Bill Leeper
      Sep 22 '14 at 20:13




      1




      1




      @BillLeeper: We're both guessing. I'm sticking with my guess. Your mileage will vary.
      – keshlam
      Sep 22 '14 at 21:30




      @BillLeeper: We're both guessing. I'm sticking with my guess. Your mileage will vary.
      – keshlam
      Sep 22 '14 at 21:30












      up vote
      3
      down vote













      The CRM model of communicating



      This is a very old post, but for the sake of people finding themselves in a similar situation...



      Crew Resource Management provides a method to communicate serious issues in such a way that it increases your likelihood of being heard. CRM was created for flight crews but can be used elsewhere as well.



      The method is thus...




      • Opening or attention getter - Address the individual: "Hey Chief," or "Captain Smith," or "Bob," or whatever name or title will get the person's attention.


      • State your concern - Express your analysis of the situation in a direct manner while owning your emotions about it. "I'm concerned that we may not have enough fuel to fly around this storm system," or "I'm worried that the roof might collapse."


      • State the problem as you see it - "We're showing only 40 minutes of fuel left," or "This building has a lightweight steel truss roof, and we may have fire extension into the roof structure."


      • State a solution - "Let's divert to another airport and refuel," or "I think we should pull some tiles and take a look with the thermal imaging camera before we commit crews inside."


      • Obtain agreement (or buy-in) - "Does that sound good to you, Captain?"

      You should do this by yourself first, and write the whole thing down. This lets you put words on...



      1. What you think the issue is

      2. What kind of problems and risk you think the issue presents to your employer

      3. What you think a good solution might be

      This bit is important because it allows you to be critical of yourself and your suspicions. It lets you find proper arguments for your misgivings about the product. It lets you move beyond "Y'know... I think does not look quite right" and instead find yourself where you can say "If this scenario becomes reality, the company stands to lose a lot of reputation and [amount of money]".



      Try it, and see how it works out for you.






      share|improve this answer
























        up vote
        3
        down vote













        The CRM model of communicating



        This is a very old post, but for the sake of people finding themselves in a similar situation...



        Crew Resource Management provides a method to communicate serious issues in such a way that it increases your likelihood of being heard. CRM was created for flight crews but can be used elsewhere as well.



        The method is thus...




        • Opening or attention getter - Address the individual: "Hey Chief," or "Captain Smith," or "Bob," or whatever name or title will get the person's attention.


        • State your concern - Express your analysis of the situation in a direct manner while owning your emotions about it. "I'm concerned that we may not have enough fuel to fly around this storm system," or "I'm worried that the roof might collapse."


        • State the problem as you see it - "We're showing only 40 minutes of fuel left," or "This building has a lightweight steel truss roof, and we may have fire extension into the roof structure."


        • State a solution - "Let's divert to another airport and refuel," or "I think we should pull some tiles and take a look with the thermal imaging camera before we commit crews inside."


        • Obtain agreement (or buy-in) - "Does that sound good to you, Captain?"

        You should do this by yourself first, and write the whole thing down. This lets you put words on...



        1. What you think the issue is

        2. What kind of problems and risk you think the issue presents to your employer

        3. What you think a good solution might be

        This bit is important because it allows you to be critical of yourself and your suspicions. It lets you find proper arguments for your misgivings about the product. It lets you move beyond "Y'know... I think does not look quite right" and instead find yourself where you can say "If this scenario becomes reality, the company stands to lose a lot of reputation and [amount of money]".



        Try it, and see how it works out for you.






        share|improve this answer






















          up vote
          3
          down vote










          up vote
          3
          down vote









          The CRM model of communicating



          This is a very old post, but for the sake of people finding themselves in a similar situation...



          Crew Resource Management provides a method to communicate serious issues in such a way that it increases your likelihood of being heard. CRM was created for flight crews but can be used elsewhere as well.



          The method is thus...




          • Opening or attention getter - Address the individual: "Hey Chief," or "Captain Smith," or "Bob," or whatever name or title will get the person's attention.


          • State your concern - Express your analysis of the situation in a direct manner while owning your emotions about it. "I'm concerned that we may not have enough fuel to fly around this storm system," or "I'm worried that the roof might collapse."


          • State the problem as you see it - "We're showing only 40 minutes of fuel left," or "This building has a lightweight steel truss roof, and we may have fire extension into the roof structure."


          • State a solution - "Let's divert to another airport and refuel," or "I think we should pull some tiles and take a look with the thermal imaging camera before we commit crews inside."


          • Obtain agreement (or buy-in) - "Does that sound good to you, Captain?"

          You should do this by yourself first, and write the whole thing down. This lets you put words on...



          1. What you think the issue is

          2. What kind of problems and risk you think the issue presents to your employer

          3. What you think a good solution might be

          This bit is important because it allows you to be critical of yourself and your suspicions. It lets you find proper arguments for your misgivings about the product. It lets you move beyond "Y'know... I think does not look quite right" and instead find yourself where you can say "If this scenario becomes reality, the company stands to lose a lot of reputation and [amount of money]".



          Try it, and see how it works out for you.






          share|improve this answer












          The CRM model of communicating



          This is a very old post, but for the sake of people finding themselves in a similar situation...



          Crew Resource Management provides a method to communicate serious issues in such a way that it increases your likelihood of being heard. CRM was created for flight crews but can be used elsewhere as well.



          The method is thus...




          • Opening or attention getter - Address the individual: "Hey Chief," or "Captain Smith," or "Bob," or whatever name or title will get the person's attention.


          • State your concern - Express your analysis of the situation in a direct manner while owning your emotions about it. "I'm concerned that we may not have enough fuel to fly around this storm system," or "I'm worried that the roof might collapse."


          • State the problem as you see it - "We're showing only 40 minutes of fuel left," or "This building has a lightweight steel truss roof, and we may have fire extension into the roof structure."


          • State a solution - "Let's divert to another airport and refuel," or "I think we should pull some tiles and take a look with the thermal imaging camera before we commit crews inside."


          • Obtain agreement (or buy-in) - "Does that sound good to you, Captain?"

          You should do this by yourself first, and write the whole thing down. This lets you put words on...



          1. What you think the issue is

          2. What kind of problems and risk you think the issue presents to your employer

          3. What you think a good solution might be

          This bit is important because it allows you to be critical of yourself and your suspicions. It lets you find proper arguments for your misgivings about the product. It lets you move beyond "Y'know... I think does not look quite right" and instead find yourself where you can say "If this scenario becomes reality, the company stands to lose a lot of reputation and [amount of money]".



          Try it, and see how it works out for you.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 1 hour ago









          MichaelK

          64936




          64936




















              up vote
              2
              down vote













              When you point out something negative, people have a natural tendency to go on the defensive. There are a bunch of pointers which you can get from the book "How to Win Friends and Influence People" - you can go through this summary if you don't want to take the time to read it.



              The thing is that once the boss goes on the defensive and the conversation deteriorates into an argument, there's little in the way of communication as it's mostly noise. So you have to be subtle about how you break the news to him.



              One way is to use a compliment sandwich, in which you start off with a compliment in order to set a positive vibe, then you break the (negative) news, and then you end with another compliment so as to not leave on a negative note.



              The book (and summary) I mentioned above has several other tactics you might want to look at. Some include:



              • Begin in a friendly way. Focus on the things you have in common, and get your boss to say "yes" a lot.

              • Let the person feel that the idea is his or hers.

              • Appeal to the nobler motives.

              • Really you should see most of "Part 4: Be a Leader: How to Change People Without Giving Offense or Arousing Resentment" which is more or less what you need.





              share|improve this answer
























                up vote
                2
                down vote













                When you point out something negative, people have a natural tendency to go on the defensive. There are a bunch of pointers which you can get from the book "How to Win Friends and Influence People" - you can go through this summary if you don't want to take the time to read it.



                The thing is that once the boss goes on the defensive and the conversation deteriorates into an argument, there's little in the way of communication as it's mostly noise. So you have to be subtle about how you break the news to him.



                One way is to use a compliment sandwich, in which you start off with a compliment in order to set a positive vibe, then you break the (negative) news, and then you end with another compliment so as to not leave on a negative note.



                The book (and summary) I mentioned above has several other tactics you might want to look at. Some include:



                • Begin in a friendly way. Focus on the things you have in common, and get your boss to say "yes" a lot.

                • Let the person feel that the idea is his or hers.

                • Appeal to the nobler motives.

                • Really you should see most of "Part 4: Be a Leader: How to Change People Without Giving Offense or Arousing Resentment" which is more or less what you need.





                share|improve this answer






















                  up vote
                  2
                  down vote










                  up vote
                  2
                  down vote









                  When you point out something negative, people have a natural tendency to go on the defensive. There are a bunch of pointers which you can get from the book "How to Win Friends and Influence People" - you can go through this summary if you don't want to take the time to read it.



                  The thing is that once the boss goes on the defensive and the conversation deteriorates into an argument, there's little in the way of communication as it's mostly noise. So you have to be subtle about how you break the news to him.



                  One way is to use a compliment sandwich, in which you start off with a compliment in order to set a positive vibe, then you break the (negative) news, and then you end with another compliment so as to not leave on a negative note.



                  The book (and summary) I mentioned above has several other tactics you might want to look at. Some include:



                  • Begin in a friendly way. Focus on the things you have in common, and get your boss to say "yes" a lot.

                  • Let the person feel that the idea is his or hers.

                  • Appeal to the nobler motives.

                  • Really you should see most of "Part 4: Be a Leader: How to Change People Without Giving Offense or Arousing Resentment" which is more or less what you need.





                  share|improve this answer












                  When you point out something negative, people have a natural tendency to go on the defensive. There are a bunch of pointers which you can get from the book "How to Win Friends and Influence People" - you can go through this summary if you don't want to take the time to read it.



                  The thing is that once the boss goes on the defensive and the conversation deteriorates into an argument, there's little in the way of communication as it's mostly noise. So you have to be subtle about how you break the news to him.



                  One way is to use a compliment sandwich, in which you start off with a compliment in order to set a positive vibe, then you break the (negative) news, and then you end with another compliment so as to not leave on a negative note.



                  The book (and summary) I mentioned above has several other tactics you might want to look at. Some include:



                  • Begin in a friendly way. Focus on the things you have in common, and get your boss to say "yes" a lot.

                  • Let the person feel that the idea is his or hers.

                  • Appeal to the nobler motives.

                  • Really you should see most of "Part 4: Be a Leader: How to Change People Without Giving Offense or Arousing Resentment" which is more or less what you need.






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Sep 22 '14 at 21:25









                  Gigi

                  999612




                  999612






















                       

                      draft saved


                      draft discarded


























                       


                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f34048%2fpointing-out-a-perceived-flaw-in-a-product-when-your-job-security-is-thin%23new-answer', 'question_page');

                      );

                      Post as a guest

















































































                      Comments

                      Popular posts from this blog

                      What does second last employer means? [closed]

                      List of Gilmore Girls characters

                      Confectionery