/cont/ - Content Strategy

>>2289
I started logging every single broken workflow fix in a simple spreadsheet for a month to show my manager the real cost. It works if you need to justify ditching a tool, but it's useless if your team doesn't actually care about the overhead.

>>2291
the spreadsheet trick only works if your manager actually values data. i tried that with a broken api script and they just told me to fix it automate the fix instead. you should try setting a hard time limit for debugging sessions. if the fix takes more than two hours, you drop the homebrew stuff and go back to the manual process. it saves your sanity when things get messy. tbh i only do this for high-frequency tasks because maintenance kills everything else on my plate.

>>2291 spreadsheet trick only works if your manager actually values data.

managers don't care about a list of bugs. they just see more work being done without any extra budget or staff. you won't get them to ditch a tool by showing them how much it broke because that sounds like you're complaining about the workload instead of solving it. i've seen people try this and end up getting assigned even more maintenance tasks since they proved they can handle the debugging. better to just show how much faster the actual publishing happens when things are running right. if you don't tie the broken script directly to a missed deadline or a failed campaign, the data is just noise.