Management is cutting my job after I automated 15 hours of weekly work, do I have to document it for them?

[u/Claptrap_5Z]

When I took this coordinator job, our team was losing fifteen to twenty hours every week just updating client logs and manually formatting spreadsheets.

I built a few simple macros and formula templates that cut all that data entry down to an hour. I thought saving twenty hours a week would free me up for higher-level projects.

instead, my manager called me into a meeting last Friday. She told me that because our administrative workload dropped, they are merging my role with a part-time position and letting me go. To get my severance check, they want me to write step-by-step documentation for every macro I set up.

I literally worked myself out of a salary. I should of just kept doing the data entry by hand like the last person.

Do I ACTUALLY have to document processes I created that were not in my original job description?

[u/B9-97-C5-11-DE-19]

I pasted your exact comment after "How do I download Firefox?". It did not disappoint.

It created no less than 50 sections of the most unapproachable technical slop I've ever had the misfortune of reading.

[u/FormerGameDev → u/B9-97-C5-11-DE-19]

was it technically correct?

edit: holy crap, i just tried it with "How do I download and install Visual Studio Code?" and it came out with 8 extremely extensive chapters. I have absolutely no idea if it is technically correct, because I'm pretty sure it's as long as Apple's TOS.

We probably just burned down a couple of forests.

[u/B9-97-C5-11-DE-19 → u/FormerGameDev]

We probably just burned down a couple of forests.

Training the data burns down the forests. Actual generation is much cheaper/less carbon-intensive (not that that makes it okay)

[u/dimwalker → u/FormerGameDev]

Did you try the reverse - feed it the bloated manual and ask to sum it up?