3 ms·
You should always strive to measure the impact of your work. Always. And if you can't measure it, you should ask your users for ballpark estimates. "Hey George
by enraged_camel 9y ago
You should always strive to measure the impact of your work. Always.
And if you can't measure it, you should ask your users for ballpark estimates. "Hey George, how many minutes a day does the new feature I added save you?" From there you can convert it to an estimated average financial impact fairly easily.
- bsjob 9y agoSo by that point, I've already made like three things up because there's absolutely no way for them to fact check this nonsense. Why talk to George when I can just pull something out of my ass? "Yeah, the process totally saved a half hour every week, which is about $500 because BUSINESS. Good luck verifying that, asshole."
- enraged_camel 9y agoWait, so you think that when you say "I made the process 13% more efficient and saved the company $12.5 million dollars" that they actually call the company to verify? >>Why talk to George when I can just pull something out of my ass? Because lying is bad? I mean when you talk to George you are at least making a good faith effort to come up with a realistic estimate (which you would be honest in your resume by using words like "approximately" for instance). That's preferable if you have no other way to calculate the business impact of your work.
- sdiupIGPWEfh 9y agoAnd at the end of some successful two year project, having moved on to a new position at a new company, am I to call George back a few years later and ask for him to leak me info about my project's impact, assuming George still works there himself?