How not to design an interface
A logical user journey for timesheets goes like this:
1. Date
2. Charge Code
2a: recent charge codes / client charge codes
3. Hours / Time
4. Description
5. Post
This design however assumes a random user journey / process with all possible permutations for the advanced posting of timesheets in the 'regular' design.
Most admin systems are like this - they give so little thought to the end user - probably because they're bought by senior managers who'll never use the systems. It's so unproductive!
How not to design an interface
A logical user journey for timesheets goes like this:
1. Date
2. Charge Code
2a: recent charge codes / client charge codes
3. Hours / Time
4. Description
5. Post
This design however assumes a random user journey / process with all possible permutations for the advanced posting of timesheets in the 'regular' design.
Most admin systems are like this - they give so little thought to the end user - probably because they're bought by senior managers who'll never use the systems. It's so unproductive!