If the employee violates the IP then sue him for that. No need for non-compete agreements. If you're worried the employee will steal your clients then you're not giving your clients a good deal at first place, and the employee shouldn't be prevented from working with your clients. This is a free market. Non compete agreements are completely anti-freedom of both enterprise and work.
> Company ABC brings you in, trains you on their know-how and core IP, which took a lot of struggle, $, and R&D to create - then you leave, go to a competitor, and effectively communicate and give away ABC Corps. most valuable asset.
Then the burden of proof should lie with the previous company, there shouldn't be any possibility of preemptive clause within the former contract. If it's clear corporate secrets were leaked then sue. If you don't want your employee go work somewhere else then compensate him, that's the problem here , most of the time there is no compensation.
It doesn't matter how much R&D was created. That's the role of patents to deal with that thing.
Maybe ABC corp was mistaken, and their most valuable asset was that employee and not just the model parameters he struggled for years to optimize?
I'm beginning to think none of you have ever worked in companies that actually produce IP.
First off - that's not what patents are for. Patents protect publicly known information - not trade secrets. And they don't do it very well. There are very few things you can defend with a patent.
What companies are concerned with is 'trade secrets' and 'know how' - and it's a serious thing.
"Then the burden of proof should lie with the previous company, there shouldn't be any possibility of preemptive clause within the former contract."
If you work at DWAVE for 5 years and learn everything you know about Quantum Computing there - and go to Google to work on Quantum Computing - then there is basically a 100% chance that you are passing on 'know how' and 'trade secrets' - otherwise - Google would not hire you.
Your comments about customers etc. are irrelevant with respect to IP issues.
If you work for ABC corp and they make a 'sales automation tool' - and you go off and build your own 'sales automation tool' - then fine. It's not about IP or trade secrets. You can do as you like.
But for other types of things, no way. You work at Nuance on Speech recognition - then you leave and build a nearly identical speech recognition system? That's probably IP theft.
There would not be any technology if IP could not be protected in some reasonable way.
I'm not suggesting that many of these contracts are crazy - and that there can be absurd limitations and weird corner cases - of course it's very tricky - but companies deserve the right to protect their IP in some manner.
That isn't trade secrets, it's experience.
No.
100% false.
If that information is key to the nature and success of a product, then it's called 'know how' and it's both legally and rationally protectable.
You people need to grow up and grasp that fact that once you go to a company and they teach you what they have spent $100 Million dollars on developing, that you cannot walk across the street and spill the beans on 80% of the materiality of that R&D which happens to be such details.
All you care about is the profitability of the company, and you think forcing employees to sign away their ability to work in their field is an acceptable solution.
People are getting hired for 3-month contracts and then getting sued when they find a similar job a year later. People are getting laid off and then getting sued by the companies that laid them off for getting a job at a competitor.
Fuck that. The job market needs competition, not a focus on raw profits above all else.
If your employee leaves your company, joins your competitor, and then leaks your trade secrets, then sue them for that. Don't sue them for even getting a job at your competitor - that doesn't mean that they are leaking secrets.
And if you think that your employees are so untrustworthy that getting hired by a competitor is a guaranteed leak of trade secrets, then that probably explains why you are so terrified that they will leave you to find a new job. You're a terrible employer, and they would be better off with a different job.
But let's face it, you don't have any employees, because you aren't an employer. You're a "temporarily embarrassed" entrepreneur who is already convinced that someone will try to steal that million-dollar idea you haven't had yet. Well, I wouldn't work for you, nor should anyone else, so good luck with that idea once you have it.
That said, it doesn't mean that it's either ethical or necessarily legal for them to go to company Y and immediately do a core dump of every marketing campaign they ran and what the results were. But there's a fuzzy line between doing that and saying "Oh, millennials really respond well to this sort of language, but be careful not to say this."
Unless you have a noncompete clause. That's exactly why they're a problem. You can't develop your professional skills. When you leave, you have to start from scratch in a different industry.
Buddy - I'm saying there should be no 'non compete' clause in that situation. Obviously - there's no basis for it because there is no IP involved. Which is a case of over-aggressive application of these protocols.
Sure. What I have in my head isn't the companies IP though, it's my experience.
"IP" is often confused with "the collective experience of your employees". IP is physical artifacts such as code, drawings, patents etc. The memory of having written that code is not part of the IP, nor is the capability of doing it again in a fraction of the time.
Again - 100% false. A lot of 'what is in your head' is the IP of the company you worked for.
Clearly, you grasp this, because you people seem to accept that NDA's are valid.
So - that yo accept and 'NDA' is valid, means you accept that 'what is in your head' can be the property of the company.
These 'I'm paid for labour' arguments are naive. You are paid to create outcomes, and to keep information about the company private - indefinitely.
I consider most of it "experience". How would you draw the line between what is "experience" and what is "IP"?
> you people seem to accept that NDA's are valid.
> 'NDA' is valid, means you accept that 'what is in your head' can be the property of the company
Well it rather means that I can't disclose things to certain people at certain times. I accept that e.g. for unreleased products and other secrets.
> to keep information about the company private - indefinitely.
Not sure what that means? If I work for ABC corp to develop over 10 years some advanced tech for ad targeting, and I have a non-compete that doesn't let me go to google for a year. For that full year they pay me full salary. That is the non-compete. I accept that (only with full salary). While at ABC, I had an NDA. That's cool.
After that year I can clean room implement something similar. I might have to avoid making the exact same system I did at ABC corp if there are IP issues such as patents. Note that this IP (patents) is not secret. I don't necessarily agree with software patents of most kinds however.
I develop the similar system at google in 1 year. That's what experience does: I take none of the dead ends I did at ABC corp. That's why google can pay me a load of money: I have experience. Is that experience in large part the SAME as ABC corps "IP"? yes. Of course. Do they "own" all of that experience? No. They still have their product. They own that. Google will have a product too, which they own. I wrote both.
And yes, I have a lot of patents and trade-secrets to my name.
I've seen people talk with a straight face how they think their company invented the use of IFNDEF/DEFINE for C .h files
And parent comment only goes to show how there are cattle that supports barbecues
All software companies produce intellectual property.
If the person from your quantum computer example gets fired with non-compete, it would mean being forced out of he field with 100% certainty. Quite a leverage for a company.
In my opinion, there is still enough stuff out there benefiting corps over employees even if non-competes go away.
Not being able to work work in the same field for up to 2 years (non-compete) and not disclosing internal ip, processes, etc when you go work at another company (NDA) in the field are much different.
Preventing someone from working in a field and not disclosing or sharing secrets/ip are two different animals.
NDAs are useful and I use them myself when contractors work with us, but non-competes create a very master/slave type of relationship, ownership of someone's skill that they need to work.
Paid non-competes are something that isn't as bad but non paid non-competes are horrible for the little guy and really a form of ownership that really goes against 'pro-business' ideals for smaller companies trying to compete while seemingly being 'pro-business' for the company doling out non-competes (big fish).
Contractors can't be told where to work, how to work or times to work, why are we allowing companies to tell skilled workers what they can and can't work on after the contract is up aside from what is under NDA?
Um, that's covered by an NDA--Non-Disclosure Agreement.
Those are generally QUITE enforceable, even in California and often last for 3 to 5 years.
Non-compete is quite different.
Pragmatically speaking, it's nary impossible to work in some fields, and then move to a competing firm without passing on know how or trade secrets.
Even the 'manner of approach' to a problem, while it may not be a trade secret, is basically a core part of the 'true IP' that is developed by a company.
Using DWAVE as an example - there are thousands of 'little things' that they will have had to figure out along the way - from which parts to use, which vendors work well, material types, tooling, physical test units, support gear (like cooling etc.) - all of this is IP.
Any number of small issues can be the 'key ingredients' that make or break a project. When DWAVE spends a year trying to figure out how to keep some material at a steady temperature in order to bind it to another ... then that's IP.
It's a paradox when nearly one's entire skill set is tantamount to 'trade secrets' but it's feasible.
An NDA - in the broadest sense - in this case would be a de-facto 'non compete' - because there's hardly a thing this Eng could do for Google that wouldn't involve giving away important information.
In case you guys are not aware: hiring people to steal away trade secrets and know-how is very common in the Valley, often by major players and firms.
If you haven't noticed - the biggest and most successful tech companies all have either natural monopolies (i.e. Facebook/Twitter with network externalities), or insurmountable massive barriers to entry keeping others out (i.e. Apple having MacOS/iOS, a retail distribution chain, massive leverage over supply chain, and market share).
In business scenarios it happens as well, in less 'protectable' scenarios. Apple snared away tons of BlackBerry sales/BD execs - not because they were necessarily skilled or talented - but because of their established relationships within carrier channels. Apple was buying access to Verizon and AT&T - not random sales guys abilities.
Don't forget that not only do companies lose their "IP" with outgoing workers, but they also get more free with incoming ones. Perhaps it balances out but with a net positive effect since effective skills get spread around the industry instead of being locked up whereever they were discovered.
I think this is part of a bigger argument about how much IP protection is enough to encourage innovation but not so much that it stifles the market. You seem to be advocating protecting every last little bit of knowledge but perhaps that's stifling for the economy overall even if it is more fair for individual members.
Intellectual property is a bit of a misnomer it has very little in common with property of the standard sort and the burden falls upon you to explain why we ought to create greater artificial scarcity for imaginary property.
+ My point is nearly everything that you learn at a company could be considered a 'trade secret' - depending on the company or project.
In the example I gave, I listed a variety of situations in which minute operational skills and knowledge, all contribute to be 'key information' regarding the development of the product, and can essentially be 'trade secrets'.
Ergo - it would be nary difficult to work for a competitor and not give that information up.
Were Soft Engs simply to do 'work' then you would be absolutely right.
But in a world of IP ... it's a different story.
Company ABC brings you in, trains you on their know-how and core IP, which took a lot of struggle, $, and R&D to create - then you leave, go to a competitor, and effectively communicate and give away ABC Corps. most valuable asset.
Non-competes can certainly applied far too aggressively, esp. in situations where there is not merit ... but there are definitely cases wherein I think it does make sense.
I'm thinking companies like DWAVE in Vancouver that built the 'first' qubit/quantum computer. The guy spent his whole life developing that tech. It's feasible that Google just grabs up some of the team and internalizes all that work and effort for the price of a few headcount.
It's a real problem in some cases, but worse - very difficult to parameterize.