|
|
|
|
|
by humanrebar
3065 days ago
|
|
> Just make sure that overall your total hours are what we agreed to in the employment contract. What's the justification for monitoring total hours and not something more directly tied to business success? End users and profit margins (assuming your engineers are salaried) don't care about whether your engineers had consistent 40+ hour work weeks. |
|
- Inputs are the things employees can act on easily, like the number of LoC written or the number of features developped.
- Outputs are related to business success, for example the number of customers, or the revenue.
The key here is to consider the external business environment as a complex machine, in which you put some effort, measured by inputs, and you observe the outputs as a result (reward). Because you don't know how the environment is going to respond, running the activity consists in adjusting the measures of inputs according to previous results, and trying to maximize those.
This is sane for business because executives can focus on maximizing the input metrics, without caring too much about the outputs, and evaluate separately the assumptions they made about the business (e.g. that x number of features requested by customers developped within 1 month increase the userbase).
It kind of looks like a reinforcement learning process actually.