Engineer refusing to file/disclose patents












42















We have a senior engineer on our team that routinely excels at his work. In addition to his regular work, our company has a patent program where engineers can write up a patent for a novel idea, and submit it to our patent team. Within about 6 months, the engineer will get anything in the range of $300 to $5000, depending on the value of the patent from the perspective of the patent team. This engineer has filed over 30 successful patents over the past 2 years, and all of these inventions are used in our products (and he's made about $110,000.00 from the patent disclosures alone).



The company has recently decided to dial back the benefits for this program, to a simple $100 "finder's fee" for a patent submission, and an additional $900 for a "good" patent. Since employees write these in their spare time, it doesn't surprise me that the number of applications has dropped from 2 per week to maybe 3 per quarter.



Our senior engineer has expressed concern with the company, as he can only make more money by being promoted (our bonus structure is based on length of stay, so employees have to be on board for at least 7 years to earn a decent bonus), and the only offices with openings for higher-level engineering positions would require him and his family to relocate (moving across the country). He's also noted that the decrease in patent-related bonuses hits him hard.



My problem: our senior engineer recently (before the change in benefits) demonstrated some very impressive technology that would speed up a certain process of ours. He also claimed to have written 5 patents associated with it. He's delivered impressive results in the past, so I doubt he was blowing smoke. After the reduction in benefits, he can't seem to recall the patents or find any of the code he used to create his demo. Since he did this all in spare time, it's not in violation of our data retention policies if he just did it all on his home laptop, provided he didn't copy company data to it.



I think he's getting ready to switch jobs, and we need the technical information/code he used to create the demo. His employment agreement states that any and all intellectual property he generates while employed with us, even during weekends/free-time, is the property of the company. IT has searched his OneDrive, laptop, etc., and we can't find a single shred of code/documentation on these ideas. I've tried offering a one-off bonus for him to just anonymously leave a thumb drive with the data on my desk after hours, but he just claims he "doesn't know what I'm talking about".



How can I resolve this?



I can offer a one-off bonus, and I can offer him a significant promotion (but it requires he move to a less desirable part of the country). I can't give him a raise in his current position, and members of senior management no longer trust him due to his "funny" behavior as of late (well has been poisoned a bit). He doesn't want to move at all, and even an offer of $25,000.00 for the IP didn't work, which would have been according to the "old rules". I think he's worried that by agreeing to such a deal, he's opening himself up to legal liability (it would involve indirectly admitting he was being dicey/dishonest about "not knowing what I'm talking about").










share|improve this question









New contributor




Gen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Comments are not for extended discussion; this conversation has been moved to chat.

    – Mister Positive
    1 hour ago
















42















We have a senior engineer on our team that routinely excels at his work. In addition to his regular work, our company has a patent program where engineers can write up a patent for a novel idea, and submit it to our patent team. Within about 6 months, the engineer will get anything in the range of $300 to $5000, depending on the value of the patent from the perspective of the patent team. This engineer has filed over 30 successful patents over the past 2 years, and all of these inventions are used in our products (and he's made about $110,000.00 from the patent disclosures alone).



The company has recently decided to dial back the benefits for this program, to a simple $100 "finder's fee" for a patent submission, and an additional $900 for a "good" patent. Since employees write these in their spare time, it doesn't surprise me that the number of applications has dropped from 2 per week to maybe 3 per quarter.



Our senior engineer has expressed concern with the company, as he can only make more money by being promoted (our bonus structure is based on length of stay, so employees have to be on board for at least 7 years to earn a decent bonus), and the only offices with openings for higher-level engineering positions would require him and his family to relocate (moving across the country). He's also noted that the decrease in patent-related bonuses hits him hard.



My problem: our senior engineer recently (before the change in benefits) demonstrated some very impressive technology that would speed up a certain process of ours. He also claimed to have written 5 patents associated with it. He's delivered impressive results in the past, so I doubt he was blowing smoke. After the reduction in benefits, he can't seem to recall the patents or find any of the code he used to create his demo. Since he did this all in spare time, it's not in violation of our data retention policies if he just did it all on his home laptop, provided he didn't copy company data to it.



I think he's getting ready to switch jobs, and we need the technical information/code he used to create the demo. His employment agreement states that any and all intellectual property he generates while employed with us, even during weekends/free-time, is the property of the company. IT has searched his OneDrive, laptop, etc., and we can't find a single shred of code/documentation on these ideas. I've tried offering a one-off bonus for him to just anonymously leave a thumb drive with the data on my desk after hours, but he just claims he "doesn't know what I'm talking about".



How can I resolve this?



I can offer a one-off bonus, and I can offer him a significant promotion (but it requires he move to a less desirable part of the country). I can't give him a raise in his current position, and members of senior management no longer trust him due to his "funny" behavior as of late (well has been poisoned a bit). He doesn't want to move at all, and even an offer of $25,000.00 for the IP didn't work, which would have been according to the "old rules". I think he's worried that by agreeing to such a deal, he's opening himself up to legal liability (it would involve indirectly admitting he was being dicey/dishonest about "not knowing what I'm talking about").










share|improve this question









New contributor




Gen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Comments are not for extended discussion; this conversation has been moved to chat.

    – Mister Positive
    1 hour ago














42












42








42


14






We have a senior engineer on our team that routinely excels at his work. In addition to his regular work, our company has a patent program where engineers can write up a patent for a novel idea, and submit it to our patent team. Within about 6 months, the engineer will get anything in the range of $300 to $5000, depending on the value of the patent from the perspective of the patent team. This engineer has filed over 30 successful patents over the past 2 years, and all of these inventions are used in our products (and he's made about $110,000.00 from the patent disclosures alone).



The company has recently decided to dial back the benefits for this program, to a simple $100 "finder's fee" for a patent submission, and an additional $900 for a "good" patent. Since employees write these in their spare time, it doesn't surprise me that the number of applications has dropped from 2 per week to maybe 3 per quarter.



Our senior engineer has expressed concern with the company, as he can only make more money by being promoted (our bonus structure is based on length of stay, so employees have to be on board for at least 7 years to earn a decent bonus), and the only offices with openings for higher-level engineering positions would require him and his family to relocate (moving across the country). He's also noted that the decrease in patent-related bonuses hits him hard.



My problem: our senior engineer recently (before the change in benefits) demonstrated some very impressive technology that would speed up a certain process of ours. He also claimed to have written 5 patents associated with it. He's delivered impressive results in the past, so I doubt he was blowing smoke. After the reduction in benefits, he can't seem to recall the patents or find any of the code he used to create his demo. Since he did this all in spare time, it's not in violation of our data retention policies if he just did it all on his home laptop, provided he didn't copy company data to it.



I think he's getting ready to switch jobs, and we need the technical information/code he used to create the demo. His employment agreement states that any and all intellectual property he generates while employed with us, even during weekends/free-time, is the property of the company. IT has searched his OneDrive, laptop, etc., and we can't find a single shred of code/documentation on these ideas. I've tried offering a one-off bonus for him to just anonymously leave a thumb drive with the data on my desk after hours, but he just claims he "doesn't know what I'm talking about".



How can I resolve this?



I can offer a one-off bonus, and I can offer him a significant promotion (but it requires he move to a less desirable part of the country). I can't give him a raise in his current position, and members of senior management no longer trust him due to his "funny" behavior as of late (well has been poisoned a bit). He doesn't want to move at all, and even an offer of $25,000.00 for the IP didn't work, which would have been according to the "old rules". I think he's worried that by agreeing to such a deal, he's opening himself up to legal liability (it would involve indirectly admitting he was being dicey/dishonest about "not knowing what I'm talking about").










share|improve this question









New contributor




Gen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












We have a senior engineer on our team that routinely excels at his work. In addition to his regular work, our company has a patent program where engineers can write up a patent for a novel idea, and submit it to our patent team. Within about 6 months, the engineer will get anything in the range of $300 to $5000, depending on the value of the patent from the perspective of the patent team. This engineer has filed over 30 successful patents over the past 2 years, and all of these inventions are used in our products (and he's made about $110,000.00 from the patent disclosures alone).



The company has recently decided to dial back the benefits for this program, to a simple $100 "finder's fee" for a patent submission, and an additional $900 for a "good" patent. Since employees write these in their spare time, it doesn't surprise me that the number of applications has dropped from 2 per week to maybe 3 per quarter.



Our senior engineer has expressed concern with the company, as he can only make more money by being promoted (our bonus structure is based on length of stay, so employees have to be on board for at least 7 years to earn a decent bonus), and the only offices with openings for higher-level engineering positions would require him and his family to relocate (moving across the country). He's also noted that the decrease in patent-related bonuses hits him hard.



My problem: our senior engineer recently (before the change in benefits) demonstrated some very impressive technology that would speed up a certain process of ours. He also claimed to have written 5 patents associated with it. He's delivered impressive results in the past, so I doubt he was blowing smoke. After the reduction in benefits, he can't seem to recall the patents or find any of the code he used to create his demo. Since he did this all in spare time, it's not in violation of our data retention policies if he just did it all on his home laptop, provided he didn't copy company data to it.



I think he's getting ready to switch jobs, and we need the technical information/code he used to create the demo. His employment agreement states that any and all intellectual property he generates while employed with us, even during weekends/free-time, is the property of the company. IT has searched his OneDrive, laptop, etc., and we can't find a single shred of code/documentation on these ideas. I've tried offering a one-off bonus for him to just anonymously leave a thumb drive with the data on my desk after hours, but he just claims he "doesn't know what I'm talking about".



How can I resolve this?



I can offer a one-off bonus, and I can offer him a significant promotion (but it requires he move to a less desirable part of the country). I can't give him a raise in his current position, and members of senior management no longer trust him due to his "funny" behavior as of late (well has been poisoned a bit). He doesn't want to move at all, and even an offer of $25,000.00 for the IP didn't work, which would have been according to the "old rules". I think he's worried that by agreeing to such a deal, he's opening himself up to legal liability (it would involve indirectly admitting he was being dicey/dishonest about "not knowing what I'm talking about").







conflict company-policy performance benefits intellectual-property






share|improve this question









New contributor




Gen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




Gen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 7 hours ago









Sourav Ghosh

7,20643655




7,20643655






New contributor




Gen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 10 hours ago









GenGen

206125




206125




New contributor




Gen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Gen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Gen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • Comments are not for extended discussion; this conversation has been moved to chat.

    – Mister Positive
    1 hour ago



















  • Comments are not for extended discussion; this conversation has been moved to chat.

    – Mister Positive
    1 hour ago

















Comments are not for extended discussion; this conversation has been moved to chat.

– Mister Positive
1 hour ago





Comments are not for extended discussion; this conversation has been moved to chat.

– Mister Positive
1 hour ago










11 Answers
11






active

oldest

votes


















145














I find it interesting that your company has devalued patents significantly, and then seemed surprised when some of your engineers have decided it's not worth their time.



You talk about trust, but it's evident that the engineer does not trust you, as he opted to lie about forgetting, rather than saying "No thank you. I do not wish to share this work.".



I wonder, did he say "no", and was he forced into saying he forgot because he was threatened either explicitly or implicitly by you or the company?



The very fact you have IT going through everything he has touched at work, presumably for a scrap of proof that will allow you to force him to produce work that he did in his free time suggests to me that he is right to lie, play stupid, and refuse your advances.



The business has made a decision to significantly reduce the benefit for patents. They would have factored in scenarios such as this, as the cost of doing business. There is a chance that you'll lose not just a stream of patents, but engineers. Probably starting with your best ones.



It sounds like you've committed to lose him. Because you wouldn't be treating him like this if you wanted to keep him. Clearly you've put a significant value on some of his work, at the expense all all future work of his, and you'll get neither.



I'd just chalk this off as a learning exercise for the company.






share|improve this answer





















  • 9





    The employee is lying rather than sharing the work because the clause in his contract makes it the companies property. He is legally required to share it if he has it. But if he doesn't remember where it is. . .

    – bruglesco
    7 hours ago






  • 4





    @bruglesco could forgetting where it is be considered contractual negligence?

    – PyRulez
    6 hours ago






  • 1





    @PyRulez IANAL I'm not really sure.

    – bruglesco
    6 hours ago






  • 11





    @PyRulez (again IANAL), but I don't see how — from what the OP has said, it sounds like work that he was doing in his own time. The company could put in a clause around copyright belonging to them on everything you do, but I don't think they could have a clause saying that you have to keep everything you ever do, even out of hours

    – anotherdave
    5 hours ago






  • 3





    If the company somehow decides "forgetting" == "contractual negligence", I suspect it will greatly increase the exodus of the rest of the decent engineers. Who would want to work somewhere where the mere suggestion they forgot something could be held against them, whether it's as a barrier to advancement or a legal liability?

    – gregmac
    2 hours ago



















104














30 patents in two years is roughly $75k a year that's been changed to $15k. So he's been given a $60k a year in pay reduction.



So, yeah, he's probably going to quit and go work for someone else. Further everyone is acting like that's the case. The company's relationship with him is broken, it can't be fixed.




How can I resolve this?




In terms of getting the current code, which he developed on his own time and not on company computers or using company resources:



Wait until he quits, then offer to hire him as a consultant to develop the code you know darn well he has. Let's make some WAGs here. 1000 hours to make this code at $250/hour. So if it's worth $250k to you, offer him that and wait a few months for him to do it so everyone can say with a straight face that he developed it while not under that clause which says the company owns everything in his head while he works for you.






share|improve this answer



















  • 45





    +1 for the "consulting" idea. That's a good way for everyone to have at least a chance to get what they want and it allows everyone to save face in a screwed up situation.

    – Hilmar
    7 hours ago











  • @Hilmar Yes. The problem with most other solutions is they involve not getting into this mess (i.e. time travel) or are things which can't be done because of senior management (SM) restrictions. From SM's stand point they have a disloyal employee and that can't be tolerated so it's just a matter of time before he's fired. So it's either worth serious money for this technology or it's not.

    – Dark Matter
    6 hours ago






  • 3





    Furthermore, this idea could mend the relationship and make it possible to rehire him afterwards, but under more reasonable conditions.

    – d-b
    5 hours ago






  • 2





    I really hope the company does make this formal offer, because it will constitute an acknowledgement that the IP in question belongs de jure to the senior engineer. He will then be free to sell it to the highest bidder.

    – A. I. Breveleri
    4 hours ago













  • @A.I.Breveleri: That is not necessarily the case. The offer may state that the IP as it stands now is not patent-worthy due to formalities (IP lawyer to define those formalities), and that the contract is for the completion of these formal patent requirements, not for the idea itself.

    – MSalters
    54 mins ago



















26















This engineer has filed over 30 successful patents over the past 2 years, and all of these inventions are used in our products.




This was indication enough for your senior management to not to call of the patent encouragement program. The management was somehow unwise enough to change that and put a new policy in place which reduces the benefits of investing time and effort in getting the work done. So, it's no surprise that the people who were "inspired" by the previous program are not interested in continuing with your organization anymore.




His employment agreement states that any and all intellectual property he generates while employed with us, even during weekends/free-time, is the property of the company. IT has searched his OneDrive, laptop, etc., and we can't find a single shred of code/documentation on these ideas.




I don't know why some organization choose to under-estimate the capability of their workforce!! If you believe on that person to be smart enough to deliver the results you described, do you believe he will be fool enough to carry around the pieces of evidence in case he does not want to reveal something? This incident might have just made him more determined to leave the organization, for good.



The situation is tough: the only way this ends with a positive outcome for you and your organization is, ensure the engineer gets treated with the "respect" they deserve. If you think he (and his ideas) is as valuable as you describe, talk to your higher management, and create an exception. Make the old rule part of his contract (as an exception) and mention that now and in future also, he would get benefits as he was getting before the introduction of the change.



Also, ensure that you do not pressurize him to reveal this particular patent. As you mentioned, he might already has a concern of the legal liabilities. If you can make him comfortable enough, in time, he will come out with patent ideas which will help your organization, but allow him the time he needs to "regain" the confidence.



To add a touch of reality: After trying all these damage control and more, if he choose to stay, I'd consider you and your organization incredibly lucky. He added value to your organization, and he was paid off by change in policy which basically invalidates all his effort and talent. Try hard to retain him, but don't get your hopes high.



TL;DR Do not give him the feeling that any of the actions you take to try to retain him is a one-off activity. Show him that the company values him and his contribution, and he is safeguarded against any possible de-valuation of his efforts / contribution. His interests will be taken care of this time and in future, also.






share|improve this answer





















  • 16





    That IP clause is only going to ensure that he never uses the property on his own. It won't compel him to turn over the work. +1

    – bruglesco
    8 hours ago











  • typo. to not to call of => to not call off

    – user21444
    2 hours ago



















24














Your best alternative really sounds like it is for you to walk away; You are throwing good time after bad trying to entice/squeeze your employee for the new patent. Giving it to you now is an admission that he was lying and opens up his legal exposure.




His employment agreement states that any and all intellectual property he generates while employed with us, even during weekends/free-time, is the property of the company.




Invention-rights assignments for off-hours are unenforceable depending on the state. (See, for example, https://law.justia.com/codes/california/2005/lab/2870-2872.html) It really is a signal that your company has a fairly predatory legal culture, or at least an outdated one.






share|improve this answer








New contributor




JP. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • According to the California law you cite, the statutory exclusion does not include inventions which "[r]elate ... to the employer's business, or actual or demonstrably anticipated research or development of the employer", Cal. Labor Code Sec. 2870(a)(1). Here, where the present invention "would speed up a certain process of ours", the statutory exclusion may not apply. If that is the case, then the invention rights assignment would be valid.

    – bdowling
    3 hours ago











  • If the employer written the off-hours invention-rights assignment to reflect that subtlety, I would retract my "predatory legal culture, or at least an outdated one" comment. However, the very general comment by OP is a good indication that he is unaware of the unenforceability issues, and that very specific claims are required. (And to be fair: It's rare for middle managers to have to deal with such minutia.) Naturally, the real determinants are the abilities and resources to litigate, but that is a larger discussion.

    – JP.
    2 hours ago



















11














This is a negotiation. Your senior engineer was doing this work in his spare time in exchange for financial compensation. Your company suddenly changed the price they were willing to pay. Your senior is Not offering the product at that price.



Any attempt to compel him to provide the patents will likely cause him to dig in his heels and also find work elsewhere.



You are raving up and down throughout your entire post about how awesome he is. Find a way to get him his money. He is clearly worth it. Upper management may not be happy with his current stance. It sounds like they are digging in their heels. Negotiation will partly need to be with them. You will need to convince them that smoothing things over with him and his ego are worth it (that's assuming it is, not every brilliant worker is worth the entitlement that pursues them.)



As for him balking at the offer at the previous price, you need to find a way to smooth things over. To assure him that things will be better. Probably now and moving forward. His ego is probably a little (understandably) bruised. So factor that into your attempts to smooth things over. After all the company just drastically devalued the work he was doing. It had to feel like a slap in the face and the wallet. It may also take getting legal reassurances from a lawyer to mitigate his concern for legal liabilities.



(If the promotion with the move is unappealing to him then take it off the table. It has no negotiable value.)






share|improve this answer

































    8














    You solve it by figuring out how to offer this stellar engineer a very large sum of money in terms of a salary to stay on board. If he earned $110k on patents through your company patent program then this guy knows what he is talking about and basically needs to be paid tenure. You then grin and bear it with his recent memory loss.






    share|improve this answer































      5














      Reading through your description of the situation, it is quite obvious that you are a junior manager who is out of his depth.



      Your real problem is not the engineer.
      Your real problem is that you failed as a manager.



      You failed:
      1. the people who you are supposed to manage (you certainly are not a leader, despite the inflation in the terminology today - leader vs. manager) and protect from arbitrarily detrimental decisions of highly placed bean counters
      2. the company - as a manager in the company, you are supposed to act in company's best interests and fight against decisions that are detrimental to the company (as the devaluation of patents obviously is, not because of the value of patents, they have little to none, except in very specific legal situations, but because that policy will cause the best and brightest to leave)
      3. the engineer in question - who is obviously significantly smarter than you are and you do not deserve to be managing someone like him. For his sake, and yours, I hope he sticks to his guns and does not recall any element of that technology he forgot. Your inaction and bad decision making cut his career in your company from underneath him



      Clearly you are not aware of these obligations because noone ever explained them to you.



      At this point all you do is desperately try to save your own next performance review as a manager.



      As to the issue of patents in general - being a fairly prolific patent author myself and serving on various patent review/approval committees, I can claim with confidence that the vast majority of patents are not worth the electronic bits that comprise their description. The vast majority of them are neither novel nor enforceable. The only entities who benefit from patents are the large incorporated entities fighting each other in court for business mistakes that one side made and has no real way of repairing (e.g. Qualcomm vs. Apple cases). The real competitors certainly do not respect or care about any of these patents (e.g. China vs. US).






      share|improve this answer








      New contributor




      Don T. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.
















      • 2





        The first two bits are superb - let's hope the OP reads and understands... plus 1 from me.

        – Solar Mike
        3 hours ago








      • 6





        This answer seems way too harsh. I doubt that OP had any control over the decisions that set this debacle in motion.

        – Jim Clay
        2 hours ago






      • 2





        @JimClay given that the OP is mentioning "how they hope to solve the problem" then they seem to be close to the centre....

        – Solar Mike
        2 hours ago



















      2















      I think he's worried that by agreeing to such a deal, he's opening himself up to legal liability (it would involve indirectly admitting he was being dicey/dishonest about "not knowing what I'm talking about").




      If he is concerned about liability, then why don't you offer him a release or waiver of liability? A lawyer should be able to help you with this.






      share|improve this answer








      New contributor




      bdowling is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




























        0














        He makes the bux. You pass the buck. Looking here for a solution to save your job (or at least look good so you can get a promotion)? Offer to take a pay cut. Or better yet tell senior management to take a pay cut to get the funds to pay this guy. Senior Management is an overpaid cancer. Wait till you find out how expensive it is to do 'design by committee'.






        share|improve this answer








        New contributor




        aquagremlin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.




























          0














          How about talking with him off company property and suggest that you both quit your obviously rotten company and start a competitor?






          share|improve this answer








          New contributor




          Olivercomputing is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.










          We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.










          • 1





            without an explanation, this answer may become useless in case if someone else posts an opposite opinion. For example, if someone posts a claim like "Avoid talking with him off company property and suggesting that you both quit your obviously rotten company and start a competitor.", how would this answer help reader to pick of two opposing opinions? Consider editing it into a better shape, to meet How to Answer guidelines

            – gnat
            2 hours ago



















          -4















          I can offer a one-off bonus, and I can offer him a significant promotion




          As far as I've understood, it's a "cash cow" sutiation for this dude.



          So, it's obvious that he'll be looking for other ways to exploit this opportunity, which will surely end up in leaving your company. Empty handed or not - depends on moral qualities and legal agreements, but I really doubt that a lucrative person will hurt his wallet with moral decisions.



          Everything else is just a personal fear for making hard decisions, that's why you've asked about it in the first place.




          I can't give him a raise in his current position, and members of senior management no longer trust him due to his "funny" behavior




          You'll need to find out another source of motivation - it'll be very tricky, and I really doubt that it would be worthy. Having a "single head of knowledge" and a
          "knight in shining armor" considered as antipatters for a reason. Those mistakes cost from 8 up to 40mil in IBM'ish / wh'Oracle'ish scale.




          doesn't know what I'm talking about




          Playing dumb just proves that it's either "always not enough" game or just a simple bluf - he was trying to be manipulative, but had failed at some point.



          There's a post-soviet "The Tale of the Fisherman and the Fish ", but it's also a set of psychological patterns.



          tldr; People who're playing "always not enough" plate, might not learn a thing even after getting broke.



          It's never too late to make a hard decision, but you'll have to be prepared for what's to come afterwards.




          He's delivered impressive results in the past, so I doubt he was blowing smoke




          Nah... 99% of existing projects are low quality ones.



          I really doubt you've got any DevOps/SRE practices applied, decent code coverage and low tech debt.



          Get to at least 80% code coverage, and verify it with some Mutational tests and Fuzzing, so you'll be able to get rid of the linchpin, and reduce the risks while getting new folks on board.



          Managers are often too dumb even to distinguish between Iterative and Incremental development processes (ask about it someone with an opened "agile bicycle" pic).



          Having a set of "cash cows" will surely result in a professional growth stall, I'd suggest looking for a new guy, preferably a humble one, in the middle of nowhere (just like myself :p).



          It doesn't mean much if stuff just works somehow - longterm support and operational costs can be up to 10 times bigger than the development ones.



          Fix your management first, get rid of Mushroom Management, learn how to invest in People in the first place, so you can keep loyal staff and bus factor more than 1.



          The definition of loyalty may lack due to psychological compensational needs, but that's completely another story.



          Review some of the existing antipatterns and try to fix at least something, before making any life-turning crucial decisions. Improve the quality of the product itself, so you'll be able to get a "Cash Pillow" if things go sideways.



          An Example



          One day.
          There was a smart dude, who prepped a patent for an API based website pre-rendering, and wanted some cash in return from Netflix.



          Without a trial, he handed some of the rights to Netflix, and gotten himself fired (as far as I know). All his prior related network activity for about 2 years (tweets, chat/forum/facebook posts) miraculously disappeared. People were speculating that he's been assassinated etc, but actually he went rouge (i.e converted to facebook).



          BTW google and facebook has the same prerender patents, because US patent laws are crap.



          You may consider exploiting leaky patent formulas and re-patenting stuff for yourself just as a countermeasure... which may result in bribing here and there, but that's how this thing rolls nowadays.






          share|improve this answer










          New contributor




          Yuriy Yarosh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.
















          • 1





            DevOps? Code Coverage? You're assuming things here. Not all code is production code. Plenty of non-IT engineers write code to simulate things, especially for demo's. It's rather expensive to build a chemical plant for a demo, after all.

            – MSalters
            45 mins ago










          protected by Mister Positive 1 hour ago



          Thank you for your interest in this question.
          Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



          Would you like to answer one of these unanswered questions instead?














          11 Answers
          11






          active

          oldest

          votes








          11 Answers
          11






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          145














          I find it interesting that your company has devalued patents significantly, and then seemed surprised when some of your engineers have decided it's not worth their time.



          You talk about trust, but it's evident that the engineer does not trust you, as he opted to lie about forgetting, rather than saying "No thank you. I do not wish to share this work.".



          I wonder, did he say "no", and was he forced into saying he forgot because he was threatened either explicitly or implicitly by you or the company?



          The very fact you have IT going through everything he has touched at work, presumably for a scrap of proof that will allow you to force him to produce work that he did in his free time suggests to me that he is right to lie, play stupid, and refuse your advances.



          The business has made a decision to significantly reduce the benefit for patents. They would have factored in scenarios such as this, as the cost of doing business. There is a chance that you'll lose not just a stream of patents, but engineers. Probably starting with your best ones.



          It sounds like you've committed to lose him. Because you wouldn't be treating him like this if you wanted to keep him. Clearly you've put a significant value on some of his work, at the expense all all future work of his, and you'll get neither.



          I'd just chalk this off as a learning exercise for the company.






          share|improve this answer





















          • 9





            The employee is lying rather than sharing the work because the clause in his contract makes it the companies property. He is legally required to share it if he has it. But if he doesn't remember where it is. . .

            – bruglesco
            7 hours ago






          • 4





            @bruglesco could forgetting where it is be considered contractual negligence?

            – PyRulez
            6 hours ago






          • 1





            @PyRulez IANAL I'm not really sure.

            – bruglesco
            6 hours ago






          • 11





            @PyRulez (again IANAL), but I don't see how — from what the OP has said, it sounds like work that he was doing in his own time. The company could put in a clause around copyright belonging to them on everything you do, but I don't think they could have a clause saying that you have to keep everything you ever do, even out of hours

            – anotherdave
            5 hours ago






          • 3





            If the company somehow decides "forgetting" == "contractual negligence", I suspect it will greatly increase the exodus of the rest of the decent engineers. Who would want to work somewhere where the mere suggestion they forgot something could be held against them, whether it's as a barrier to advancement or a legal liability?

            – gregmac
            2 hours ago
















          145














          I find it interesting that your company has devalued patents significantly, and then seemed surprised when some of your engineers have decided it's not worth their time.



          You talk about trust, but it's evident that the engineer does not trust you, as he opted to lie about forgetting, rather than saying "No thank you. I do not wish to share this work.".



          I wonder, did he say "no", and was he forced into saying he forgot because he was threatened either explicitly or implicitly by you or the company?



          The very fact you have IT going through everything he has touched at work, presumably for a scrap of proof that will allow you to force him to produce work that he did in his free time suggests to me that he is right to lie, play stupid, and refuse your advances.



          The business has made a decision to significantly reduce the benefit for patents. They would have factored in scenarios such as this, as the cost of doing business. There is a chance that you'll lose not just a stream of patents, but engineers. Probably starting with your best ones.



          It sounds like you've committed to lose him. Because you wouldn't be treating him like this if you wanted to keep him. Clearly you've put a significant value on some of his work, at the expense all all future work of his, and you'll get neither.



          I'd just chalk this off as a learning exercise for the company.






          share|improve this answer





















          • 9





            The employee is lying rather than sharing the work because the clause in his contract makes it the companies property. He is legally required to share it if he has it. But if he doesn't remember where it is. . .

            – bruglesco
            7 hours ago






          • 4





            @bruglesco could forgetting where it is be considered contractual negligence?

            – PyRulez
            6 hours ago






          • 1





            @PyRulez IANAL I'm not really sure.

            – bruglesco
            6 hours ago






          • 11





            @PyRulez (again IANAL), but I don't see how — from what the OP has said, it sounds like work that he was doing in his own time. The company could put in a clause around copyright belonging to them on everything you do, but I don't think they could have a clause saying that you have to keep everything you ever do, even out of hours

            – anotherdave
            5 hours ago






          • 3





            If the company somehow decides "forgetting" == "contractual negligence", I suspect it will greatly increase the exodus of the rest of the decent engineers. Who would want to work somewhere where the mere suggestion they forgot something could be held against them, whether it's as a barrier to advancement or a legal liability?

            – gregmac
            2 hours ago














          145












          145








          145







          I find it interesting that your company has devalued patents significantly, and then seemed surprised when some of your engineers have decided it's not worth their time.



          You talk about trust, but it's evident that the engineer does not trust you, as he opted to lie about forgetting, rather than saying "No thank you. I do not wish to share this work.".



          I wonder, did he say "no", and was he forced into saying he forgot because he was threatened either explicitly or implicitly by you or the company?



          The very fact you have IT going through everything he has touched at work, presumably for a scrap of proof that will allow you to force him to produce work that he did in his free time suggests to me that he is right to lie, play stupid, and refuse your advances.



          The business has made a decision to significantly reduce the benefit for patents. They would have factored in scenarios such as this, as the cost of doing business. There is a chance that you'll lose not just a stream of patents, but engineers. Probably starting with your best ones.



          It sounds like you've committed to lose him. Because you wouldn't be treating him like this if you wanted to keep him. Clearly you've put a significant value on some of his work, at the expense all all future work of his, and you'll get neither.



          I'd just chalk this off as a learning exercise for the company.






          share|improve this answer















          I find it interesting that your company has devalued patents significantly, and then seemed surprised when some of your engineers have decided it's not worth their time.



          You talk about trust, but it's evident that the engineer does not trust you, as he opted to lie about forgetting, rather than saying "No thank you. I do not wish to share this work.".



          I wonder, did he say "no", and was he forced into saying he forgot because he was threatened either explicitly or implicitly by you or the company?



          The very fact you have IT going through everything he has touched at work, presumably for a scrap of proof that will allow you to force him to produce work that he did in his free time suggests to me that he is right to lie, play stupid, and refuse your advances.



          The business has made a decision to significantly reduce the benefit for patents. They would have factored in scenarios such as this, as the cost of doing business. There is a chance that you'll lose not just a stream of patents, but engineers. Probably starting with your best ones.



          It sounds like you've committed to lose him. Because you wouldn't be treating him like this if you wanted to keep him. Clearly you've put a significant value on some of his work, at the expense all all future work of his, and you'll get neither.



          I'd just chalk this off as a learning exercise for the company.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 5 hours ago









          yoozer8

          4,17643056




          4,17643056










          answered 8 hours ago









          Gregory CurrieGregory Currie

          3,51072032




          3,51072032








          • 9





            The employee is lying rather than sharing the work because the clause in his contract makes it the companies property. He is legally required to share it if he has it. But if he doesn't remember where it is. . .

            – bruglesco
            7 hours ago






          • 4





            @bruglesco could forgetting where it is be considered contractual negligence?

            – PyRulez
            6 hours ago






          • 1





            @PyRulez IANAL I'm not really sure.

            – bruglesco
            6 hours ago






          • 11





            @PyRulez (again IANAL), but I don't see how — from what the OP has said, it sounds like work that he was doing in his own time. The company could put in a clause around copyright belonging to them on everything you do, but I don't think they could have a clause saying that you have to keep everything you ever do, even out of hours

            – anotherdave
            5 hours ago






          • 3





            If the company somehow decides "forgetting" == "contractual negligence", I suspect it will greatly increase the exodus of the rest of the decent engineers. Who would want to work somewhere where the mere suggestion they forgot something could be held against them, whether it's as a barrier to advancement or a legal liability?

            – gregmac
            2 hours ago














          • 9





            The employee is lying rather than sharing the work because the clause in his contract makes it the companies property. He is legally required to share it if he has it. But if he doesn't remember where it is. . .

            – bruglesco
            7 hours ago






          • 4





            @bruglesco could forgetting where it is be considered contractual negligence?

            – PyRulez
            6 hours ago






          • 1





            @PyRulez IANAL I'm not really sure.

            – bruglesco
            6 hours ago






          • 11





            @PyRulez (again IANAL), but I don't see how — from what the OP has said, it sounds like work that he was doing in his own time. The company could put in a clause around copyright belonging to them on everything you do, but I don't think they could have a clause saying that you have to keep everything you ever do, even out of hours

            – anotherdave
            5 hours ago






          • 3





            If the company somehow decides "forgetting" == "contractual negligence", I suspect it will greatly increase the exodus of the rest of the decent engineers. Who would want to work somewhere where the mere suggestion they forgot something could be held against them, whether it's as a barrier to advancement or a legal liability?

            – gregmac
            2 hours ago








          9




          9





          The employee is lying rather than sharing the work because the clause in his contract makes it the companies property. He is legally required to share it if he has it. But if he doesn't remember where it is. . .

          – bruglesco
          7 hours ago





          The employee is lying rather than sharing the work because the clause in his contract makes it the companies property. He is legally required to share it if he has it. But if he doesn't remember where it is. . .

          – bruglesco
          7 hours ago




          4




          4





          @bruglesco could forgetting where it is be considered contractual negligence?

          – PyRulez
          6 hours ago





          @bruglesco could forgetting where it is be considered contractual negligence?

          – PyRulez
          6 hours ago




          1




          1





          @PyRulez IANAL I'm not really sure.

          – bruglesco
          6 hours ago





          @PyRulez IANAL I'm not really sure.

          – bruglesco
          6 hours ago




          11




          11





          @PyRulez (again IANAL), but I don't see how — from what the OP has said, it sounds like work that he was doing in his own time. The company could put in a clause around copyright belonging to them on everything you do, but I don't think they could have a clause saying that you have to keep everything you ever do, even out of hours

          – anotherdave
          5 hours ago





          @PyRulez (again IANAL), but I don't see how — from what the OP has said, it sounds like work that he was doing in his own time. The company could put in a clause around copyright belonging to them on everything you do, but I don't think they could have a clause saying that you have to keep everything you ever do, even out of hours

          – anotherdave
          5 hours ago




          3




          3





          If the company somehow decides "forgetting" == "contractual negligence", I suspect it will greatly increase the exodus of the rest of the decent engineers. Who would want to work somewhere where the mere suggestion they forgot something could be held against them, whether it's as a barrier to advancement or a legal liability?

          – gregmac
          2 hours ago





          If the company somehow decides "forgetting" == "contractual negligence", I suspect it will greatly increase the exodus of the rest of the decent engineers. Who would want to work somewhere where the mere suggestion they forgot something could be held against them, whether it's as a barrier to advancement or a legal liability?

          – gregmac
          2 hours ago













          104














          30 patents in two years is roughly $75k a year that's been changed to $15k. So he's been given a $60k a year in pay reduction.



          So, yeah, he's probably going to quit and go work for someone else. Further everyone is acting like that's the case. The company's relationship with him is broken, it can't be fixed.




          How can I resolve this?




          In terms of getting the current code, which he developed on his own time and not on company computers or using company resources:



          Wait until he quits, then offer to hire him as a consultant to develop the code you know darn well he has. Let's make some WAGs here. 1000 hours to make this code at $250/hour. So if it's worth $250k to you, offer him that and wait a few months for him to do it so everyone can say with a straight face that he developed it while not under that clause which says the company owns everything in his head while he works for you.






          share|improve this answer



















          • 45





            +1 for the "consulting" idea. That's a good way for everyone to have at least a chance to get what they want and it allows everyone to save face in a screwed up situation.

            – Hilmar
            7 hours ago











          • @Hilmar Yes. The problem with most other solutions is they involve not getting into this mess (i.e. time travel) or are things which can't be done because of senior management (SM) restrictions. From SM's stand point they have a disloyal employee and that can't be tolerated so it's just a matter of time before he's fired. So it's either worth serious money for this technology or it's not.

            – Dark Matter
            6 hours ago






          • 3





            Furthermore, this idea could mend the relationship and make it possible to rehire him afterwards, but under more reasonable conditions.

            – d-b
            5 hours ago






          • 2





            I really hope the company does make this formal offer, because it will constitute an acknowledgement that the IP in question belongs de jure to the senior engineer. He will then be free to sell it to the highest bidder.

            – A. I. Breveleri
            4 hours ago













          • @A.I.Breveleri: That is not necessarily the case. The offer may state that the IP as it stands now is not patent-worthy due to formalities (IP lawyer to define those formalities), and that the contract is for the completion of these formal patent requirements, not for the idea itself.

            – MSalters
            54 mins ago
















          104














          30 patents in two years is roughly $75k a year that's been changed to $15k. So he's been given a $60k a year in pay reduction.



          So, yeah, he's probably going to quit and go work for someone else. Further everyone is acting like that's the case. The company's relationship with him is broken, it can't be fixed.




          How can I resolve this?




          In terms of getting the current code, which he developed on his own time and not on company computers or using company resources:



          Wait until he quits, then offer to hire him as a consultant to develop the code you know darn well he has. Let's make some WAGs here. 1000 hours to make this code at $250/hour. So if it's worth $250k to you, offer him that and wait a few months for him to do it so everyone can say with a straight face that he developed it while not under that clause which says the company owns everything in his head while he works for you.






          share|improve this answer



















          • 45





            +1 for the "consulting" idea. That's a good way for everyone to have at least a chance to get what they want and it allows everyone to save face in a screwed up situation.

            – Hilmar
            7 hours ago











          • @Hilmar Yes. The problem with most other solutions is they involve not getting into this mess (i.e. time travel) or are things which can't be done because of senior management (SM) restrictions. From SM's stand point they have a disloyal employee and that can't be tolerated so it's just a matter of time before he's fired. So it's either worth serious money for this technology or it's not.

            – Dark Matter
            6 hours ago






          • 3





            Furthermore, this idea could mend the relationship and make it possible to rehire him afterwards, but under more reasonable conditions.

            – d-b
            5 hours ago






          • 2





            I really hope the company does make this formal offer, because it will constitute an acknowledgement that the IP in question belongs de jure to the senior engineer. He will then be free to sell it to the highest bidder.

            – A. I. Breveleri
            4 hours ago













          • @A.I.Breveleri: That is not necessarily the case. The offer may state that the IP as it stands now is not patent-worthy due to formalities (IP lawyer to define those formalities), and that the contract is for the completion of these formal patent requirements, not for the idea itself.

            – MSalters
            54 mins ago














          104












          104








          104







          30 patents in two years is roughly $75k a year that's been changed to $15k. So he's been given a $60k a year in pay reduction.



          So, yeah, he's probably going to quit and go work for someone else. Further everyone is acting like that's the case. The company's relationship with him is broken, it can't be fixed.




          How can I resolve this?




          In terms of getting the current code, which he developed on his own time and not on company computers or using company resources:



          Wait until he quits, then offer to hire him as a consultant to develop the code you know darn well he has. Let's make some WAGs here. 1000 hours to make this code at $250/hour. So if it's worth $250k to you, offer him that and wait a few months for him to do it so everyone can say with a straight face that he developed it while not under that clause which says the company owns everything in his head while he works for you.






          share|improve this answer













          30 patents in two years is roughly $75k a year that's been changed to $15k. So he's been given a $60k a year in pay reduction.



          So, yeah, he's probably going to quit and go work for someone else. Further everyone is acting like that's the case. The company's relationship with him is broken, it can't be fixed.




          How can I resolve this?




          In terms of getting the current code, which he developed on his own time and not on company computers or using company resources:



          Wait until he quits, then offer to hire him as a consultant to develop the code you know darn well he has. Let's make some WAGs here. 1000 hours to make this code at $250/hour. So if it's worth $250k to you, offer him that and wait a few months for him to do it so everyone can say with a straight face that he developed it while not under that clause which says the company owns everything in his head while he works for you.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 7 hours ago









          Dark Matter Dark Matter

          4,96121122




          4,96121122








          • 45





            +1 for the "consulting" idea. That's a good way for everyone to have at least a chance to get what they want and it allows everyone to save face in a screwed up situation.

            – Hilmar
            7 hours ago











          • @Hilmar Yes. The problem with most other solutions is they involve not getting into this mess (i.e. time travel) or are things which can't be done because of senior management (SM) restrictions. From SM's stand point they have a disloyal employee and that can't be tolerated so it's just a matter of time before he's fired. So it's either worth serious money for this technology or it's not.

            – Dark Matter
            6 hours ago






          • 3





            Furthermore, this idea could mend the relationship and make it possible to rehire him afterwards, but under more reasonable conditions.

            – d-b
            5 hours ago






          • 2





            I really hope the company does make this formal offer, because it will constitute an acknowledgement that the IP in question belongs de jure to the senior engineer. He will then be free to sell it to the highest bidder.

            – A. I. Breveleri
            4 hours ago













          • @A.I.Breveleri: That is not necessarily the case. The offer may state that the IP as it stands now is not patent-worthy due to formalities (IP lawyer to define those formalities), and that the contract is for the completion of these formal patent requirements, not for the idea itself.

            – MSalters
            54 mins ago














          • 45





            +1 for the "consulting" idea. That's a good way for everyone to have at least a chance to get what they want and it allows everyone to save face in a screwed up situation.

            – Hilmar
            7 hours ago











          • @Hilmar Yes. The problem with most other solutions is they involve not getting into this mess (i.e. time travel) or are things which can't be done because of senior management (SM) restrictions. From SM's stand point they have a disloyal employee and that can't be tolerated so it's just a matter of time before he's fired. So it's either worth serious money for this technology or it's not.

            – Dark Matter
            6 hours ago






          • 3





            Furthermore, this idea could mend the relationship and make it possible to rehire him afterwards, but under more reasonable conditions.

            – d-b
            5 hours ago






          • 2





            I really hope the company does make this formal offer, because it will constitute an acknowledgement that the IP in question belongs de jure to the senior engineer. He will then be free to sell it to the highest bidder.

            – A. I. Breveleri
            4 hours ago













          • @A.I.Breveleri: That is not necessarily the case. The offer may state that the IP as it stands now is not patent-worthy due to formalities (IP lawyer to define those formalities), and that the contract is for the completion of these formal patent requirements, not for the idea itself.

            – MSalters
            54 mins ago








          45




          45





          +1 for the "consulting" idea. That's a good way for everyone to have at least a chance to get what they want and it allows everyone to save face in a screwed up situation.

          – Hilmar
          7 hours ago





          +1 for the "consulting" idea. That's a good way for everyone to have at least a chance to get what they want and it allows everyone to save face in a screwed up situation.

          – Hilmar
          7 hours ago













          @Hilmar Yes. The problem with most other solutions is they involve not getting into this mess (i.e. time travel) or are things which can't be done because of senior management (SM) restrictions. From SM's stand point they have a disloyal employee and that can't be tolerated so it's just a matter of time before he's fired. So it's either worth serious money for this technology or it's not.

          – Dark Matter
          6 hours ago





          @Hilmar Yes. The problem with most other solutions is they involve not getting into this mess (i.e. time travel) or are things which can't be done because of senior management (SM) restrictions. From SM's stand point they have a disloyal employee and that can't be tolerated so it's just a matter of time before he's fired. So it's either worth serious money for this technology or it's not.

          – Dark Matter
          6 hours ago




          3




          3





          Furthermore, this idea could mend the relationship and make it possible to rehire him afterwards, but under more reasonable conditions.

          – d-b
          5 hours ago





          Furthermore, this idea could mend the relationship and make it possible to rehire him afterwards, but under more reasonable conditions.

          – d-b
          5 hours ago




          2




          2





          I really hope the company does make this formal offer, because it will constitute an acknowledgement that the IP in question belongs de jure to the senior engineer. He will then be free to sell it to the highest bidder.

          – A. I. Breveleri
          4 hours ago







          I really hope the company does make this formal offer, because it will constitute an acknowledgement that the IP in question belongs de jure to the senior engineer. He will then be free to sell it to the highest bidder.

          – A. I. Breveleri
          4 hours ago















          @A.I.Breveleri: That is not necessarily the case. The offer may state that the IP as it stands now is not patent-worthy due to formalities (IP lawyer to define those formalities), and that the contract is for the completion of these formal patent requirements, not for the idea itself.

          – MSalters
          54 mins ago





          @A.I.Breveleri: That is not necessarily the case. The offer may state that the IP as it stands now is not patent-worthy due to formalities (IP lawyer to define those formalities), and that the contract is for the completion of these formal patent requirements, not for the idea itself.

          – MSalters
          54 mins ago











          26















          This engineer has filed over 30 successful patents over the past 2 years, and all of these inventions are used in our products.




          This was indication enough for your senior management to not to call of the patent encouragement program. The management was somehow unwise enough to change that and put a new policy in place which reduces the benefits of investing time and effort in getting the work done. So, it's no surprise that the people who were "inspired" by the previous program are not interested in continuing with your organization anymore.




          His employment agreement states that any and all intellectual property he generates while employed with us, even during weekends/free-time, is the property of the company. IT has searched his OneDrive, laptop, etc., and we can't find a single shred of code/documentation on these ideas.




          I don't know why some organization choose to under-estimate the capability of their workforce!! If you believe on that person to be smart enough to deliver the results you described, do you believe he will be fool enough to carry around the pieces of evidence in case he does not want to reveal something? This incident might have just made him more determined to leave the organization, for good.



          The situation is tough: the only way this ends with a positive outcome for you and your organization is, ensure the engineer gets treated with the "respect" they deserve. If you think he (and his ideas) is as valuable as you describe, talk to your higher management, and create an exception. Make the old rule part of his contract (as an exception) and mention that now and in future also, he would get benefits as he was getting before the introduction of the change.



          Also, ensure that you do not pressurize him to reveal this particular patent. As you mentioned, he might already has a concern of the legal liabilities. If you can make him comfortable enough, in time, he will come out with patent ideas which will help your organization, but allow him the time he needs to "regain" the confidence.



          To add a touch of reality: After trying all these damage control and more, if he choose to stay, I'd consider you and your organization incredibly lucky. He added value to your organization, and he was paid off by change in policy which basically invalidates all his effort and talent. Try hard to retain him, but don't get your hopes high.



          TL;DR Do not give him the feeling that any of the actions you take to try to retain him is a one-off activity. Show him that the company values him and his contribution, and he is safeguarded against any possible de-valuation of his efforts / contribution. His interests will be taken care of this time and in future, also.






          share|improve this answer





















          • 16





            That IP clause is only going to ensure that he never uses the property on his own. It won't compel him to turn over the work. +1

            – bruglesco
            8 hours ago











          • typo. to not to call of => to not call off

            – user21444
            2 hours ago
















          26















          This engineer has filed over 30 successful patents over the past 2 years, and all of these inventions are used in our products.




          This was indication enough for your senior management to not to call of the patent encouragement program. The management was somehow unwise enough to change that and put a new policy in place which reduces the benefits of investing time and effort in getting the work done. So, it's no surprise that the people who were "inspired" by the previous program are not interested in continuing with your organization anymore.




          His employment agreement states that any and all intellectual property he generates while employed with us, even during weekends/free-time, is the property of the company. IT has searched his OneDrive, laptop, etc., and we can't find a single shred of code/documentation on these ideas.




          I don't know why some organization choose to under-estimate the capability of their workforce!! If you believe on that person to be smart enough to deliver the results you described, do you believe he will be fool enough to carry around the pieces of evidence in case he does not want to reveal something? This incident might have just made him more determined to leave the organization, for good.



          The situation is tough: the only way this ends with a positive outcome for you and your organization is, ensure the engineer gets treated with the "respect" they deserve. If you think he (and his ideas) is as valuable as you describe, talk to your higher management, and create an exception. Make the old rule part of his contract (as an exception) and mention that now and in future also, he would get benefits as he was getting before the introduction of the change.



          Also, ensure that you do not pressurize him to reveal this particular patent. As you mentioned, he might already has a concern of the legal liabilities. If you can make him comfortable enough, in time, he will come out with patent ideas which will help your organization, but allow him the time he needs to "regain" the confidence.



          To add a touch of reality: After trying all these damage control and more, if he choose to stay, I'd consider you and your organization incredibly lucky. He added value to your organization, and he was paid off by change in policy which basically invalidates all his effort and talent. Try hard to retain him, but don't get your hopes high.



          TL;DR Do not give him the feeling that any of the actions you take to try to retain him is a one-off activity. Show him that the company values him and his contribution, and he is safeguarded against any possible de-valuation of his efforts / contribution. His interests will be taken care of this time and in future, also.






          share|improve this answer





















          • 16





            That IP clause is only going to ensure that he never uses the property on his own. It won't compel him to turn over the work. +1

            – bruglesco
            8 hours ago











          • typo. to not to call of => to not call off

            – user21444
            2 hours ago














          26












          26








          26








          This engineer has filed over 30 successful patents over the past 2 years, and all of these inventions are used in our products.




          This was indication enough for your senior management to not to call of the patent encouragement program. The management was somehow unwise enough to change that and put a new policy in place which reduces the benefits of investing time and effort in getting the work done. So, it's no surprise that the people who were "inspired" by the previous program are not interested in continuing with your organization anymore.




          His employment agreement states that any and all intellectual property he generates while employed with us, even during weekends/free-time, is the property of the company. IT has searched his OneDrive, laptop, etc., and we can't find a single shred of code/documentation on these ideas.




          I don't know why some organization choose to under-estimate the capability of their workforce!! If you believe on that person to be smart enough to deliver the results you described, do you believe he will be fool enough to carry around the pieces of evidence in case he does not want to reveal something? This incident might have just made him more determined to leave the organization, for good.



          The situation is tough: the only way this ends with a positive outcome for you and your organization is, ensure the engineer gets treated with the "respect" they deserve. If you think he (and his ideas) is as valuable as you describe, talk to your higher management, and create an exception. Make the old rule part of his contract (as an exception) and mention that now and in future also, he would get benefits as he was getting before the introduction of the change.



          Also, ensure that you do not pressurize him to reveal this particular patent. As you mentioned, he might already has a concern of the legal liabilities. If you can make him comfortable enough, in time, he will come out with patent ideas which will help your organization, but allow him the time he needs to "regain" the confidence.



          To add a touch of reality: After trying all these damage control and more, if he choose to stay, I'd consider you and your organization incredibly lucky. He added value to your organization, and he was paid off by change in policy which basically invalidates all his effort and talent. Try hard to retain him, but don't get your hopes high.



          TL;DR Do not give him the feeling that any of the actions you take to try to retain him is a one-off activity. Show him that the company values him and his contribution, and he is safeguarded against any possible de-valuation of his efforts / contribution. His interests will be taken care of this time and in future, also.






          share|improve this answer
















          This engineer has filed over 30 successful patents over the past 2 years, and all of these inventions are used in our products.




          This was indication enough for your senior management to not to call of the patent encouragement program. The management was somehow unwise enough to change that and put a new policy in place which reduces the benefits of investing time and effort in getting the work done. So, it's no surprise that the people who were "inspired" by the previous program are not interested in continuing with your organization anymore.




          His employment agreement states that any and all intellectual property he generates while employed with us, even during weekends/free-time, is the property of the company. IT has searched his OneDrive, laptop, etc., and we can't find a single shred of code/documentation on these ideas.




          I don't know why some organization choose to under-estimate the capability of their workforce!! If you believe on that person to be smart enough to deliver the results you described, do you believe he will be fool enough to carry around the pieces of evidence in case he does not want to reveal something? This incident might have just made him more determined to leave the organization, for good.



          The situation is tough: the only way this ends with a positive outcome for you and your organization is, ensure the engineer gets treated with the "respect" they deserve. If you think he (and his ideas) is as valuable as you describe, talk to your higher management, and create an exception. Make the old rule part of his contract (as an exception) and mention that now and in future also, he would get benefits as he was getting before the introduction of the change.



          Also, ensure that you do not pressurize him to reveal this particular patent. As you mentioned, he might already has a concern of the legal liabilities. If you can make him comfortable enough, in time, he will come out with patent ideas which will help your organization, but allow him the time he needs to "regain" the confidence.



          To add a touch of reality: After trying all these damage control and more, if he choose to stay, I'd consider you and your organization incredibly lucky. He added value to your organization, and he was paid off by change in policy which basically invalidates all his effort and talent. Try hard to retain him, but don't get your hopes high.



          TL;DR Do not give him the feeling that any of the actions you take to try to retain him is a one-off activity. Show him that the company values him and his contribution, and he is safeguarded against any possible de-valuation of his efforts / contribution. His interests will be taken care of this time and in future, also.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 7 hours ago

























          answered 8 hours ago









          Sourav GhoshSourav Ghosh

          7,20643655




          7,20643655








          • 16





            That IP clause is only going to ensure that he never uses the property on his own. It won't compel him to turn over the work. +1

            – bruglesco
            8 hours ago











          • typo. to not to call of => to not call off

            – user21444
            2 hours ago














          • 16





            That IP clause is only going to ensure that he never uses the property on his own. It won't compel him to turn over the work. +1

            – bruglesco
            8 hours ago











          • typo. to not to call of => to not call off

            – user21444
            2 hours ago








          16




          16





          That IP clause is only going to ensure that he never uses the property on his own. It won't compel him to turn over the work. +1

          – bruglesco
          8 hours ago





          That IP clause is only going to ensure that he never uses the property on his own. It won't compel him to turn over the work. +1

          – bruglesco
          8 hours ago













          typo. to not to call of => to not call off

          – user21444
          2 hours ago





          typo. to not to call of => to not call off

          – user21444
          2 hours ago











          24














          Your best alternative really sounds like it is for you to walk away; You are throwing good time after bad trying to entice/squeeze your employee for the new patent. Giving it to you now is an admission that he was lying and opens up his legal exposure.




          His employment agreement states that any and all intellectual property he generates while employed with us, even during weekends/free-time, is the property of the company.




          Invention-rights assignments for off-hours are unenforceable depending on the state. (See, for example, https://law.justia.com/codes/california/2005/lab/2870-2872.html) It really is a signal that your company has a fairly predatory legal culture, or at least an outdated one.






          share|improve this answer








          New contributor




          JP. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.





















          • According to the California law you cite, the statutory exclusion does not include inventions which "[r]elate ... to the employer's business, or actual or demonstrably anticipated research or development of the employer", Cal. Labor Code Sec. 2870(a)(1). Here, where the present invention "would speed up a certain process of ours", the statutory exclusion may not apply. If that is the case, then the invention rights assignment would be valid.

            – bdowling
            3 hours ago











          • If the employer written the off-hours invention-rights assignment to reflect that subtlety, I would retract my "predatory legal culture, or at least an outdated one" comment. However, the very general comment by OP is a good indication that he is unaware of the unenforceability issues, and that very specific claims are required. (And to be fair: It's rare for middle managers to have to deal with such minutia.) Naturally, the real determinants are the abilities and resources to litigate, but that is a larger discussion.

            – JP.
            2 hours ago
















          24














          Your best alternative really sounds like it is for you to walk away; You are throwing good time after bad trying to entice/squeeze your employee for the new patent. Giving it to you now is an admission that he was lying and opens up his legal exposure.




          His employment agreement states that any and all intellectual property he generates while employed with us, even during weekends/free-time, is the property of the company.




          Invention-rights assignments for off-hours are unenforceable depending on the state. (See, for example, https://law.justia.com/codes/california/2005/lab/2870-2872.html) It really is a signal that your company has a fairly predatory legal culture, or at least an outdated one.






          share|improve this answer








          New contributor




          JP. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.





















          • According to the California law you cite, the statutory exclusion does not include inventions which "[r]elate ... to the employer's business, or actual or demonstrably anticipated research or development of the employer", Cal. Labor Code Sec. 2870(a)(1). Here, where the present invention "would speed up a certain process of ours", the statutory exclusion may not apply. If that is the case, then the invention rights assignment would be valid.

            – bdowling
            3 hours ago











          • If the employer written the off-hours invention-rights assignment to reflect that subtlety, I would retract my "predatory legal culture, or at least an outdated one" comment. However, the very general comment by OP is a good indication that he is unaware of the unenforceability issues, and that very specific claims are required. (And to be fair: It's rare for middle managers to have to deal with such minutia.) Naturally, the real determinants are the abilities and resources to litigate, but that is a larger discussion.

            – JP.
            2 hours ago














          24












          24








          24







          Your best alternative really sounds like it is for you to walk away; You are throwing good time after bad trying to entice/squeeze your employee for the new patent. Giving it to you now is an admission that he was lying and opens up his legal exposure.




          His employment agreement states that any and all intellectual property he generates while employed with us, even during weekends/free-time, is the property of the company.




          Invention-rights assignments for off-hours are unenforceable depending on the state. (See, for example, https://law.justia.com/codes/california/2005/lab/2870-2872.html) It really is a signal that your company has a fairly predatory legal culture, or at least an outdated one.






          share|improve this answer








          New contributor




          JP. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.










          Your best alternative really sounds like it is for you to walk away; You are throwing good time after bad trying to entice/squeeze your employee for the new patent. Giving it to you now is an admission that he was lying and opens up his legal exposure.




          His employment agreement states that any and all intellectual property he generates while employed with us, even during weekends/free-time, is the property of the company.




          Invention-rights assignments for off-hours are unenforceable depending on the state. (See, for example, https://law.justia.com/codes/california/2005/lab/2870-2872.html) It really is a signal that your company has a fairly predatory legal culture, or at least an outdated one.







          share|improve this answer








          New contributor




          JP. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.









          share|improve this answer



          share|improve this answer






          New contributor




          JP. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.









          answered 5 hours ago









          JP.JP.

          3115




          3115




          New contributor




          JP. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.





          New contributor





          JP. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.






          JP. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.













          • According to the California law you cite, the statutory exclusion does not include inventions which "[r]elate ... to the employer's business, or actual or demonstrably anticipated research or development of the employer", Cal. Labor Code Sec. 2870(a)(1). Here, where the present invention "would speed up a certain process of ours", the statutory exclusion may not apply. If that is the case, then the invention rights assignment would be valid.

            – bdowling
            3 hours ago











          • If the employer written the off-hours invention-rights assignment to reflect that subtlety, I would retract my "predatory legal culture, or at least an outdated one" comment. However, the very general comment by OP is a good indication that he is unaware of the unenforceability issues, and that very specific claims are required. (And to be fair: It's rare for middle managers to have to deal with such minutia.) Naturally, the real determinants are the abilities and resources to litigate, but that is a larger discussion.

            – JP.
            2 hours ago



















          • According to the California law you cite, the statutory exclusion does not include inventions which "[r]elate ... to the employer's business, or actual or demonstrably anticipated research or development of the employer", Cal. Labor Code Sec. 2870(a)(1). Here, where the present invention "would speed up a certain process of ours", the statutory exclusion may not apply. If that is the case, then the invention rights assignment would be valid.

            – bdowling
            3 hours ago











          • If the employer written the off-hours invention-rights assignment to reflect that subtlety, I would retract my "predatory legal culture, or at least an outdated one" comment. However, the very general comment by OP is a good indication that he is unaware of the unenforceability issues, and that very specific claims are required. (And to be fair: It's rare for middle managers to have to deal with such minutia.) Naturally, the real determinants are the abilities and resources to litigate, but that is a larger discussion.

            – JP.
            2 hours ago

















          According to the California law you cite, the statutory exclusion does not include inventions which "[r]elate ... to the employer's business, or actual or demonstrably anticipated research or development of the employer", Cal. Labor Code Sec. 2870(a)(1). Here, where the present invention "would speed up a certain process of ours", the statutory exclusion may not apply. If that is the case, then the invention rights assignment would be valid.

          – bdowling
          3 hours ago





          According to the California law you cite, the statutory exclusion does not include inventions which "[r]elate ... to the employer's business, or actual or demonstrably anticipated research or development of the employer", Cal. Labor Code Sec. 2870(a)(1). Here, where the present invention "would speed up a certain process of ours", the statutory exclusion may not apply. If that is the case, then the invention rights assignment would be valid.

          – bdowling
          3 hours ago













          If the employer written the off-hours invention-rights assignment to reflect that subtlety, I would retract my "predatory legal culture, or at least an outdated one" comment. However, the very general comment by OP is a good indication that he is unaware of the unenforceability issues, and that very specific claims are required. (And to be fair: It's rare for middle managers to have to deal with such minutia.) Naturally, the real determinants are the abilities and resources to litigate, but that is a larger discussion.

          – JP.
          2 hours ago





          If the employer written the off-hours invention-rights assignment to reflect that subtlety, I would retract my "predatory legal culture, or at least an outdated one" comment. However, the very general comment by OP is a good indication that he is unaware of the unenforceability issues, and that very specific claims are required. (And to be fair: It's rare for middle managers to have to deal with such minutia.) Naturally, the real determinants are the abilities and resources to litigate, but that is a larger discussion.

          – JP.
          2 hours ago











          11














          This is a negotiation. Your senior engineer was doing this work in his spare time in exchange for financial compensation. Your company suddenly changed the price they were willing to pay. Your senior is Not offering the product at that price.



          Any attempt to compel him to provide the patents will likely cause him to dig in his heels and also find work elsewhere.



          You are raving up and down throughout your entire post about how awesome he is. Find a way to get him his money. He is clearly worth it. Upper management may not be happy with his current stance. It sounds like they are digging in their heels. Negotiation will partly need to be with them. You will need to convince them that smoothing things over with him and his ego are worth it (that's assuming it is, not every brilliant worker is worth the entitlement that pursues them.)



          As for him balking at the offer at the previous price, you need to find a way to smooth things over. To assure him that things will be better. Probably now and moving forward. His ego is probably a little (understandably) bruised. So factor that into your attempts to smooth things over. After all the company just drastically devalued the work he was doing. It had to feel like a slap in the face and the wallet. It may also take getting legal reassurances from a lawyer to mitigate his concern for legal liabilities.



          (If the promotion with the move is unappealing to him then take it off the table. It has no negotiable value.)






          share|improve this answer






























            11














            This is a negotiation. Your senior engineer was doing this work in his spare time in exchange for financial compensation. Your company suddenly changed the price they were willing to pay. Your senior is Not offering the product at that price.



            Any attempt to compel him to provide the patents will likely cause him to dig in his heels and also find work elsewhere.



            You are raving up and down throughout your entire post about how awesome he is. Find a way to get him his money. He is clearly worth it. Upper management may not be happy with his current stance. It sounds like they are digging in their heels. Negotiation will partly need to be with them. You will need to convince them that smoothing things over with him and his ego are worth it (that's assuming it is, not every brilliant worker is worth the entitlement that pursues them.)



            As for him balking at the offer at the previous price, you need to find a way to smooth things over. To assure him that things will be better. Probably now and moving forward. His ego is probably a little (understandably) bruised. So factor that into your attempts to smooth things over. After all the company just drastically devalued the work he was doing. It had to feel like a slap in the face and the wallet. It may also take getting legal reassurances from a lawyer to mitigate his concern for legal liabilities.



            (If the promotion with the move is unappealing to him then take it off the table. It has no negotiable value.)






            share|improve this answer




























              11












              11








              11







              This is a negotiation. Your senior engineer was doing this work in his spare time in exchange for financial compensation. Your company suddenly changed the price they were willing to pay. Your senior is Not offering the product at that price.



              Any attempt to compel him to provide the patents will likely cause him to dig in his heels and also find work elsewhere.



              You are raving up and down throughout your entire post about how awesome he is. Find a way to get him his money. He is clearly worth it. Upper management may not be happy with his current stance. It sounds like they are digging in their heels. Negotiation will partly need to be with them. You will need to convince them that smoothing things over with him and his ego are worth it (that's assuming it is, not every brilliant worker is worth the entitlement that pursues them.)



              As for him balking at the offer at the previous price, you need to find a way to smooth things over. To assure him that things will be better. Probably now and moving forward. His ego is probably a little (understandably) bruised. So factor that into your attempts to smooth things over. After all the company just drastically devalued the work he was doing. It had to feel like a slap in the face and the wallet. It may also take getting legal reassurances from a lawyer to mitigate his concern for legal liabilities.



              (If the promotion with the move is unappealing to him then take it off the table. It has no negotiable value.)






              share|improve this answer















              This is a negotiation. Your senior engineer was doing this work in his spare time in exchange for financial compensation. Your company suddenly changed the price they were willing to pay. Your senior is Not offering the product at that price.



              Any attempt to compel him to provide the patents will likely cause him to dig in his heels and also find work elsewhere.



              You are raving up and down throughout your entire post about how awesome he is. Find a way to get him his money. He is clearly worth it. Upper management may not be happy with his current stance. It sounds like they are digging in their heels. Negotiation will partly need to be with them. You will need to convince them that smoothing things over with him and his ego are worth it (that's assuming it is, not every brilliant worker is worth the entitlement that pursues them.)



              As for him balking at the offer at the previous price, you need to find a way to smooth things over. To assure him that things will be better. Probably now and moving forward. His ego is probably a little (understandably) bruised. So factor that into your attempts to smooth things over. After all the company just drastically devalued the work he was doing. It had to feel like a slap in the face and the wallet. It may also take getting legal reassurances from a lawyer to mitigate his concern for legal liabilities.



              (If the promotion with the move is unappealing to him then take it off the table. It has no negotiable value.)







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited 9 hours ago

























              answered 10 hours ago









              bruglescobruglesco

              4,46141343




              4,46141343























                  8














                  You solve it by figuring out how to offer this stellar engineer a very large sum of money in terms of a salary to stay on board. If he earned $110k on patents through your company patent program then this guy knows what he is talking about and basically needs to be paid tenure. You then grin and bear it with his recent memory loss.






                  share|improve this answer




























                    8














                    You solve it by figuring out how to offer this stellar engineer a very large sum of money in terms of a salary to stay on board. If he earned $110k on patents through your company patent program then this guy knows what he is talking about and basically needs to be paid tenure. You then grin and bear it with his recent memory loss.






                    share|improve this answer


























                      8












                      8








                      8







                      You solve it by figuring out how to offer this stellar engineer a very large sum of money in terms of a salary to stay on board. If he earned $110k on patents through your company patent program then this guy knows what he is talking about and basically needs to be paid tenure. You then grin and bear it with his recent memory loss.






                      share|improve this answer













                      You solve it by figuring out how to offer this stellar engineer a very large sum of money in terms of a salary to stay on board. If he earned $110k on patents through your company patent program then this guy knows what he is talking about and basically needs to be paid tenure. You then grin and bear it with his recent memory loss.







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered 10 hours ago









                      BrianBrian

                      1,9051510




                      1,9051510























                          5














                          Reading through your description of the situation, it is quite obvious that you are a junior manager who is out of his depth.



                          Your real problem is not the engineer.
                          Your real problem is that you failed as a manager.



                          You failed:
                          1. the people who you are supposed to manage (you certainly are not a leader, despite the inflation in the terminology today - leader vs. manager) and protect from arbitrarily detrimental decisions of highly placed bean counters
                          2. the company - as a manager in the company, you are supposed to act in company's best interests and fight against decisions that are detrimental to the company (as the devaluation of patents obviously is, not because of the value of patents, they have little to none, except in very specific legal situations, but because that policy will cause the best and brightest to leave)
                          3. the engineer in question - who is obviously significantly smarter than you are and you do not deserve to be managing someone like him. For his sake, and yours, I hope he sticks to his guns and does not recall any element of that technology he forgot. Your inaction and bad decision making cut his career in your company from underneath him



                          Clearly you are not aware of these obligations because noone ever explained them to you.



                          At this point all you do is desperately try to save your own next performance review as a manager.



                          As to the issue of patents in general - being a fairly prolific patent author myself and serving on various patent review/approval committees, I can claim with confidence that the vast majority of patents are not worth the electronic bits that comprise their description. The vast majority of them are neither novel nor enforceable. The only entities who benefit from patents are the large incorporated entities fighting each other in court for business mistakes that one side made and has no real way of repairing (e.g. Qualcomm vs. Apple cases). The real competitors certainly do not respect or care about any of these patents (e.g. China vs. US).






                          share|improve this answer








                          New contributor




                          Don T. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.
















                          • 2





                            The first two bits are superb - let's hope the OP reads and understands... plus 1 from me.

                            – Solar Mike
                            3 hours ago








                          • 6





                            This answer seems way too harsh. I doubt that OP had any control over the decisions that set this debacle in motion.

                            – Jim Clay
                            2 hours ago






                          • 2





                            @JimClay given that the OP is mentioning "how they hope to solve the problem" then they seem to be close to the centre....

                            – Solar Mike
                            2 hours ago
















                          5














                          Reading through your description of the situation, it is quite obvious that you are a junior manager who is out of his depth.



                          Your real problem is not the engineer.
                          Your real problem is that you failed as a manager.



                          You failed:
                          1. the people who you are supposed to manage (you certainly are not a leader, despite the inflation in the terminology today - leader vs. manager) and protect from arbitrarily detrimental decisions of highly placed bean counters
                          2. the company - as a manager in the company, you are supposed to act in company's best interests and fight against decisions that are detrimental to the company (as the devaluation of patents obviously is, not because of the value of patents, they have little to none, except in very specific legal situations, but because that policy will cause the best and brightest to leave)
                          3. the engineer in question - who is obviously significantly smarter than you are and you do not deserve to be managing someone like him. For his sake, and yours, I hope he sticks to his guns and does not recall any element of that technology he forgot. Your inaction and bad decision making cut his career in your company from underneath him



                          Clearly you are not aware of these obligations because noone ever explained them to you.



                          At this point all you do is desperately try to save your own next performance review as a manager.



                          As to the issue of patents in general - being a fairly prolific patent author myself and serving on various patent review/approval committees, I can claim with confidence that the vast majority of patents are not worth the electronic bits that comprise their description. The vast majority of them are neither novel nor enforceable. The only entities who benefit from patents are the large incorporated entities fighting each other in court for business mistakes that one side made and has no real way of repairing (e.g. Qualcomm vs. Apple cases). The real competitors certainly do not respect or care about any of these patents (e.g. China vs. US).






                          share|improve this answer








                          New contributor




                          Don T. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.
















                          • 2





                            The first two bits are superb - let's hope the OP reads and understands... plus 1 from me.

                            – Solar Mike
                            3 hours ago








                          • 6





                            This answer seems way too harsh. I doubt that OP had any control over the decisions that set this debacle in motion.

                            – Jim Clay
                            2 hours ago






                          • 2





                            @JimClay given that the OP is mentioning "how they hope to solve the problem" then they seem to be close to the centre....

                            – Solar Mike
                            2 hours ago














                          5












                          5








                          5







                          Reading through your description of the situation, it is quite obvious that you are a junior manager who is out of his depth.



                          Your real problem is not the engineer.
                          Your real problem is that you failed as a manager.



                          You failed:
                          1. the people who you are supposed to manage (you certainly are not a leader, despite the inflation in the terminology today - leader vs. manager) and protect from arbitrarily detrimental decisions of highly placed bean counters
                          2. the company - as a manager in the company, you are supposed to act in company's best interests and fight against decisions that are detrimental to the company (as the devaluation of patents obviously is, not because of the value of patents, they have little to none, except in very specific legal situations, but because that policy will cause the best and brightest to leave)
                          3. the engineer in question - who is obviously significantly smarter than you are and you do not deserve to be managing someone like him. For his sake, and yours, I hope he sticks to his guns and does not recall any element of that technology he forgot. Your inaction and bad decision making cut his career in your company from underneath him



                          Clearly you are not aware of these obligations because noone ever explained them to you.



                          At this point all you do is desperately try to save your own next performance review as a manager.



                          As to the issue of patents in general - being a fairly prolific patent author myself and serving on various patent review/approval committees, I can claim with confidence that the vast majority of patents are not worth the electronic bits that comprise their description. The vast majority of them are neither novel nor enforceable. The only entities who benefit from patents are the large incorporated entities fighting each other in court for business mistakes that one side made and has no real way of repairing (e.g. Qualcomm vs. Apple cases). The real competitors certainly do not respect or care about any of these patents (e.g. China vs. US).






                          share|improve this answer








                          New contributor




                          Don T. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.










                          Reading through your description of the situation, it is quite obvious that you are a junior manager who is out of his depth.



                          Your real problem is not the engineer.
                          Your real problem is that you failed as a manager.



                          You failed:
                          1. the people who you are supposed to manage (you certainly are not a leader, despite the inflation in the terminology today - leader vs. manager) and protect from arbitrarily detrimental decisions of highly placed bean counters
                          2. the company - as a manager in the company, you are supposed to act in company's best interests and fight against decisions that are detrimental to the company (as the devaluation of patents obviously is, not because of the value of patents, they have little to none, except in very specific legal situations, but because that policy will cause the best and brightest to leave)
                          3. the engineer in question - who is obviously significantly smarter than you are and you do not deserve to be managing someone like him. For his sake, and yours, I hope he sticks to his guns and does not recall any element of that technology he forgot. Your inaction and bad decision making cut his career in your company from underneath him



                          Clearly you are not aware of these obligations because noone ever explained them to you.



                          At this point all you do is desperately try to save your own next performance review as a manager.



                          As to the issue of patents in general - being a fairly prolific patent author myself and serving on various patent review/approval committees, I can claim with confidence that the vast majority of patents are not worth the electronic bits that comprise their description. The vast majority of them are neither novel nor enforceable. The only entities who benefit from patents are the large incorporated entities fighting each other in court for business mistakes that one side made and has no real way of repairing (e.g. Qualcomm vs. Apple cases). The real competitors certainly do not respect or care about any of these patents (e.g. China vs. US).







                          share|improve this answer








                          New contributor




                          Don T. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.









                          share|improve this answer



                          share|improve this answer






                          New contributor




                          Don T. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.









                          answered 3 hours ago









                          Don T.Don T.

                          911




                          911




                          New contributor




                          Don T. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.





                          New contributor





                          Don T. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.






                          Don T. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.








                          • 2





                            The first two bits are superb - let's hope the OP reads and understands... plus 1 from me.

                            – Solar Mike
                            3 hours ago








                          • 6





                            This answer seems way too harsh. I doubt that OP had any control over the decisions that set this debacle in motion.

                            – Jim Clay
                            2 hours ago






                          • 2





                            @JimClay given that the OP is mentioning "how they hope to solve the problem" then they seem to be close to the centre....

                            – Solar Mike
                            2 hours ago














                          • 2





                            The first two bits are superb - let's hope the OP reads and understands... plus 1 from me.

                            – Solar Mike
                            3 hours ago








                          • 6





                            This answer seems way too harsh. I doubt that OP had any control over the decisions that set this debacle in motion.

                            – Jim Clay
                            2 hours ago






                          • 2





                            @JimClay given that the OP is mentioning "how they hope to solve the problem" then they seem to be close to the centre....

                            – Solar Mike
                            2 hours ago








                          2




                          2





                          The first two bits are superb - let's hope the OP reads and understands... plus 1 from me.

                          – Solar Mike
                          3 hours ago







                          The first two bits are superb - let's hope the OP reads and understands... plus 1 from me.

                          – Solar Mike
                          3 hours ago






                          6




                          6





                          This answer seems way too harsh. I doubt that OP had any control over the decisions that set this debacle in motion.

                          – Jim Clay
                          2 hours ago





                          This answer seems way too harsh. I doubt that OP had any control over the decisions that set this debacle in motion.

                          – Jim Clay
                          2 hours ago




                          2




                          2





                          @JimClay given that the OP is mentioning "how they hope to solve the problem" then they seem to be close to the centre....

                          – Solar Mike
                          2 hours ago





                          @JimClay given that the OP is mentioning "how they hope to solve the problem" then they seem to be close to the centre....

                          – Solar Mike
                          2 hours ago











                          2















                          I think he's worried that by agreeing to such a deal, he's opening himself up to legal liability (it would involve indirectly admitting he was being dicey/dishonest about "not knowing what I'm talking about").




                          If he is concerned about liability, then why don't you offer him a release or waiver of liability? A lawyer should be able to help you with this.






                          share|improve this answer








                          New contributor




                          bdowling is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.

























                            2















                            I think he's worried that by agreeing to such a deal, he's opening himself up to legal liability (it would involve indirectly admitting he was being dicey/dishonest about "not knowing what I'm talking about").




                            If he is concerned about liability, then why don't you offer him a release or waiver of liability? A lawyer should be able to help you with this.






                            share|improve this answer








                            New contributor




                            bdowling is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.























                              2












                              2








                              2








                              I think he's worried that by agreeing to such a deal, he's opening himself up to legal liability (it would involve indirectly admitting he was being dicey/dishonest about "not knowing what I'm talking about").




                              If he is concerned about liability, then why don't you offer him a release or waiver of liability? A lawyer should be able to help you with this.






                              share|improve this answer








                              New contributor




                              bdowling is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                              Check out our Code of Conduct.











                              I think he's worried that by agreeing to such a deal, he's opening himself up to legal liability (it would involve indirectly admitting he was being dicey/dishonest about "not knowing what I'm talking about").




                              If he is concerned about liability, then why don't you offer him a release or waiver of liability? A lawyer should be able to help you with this.







                              share|improve this answer








                              New contributor




                              bdowling is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                              Check out our Code of Conduct.









                              share|improve this answer



                              share|improve this answer






                              New contributor




                              bdowling is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                              Check out our Code of Conduct.









                              answered 3 hours ago









                              bdowlingbdowling

                              1291




                              1291




                              New contributor




                              bdowling is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                              Check out our Code of Conduct.





                              New contributor





                              bdowling is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                              Check out our Code of Conduct.






                              bdowling is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                              Check out our Code of Conduct.























                                  0














                                  He makes the bux. You pass the buck. Looking here for a solution to save your job (or at least look good so you can get a promotion)? Offer to take a pay cut. Or better yet tell senior management to take a pay cut to get the funds to pay this guy. Senior Management is an overpaid cancer. Wait till you find out how expensive it is to do 'design by committee'.






                                  share|improve this answer








                                  New contributor




                                  aquagremlin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                  Check out our Code of Conduct.

























                                    0














                                    He makes the bux. You pass the buck. Looking here for a solution to save your job (or at least look good so you can get a promotion)? Offer to take a pay cut. Or better yet tell senior management to take a pay cut to get the funds to pay this guy. Senior Management is an overpaid cancer. Wait till you find out how expensive it is to do 'design by committee'.






                                    share|improve this answer








                                    New contributor




                                    aquagremlin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                    Check out our Code of Conduct.























                                      0












                                      0








                                      0







                                      He makes the bux. You pass the buck. Looking here for a solution to save your job (or at least look good so you can get a promotion)? Offer to take a pay cut. Or better yet tell senior management to take a pay cut to get the funds to pay this guy. Senior Management is an overpaid cancer. Wait till you find out how expensive it is to do 'design by committee'.






                                      share|improve this answer








                                      New contributor




                                      aquagremlin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                      Check out our Code of Conduct.










                                      He makes the bux. You pass the buck. Looking here for a solution to save your job (or at least look good so you can get a promotion)? Offer to take a pay cut. Or better yet tell senior management to take a pay cut to get the funds to pay this guy. Senior Management is an overpaid cancer. Wait till you find out how expensive it is to do 'design by committee'.







                                      share|improve this answer








                                      New contributor




                                      aquagremlin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                      Check out our Code of Conduct.









                                      share|improve this answer



                                      share|improve this answer






                                      New contributor




                                      aquagremlin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                      Check out our Code of Conduct.









                                      answered 5 hours ago









                                      aquagremlinaquagremlin

                                      1332




                                      1332




                                      New contributor




                                      aquagremlin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                      Check out our Code of Conduct.





                                      New contributor





                                      aquagremlin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                      Check out our Code of Conduct.






                                      aquagremlin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                      Check out our Code of Conduct.























                                          0














                                          How about talking with him off company property and suggest that you both quit your obviously rotten company and start a competitor?






                                          share|improve this answer








                                          New contributor




                                          Olivercomputing is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.










                                          We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.










                                          • 1





                                            without an explanation, this answer may become useless in case if someone else posts an opposite opinion. For example, if someone posts a claim like "Avoid talking with him off company property and suggesting that you both quit your obviously rotten company and start a competitor.", how would this answer help reader to pick of two opposing opinions? Consider editing it into a better shape, to meet How to Answer guidelines

                                            – gnat
                                            2 hours ago
















                                          0














                                          How about talking with him off company property and suggest that you both quit your obviously rotten company and start a competitor?






                                          share|improve this answer








                                          New contributor




                                          Olivercomputing is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.










                                          We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.










                                          • 1





                                            without an explanation, this answer may become useless in case if someone else posts an opposite opinion. For example, if someone posts a claim like "Avoid talking with him off company property and suggesting that you both quit your obviously rotten company and start a competitor.", how would this answer help reader to pick of two opposing opinions? Consider editing it into a better shape, to meet How to Answer guidelines

                                            – gnat
                                            2 hours ago














                                          0












                                          0








                                          0







                                          How about talking with him off company property and suggest that you both quit your obviously rotten company and start a competitor?






                                          share|improve this answer








                                          New contributor




                                          Olivercomputing is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.










                                          How about talking with him off company property and suggest that you both quit your obviously rotten company and start a competitor?







                                          share|improve this answer








                                          New contributor




                                          Olivercomputing is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.









                                          share|improve this answer



                                          share|improve this answer






                                          New contributor




                                          Olivercomputing is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.









                                          answered 4 hours ago









                                          OlivercomputingOlivercomputing

                                          412




                                          412




                                          New contributor




                                          Olivercomputing is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.





                                          New contributor





                                          Olivercomputing is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.






                                          Olivercomputing is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.



                                          We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.




                                          We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.









                                          • 1





                                            without an explanation, this answer may become useless in case if someone else posts an opposite opinion. For example, if someone posts a claim like "Avoid talking with him off company property and suggesting that you both quit your obviously rotten company and start a competitor.", how would this answer help reader to pick of two opposing opinions? Consider editing it into a better shape, to meet How to Answer guidelines

                                            – gnat
                                            2 hours ago














                                          • 1





                                            without an explanation, this answer may become useless in case if someone else posts an opposite opinion. For example, if someone posts a claim like "Avoid talking with him off company property and suggesting that you both quit your obviously rotten company and start a competitor.", how would this answer help reader to pick of two opposing opinions? Consider editing it into a better shape, to meet How to Answer guidelines

                                            – gnat
                                            2 hours ago








                                          1




                                          1





                                          without an explanation, this answer may become useless in case if someone else posts an opposite opinion. For example, if someone posts a claim like "Avoid talking with him off company property and suggesting that you both quit your obviously rotten company and start a competitor.", how would this answer help reader to pick of two opposing opinions? Consider editing it into a better shape, to meet How to Answer guidelines

                                          – gnat
                                          2 hours ago





                                          without an explanation, this answer may become useless in case if someone else posts an opposite opinion. For example, if someone posts a claim like "Avoid talking with him off company property and suggesting that you both quit your obviously rotten company and start a competitor.", how would this answer help reader to pick of two opposing opinions? Consider editing it into a better shape, to meet How to Answer guidelines

                                          – gnat
                                          2 hours ago











                                          -4















                                          I can offer a one-off bonus, and I can offer him a significant promotion




                                          As far as I've understood, it's a "cash cow" sutiation for this dude.



                                          So, it's obvious that he'll be looking for other ways to exploit this opportunity, which will surely end up in leaving your company. Empty handed or not - depends on moral qualities and legal agreements, but I really doubt that a lucrative person will hurt his wallet with moral decisions.



                                          Everything else is just a personal fear for making hard decisions, that's why you've asked about it in the first place.




                                          I can't give him a raise in his current position, and members of senior management no longer trust him due to his "funny" behavior




                                          You'll need to find out another source of motivation - it'll be very tricky, and I really doubt that it would be worthy. Having a "single head of knowledge" and a
                                          "knight in shining armor" considered as antipatters for a reason. Those mistakes cost from 8 up to 40mil in IBM'ish / wh'Oracle'ish scale.




                                          doesn't know what I'm talking about




                                          Playing dumb just proves that it's either "always not enough" game or just a simple bluf - he was trying to be manipulative, but had failed at some point.



                                          There's a post-soviet "The Tale of the Fisherman and the Fish ", but it's also a set of psychological patterns.



                                          tldr; People who're playing "always not enough" plate, might not learn a thing even after getting broke.



                                          It's never too late to make a hard decision, but you'll have to be prepared for what's to come afterwards.




                                          He's delivered impressive results in the past, so I doubt he was blowing smoke




                                          Nah... 99% of existing projects are low quality ones.



                                          I really doubt you've got any DevOps/SRE practices applied, decent code coverage and low tech debt.



                                          Get to at least 80% code coverage, and verify it with some Mutational tests and Fuzzing, so you'll be able to get rid of the linchpin, and reduce the risks while getting new folks on board.



                                          Managers are often too dumb even to distinguish between Iterative and Incremental development processes (ask about it someone with an opened "agile bicycle" pic).



                                          Having a set of "cash cows" will surely result in a professional growth stall, I'd suggest looking for a new guy, preferably a humble one, in the middle of nowhere (just like myself :p).



                                          It doesn't mean much if stuff just works somehow - longterm support and operational costs can be up to 10 times bigger than the development ones.



                                          Fix your management first, get rid of Mushroom Management, learn how to invest in People in the first place, so you can keep loyal staff and bus factor more than 1.



                                          The definition of loyalty may lack due to psychological compensational needs, but that's completely another story.



                                          Review some of the existing antipatterns and try to fix at least something, before making any life-turning crucial decisions. Improve the quality of the product itself, so you'll be able to get a "Cash Pillow" if things go sideways.



                                          An Example



                                          One day.
                                          There was a smart dude, who prepped a patent for an API based website pre-rendering, and wanted some cash in return from Netflix.



                                          Without a trial, he handed some of the rights to Netflix, and gotten himself fired (as far as I know). All his prior related network activity for about 2 years (tweets, chat/forum/facebook posts) miraculously disappeared. People were speculating that he's been assassinated etc, but actually he went rouge (i.e converted to facebook).



                                          BTW google and facebook has the same prerender patents, because US patent laws are crap.



                                          You may consider exploiting leaky patent formulas and re-patenting stuff for yourself just as a countermeasure... which may result in bribing here and there, but that's how this thing rolls nowadays.






                                          share|improve this answer










                                          New contributor




                                          Yuriy Yarosh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.
















                                          • 1





                                            DevOps? Code Coverage? You're assuming things here. Not all code is production code. Plenty of non-IT engineers write code to simulate things, especially for demo's. It's rather expensive to build a chemical plant for a demo, after all.

                                            – MSalters
                                            45 mins ago
















                                          -4















                                          I can offer a one-off bonus, and I can offer him a significant promotion




                                          As far as I've understood, it's a "cash cow" sutiation for this dude.



                                          So, it's obvious that he'll be looking for other ways to exploit this opportunity, which will surely end up in leaving your company. Empty handed or not - depends on moral qualities and legal agreements, but I really doubt that a lucrative person will hurt his wallet with moral decisions.



                                          Everything else is just a personal fear for making hard decisions, that's why you've asked about it in the first place.




                                          I can't give him a raise in his current position, and members of senior management no longer trust him due to his "funny" behavior




                                          You'll need to find out another source of motivation - it'll be very tricky, and I really doubt that it would be worthy. Having a "single head of knowledge" and a
                                          "knight in shining armor" considered as antipatters for a reason. Those mistakes cost from 8 up to 40mil in IBM'ish / wh'Oracle'ish scale.




                                          doesn't know what I'm talking about




                                          Playing dumb just proves that it's either "always not enough" game or just a simple bluf - he was trying to be manipulative, but had failed at some point.



                                          There's a post-soviet "The Tale of the Fisherman and the Fish ", but it's also a set of psychological patterns.



                                          tldr; People who're playing "always not enough" plate, might not learn a thing even after getting broke.



                                          It's never too late to make a hard decision, but you'll have to be prepared for what's to come afterwards.




                                          He's delivered impressive results in the past, so I doubt he was blowing smoke




                                          Nah... 99% of existing projects are low quality ones.



                                          I really doubt you've got any DevOps/SRE practices applied, decent code coverage and low tech debt.



                                          Get to at least 80% code coverage, and verify it with some Mutational tests and Fuzzing, so you'll be able to get rid of the linchpin, and reduce the risks while getting new folks on board.



                                          Managers are often too dumb even to distinguish between Iterative and Incremental development processes (ask about it someone with an opened "agile bicycle" pic).



                                          Having a set of "cash cows" will surely result in a professional growth stall, I'd suggest looking for a new guy, preferably a humble one, in the middle of nowhere (just like myself :p).



                                          It doesn't mean much if stuff just works somehow - longterm support and operational costs can be up to 10 times bigger than the development ones.



                                          Fix your management first, get rid of Mushroom Management, learn how to invest in People in the first place, so you can keep loyal staff and bus factor more than 1.



                                          The definition of loyalty may lack due to psychological compensational needs, but that's completely another story.



                                          Review some of the existing antipatterns and try to fix at least something, before making any life-turning crucial decisions. Improve the quality of the product itself, so you'll be able to get a "Cash Pillow" if things go sideways.



                                          An Example



                                          One day.
                                          There was a smart dude, who prepped a patent for an API based website pre-rendering, and wanted some cash in return from Netflix.



                                          Without a trial, he handed some of the rights to Netflix, and gotten himself fired (as far as I know). All his prior related network activity for about 2 years (tweets, chat/forum/facebook posts) miraculously disappeared. People were speculating that he's been assassinated etc, but actually he went rouge (i.e converted to facebook).



                                          BTW google and facebook has the same prerender patents, because US patent laws are crap.



                                          You may consider exploiting leaky patent formulas and re-patenting stuff for yourself just as a countermeasure... which may result in bribing here and there, but that's how this thing rolls nowadays.






                                          share|improve this answer










                                          New contributor




                                          Yuriy Yarosh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.
















                                          • 1





                                            DevOps? Code Coverage? You're assuming things here. Not all code is production code. Plenty of non-IT engineers write code to simulate things, especially for demo's. It's rather expensive to build a chemical plant for a demo, after all.

                                            – MSalters
                                            45 mins ago














                                          -4












                                          -4








                                          -4








                                          I can offer a one-off bonus, and I can offer him a significant promotion




                                          As far as I've understood, it's a "cash cow" sutiation for this dude.



                                          So, it's obvious that he'll be looking for other ways to exploit this opportunity, which will surely end up in leaving your company. Empty handed or not - depends on moral qualities and legal agreements, but I really doubt that a lucrative person will hurt his wallet with moral decisions.



                                          Everything else is just a personal fear for making hard decisions, that's why you've asked about it in the first place.




                                          I can't give him a raise in his current position, and members of senior management no longer trust him due to his "funny" behavior




                                          You'll need to find out another source of motivation - it'll be very tricky, and I really doubt that it would be worthy. Having a "single head of knowledge" and a
                                          "knight in shining armor" considered as antipatters for a reason. Those mistakes cost from 8 up to 40mil in IBM'ish / wh'Oracle'ish scale.




                                          doesn't know what I'm talking about




                                          Playing dumb just proves that it's either "always not enough" game or just a simple bluf - he was trying to be manipulative, but had failed at some point.



                                          There's a post-soviet "The Tale of the Fisherman and the Fish ", but it's also a set of psychological patterns.



                                          tldr; People who're playing "always not enough" plate, might not learn a thing even after getting broke.



                                          It's never too late to make a hard decision, but you'll have to be prepared for what's to come afterwards.




                                          He's delivered impressive results in the past, so I doubt he was blowing smoke




                                          Nah... 99% of existing projects are low quality ones.



                                          I really doubt you've got any DevOps/SRE practices applied, decent code coverage and low tech debt.



                                          Get to at least 80% code coverage, and verify it with some Mutational tests and Fuzzing, so you'll be able to get rid of the linchpin, and reduce the risks while getting new folks on board.



                                          Managers are often too dumb even to distinguish between Iterative and Incremental development processes (ask about it someone with an opened "agile bicycle" pic).



                                          Having a set of "cash cows" will surely result in a professional growth stall, I'd suggest looking for a new guy, preferably a humble one, in the middle of nowhere (just like myself :p).



                                          It doesn't mean much if stuff just works somehow - longterm support and operational costs can be up to 10 times bigger than the development ones.



                                          Fix your management first, get rid of Mushroom Management, learn how to invest in People in the first place, so you can keep loyal staff and bus factor more than 1.



                                          The definition of loyalty may lack due to psychological compensational needs, but that's completely another story.



                                          Review some of the existing antipatterns and try to fix at least something, before making any life-turning crucial decisions. Improve the quality of the product itself, so you'll be able to get a "Cash Pillow" if things go sideways.



                                          An Example



                                          One day.
                                          There was a smart dude, who prepped a patent for an API based website pre-rendering, and wanted some cash in return from Netflix.



                                          Without a trial, he handed some of the rights to Netflix, and gotten himself fired (as far as I know). All his prior related network activity for about 2 years (tweets, chat/forum/facebook posts) miraculously disappeared. People were speculating that he's been assassinated etc, but actually he went rouge (i.e converted to facebook).



                                          BTW google and facebook has the same prerender patents, because US patent laws are crap.



                                          You may consider exploiting leaky patent formulas and re-patenting stuff for yourself just as a countermeasure... which may result in bribing here and there, but that's how this thing rolls nowadays.






                                          share|improve this answer










                                          New contributor




                                          Yuriy Yarosh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.











                                          I can offer a one-off bonus, and I can offer him a significant promotion




                                          As far as I've understood, it's a "cash cow" sutiation for this dude.



                                          So, it's obvious that he'll be looking for other ways to exploit this opportunity, which will surely end up in leaving your company. Empty handed or not - depends on moral qualities and legal agreements, but I really doubt that a lucrative person will hurt his wallet with moral decisions.



                                          Everything else is just a personal fear for making hard decisions, that's why you've asked about it in the first place.




                                          I can't give him a raise in his current position, and members of senior management no longer trust him due to his "funny" behavior




                                          You'll need to find out another source of motivation - it'll be very tricky, and I really doubt that it would be worthy. Having a "single head of knowledge" and a
                                          "knight in shining armor" considered as antipatters for a reason. Those mistakes cost from 8 up to 40mil in IBM'ish / wh'Oracle'ish scale.




                                          doesn't know what I'm talking about




                                          Playing dumb just proves that it's either "always not enough" game or just a simple bluf - he was trying to be manipulative, but had failed at some point.



                                          There's a post-soviet "The Tale of the Fisherman and the Fish ", but it's also a set of psychological patterns.



                                          tldr; People who're playing "always not enough" plate, might not learn a thing even after getting broke.



                                          It's never too late to make a hard decision, but you'll have to be prepared for what's to come afterwards.




                                          He's delivered impressive results in the past, so I doubt he was blowing smoke




                                          Nah... 99% of existing projects are low quality ones.



                                          I really doubt you've got any DevOps/SRE practices applied, decent code coverage and low tech debt.



                                          Get to at least 80% code coverage, and verify it with some Mutational tests and Fuzzing, so you'll be able to get rid of the linchpin, and reduce the risks while getting new folks on board.



                                          Managers are often too dumb even to distinguish between Iterative and Incremental development processes (ask about it someone with an opened "agile bicycle" pic).



                                          Having a set of "cash cows" will surely result in a professional growth stall, I'd suggest looking for a new guy, preferably a humble one, in the middle of nowhere (just like myself :p).



                                          It doesn't mean much if stuff just works somehow - longterm support and operational costs can be up to 10 times bigger than the development ones.



                                          Fix your management first, get rid of Mushroom Management, learn how to invest in People in the first place, so you can keep loyal staff and bus factor more than 1.



                                          The definition of loyalty may lack due to psychological compensational needs, but that's completely another story.



                                          Review some of the existing antipatterns and try to fix at least something, before making any life-turning crucial decisions. Improve the quality of the product itself, so you'll be able to get a "Cash Pillow" if things go sideways.



                                          An Example



                                          One day.
                                          There was a smart dude, who prepped a patent for an API based website pre-rendering, and wanted some cash in return from Netflix.



                                          Without a trial, he handed some of the rights to Netflix, and gotten himself fired (as far as I know). All his prior related network activity for about 2 years (tweets, chat/forum/facebook posts) miraculously disappeared. People were speculating that he's been assassinated etc, but actually he went rouge (i.e converted to facebook).



                                          BTW google and facebook has the same prerender patents, because US patent laws are crap.



                                          You may consider exploiting leaky patent formulas and re-patenting stuff for yourself just as a countermeasure... which may result in bribing here and there, but that's how this thing rolls nowadays.







                                          share|improve this answer










                                          New contributor




                                          Yuriy Yarosh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.









                                          share|improve this answer



                                          share|improve this answer








                                          edited 2 hours ago





















                                          New contributor




                                          Yuriy Yarosh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.









                                          answered 2 hours ago









                                          Yuriy YaroshYuriy Yarosh

                                          11




                                          11




                                          New contributor




                                          Yuriy Yarosh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.





                                          New contributor





                                          Yuriy Yarosh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.






                                          Yuriy Yarosh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.








                                          • 1





                                            DevOps? Code Coverage? You're assuming things here. Not all code is production code. Plenty of non-IT engineers write code to simulate things, especially for demo's. It's rather expensive to build a chemical plant for a demo, after all.

                                            – MSalters
                                            45 mins ago














                                          • 1





                                            DevOps? Code Coverage? You're assuming things here. Not all code is production code. Plenty of non-IT engineers write code to simulate things, especially for demo's. It's rather expensive to build a chemical plant for a demo, after all.

                                            – MSalters
                                            45 mins ago








                                          1




                                          1





                                          DevOps? Code Coverage? You're assuming things here. Not all code is production code. Plenty of non-IT engineers write code to simulate things, especially for demo's. It's rather expensive to build a chemical plant for a demo, after all.

                                          – MSalters
                                          45 mins ago





                                          DevOps? Code Coverage? You're assuming things here. Not all code is production code. Plenty of non-IT engineers write code to simulate things, especially for demo's. It's rather expensive to build a chemical plant for a demo, after all.

                                          – MSalters
                                          45 mins ago





                                          protected by Mister Positive 1 hour ago



                                          Thank you for your interest in this question.
                                          Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                                          Would you like to answer one of these unanswered questions instead?



                                          Popular posts from this blog

                                          How to make a Squid Proxy server?

                                          第一次世界大戦

                                          Touch on Surface Book