I don't think that anyone would voluntarily use EZ-labour themselves. EZ-labour is the sort of software that you choose for OTHER people to use. In other words,

I don't think that anyone would voluntarily use EZ-labour themselves. EZ-labour is the sort of software that you choose for OTHER people to use. In other words, Enterprise-Grade Software. Our accounting department uses EZ-labour to keep track of our work on different projects and for registering time-off and vacation. Realistically most of us only work on one project, but accounting wants the time cards filled out anyways. EZ-Labour is unfit for personal time-tracking. For one thing, the UI is clumsy and repetitive. If I work on one thing consistently for a week, I have 5*8 slowly updating combo box fields to enter at the end of the week. For another thing, the work categories are defined by the accounting department, not by the users. The categories aren't useful for me - they're useful for accounting. Also, you can't always fix errors. There's at least one bug in EZ-labour where accidentally entering hours on a weekend can't be removed. EZ-Labour's front end could probably be improved a LOT, quite easily. But it's Enterprise-Grade Software - no one who made it is using it, no one who is buying it is using it, no one who uses it has an opportunity to fix it, and there's clearly no user-feedback being incorporated into the design. It's bad software being shovelled out by a big, dumb, blind company. That's really what characterized Enterprise-Grade Software - it's produced by a silo-ed organization and there's no opportunity for feedback and iteration, so it never gets past it's shitty v0.1 state.