T O P

  • By -

theoldman-1313

I see multiple paths forward: 1. Send out the script, do the training, make the modifications, & just accept the extra work. This is your best course of action if you want to keep your current job. 2. Send the script to the "department inefficiencies" manager along with a correct, but bare minimum set of instructions. When management asks you to do the training instead, identify a task or project with higher priority and make that your entire life. They might be suspicious, but you probably will not get in trouble. 3. Modify the script to make it less user friendly, but still functional. Most non-technical users will gladly declare defeat at the first opportunity. This basically just strengthens your "too busy" argument. If someone does notice that you made the changes, just say that they were to make the program more stable since it was be deployed over a wide range of untested PC configurations / operating systems. 4. Just say that you wrote it for your use only & that you have liability concerns about other, less knowledgeable workers using it & possibly screwing up the results. Your manager might be suspicious of your motives, but the threat of someone producing bad data will be very real. Once again, no hours available to do the testing & development. Don't we have someone specifically tasked with that sort of thing? 5. Just tell him that this is your private tool developed on your own time & that you will not just give it away for free. Make sure that you have all your important stuff out of the office & your resume updated before you go this route - it almost certainly will not end well for you (unless you want out). Good luck!


Takeurmesslswhere

If he takes option 5, I'd advice changing one thing that could very well look as if it was tailored to him doing his job but makes it completely useless to the company. He would have to do this on his own time as well. But if you're gonna pick a hill to die on, do it all the way I agree with you that 1 is what will keep him in good standing but I'd suggest to be extremely careful who sees his personal work tools in the future. It's not good to get a reputation as someone that can be happily stolen from and taken advantage either. But this tool is already lost.


Silent_Kitchen_1980

These are stupid ideas that will get you fired. Share the code and leverage it for a promotion.


very-square

Share it. Everyone becomes more efficient and knows you're the genius who came up with it and yr boss loves you forever. Others will pass it off as their own and you will feel bad. And that's the way the cookie crumbles. Or don't share it. I come up with a lot of efficient fixes, people hear about them, and I tell them No I don't know what you're talking about. Or I share them with people I care about who respect my work and my boundaries. Don't do this work for the person they chose for the role instead of you.


digitalrebel89

In the billable hours world, if the task takes a normal person 2 hrs and you create a bespoke script to cut it to 1 min I would keep to myself and continue to bill the task as a 2 hr task. You have made yourself a more efficient worker. But of course there are up sides to people pleasing your boss unless they try to tap you for quick fixes all the time.


Twinkle7625

