For anyone (lawyer or otherwise) interested in the tensions associated with employee mobility, a truly must-read is Talent Wants to Be Free, by Orly Lobel.
Professor Lobel discusses a wide range of issues associated with talent and knowledge flows, and she incorporates thoughts that transcend the law and devolve into economics and sociology. The book is, to say the least, thought-provoking even for those who may choose to disagree with some of her conclusions. There's a particular issue that Professor Lobel discusses that touches upon one of competition law's great tensions.
In my judgment, one of the most difficult areas of the law for lawyers, judges, and clients is drawing a distinction between two concepts: general skill and knowledge (which is not protectable) and a trade secret (which is). Consider the following from an Illinois decision some twenty years ago:
"General skills and knowledge acquired in the course of employment...are things an employee is free to take and to use in later pursuits, especially if they do not take the form of written records, compilations or analyses." Passage quoted from Colson Co. v. Wittel, 569 N.E.2d 1082, 1087 (4th Dist. 1991).
This is somewhat (largely?) unhelpful for two reasons. First, it's so obvious that we shouldn't feel the need to use it as a guidepost or legal marker. Second, the notion of "general skills and knowledge" suggests a disconnect from experiential information or data the employee may have obtained by reason of his or her employment with a business. Put another way, GSK sounds like information an employee may acquire just by virtue of being in a particular field and that generally may be available to anyone, but not of any real use to people who are engaged in other occupations.
This disconnect is troubling when trying to parse out what kinds of information a business can protect by contract or through assertion of a trade secret right. A passage in Chapter 4 of Professor Lobel's book gets closer to solving the disconnect and bridging the ideas of general skill and knowledge, on the one hand, and trade secrets, on the other.
She talks of "embedded knowledge." Here's how she puts it in context:
"Knowledge that is embedded comes from experience, from learning by doing or observing; this kind of knowledge is difficult to codify and write down. Embedded knowledge (also known as tacit knowledge) is learned informally through direct and repeated contacts."
This formulation actually gets us closer to determining what is protectable and what is not, but only if we say embedded knowledge is something only an enforceable non-compete can safeguard. In other words, we should be careful not to lump in embedded knowledge with the amorphous (some might say rudderless) definition of a trade secret.
Examples of embedded knowledge likely include a person's familiarity with key contacts and customer requirements or buying habits. It also may include the odd concept of "negative know-how" (that which isn't effective). It certainly includes pricing patterns or strategies. Perhaps, too, it encompasses knowledge of which particular vendors are reliable or can lead to efficient sales distribution. To be sure, this will be company-specific data; they're not "general" in the fair sense of the word.
Professor Lobel also makes the point that "embedded knowledge" doesn't spread with great accuracy. Again, from Chapter 4:
"As you can imagine by now, the way tacit knowledge spreads depends on the shape of the network and the complexity of the information being diffused. When knowedge is transmitted, it usually does not diffuse accurately and flawlessly across companies."
This is another way of saying that embedded knowledge can be (and likely is) fleeting or ephemeral; it changes, in other words.
Consider this example. An employee is charged with developing a new product and has his hands in various business units that may impact the development of the good before it's rolled out publicly. If that employee leaves, he may have knowledge that his former company still is rolling out the product. But much likely has changed since his departure. Perhaps the company switched vendors, changed chemicals that go into the product formulation, or had to purchase new equipment (thereby decreasing the amount of months it would take to generate a positive return on investment).
It is entirely reasonable that the employee would not know anything about these developments, even if he had day-to-day involvement in the product for a long time while he was there. To Professor Lobel's point, if he then used his prior information about the product (his embedded knowledge) in a new position with a new company, it's likely to be inaccurate. That is to say, the passage of time and fluidity of useful information reshapes the employee's knowledge in such a way as to render it less valuable and even counterproductive to a competitor.
A trade secret, by contrast, shouldn't face the diffusion problem. The central point of a trade secret is that it's a patent substitute. An owner achieves an economic advantage (possibly in perpetuity) by keeping the information secret, rather than gaining a limited monopoly through the patent system. If that's the case, then the trade secret should be something the firm can monetize. Embedded knowledge, by contrast, is that which shifts and is not capable of monetization.
An alternative way for lawyers and judges to look at whether something meets the definition of a trade secret may be to get away from the mutli-factored standard that yields more questions than answers and determine whether, in Professor Lobel's words, it can "diffuse accurately and flawlessly across companies."