My Boss wants all my VBA coding disclosed before termination

[MrMarlon]

Hi team, I have worked with this company two years and business is not going well with this company, ant to make this story short the company will be laying-off a group of employees and I am on that list.
My boss has always been very impress with my job performance as I have through the years and with the help of the brilliant people from this forum, managed to automate every single office task in this department otherwise would be very time consuming or hiring extra personnel would be necessary to accomplished it.

He wants every single line of code I have been able to put together to disclose it in very detailed so the next guy that comes in will be able to operate and do the job in the same way.
I need to know how far can a company legally force you to disclose that information or "intellectual property" so they can re use it to their advantage the minute I walk out the door. I will appreciate all the MrExcel community comments in regards to this issue.

 

[Richard Schollar]

Assuming you've created the code on company time (and sometimes, even if it's on your own time, depending on the wording of your contract) the company owns the rights pertaining to your code. Of course, owning the rights and knowing how to utilise the code are two separate things. I think it's up to you whether you give a detailed useful account of how to operate the code, or whether you just write a load of crap. Guess it depends on how much you value a reference from your boss...

 

[MrMarlon]

Thanks Richard, is a very good input, not what I wanted to heare though,
and yes 25 percent of code was created on my own time, but again I could you just write anything I want right?, just don't want to be liable if they later find out that the code I disclosed was actually an old chineesee soupe recipy.


OK team: any other comments on "Intellectual Property" please?..

 

[Charlie45]

It would seem to be you could just reveal the code. An explanation on how to use the code would be YOUR "Intellectual Property" because that is your knowledge you brought with you to the job. This came from your education, background and previous work experiences. Now if he wanted to reimburse you for your education and previous employers for what they spent in trainging you he might have a valid case.

 

[Smitty]

The code's the company's, period. But I'm pretty much of the opinion that any explanation that's not already documented in the code is entirely up to you and how generous you feel.

I feel it's never a good idea to burn bridges, especially if there's an opportunity to go back, although I don't know how much I'd want back with someone who axe'd my a$$. Or as Richard mentioned, you value a reference. Sometimes going out of your way on the way out can help your reputation, especially in a small industry.

I document all of my code, be it for my company, consulting projects, or just stuff that I do, but that's just my habit. Documenting doesn't mean that any Tom, **** or Harry can just pick it right up where you left off, and it's not your responsibility to teach the next guy how you did what you did, unless they make that deal with you. I also have my own style of documenting, just like anyone else, so what may make sense to you could be Chinese to someone else.

Frankly if the code's that important to their processes, I'd be asking how to get my name off of that list, unless you don't mind being on it, in which case it's your bridge to torch or not.

HTH,

Smitty

 

[Joe4]

Quit today, and offer your services back as a consultant at twice your salary to do they job they want! OK, that's probably not feasible, but wouldn't you just love to that?

Like the other's said, anything you did for them is not your intellectual property, its their's. I would document it, but not in great detail. Also, be prepared to be contacted numerous times after you leave your job by them, as they have questions (that happened to me). There's your chance to make consulting $$$'s (or stick it to 'em!).

 

[MrMarlon]

I appreciate all of your comments, and definatly will try not to document in great detail. One thing is for sure:
Everything I know and learned from all of you here, will stayed with me and that is all I need to move on.

THANKS again Guys!

 

[Greg Truby]

Ditto to what Smitty said.

• You don't own the code you wrote while using their computers/resources and getting paid to do it any more than someone in marketing would own a catalog or a print ad he designed.
• Never burn a bridge, no matter how much you might be itchin' to do it. Be gracious as you can possibly muster. A poor exit can erase years of hard work in people's memory. Leave everyone with a wonderful impression of you. More people than just your boss will be noticing how graceful your exit is.

 

[MrMarlon]

You Got a point there,
Thanks Greg!

 

[Greg Truby]

I jotted that down quickly yesterday to encourage you not to do anything "hasty", but I had to scoot out the door (kids'll do that to ya).

Four things to do or think about:<ul>[*]It sounds a bit hokey, but you might just try applying a tip that is given to Customer Service Reps for how to handle on-the-job stress. Get a few Q-Tips and place them in places your eyes will fall from time-to-time. The Q-Tip is to remind you to Quit Taking It Personally. Sounds like there are lots of folks that are going through this. It's not about you personally. So don't internalize the stress by interpreting that way. Be teflon, not a sponge.[*]Understand that what you're feeling is indeed quite common and to be expected. Don't feel too guilty about your initial reaction. You're bound to be somewhere between a-bit-ticked to mad-as-he11. And all of us that code tend to think of our code as "our babies". We wrote it. Our programs are the offspring of our intelligence and problem solving skills. If it helps, liken yourself to an artist that has been doing commission work for a patron that has been buying all your canvasses.[*]Put yourself in you boss' shoes if you can. The very fact that he even cares about how well documented the code you wrote is, indicates that he is cognizant of its value to his operations. Now he has to deal with a headcount reduction which sucks from all points of view. Those that are cut are unemployed and probably uninsured. Some may be breadwinners. Those that stay are wondering "how long until I get cut" while simultaneously thinking "great, now we'll all have to do our jobs plus all the work those that are leaving used to do." Your boss has to cope with all of this upheaval and plummeting morale while still taking care of the regular business of the company. If he's been a good guy to work with, what's the harm in bending over backwards to help him out right now when he could really use one less whiner and one more "go-to-kinda-guy". Before you walk out the door that last time, ask him if there's anything else you can do before you go. Shake his hand and tell him you wish him all the best in turning things around. If you enjoyed working with him, tell him so. Remember, he's probably having a pretty crappy month/quarter/year too.[*]And finally think long term. Depending on the size of your market (city + industry) this could really pay dividends one, two or three years down the road. Who knows? Your boss may know somebody and mention what a great chap you were during a real shi_storm. Plus kindness and goodwill always nourish your spirit more than "giving in to the dark side". And remember: you took the know-how with you, didn't ya?! :wink: [/list]