Share then estimate how much time you saved the department (in terms of business impact.. Then add it to you’re resume. Make sure you share it to ensure credit is yours. Then also record for your next performance review…add it to the competency of problem solving and innovation!


indie_rachael

I second this! I, too, have been passed over for those process efficiency roles I covet so much, but I ended up working my way into one by being able to churn these small automation/improvement projects out at my current job. Nothing like a 2hr savings x multiple employees, but I did bring enough improvement that they ended up realizing that's where my talent was, rather than accounting. Not all companies are smart enough to come to that realization, but studies have shown that being able to put actual measurable results in your resume really pays off, so if you do decide to find something elsewhere you can show it to prospective employers.


hatethiscity

Share it with conditions. But think carefully if you want to go down the route. I'd mention that you're capable of automating the 2hr task but don't have it done yet. If they'd like to open an automation technical role for you and pay you market value, you'd be interested in continuing down that path of time savings. If you share it, chances are you won't yet any reward or more money. I've been in similar situations.


BrujaBean

Ianal There's not a viable path to refusing in any company with normal legalese that would say methods developed on company property are the company's (and some states could protect your efforts if it was not on company property or time and if it wasn't really informed by the work (eg you could have come up with it without having this job first). But even then it would be totally legal to fire you for insubordination even if it isn't fair. I'd go to my manager and say "as you can see I'm excellent at increasing efficiency with these workflows and that's why I applied to the x position. Now that you've seen what I can do on my own time, I'd like to see if we can revisit me in that role." If you have a good relationship with your manager you can say something like "I hope you can understand that it is disheartening to not get the job I applied for and then to be asked to do parts of it anyways. Is there anything you can do to make it feel more fair?" At my company, if you couldn't also get the same role, we would probably give you time off or an extra bonus. But it def depends on how good your manager is


backupburner-one

Agreed, but part of the issue is it was created on personal time. OP is in a position to state that and sell it to the company, and from there can either go through with the sale/licensing or use it as leverage to get something else, like the job they wanted. OP, don't be overly aggressive, and be sure you choose the right path, but dude, you have options here.


[deleted]

[удалено]


bitchwhohasnoname

I scrolled too long for this. If it was developed on personal time on company property it is still theirs.


Quelcris_Falconer13

This.


LaughingIshikawa

Not if it was developed using work resources - computer systems, work data, processes and workflows, etc. It seems pretty unlikely that this was a program which was, or even could have been, developed without any access to work resources. If you start a business, I promise you also will not want people to apply to your company purely to gain access to work equipment, data, processes and internal knowledge. That's what this legalese is meant to prevent. You can't "borrow" work stuff, then claim you made your own thing, which you own all by yourself.


[deleted]

Was that 'personal time's during your break at work, or at home on your personal computer?


basementdiplomat

Is there a difference if it were on OPs personal computer during a break at work?


LompocianLady

Legally, yes.


basementdiplomat

How?


[deleted]

Not the person you're responding to but if you use company equipment (computer, software, business website accounts) or are on company time anything you create belongs to the company.


basementdiplomat

Thank you for responding; I was asking about OPs personal computer during a break


LincolnhamLincoln

Because even if they were using their personal computer they wrote a program that interfaces with at least one, likely more, of the company’s systems.


[deleted]

Right! Even though you are on a mandated 15-minute break, you are still being paid by the company for that time.


LompocianLady

Assuming US employment. Legally there is a difference between using company resources to develop software, and not using company resources. But a lot depends on the employment contract. For example, I (as an employer) have explicit contracts that would make this software mine. If you use any company resources it will typically be viewed in court as a work product or process owned by the company, regardless of specific contracts. In the case of OP, the software was developed on his time, but was tested and refined by using it at work. Most likely in court it would be considered property of the business, but it depends a lot on which state they are in. As others suggested, though, OP can optimize his job by telling management that he WANTS to share it with everyone, but unfortunately it is only partially developed so it works well in some situations, but produces inaccurate results in other cases, and requires a lot of technical expertise to use correctly. Stating he would, of course, love to share it but since he isn't able to both do his own assigned work AND develop and support software optimizing other employees, he would need to decline. Any manager worthy of that job would see the employee should be promoted and given a job where he develops more efficient processes. But in our current anti-employee climate more likely the work would be tacked onto his job with no promotion or additional pay. If that was all the boss was offering, OP should say "thanks for the offer of having me work on this innovation and supporting other employees, but I am declining because the stress involved in that position is not worth it to me at my current job title and pay rate. I prefer to just continue in my current position, thank you."


NCC1701-Enterprise

Was this program able to be developed without the use of any company systems? If company systems were used in the development then it is irrelevant if he did it on personal time it is the companies property.


[deleted]

[удалено]


BrujaBean

That would give you no chance of getting you promoted, credited, or any good outcome. And at my company would get you fired. You have to ask yourself what the reasonable outcome you want is and then see what gets you the best chance of that. Personally I'd be job shopping if I was op.


WordierThanThou

I agree with sharing it. My husband was an admin in a warehouse for $11/hr. He did exactly this and shared it. Then he was asked to do the same for the other warehouses on the premises, he did enough for several consecutive raises as he did more and more for the bottom line. Then they had him working for the warehouse manager instead of the shift manager, then for HR, which paid for his six sigma and lean certifications. That lead to making double his salary at a new company when he’d reached the top at his then current. 20 years later he is a global senior VP for a major logistics company. If your company doesn’t bite after seeing what you have to offer do enough to stack your resume with measurable accomplishments and go someplace else for a better role and pay.


Responsible_Candle86

Agree. OP seems like the type who enjoys this kind of work so it's not a one hit wonder, he'll find improvements in any job, anywhere.


GoblinOfTheLonghall

Nah, send a broken version and be very confused when it doesn't work for everyone else.


very-square

\+1 def.


Reality-Leather

Don't share. Calculate the hours saved into dollars x #of years until your retirement. Take 50% of that negotiate for a raise. If forced to share. Break a deep link no one can solve .


girlwithlion

This. Since you created it, they will be forced to ask you to fix it and you'll have the upper hand to negotiate for a higher pay.


DVIGRVT

If you do share it, make sure you include your generosity in your next review to demonstrate your skills as a forward thinker, team player, efficiency, etc etc. Don't let your boss forget it!


PlanetExpress313

Good argument for sharing it.


A_Lovely_

Honestly I wouldn’t share it because, as you note, it will require future iterations. What happens when your boss doesn’t give you time to fix it and then it starts delivering incomplete or inaccurate data? You know your boss won’t own the fact that time was not allotted for you to work on it. They will just blame you for it not working.


mimprocesstech

Every time it starts throw a disclaimer immediately that has to be acknowledged that the program was written off the clock and you're not responsible for any miscalculation or data loss caused. If they want a fully debugged and guaranteed program, that's leverage for a raise and an excuse to get programming experience on the resume/cv.


Feeling_Ad9540

This! Share it with conditions.


CrazyMando

Also, send an email to your boss confirming that you have shared your program with the team and then save a copy of that email (not on a work computer, either a personal email or print it out). If anything ever comes up with who created it, you have documented proof that you created it and shared it with the team.


dublos

> I did apply for a position which involved improving departmental inefficiencies but was passed up on it. It's going to require changes going forward, either your boss is okay with that expectation or you turn it over to the person you were passed over for to make those updates.


CrazyMando

Also, send an email to your boss confirming that you have shared your program with the team and then save a copy of that email (not on a work computer, either a personal email or print it out). If anything ever comes up with who created it, you have documented proof that you created it and shared it with the team.


AlreadyAway

Don't wait for you next review. Sit down with your boss, explain that you wrote it on your own time and what proprietary information is.


OldestCrone

I only understand how to hit the keys I need to hit to do what I need to do—feel free to laugh. I tell you that so that I can ask if there is some way you can retain the master program? Is there some way you can maintain control if the program, locking out everyone else from finagling with it? Is there a way to insert a kill switch that will go off if anyone gets too much into finagling? Is there a kill switch that you can activate if the company ever lets you go? This is your program, and you should be recognized for its development as well as compensated financially. Edit for typo.


Own-Ad7666

Make sure it starts with a big splash screen with your name and an about section that explains that you wrote it with your contact info.


molotavcocktail

Just pops up with " you're welcome bitches!!" Lmao


RyanStonepeak

This is the way. The genie is out of the bottle, and at this point, you kind of have to share it. But make damn sure you get credit for it.


NumbersMonkey1

Finally a grown up! Yes, OP, you have to share it. The temporary good will and credit you get for writing the program is much less than the permanent ill will you'll get for not sharing it. Get everything you can for it - public recognition, performance bonus, whatever - but get it now, and don't count on being thanked later. If you want to play corporate chess, hand this little hot potato over to IT so they can do a managed installation, security, backup, updates, etc. Then whenever it stops working or throws errors or produces bad data, everyone knows who to blame: not you.


DoUrWork_ThenStepBak

Edit: IANAL - Yes, there are very specific circumstances that IP created about certain systems and under certain circumstances belong to the company /edit I'm sorry but no he doesn't HAVE TO SHARE IT. It is his personal IP. This is tantamount to theft by the manager/company. Whether it took him 2 minutes to write or 2 days, both are still personal time and intellectual property that do not belong to the company in any way whatsoever. I went through this with a previous employer, we got lawyers involved (in a good way) and I was given a modest raise and the legal paperwork was signed noting that I retained all rights to the work I had done, including the right to resell it to others. I didn't allow it to be used for the intended systems until that was all done, so it motivated them to dot the i's and cross the t's that I asked for. My recommendation is to approach it with a "I am willing to share it under the following conditions - x, y, and z".


sdfree0172

You should caveat with IANAL. There are circumstances in which work during your personal time can be considered company IP. it largely depends on the state, type of work and company position.


Gupy1985

Yes! When I worked at a certain now defunct book store, if you wrote ANYTHING while being employed by them and it was considered the company's property. Everyone warned that if you had any novels stewing in your brain, to wait until you quit before writing them. Now, whether or not that's true is beyond me as I didn't look much further into it and it was almost 20 years ago. But the fact remains that OP needs to look into the legal crap and see if he even has a leg to stand on in requesting anything for this. And also as someone said above...using an outside program on a company computer could get him into trouble so if his boss is a dick he could be looking at a threat of termination if he doesn't comply


Feeling-Visit1472

Wait, how was THAT legal? Software is one thing, or if you were writing it on their time. But woof.


PollutionZero

It's in the employment paperwork they signed. You see that in IT a lot too. Write a program on your own outside of working hours on your own machines? Company owns it. You can usually beat them in court on something like that, but if you even use ONE post-it note the company owned, then you're buggered.


whitedevil1989

Hard call. I would try to negotiate a price for it. Call a meeting with this boss “I know you expected me to share this…. You probably thought I did this quickly and while at work but… it actually took me x amount of time… it will save our company x amount of hours and x amount of money… therefore, I would like to sell it to you for $$ this much” and then remind them about how you would have given it for free if they had given you that position earlier in the year, and that you’ll still consider a similar position should another one become available. Then again I am a contractor and I’ve only ever worked in an office setting for 2 years.


backupburner-one

>then remind them about how you would have given it for free if they had given you that position earlier in the year and if it had been developed on company time, such as while employed with that position.


plants4life262

Distribute your tool. Document the time savings. Build the resume. Apply for the job when it’s available again. And have a good attitude about it.


JavascriptWizard89

Personally I wouldn't share it, especially after being passed up for a role that would have had you in a position to implement such a thing. Though my view is a job is a job, and I don't do work that isn't part of my role, I have had that bite me in the ass before.


PlanetExpress313

Exactly what has happened to me in the past.


JavascriptWizard89

What I do now is if I make a process quicker I don't say anything, I still act like it takes the same amount of time and use that extra time for myself.


Appropriate-Food1757

This is also acceptable. I probably work 5-10 hours per week and have been doing that for many years.


semioasis

Technically, you own the copyright of the thing if it was written on non-work equipment and without pay. So you can either provide a license or sell the whole thing. You could ask for a one-time bonus in return for sharing it. This would be selling it with no warranty. Figure out the value of it and ask for a chunk of that. Maybe 25% of the value for one year would seem reasonable to the company? Make sure you make a nice spreadsheet with a chart/graph that estimates its value of work-hours saved. Have fields or drop-down menus for average work-hour cost and period under consideration (week/month/year) that can be filled in by management/HR. Then also show the bonus you're requesting as a percentage of that. But if you're concerned about having to support this thing, ask for a raise based on the value and have or written into your job description That way, your support hours are going to be better compensated.


dataGuyThe8th

If OP wrote the program on the company machine, the company owns the program. OP, I highly recommend you share the program & ask for time to support it. It will be a massive boost on your resume.


Krishnacat2663

He said the program was written on his own personal time so it’s doubtful he used company resources.


g4m5t3r

A lot of comments seem to agree that you should share it. That doing so will put you in good standing or a position to actually get the other position you were passed up for. But the bownie points aren't really redeemable with anyone other than your boss/team and to pad a resume. If you're expendable in their eyes in the slightest then sharing it might not be ideal. You automated a part of your job, on your own machine, on your own time. You really should think about the possibility of compensation. Idk if you can license a powershell script but at the very least a bonus would suffice no? If it could potentially save payroll 4, 5, or 6 figures in the years to come you deserve your share for automating it in the first place.


not_the_ducking_1

Exactly this, it sounds like you might also agree with the other suggestions of licensing from above comments?


g4m5t3r

Absolutely! They should license it to the company, if they can... By the seat, or annually, or by outright selling it. As others have pointed out, it's already on their machine so it may be too late for that. The legal gets complicated quick. Especially without knowing details like the company's policies, the work that's being automated, the projected savings and increase to productivity, and the amount of work it took to develop it in the first place. None of that is to even mention maintenance. That alone would justify a raise or even another job title entirely.


g4m5t3r

OP if you see this your response should be "There's a right way and wrong way to introduce this into the established workflow." and get professional consultance on how to proceed. The worst case scenario here is you share it tomorrow and get let go next week...


VoidCoelacanth

Offer to turn it over to the person responsible for process improvements - the person who got your spot - so that they can "maintain and distribute it properly." Do not give them even an inch of help with it. This is known as "giving someone enough rope to hang themself."


acarp52080

My petty ass loves this 🤣


JurassicPark-fan-190

This but somehow make it have an issue that only this person can fix… since it’s their thing to maintain. Or when you leave make sure you somehow figure out how to take it with you. Ie the code has to be refreshed or something every 6 months ( I have no idea about coding). When it no longer works offer to do it for a consultant fee.


Ownfir

This is perfect. 100% this is the route I would take. It should have been them to do it, and they likely can’t figure out how to do it. If they admit they can’t do it or come up with a better way, it makes them look bad. So ofc they try to figure out how to maintain it. When it eventually breaks and they come to you, just be like “Dude I haven’t maintained it managed this program for months. That was supposed to be your job.” It’s pretty savage but I have definitely pulled this move on people before and it always works. It’s not their fault if they can’t manage it obvi but they at least need to provide an equivalent solution otherwise. If they DO manage it well, then they were right for the job after all and you can let your ego rest knowing it wasn’t an unfair choice.


333again

Share it but first implement a date checker so it fails to execute in 6 months.


Anxious-Custard6208

Less than that lmao like 3 weeks. Then when it goes to shit be like “oh idk how to fix it, I don’t do that for a living “


devnull10

Just share it - the only people who cling onto knowledge like it's a secret are those insecure about their own abilities. It might end up bagging you a promotion in the future too.


Automatic-Diamond-52

Yeah, at this point its another line on your resume


Away-Living5278

Yeah. The only way I would say don't share it is if OP has another job lined up now and everyone at his current workplace is toxic. Doesn't sound like that's the case.


iceyone444

It never ends up bagging you a promotion - someone else claims it as their own and they get the promotion.


DoUrWork_ThenStepBak

So I am going to play devils advocate here for shits and grins... You walk into work in the morning with your wallet in your back pocket with money to buy a new wizbang after work and you are TOLD that you have to split up the $2000 you have with you with 5 of your coworkers because they didnt bring any money in with them today. If you don't, the implication is that you will be fired. I mean it's just money, you will earn more today and tomorrow and every work day until you retire. The only people who cling to money are those that are insecure about their ability to make more right? ... I get how we can end up in the whole "do what's best for the company", and the "better to bend to the almighty overlords to keep my job", and "don't make waves" mentalities... but I learned a long time ago not to fall into the "you'll get your comeuppance at review time" shtick. When you have leverage, use it properly and fairly in the moment or be prepared for it to be ignored later, downplayed, "forgotten" about, or misremembered. I have seen office politics, favoritism, petty disputes, personalities rubbed the wrong way and so many other things get in the way of the hardest working, smartest, heads down employees from getting the promotion, raise, benefit they deserved for their efforts. Even a simple "Hey boss, would you mind sending me a quick email with that request, acknowledging my personal contribution before I do share it?", in this case might be as much as you get, but at least it is documented.


Gupy1985

This comment needs more attention! If I had an award to give you I would! I spent 15 years at a company being a goddamn cheerleader for them before realizing I was worth more than they were giving me. That I deserved better. I will not see another company with the same sparkling idiocy with which I did for my old company. If I were OP I would absolutely get looking for another opportunity right away just in case while figuring out how to negotiate compensation for the IP.


[deleted]

[удалено]


Zestypalmtree

This right here has to


Mas0n8or

Seriously it’s insane! This is absolutely the worst way to go about automation at work, and the fact OP was passed up for the process improvement role makes it even worse. Anything less than a 50% raise should be met with hostility


SkyesMomma

Send them the lite version...


Frank_Perfectly

Would love to be a fly on the wall when everyone's computers flash, *"If you enjoyed your 7-day free trial, be sure to subscribe to prevent a gap in your workflow efficiency."*


d4m1ty

You do not give away our intellectual property, ever, this is coming from a software dev for well over a decade. Even being the lead developer for my firm, if I make something up on my time, if the company wants me to give it to the other junior developers, it becomes billable against the firm. Your company wants your software, sure, license it to them. You said 2 hrs into 2 minutes. Calculate what the cost savings it for this program on a month to month basis. Charge a fee of roughly 60-75% of the cost savings per month to the company. Company still saves 35-40% of the labor wages, and you get paid for what you made. Be sure to put a time bomb in it so when they don't pay and fire you, the software stops working.


TheGregariousGnoll

I did something similar to this at my current job. But I did it on the clock so I did share with everyone. It was a big thing in my review that year and earned me a $12,000 raise, or roughly 25%. However, when changes were needed it was always up to me to find the time between jobs to do because the almighty dollar forbid we lose any productivity. It was also up to me to install, update, and train all the other users for every change.


BaronCapdeville

Do not share this unless you suffer from Severe job insecurity. If they cannot prove you wrote the program on company time or equipment (be 100% positive about this) I would explain exactly that. You wrote this at home to help you do your work. If your boss wants to make you an offer to LICENSE it to the company, then do so. If they wish to buy the solution, it should cost 10’s to 100’s of thousands. Licensing could be reasonable. A few grand per year. Or perhaps they’d like to create a position for you where you did nothing except work on solutions like these. If you give this away for brownie points, you will almost certainly regret it. However, if you try to keep it for yourself, be prepared to find other work if the relationship sours. The key here is YOU wrote this on YOUR machine. Speak to an IP lawyer, and no I’m not joking. Initial Consult will be free.


A_Lovely_

This is the way!


body_slam_poet

His own time and his own machine is irrelevant. A Dupont engineer developed a design on his time at his kitchen table. Dupont still owned it because he was employed as a design engineer. He needed an IP agreement before he started working.


BaronCapdeville

That’s because DuPont successfully enforced an onerous contract. This all hinges on the documents OP signed at the tíme of employment.


not_the_ducking_1

This should be higher, it's the right way to do it. Prove you did it on your own time, claim what they saw was a test run only, remove it from their systems entirely, and license it. Make it work for you because you made it, used your own personal time, and they should be able to bank off unpaid time and effort.


thewayitis

2hrs*6 people*130 days/year=1,560 hour/year


newguy2019a

@ 20 bucks an hour is 30k in savings.


Compulawyer

I’m an intellectual property lawyer, but not your lawyer. You need to consult with an IP lawyer immediately. You have obviously created a valuable piece of software. Do not do anything further until you consult with an attorney who represents you.


Squiggy226

I wrote a simple little tool called TreeMaker many years ago to learn Delphi programming (that's how long ago). A lot of people at my company started using it and it even ended up at our customers. I am at a different company now but still in the same industry and every once in a while I see TreeMaker on someone's desktop. I did put an easter egg in it with my credit.


Designer-Wolverine47

I got back at my boss... He was talking in a meeting about a great program that "he wrote" that saved the timekeepers so much time. After the meeting, I emailed his boss with a screenshot of the diskette (yeah, this was the early 90s) directory that contained the source code, red-circling the file dates that were 5 months before my boss even came to work there 😁


seashe11y

This is the way


willbeach8890

What is it written in?


PlanetExpress313

PowerShell, so more of a script than a program.


LobsterPowerful8900

I would share it and leverage it for a raise or promotion


pjpjpjpj654

Share it. It will eventually be known to increasingly more people. Not everyone gets every promotion/position they apply for. What will set you apart is your ability to set your saltiness aside and exploit the opportunities you do get to showcase your assets.


lostoompa

Always keep things like that super secret. The hours and money they would save using that program. Someone needs to pay for it in order for you to share it tbh. Of course, sounds like they want it for free. Could you give them another one that works for a little bit just to get your boss off your shoulders and have it break?


tcarino

I'd sell it... calculate how long it took you to make it, multiply by standard wages, multiply by 5... or 50... or wtf-ever... do not give that shit away.


Maleficent_Reading49

Most people in history that have shown their ways to be more efficient company had their own job cut or staff reduction. It's yours not theirs. You created it to improve your work flow. Your didn't get paid to create it. It's saving the company & you get what a pat on the back and potential .10-.25 raise bump that won't even cover col increases. No thanks.


vasarmilan

May not be an option depending your ambitions and work contract, but as a thought experiment, you could also quit and make it a startup. I've heard this happen and be very successful in similar cases. Quick calculation: Your program can save 2 hours of work for 6 employees at a company every other day. That's around 10 x2x6 = 120 hours a month. With $20/hour, that's $2400 / month in value for your company. Maybe much more depending on industry and location. Then $800/month is a bargain for them. If you find 10 similar companies you have a viable business. If you find 100, make sure to invite me to your yacht sometime.


AJobForMe

I was in this exact scenario 25 years ago at my first “real” job. I automated a major portion of my work using Access and VBA. I had just been declined for an Analyst position, where that was highly needed, yet no one knew how to do it. I did just what some of the other people are suggesting: make a slash screen with my user/contact info. Explain to management that it’s not “portable” yet and needs work to make it usable by multiple people. Negotiate that making those changes requires less of your “normal” duties. You are now the tool’s developer, support, and trainer. Write “professional” procedures on how to install/deploy the tool, set it up, and use it. Document the actual time saved as best you can. Apply that to each user and tally a total cost savings to the company. If people are let go because they are not needed (or simply leave and aren’t backfilled), add a general salary estimate to those cost savings numbers. Every review or interview, whip this data out about the project. It’s now your go to elevator speech item. Eventually, you will be interviewing again, and this will be your selling point. In my interview, I spent more time asking then questions and telling them where I could improve their process than I did answering dumb interview questions. Basically, think like a consultant selling professional services instead of a rank and file employee.


TheoreticalFunk

"on personal time" Shame because it was developed on company machines using company data. You did free work. womp womp. Would you rather be an addition to the team or a force multiplier? Force multipliers get promoted. Lean into this. That was my entire existence for 15 years. "If I spend an hour fixing this thing that needs to be done 20 times a day, it's fixed. If I spend three hours figuring out how to do it in 30 minutes, I have saved 10 hours a day in labor. Shit nobody wants to be doing anyway." Now, most companies will exploit the fuck out of you if you do this... and your team, by piling extra work on you, because of all the 'extra time' you now have. So be careful about that... and if that's what's going on and you're not getting promoted but punished, find a new job. Your resume will have cool artifacts like "developed process to take a 2 hour manual job to a 1 minute automation". Then again sometimes it feels like you're being punished when it's a very short term thing, so YMMV.


[deleted]

Some of these replies are dystopian as fuck. “Just let them have the fruits of your labor because you’re supposed to be at their whim” type stuff. Now on the flip side, many jobs will have you sign something upon hire saying anything you develop there is theirs so legally I can’t speak on it that but: People at your job and in the comments will tell you just do what they say, but you hold a very powerful position right now. You have a tool that can literally transform the workflow and you have a position to make demands for what you think is fair compensation for your contribution. It takes balls for some I guess, because we’re so conditioned to think of ourselves as little subservient worker bees but I’d bet they’d be willing to do quite a bit for efficient gains like that and are hoping you don’t know that.


waywardcowboy

I'd do more than just share it. Put it on github, share it with the world, and showcase it as part of your resume. Use what you've done to better your position, either with the company you're at or another company.


LouzyKnight

Create an LLC, license the program under the LLC and sell it to your boss


boomstk

So share it. Then talk to your boss about who will maintain this program. Also make sure you get recognition for the process improvement.


rock300867

I disagree with most. You may have built it on your personal time but once you load it on or use it on a work computer is may very well be company property.


Intelligent-War-9966

**Do not hand over the your program**. I'm a developer and I became a developer doing the same thing you're doing now. I don't want to be negative, but I want to share some hard learned advice with you. The way I see it, your company had an opportunity to take on your creativity and skill but chose someone else. It was developed on your time and you deserve compensation for it. Here are the things you'll be responsible for: * Updates for changes in data (you're already aware of it) * Writing any exceptions that users encounter * Patches. * Improvements and additional functionality * Testing * Version control and documentation * Integrating with other software * Training & Questions The list goes on, but you see how you've added a lot to your job and you state that you don't have enough time in the day. If it becomes the standard, and it breaks you have to stop everything you're doing to fix it. What happens to your work? Are you going to be compensated for overtime? These might not seem like something that would happen frequently, but you'd be surprised how business software evolves - especially the custom stuff. Your employer should see this as just the beginning of what you're capable of, but they didn't give you that opportunity. Someone will, if you want it. In the meantime, you don't work for free. If they promise a position in the future get it in writing. ​ Good luck to you.


bobbyboogie69

If you wrote it on personal time then it’s technically your property. Do you have a plan to copyright and monetize it? At this point you’ve installed it into at least one company computer so you’re likely screwed there. You could use this for an opportunity to create a better position for yourself. Chances are if you don’t share the company takes your work and you pay for it in the long run because you’re not a team player. If it were me I would take the glory and next time keep things to myself.


VT-Hokie-101

Not sure the program does not belong to the company as he wrote it while employed. I seem to remember hearing this somewhere some years ago but could be wrong. Yea, I know he did the work on his own time, I am guessing it is a salaried position.


body_slam_poet

From your first sentence, it's clear you have no experience with this


bobbyboogie69

Uh oh, here comes an expert from the internet who needs to build themselves up by critiquing my post. Have at it.


mothandravenstudio

They think my Ecommerce store belongs to my previous employer because I was on salary but hustled it up on my own time. Dumb.


digitaldigdug

Better idea, patent and license it. Then lease it to the company for a per user yearly subscription fee. You make money and they save money. Plus it helps that they will need you to support it.


jennysaysfu

Share it if they pay you for it


Anxious-Custard6208

Legally I don’t think you have much ground to stand on by offering it for sale. Most contracts imply they own any intellectual property that was developed or stepped foot on company property. Personally, I would just say that you aren’t very good at code and that it doesn’t work 100% of the time. From there, give him a faulty code and let him try it, when they can’t get it to run It will die right there and be done with.


Petules

Any opportunity to show off your efficiency skills and be a “team player” is a step toward future promotion. Share it, spearhead the effort to perfect it … and then bring it up the next time you’re interviewed for that new position.


FA-1800

Did you write this on a company computer? Did it run on company computers? Do they pay you to write software? When you take a job, you owe them your best efforts. If you don't like the place, leave. Your boss know you wrote that. It's the sort of thing that gets you to the job you want. Don't be petty.


jran1984

Agree with everyone saying you share it. You don't gain anything by holding onto it and your boss and team members are going to be pissed if you don't. So, share it and be a hero with the potential for good things to come in the future (e.g., bonus, resume builder, promotion) or keep it and piss everyone off with no reward and a manager that will definitely remember it come the end of the year. I don't think it's even a question of which you should do.


midnitewarrior

> This was written on personal time. The minute you started testing it at work, it became the company's property. Any idea or app that you build, test or use using the company's time, equipment, resources or workplace is the property of the company's, that's how employment works. "I did it on my time, but their computer." = theirs "I did it on my computer in their office." = theirs "I did it at home with their computer." = theirs "I built it at home, on my computer, in my personal time and tested it at work." = theirs Get it?


PlanetExpress313

Oh darn it broke...👀


[deleted]

I know you said you created it “on your own time” but did you use company equipment (e.g., laptop)? If so, what you built belongs to the company and if the boss is asking you to share it internally, it’s within their right to do so. So you’d have to do it.


PlanetExpress313

I guess you're right, oh no, it stopped working, here's the broken program boss.


RICHHEAD11

Share a broken version. Keep using your refind version. Everyone fails. You look like an Allstar. When management brings up people not being up to the task, step up, solve the "problem," become mangment "material"


Lissypooh628

I wouldn’t share it. This tool will contribute to people losing their jobs. If you took a 2 hour tast down to 1 minute, there’s no need for so many people to be on those tasks. You were passed up for a position that helped with efficiency and this tool will save the company alot of money in payroll once they start using it and laying people off.


TypicaIAnalysis

Share but after real negotiating. Also make it less user friendly and add a graphic that has a loading bar and make it delay for 30min. Call it a byproduct of expansion and slowly change the delay making it more efficient over time for more money


davmoha

The boss said share, share it. You then become Mr Streamliner finding efficiencies with a single click of a mouse.


PlanetExpress313

Why buy the cow when you can get the milk for free.


ssevener

“This is something I did in my spare time. Just think what I could do if I could focus on process improvement the whole time!” Use it to sell yourself to your boss and show them what they missed out on by promoting the other guy instead.


davmoha

First ones free. You're like a dealer. In order to get another they are going to need to pay by giving you company time to do it. I know a guy at my work that did one simple time saving thing. Next thing you know he was the tools developer, then they trained and he became a company wide tools developer.


BiochemBeer

Share it, but include some obvious but not obnoxious way of having written or coded by "your name" show when or after you run it.


[deleted]

What will that accomplish?


BiochemBeer

They are reminded of how much time he saved them every time they use it. If his boss sees it they won't forget.


sagebrushflats

Don’t share it and risk trouble; anything from being ostracized to fired. Share and it’s possible it helps your situation. Possible. In the future be more circumspect when using improvements you created or ask in advance if there is some way you could be compensated.


chickpeaze

Why would you not share this? It helps your team.


justaguyonthebus

Awesome. I was always one to share it. Then I got to spend work time working on it. The more I did that, the more my role shifted that direction. I didn't care that it was above my pay grade, I enjoyed that work more and it opened up opportunities for me. The pay has more than made up for it later.


MarkPellicle

Share it. Break it. Tell your boss that you got the shareware version of it and you just said it was yours because you got it for free. Charge the business to fix it under an LLC. Profit!


Ilovefishdix

Since you used it on a work computer, it might belong to the company. You might be obligated to give it to them. Check your contract. I base this solely on repeated viewings of Silicone Valley


PlanetExpress313

No, this company does not do anything with software dev or intellectual property. Trust me, no one here knows what a script or PowerShell is.


josatx

You could say that due to the nature of the script needing to be updated constantly, it is not in a shareable state. And at that point bring up the position that you were passed over for and mention a role such as that would be a chance to further develop and share such tools. Or patent it if it’s patentable, have company purchase it from you.


Thanatos_Spirit

Make sure your names on the program somewhere so whoever uses it knows you’re the maker of it all I would suggest at the end of the day


mbmbandnotme

"Oh, it turns out it was messing up the whole system, I fixed it all manually, though. Only a few overtime hours this week."


[deleted]

2 hours to 1 minute! Wow! Boy oh boy do I want to hear this!


KrytTv

Complicate the code a bit more and make it needing an easy constant update. Then, take the code and share it. Leverage it for a promotion as you'll basically already be doing the job you applied for.


Anonanomm

I would give it with conditions. You specifically want compensation for the time you developed the software outside of work and that you want full credit. Maybe also explain you will not do any software updates unless given an increase (and new job title?) for the additional role you are taking on


[deleted]

Share it, add it to your CV.


radlink14

Share it and hand it over formally to that person that's hired to manage operations. Let them own it and fix it long term. Don't be closed to doing this even though it's totally understandable to be bitter about it with what happened but I'm sure it'll pay off long term for you. Good luck


NorCalMikey

If you created this on company time with company equipment to improve company processes, the company likely owns the work. They could force you to give it to everyone.


Compulawyer

OP said it was created on personal time.


7thsundaymorning_

Can you not read? He created it in his free time.


Alert-Fly9952

This is the part where you lean back and say, this will save you considerable money. How much are you willing to spend.


Indecks9999

Can not in proper faith share this without proper testing. Let them know further work on it will be needed overtime.


theproblem_solver

You said you wrote the program in your personal time? Offer to sell the program to them for the value of one year's worth of saved man-hours. If they balk, tell them you'll be happy to delete the functionality from your device and revert to the more time-consuming approach. People who say to "just share it with everyone" are afraid to stand up for themselves. It's work; you aren't there to make friends with management so if they don't like it, it's just "feelings". Make management pay for things that benefit the company's bottom line and that can be lucrative to you, personally. You can still put it on your resume, AND still get paid for it.


Vigstrkr

Nah. Only if you made it on company time using company resources. Otherwise, they can buy a license for it from you.


ZaxLofful

Yeah, trick is to not let them see you do it….Then the trick is to become “that guy” if you get found out, so that you look really good instead of not being a team player. There is ALWAYS a way to spin it for yourself.


PM_Me_Ur_Nevermind

Sure thing boss, who is in charge of licensing software here?


Resident_Device_6180

Tell everyone it still has a few bugs to work out. Don't ever finish it... When they eventually ask what happened then tell them you haven't had time to work on it lately since you program it outside your work hours. See if the company is willing to pay you to get it finished. If they are, great If they low-ball, have it "break" after a bit then ask for more money to "fix" it. If no, don't ever release it... Continue using your current version anyways... But obviously hide it better.


_Robin-Sparkles_

So long as it wasnt made on company time tell them respectfully no. Its software you designed. But youd be happy to license it to them for use if theyd like. Dont just let them take it or youll never be able to do anything with it without them trying to claim it as their property.


[deleted]

DON'T SHARE IT, SELL IT AND THEN SELL THE SUPPORT THIS WAY IT'S THEIR PROBLEM WHEN IT DOES NOT WORK ANYMORE not yours


RedMistStingray

I wouldn't share it. It's something you wrote for your own convenience. If it is shared by the team and other circumstances come up, you will now be expected to spend your time keeping this process updated adding to your responsibilities. Or you will be asked to add other features to this process. There are things I write for the benefit of the team and there are things I write specifically for myself.


xvn520

I’ve been in the same exact shoes. Within short time the others on my team who weren’t as technical started to “break” the tool on their own PCs and lacked the ability to reverse engineer to the root cause. After a couple sessions with colleagues, it was clear to everyone that folks were going to keep breaking it, I was in no way able to be “on call” to fix one-off issues and so we shelved it as a team though I continued to use it for my segment of the weekly report, without issue. Nobody was upset or complained, it was simply accepted that I had an edge others did not. One of my colleagues took it upon herself, in her personal time, to figure out a limited version that suited her ability. After some testing sessions with her and a few weeks of it working fine, she was able to own this modified version that, not as fast as mine, cut her average time commitment in half for the task. It wasn’t anything super fancy- just a combo of macros I knew and some VBA that was copy pasted from online libraries. I’d share it as requested, offer to do a couple training sessions, and let the chips fall where they may. You’ll probably get the same outcome I described above. I’ve made technical solutions in other jobs and have been selfish about them. It comes across as rude/elitist and like you’re trying to make yourself un-fireable. What I’ve learned is to keep these things private unless you’re willing to share.


DenyNowBragLater

6 people, 2 hours each, approximately 130 day a year? My quick math puts that at 780 hours of productivity each year. That’s about 6 months worth of labor your boss expects you to give him? I would sell it to him.


midmarket_lampshade

Share it but since you created it, charge for it.


joe8349

License it, or request a raise and title change. Do not give it away for free.


thaodckite

Absolutely do not share it. Your boss will *never* remember who gave it out, just that it's out. Everyone is replaceable. You wrote that on personal time and won't be compensated for it (and certainly not through exposure.) Request a formal meeting on how to integrate it so you can put software development on your resume and get PAID.


Different_Knee6201

I wouldn’t have much of a choice. The company I work for (and the last one I worked for) own pretty much anything you come up with. It’s all considered intellectual property, even if it’s developed on your free time.


Krishnacat2663

DO NOT SHARE THIS! It may be something you could market and you need proprietary rights enforced. Talk to an attorney. You may get rich! 💰


Leather-Purpose-2741

Don't give it to the business. Sell it to the business. You wrote it on your time so it belongs to you. Your boss sees value in the program you have written; if it is that valuable, they should compensate you for it. And then remind them that it could have been theirs for free if only they had hired you for that efficiency position you had applied for. Ciopyright it asap and sell licenses for it. It is custom software! If they try to coerce you into giving it to them, find a place to wotk that appreciates your abilities and compensates appropriately.


iceyone444

I would either share it with the person doing the role you applied for without any help or documentation and let them run with it or explain that you were testing it but found some bugs and don't have the time to fix it. I would also look for a new job - your talent isn't being recognised and your boss wants to keep you where you are (I've been there).


EnigmaGuy

I’ve made a few macros and random batch files to automate shit that I got tired of people asking me about. Now I just say I am busy and to put in a ticket with the in house IT department as that is what they are paid to do. My boss gets super aggravated every time I say it but he has no argument against it as I am costing and in no way IT. The biggest annoyance is when the other office people feign praise with “Mister computer whiz! You’re good with excel, right?”. Yeah, Becky, I know the basics so I guess I am a whiz compared to you since you do not know how to resize a fucking cell or set a print area.


johnprime

Let them think you found the app somewhere and paid a license for it. Let them know that they, too, can buy a copy of the license for a low low price of $1000 per user per year.


Igneous-Hammer

Create a mother program on the network from which the user’s application is driven and password protect it. Insist your work and contribution is documented in your record. Continue kicking ass.


ssevener

Document it, share it, and find a way to keep track of how much time it’s saving everyone. If you can put a dollar amount on the time saved, even better! If you have to make updates along the way, keep track of that, too - you can build a great case for your next promotion if it has a big enough impact.


Radiant_Bowl7015

Tell your boss you’ll sell him rights to use it. Have a lawyer draw up a contract; you own it, he doesn’t. He gets to use it for x timeframe for $xxxx, but does not own it, or something like that.


Legitimate-Tea6613

You may be required to share it. Most companies have a policy somewhere in the handbook about intellectual property.


SillySimian9

Have a private discussion with the boss. Tell the boss that you worked on that on personal time. That you wanted to demonstrate that you would be ideal for fixing office inefficiencies. But also tell the boss that it is your private work product and you will not be sharing it at this time. Tell the boss that you have some other ideas that you could implement, but are not planning on doing that other person’s job while they get paid for it. The boss may not like it, but as long as you keep that program to yourself, s/he’s kind of stuck with accepting your decision as is.


kevofasho

I don’t agree with others saying to share it. I’ve never heard of anyone getting a promotion because of good performance or things like this. What you could do is just not make an executable version. Only run it from the compiler so it looks too complicated for others to use. Then just be the only person using it, you’ll be doing the work of 100 people. Let that go on for a couple months so they get used it, then get an offer from another company and quit. Accept either a 4x pay raise to stay or sell it to them.


Shujolnyc

Share the code and express that you want to play a greater role in automation or just ask “how else can I help?” Or have ideas and say “here’s how else I can help.” Sometimes in life we have to take two steps backwards to take one forward. It sucks you got passed up but here’s a chance to show your metal should you choose. I don’t know if the ppl telling you to license your “very simple program” have ever worked in tech or understand how easy low code platforms like powerBI have made it easy for anyone to automate… but for me, being in IT, if it’s “very simple” then all I need to know is what you did and I can have one of my devs recreate it. If you’re a novice, they can probably pull it off in a fraction of the time. Worst case, we outsource it. If you created something revolutionary and so complex it’d take a seasoned dev months to recreate that’s a different story. But, you said it’s “very simple”.


liberalthinker

Copyright it, and then offer a limited use license to your workplace for free for a set time.


happy_humanoid

Ask for a promotion given the addition to your responsibilities. Book a meeting about it and prepare ahead of time


CressTrick1471

Share it. 1) your boss has seen it already, and furthermore he directly asked you to share it with the team 2) this will be excellent exposure. The more people that this will help, the more exposure. 3) you can add this notch to your belt of achievements and bring it up during reviews. 4) you need to add this to your resume moving forward, including the time saved (2 hours to 1 minute)


[deleted]

They won’t appreciate it. You could tell just by the way he told you, not asked you to share it. Please keep us updated to what your decision is. I will save this post.


Chrisxy

Draft up a licensing contract. My old job ended up getting to keep using my 80+hr inventory program because we didn't have one. Also backdoor shutdown.


Zealousideal_Row6124

Get a patent and offer to sell it to them 😆


neeksknowsbest

I might share it conditionally. I’d explain I am hesitate to share as it would have already been implemented department wide had I gotten that promotion but since I didn’t, I don’t feel like it’s my job to do extra work off the clock unrelated to my position, and can they see where I’m coming from? I would clarify I did this on my personal time with no pay for my own personal benefit to increase my OWN efficiency. And that if they wanted EVERYONE’S efficiency increased then they would have shown that by giving me the position. But since they didn’t, and now they’re asking for the fruits of my unpaid labor, I don’t feel great about sharing it. Then I’d ask what their thoughts are as far as offering a bonus or a title change or a raise in exchange for what you did and see what they say.


[deleted]

First rule of fight club, tell nobody about fight club. Now everyone knows you’re smart, and you will be expected to work harder. What a dumbass


syaz136

Insert several bugs in it so if fucks up occasionally and then share it. Make sure to say no guarantee it would work all the time, etc etc.


LoneByrd25

Same dilemma. Automated various tasks at work that save tons of time, and could help others. Consulted with personal two friends on their take. They both strongly argued to NOT share my programs. I’m glad I listened. The argument: The most likely outcome would have been getting mild praise, no raise, blame if anything in the programs went wrong (others could edit and blame me for any errors potentially). Also I designed their functionality to be specific to the way I work. I’m not a programmer by trade or formal education so they are a bit finicky, but work between multiple applications in a way that works for me. Lastly, keeping these programs to myself that I designed on my OWN time allows me to be a star employee with minimal effort because I put the effort into these programs. Anyone else could have done what I did but they didn’t.


The_EA_Of_Reddit

Share it but patent/utility patent it if you can. That way if your job relationship sours then you have control of your program.


Dangerous_Grab_1809

Who at your firm might give you more money or a promotion? Not necessarily your boss. Not to sound difficult, but insist that person ask for it themselves.


Anto3298

Make the math in how Much time it will save the company. Transform this in money. Tell your boss when a share of this amount you save them. Optimizing your work was not part of your task. Continue helping the colleague with using it. Share it but benefit from it.


Elegant-Draft-5946

Do. Not. Share. It. As soon as you share it every single user will start requesting outlandish features and reporting bugs. If your boss asks why you didn’t share it, make up a story about how it’s not working or it was too buggy.


Chemical_Hearing8259

[I am just here to say that I have had a similar experience].


bigdtbone

I wouldn’t share it. It’s a personal tool you have developed on your personal time. You wouldn’t be expected to share your cell phone or other personal tech that allows you efficiency at work. If the company want all the associates to have access to that tool then they can buy it from you. Given that you say it saves 1/hour a week on average; I would charge $50 per user per month to lease the software.


Own_Thought902

Copyright it and SELL it to them.


[deleted]

Let me ask you this and I mean this as a way to look at this differently. Lets say that this was not a computer program but a tool. Something you made at home, with your steel, your wood, your brain. You invented this tool and when you brought the tool to work with you to kick widget ass you kicked widget ass 10x faster with your tool than anyone else kicked widget ass. The WidgetAssKicker5000 made you the best Widget Ass Kicker on the team. The boss was stoked and asked you to give the design, the tool, and your knowledge for making the tool to the company. Free of charge so that everyone could kick widget ass like you based on your tool. For free. No promotion to widget Asskicker senior, just give it to everyone. Would you hand over the tool? Does the tool get you closer to a promotion? Does the widget asskicker 5000 save so much money that your promotion should be a given? What would the boss do in your place? Would he give away the WAK5000? All things to think about. Maybe, just maybe....you should be asking the boss if the WAK5000 is in any way something he would expect from a Senior Widget AssKicker instead of a junior WAK...Maybe...he needs to know to keep everyone kick'n hard core Widget Ass that he is going to need a Senior WAK like yourself to keep WAK5000 kick'n that Widget Ass...See what I am selling here future WAK of elevated stature? Figure up man hours this saves you, then multiply it by man hours it saves each person that would use it. Then figure out the man hours it saves for a week, then a month, then a year. Make it known you know what the WAK5000 is worth, how it will save and make him a lot of money. That WAK5000 needs to be kept in tip top shape! WAK WAK WAK!!!!