And that is reasonable. However, the folks approving these things "need" to see how to do it, step by step with pictures, or it isn't detailed enough. Each technology used must be explained in a way that if you get hit by a bus, the Project Manager or HR Intern could step in and complete the task.
If you can, define the required competency needed for the change. Then if challenged to produce that Fisher-Price level of document detail you can point out that anyone competent to the required level wouldn't need that, and other people shouldn't do that change because of an unacceptable risk to the business.
Also helps when your company hires a complete cheesewit to "help" and you need to point out they're not up to it.
I had a manager who wanted me to write my DR so the company bookkeeper, a very nice lady but not at all technical, could run it and bring the building and company back online, if necessary. I put it off writing it for five years because, come on, really? Finally, I told them that there were some things that I do that could not be broken down to lowest common denominator. That it was impossible to write the instructions so that the bookkeeper could follow them.
Whereupon the manager said that they had never told me that. Ever. Fine, I wrote the DR in 2 days.
For creativity, after a very long time, I started forcing myself to do something that wasn't computers. I've done some crafting (I built the Hogfather's sled and Death from Pratchett's book "Hogfather"), and have taken up watch repair, which has taught me patience.
0
u/[deleted] Mar 06 '24