These guidelines are part of the overarching principles here at LiteBreeze.
Detailed time entries can be prepared with little effort by creating the right habit. I prepare time entries myself, and below you can find my suggestions on how you can minimize the “administrative burden” and instead gain value from the process.
Adding maximum value and preparing a high-quality time entry both starts with planning and structuring your work. You need prioritized to-do lists and/or work plans.
Thereafter a strict focus on High-Impact Low-Effort (HILE); resist the common urge of letting your inbox and email flow decide in what order you execute tasks!
Structure to-do lists and your daily plan so that you can dedicate a continuous block of time to a specific group of closely related tasks. Don’t jump back and forth between unrelated tasks. In addition to getting things done, this will allow you to easily split up your time entry into hourly blocks.
“People with good work habits have todo lists that are reasonably prioritized, and they make themselves do what needs to be done. By contrast, people with poor work habits almost randomly react to the stuff that comes at them. People who are good at this stage can reliably execute a plan. They tend to be self-disciplined and proactive rather than reactive to the blizzard of daily tasks that can divert them from execution. -Ray Dalio”
Focus on the toughest and most challenging HILE tasks when you are most alert. For most people, this is the morning session. You may be able to crack the really hard nuts in your to-do only in the morning of your best day of the week, so don’t waste such “prime time” on simple tasks.
My routine:
Minimize interruptions. Ignore non-urgent IMs. Respect your colleagues time so that they respect yours; plan a time for meetings in advance and gather all your questions for a single meeting. Meetings that are low-effort for your senior are better scheduled for the afternoon.
Don’t check email too frequently; once an hour is more than enough even if you are involved in client communication. And use streak or add to an appropriate to-do list instead of letting new emails disrupt your daily plan.
I believe it’s healthy for the organization that everyone knows that they can’t expect their colleagues to handle non-HILE tasks swiftly. This might even give colleagues an incentive to try to get such tasks done themselves, assume how to do a task themselves, report clearly instead of in a haste and so on.
Moreover, colleagues will not grow to rely on seniors’ quick responses to non-HILE tasks and plan their work accordingly.
Seniors might check your time entries early in the morning. This is why it’s important that you register your time entries when you stop working for the day:
And for those working for clients, these benefits are added:
Time entries should ideally be booked regularly in one-hour blocks. But you are allowed to use two-hour blocks if necessary. Aim to limit the usage of two-hour blocks to a maximum of five per week.
Now some may feel that one-hour blocks are just too much detail and a hassle, however, consider:
And for those working for clients:
Read more about the benefits of our hourly time entry system.
You can register time entries more effectively using the SMS. The system will automatically match the time entries to the corresponding projects and requirements thus making it more user-friendly and time-efficient. Both tabs (SMS/ SMS – single project) are available under the time clock on our staff panel.
SMS – Single Project: Those who mostly book their hours on one single project (eg: recruitment or admin team) can use the single project tab to register the time entries.
You will need to enter the start time along with the first letters of the requirement named followed by an underscore. Once you finish the work of the day, add the end time to the last entry and copy-paste it. Example.
SMS: Those who book time under multiple projects can follow the same steps as with a single project but they should use the underscore to differentiate between the project and requirement.
When you book time under the requirement “Developer Review” on Unbillable tasks (Training – > Developer Review) you can register the time as UNB_DEV or UNB_REV, the system will recognize and match either one of these. Also, you should use this page to clock-out. Example.
You can save your time entries throughout the day in a simple text document or a sheet. Personally, I add them to a macOS Notes tab.
It shouldn’t be an administrative burden to write down and register your time entries. In addition to the section about structuring your work, this section contains more tips on how you may simplify your time entries.
Note time blocks continuously throughout the day. This way you can quickly register it even if you need to leave the office urgently. And your entries will be accurate.
If all your time entry blocks belong to the same requirement you can register all those blocks in one entry.
Be concise! Brevity is a virtue! Write “Sign up step 3: validations” instead of “Checked the client’s response and implemented the modifications. Added validations in step 3 of the signup form. Tested and uploaded.”.
The block start and end times don’t have to be exact down to each and every minute if that presents a challenge. The aim is not for this to be an administrative burden but a simple habit. You can round off 10 minutes here and there if you need to frequently jump between several tasks.
“923 Meeting personA regarding feature X, Y 945 Code review for last week: personB 1040 Meeting personA regarding featureZ 1100”.
It would be ok to simplify this to “923 Meeting personA regarding feature X, Y, Z 1000 Code review for last week: personB 1100”.
This would still reflect how time was spent, but make it easier to book the two blocks on separate requirements and easier for seniors to interpret.
If you find yourself having to register time on a lot of different requirements each day you may want to make your requirements/time overview less fine-grained or try to focus on fewer requirements at a time. Eight or more different requirements would probably be too much, though there’s no exact limit.
Sometimes you may not be able to link a block of time to one single requirement. I may for example work with a piece of content for our website that aims to improve our recruitment process. It’s related to both content marketing and recruitment.
In such a case I may break that entry down into two roughly estimated parts. Don’t waste time trying to estimate such splits in exact detail.
Like time overviews and work plans, time entries can be of legal importance in case a client fails to pay and we need to take legal action.
Push your code to a repository accessible by seniors when you stop work for the day.
Register your time entries in the commit message as well, so that it’s easy to review your code. Refer to this detailed guideline on how to write good commit messages. Only include the portion related to the project you are committing code for if you worked on more than one project that day.
Non-coding time need not be included with the commit messages. Non-coding time entries should be suffixed with “[no coding]”.
1030 – 1130 Analysed number series email, working of invoice number creation[no coding] (1)
1130 – 1230 Coded SQL query for returning the number series (1)
1337 – 1437 Tested and uploaded the changes. Emailed stakeholders (1)
Here are the code extracts corresponding to the time entry example above. It is very easy to evaluate:
https://www.dropbox.com/s/0qaok3ud05fzji6/LiteBreeze-ERP-helper.png
https://www.dropbox.com/s/z7cl56xnuwc4v2u/LiteBreeze-ERP-invoice-add.png