10,000 person tier 1 tech company, 80% of the staff are software engineers, so let’s be conservative and say the average cost of an hour of each employee’s time is $100.
I’ve got a great idea, lets implement a tool that means it takes a minimum of 4 hours to complete the process of booking flights, so that we can better enforce budget policies and make sure people don’t spend an extra $50 on flights.
Let’s also ignore the fact that the “cheaper” flight the tool makes you book is several hours different timing to the one you wanted, meaning you’re now losing nearly 8 fucking hours of productivity…
Yeah… but you saved $50 on the flight…
Yeah… but you saved $50 on the flight…"
How does a cheaper flight lose productivity, I have never been flying or in a plane before.
Then also red-eyes, it's hard to sleep on a plane, so you may get to somewhere in the morning but if you didn't have a full nights rest, what's the point? You're exhausted.
https://www.smithsonianmag.com/air-space-magazine/how-much-w...
It's really not a worthwhile effort getting everyone to learn the domain specifics, and a few domain experts to translate works pretty well, despite looking silly.
Unfortunately the software is so bad and so complex that upon deployment, they realised they couldn't just roll this out for direct access to staff. It is full of travel-industry terminology nobody understands combined with corporate org policy terminology few understand.
So they designated specific staff as "travel managers" who would be the ones to book travel for their group. These people then get special training etc. In practices however none of the managers have time for this so we are all delegating it to admin staff that already do other admin type work for our teams.
And so the whole exercise has brought us full circle to where dedicated staff are effectively manually booking travel for us. And of course then COVID hit so nobody traveled for 2 years after that and we all prefer remote / zoom as much as possible anyway.