Skip to main content

Why I don’t sign NDAs

Non-disclosure agreements (NDAs) are something I try not to sign, for various reasons. For one thing, they give a false sense of security; for another, they interfere with me doing my job. An increasing amount of academic research is supported in one way or another by companies, either directly or through co-funding agreements. This trend is only likely to increase as State funding becomes less common. As well as this, academics are sometimes approached to do consultancy or development work for companies on a more close-to-market basis. This can be great for all concerned: the companies get access to (hopefully) unbiased expert advice that can perhaps take a longer-term view, while the academics get real-world problems to work on and a reality check on some of their ideas. Despite all this, there are still some problems. Chief among them, I've found, are non-disclosure agreements (NDAs) whereby one or both sides agree not to disclose proprietary information to third parties. Some NDAs are one-way, so (for example) the university agrees not to disclose company information; many are symmetrical and protect both sides, which is obviously more desirable. (Interestingly it's often university-led NDAs that are asymmetric, implying that the companies have no intellectual input...) Although they sound like they're used for competitive reasons -- and sometimes they are -- it's more likely that they used to protect information for use in later patent applications, where discussion with a third party might be regarded as "publication" and so endanger the patent. Anyone who works in commercial research has to be sensitive to this, and since I used to run a company myself I'm conscious of protecting others' intellectual property. So why does this cause a problem? Mainly because of the bluntness of the instrument by which the protection happens. In my job, I have a lot of discussions that involve half-formed ideas. Many of these seem pretty much to condense out of the ether into several people's heads simultaneously: it's in no way uncommon to have two or three people discuss the same "novel" idea within days of each other. I suppose it's just that there's nothing really new under the sun, and people who share a common technical milieu will often see the same problems and arrive at similar solutions. Often the people involved are students: either undergraduates looking for projects, or PhD students with ideas for theses or papers. These people are my "core constituency" in the sense that my main job is to teach and supervise them in a research-led way. You can probably see where this is going. Suppose a student comes to me with an idea, and that this idea is related in some way to an idea presented by a company with whom I've signed an NDA. What do I do? Refuse to discuss the matter with the student, even though they're fired-up about it? Try to re-focus them onto another area, even though it might be a great idea, because I can't discuss it? Send them to someone else, even though I might be the right person to supervise the work? What I can't do is get involved, because however hard I try, I'll never be able to prove that information covered by the NDA had no effect on what I said or did -- or didn't say or do, for that matter. That leaves both me and the university open to legal action, especially if by some chance the student's work got a high profile and damaged the company, for example by developing an open-source solution to something they were working on. This is something of a dilemma. I like working with companies; I love working with students; and I don't like the feeling that my freedom to discuss technology and ideas is being legally constrained. I therefore minimise my exposure to NDAs and confidentiality agreements. It's sometimes unavoidable, for example as part of EU project consortium agreements. But as a general rule I don't think NDAs sit well with academics, and there's too much danger of damaging the general openness of research within a university: too much of a sacrifice just to get a single funded project. I'll happily agree to keep information confidential, but the risks of signing a blunt and broad agreement to that effect are just too great.

Share this post to:


Comments powered by Disqus