3 ms·
agreed, if the person is in a where-are-your-daily-commits kinda role, years of non-progress is an obvious firing situation. Sometimes it's less black and white
by tlack 9y ago
agreed, if the person is in a where-are-your-daily-commits kinda role, years of non-progress is an obvious firing situation. Sometimes it's less black and white.
let's say you hired two researchers to do some machine learning experiments to develop a new product category. It could easily be years before you see any ROI from that. Especially if their work has to be integrated with the rest of the (functioning) system.
or say you hired someone for their proficiency in one part of the system -- say, they've run a top level domain before, know DNSSEC/IANA/ICANN in and out, etc. If they never get to work on that, or their code never goes to production because of other complications, it doesn't ding ROI. And yet, they are technically doing what they were hired to do..
i guess my point is that ROI is the final output of many, many different factors that determine an employees usefulness and relevance to an organization.