Earlier quoted context omitted.
I feel for you. Apparently you don't have a boss who can define what they want from you. This is not uncommon, and we're struggling with that ourselves. We've all spent so many years with the belief that putting in hours is the work, that we don't really know what we've hired people to actually do. All your questions are the same questions you have in an TIME + PRESENCE = RESULTS job. What if they decide they want 11…
I'm all for the 'results based' work environment but I think measuring results of work that you hire people to do IS quite hard. A great example is refactoring. Say you hired a dev and he delivered a product that worked but is written terribly (already a question there, how do you gauge that in terms of 'results'?). Now you hire a second dev to clean it up and make it maintainable. How do you evaluate when he has del…
Easy. Lines of code.
The first developer did an awesome jobs, many lines of code were written. The second one is a lousy hack, he earned about $50 (not $50k).
This is ridiculous of course, but it does show how even bad measurements are preferred over non-measurement.