|
|
|
|
|
by sublinear
5 hours ago
|
|
Raw throughput and time efficiency should be treated as separate metrics. They should not be conflated with productivity, nor are they all that correlated to begin with. I define productivity as an abstract goal. The time tracking is information to satisfy my curiosity and gain insight. There's no place for quotas in my approach. There are only ever relative comparisons for me. Time efficiency is just percent of the time range you arbitrarily defined filled by the tasks you explicitly defined. If it seems low it doesn't necessarily mean you aren't tracking enough things, but that your subtask definitions are too narrow. Raw throughput is either the number of tasks completed or "points" redeemed, but often your subtask estimates are too "lumpy" or just flat out wrong. I get that it's not for everyone, but there's nothing wrong with time tracking in itself. It's its own skill. Discomfort is usually a sign you need to try new techniques. Don't give up. |
|