"I made the query for X, an operation that is performed Y times per day, Z% faster resulting in N% increase in Xs performed daily. This meant we could (defer hiring additional headcount|do more <profit-generating/cost-limiting process dependent on X> per day)."
Many teams don't invest in the tooling required to measure this kind of impact, but it's possible to ballpark it.
Re:Don't End the Week with Nothing (2014)
by ryandrake on Monday March 22, 2021 @03:10AM
(#26537683)
That’s a good example. The math doesn’t need to be precise, and you don’t need to track it down to lines of code. “Part of team of X developers who delivered product Y that produced $Z in revenue.” is enough for anyone to very roughly ballpark-estimate impact.
This is counter to GPs initial point, where there is a specific claim of direct profit generation. The advice is now just getting watered down into vague ballpark estimates and tossing in a revenue number onto your resume. The advice might as well just be "work on successful projects", which is "thanks captain obvious" advice.
We're talking about calculating the impact of your weekly or daily work directly to profit generation. There is a level of granularity and detail to your claim that is likely impossible to realistically calculate, so it would be very hard to accept such claims at face value.