As a startup founder with a technical team I've never understood the obsession with #hours worked. Perhaps it is because we originally started off working remo

As a startup founder with a technical team I've never understood the obsession with #hours worked. Perhaps it is because we originally started off working remotely and logging hours worked wasn't an option. With our current tech team, # hours worked is nowhere near top of mind. We evaluate performance based on output, team dynamics and (perhaps related to # hours worked) availability. While admittedly vague, availability is a measure of how the employee in question's work schedule negatively impacts our ability to work quickly and effectively as a team. It doesn't necessarily correlate directly to # hours worked, however, as more often than not other factors such as 'willingness to take part in group discussions' or 'prefers to work at night' have a bigger impact.