4 ms·
I've always had side projects and have always disclosed my side projects to my boss. I want to be absolutely sure there are no surprises. In one case, I let thi
by aaronbrethorst 14y ago
I've always had side projects and have always disclosed my side projects to my boss. I want to be absolutely sure there are no surprises. In one case, I let things wait almost too long and had to tell my CEO that he shouldn't be surprised to see an article about my side project in the Seattle P-I the next day[1]. That was a mistake I've never repeated. Fortunately, there were no repercussions in that case. I got lucky.
Here are my thoughts:
* My side projects have—without fail—made me better at my day job. For instance, when I had my last 'real' job as an iOS developer for a startup, my side project was Cocoa Controls[2] (http://www.cocoacontrols.com http://www.cocoacontrols.com), which shaved dozens-to-hundreds of hours off our development schedule.
* My side projects don't compete with my employer's line of business (or potential future directions). The last thing I want is to get embroiled in a lawsuit down the road over IP theft.
* My side projects never use company resources. That means no working on it at work, and no using that company laptop.
* I do my best not to discuss my side projects with my coworkers. I'm happy to chat about them if they bring them up, but I don't go out of my way to discuss them.
* Way back when, when I worked at Microsoft, I had to sign a moonlighting agreement that specifically spelled out what belonged to whom and what each party's responsibilities were. If your company doesn't have one, I recommend trying to introduce one.
[1] http://www.seattlepi.com/business/article/Seattle-startup-Dibspace-hopes-to-cash-in-on-1303182.php http://www.seattlepi.com/business/article/Seattle-startup-Di...
[2] Which is now my real job. Win.
- alok-g 14y agoLegally speaking, merely mentioning it to your boss does not necessarily shield you from a lawsuit. It certainly reduces the likeliness though in my opinion (i.e., have no data). Further, "employer's line of business" is very loosely defined. If you could share the technical skills between your job and the side project, you are most likely in the same line of business. Here's a book I highly recommend: http://www.amazon.com/Intellectual-Property-Open-Source-Protecting/dp/0596517963/ http://www.amazon.com/Intellectual-Property-Open-Source-Prot...
- rst 14y agoI've got my boss (well, actually the CEO) to sign a paper acknowledging the side project, and disclaiming any interest on behalf of the company. Hopefully, that counts for at least a little more.
- taylorbuley 14y agoYou have a very progressive boss.
- StavrosK 14y agoWait, if you don't work on it at work, why does your employer care?
- alok-g 14y agoI am not sure of the answer, but here is what I once read somewhere: If, according to the contract you may have signed with the employer, the IP you create belongs to the employer, and that IP is earning a lot of money, then the employer is liable to the shareholders for recovering that money or an appropriate portion since it legally belongs to them. This is in addition to the point in the OP, which is you may be exhausted while at work.
- grumps 14y agoYes... I've had to sign those contracts before. They are brutal. Equivalent to selling your soul.
- rst 14y agoMany employment agreements claim rights to anything the employee invents which is related to the business, whether or not on company time. And in some states, it's common for the claim to be on all inventions, whether related to the business or not. (California has a carve-out in state law: an employer can't claim stuff that was not done on company time, nor with company resources, and which does not relate to the company's business. But many states, perhaps most, have no such carve-out. And even the California rules are subject to interpretation; what isn't related to the company's business if the company is Google? So, it's wise to consult a lawyer regardless...)
- dredmorbius 14y agoWhich is a very good reason for the smart kids to stick to California for their professional lives. Trying to fight your way out from under a noncompete, or lawyer up on account of a side consulting gig or independently conceived and developed idea, really stinks. And the further you get in your career the more likely you'll encounter such a situation. Such cases ultimately seriously dampen both enthusiasm for the employer, and the odds of finding talent interested in working under such a regime. Of course, the ultimate negative would be for California's exceptions to be attacked by corporate interests.