Maker time
This metric shows the average number of hours of maker time (focus time that is spent on work without distractions like meetings, etc) by the user or the team. It also gives the percentage relative to the number of hours spent working and an indicator to show whether the user or team is getting sufficient maker time.
In other words: Maker time metric represents the distribution of the work day for your teams and their members by meeting v/s focus time availability. Focus time is the amount of time in a workday which is not spend in meetings. This is further broken down into
- Maker time: Maker time is defined as continuous blocks of at least 120 minutes time during work hours where there are no meeting interruptions. Typically you should maximize the maker time for individual contributors to help them focus on delivery.
- Fragmented time: Fragmented time is defined as gaps of less that 120 minutes between meetings. Typically you want to minimize this so that developers can have uninterrupted time for deep work and minimize loss of productivity due to context switching.
- Focus time: Time during work hours that is not spent in meetings is classified as Focus time.
What's included in Maker time
- Calendar events
- Google Meet or Zoom (video conferencing software) - actual start times and end times of every attendee.
Check out all apps supported by Hatica here: https://www.hatica.io/connectors/(opens in a new tab) (opens in a new tab)
Cases handled
Any participant in a calendar event who responded "No": Such participants are fully ignored and is not considered for the meeting time.
Calendar event includes a Google Meet or Zoom (video conferencing software) link:
- For participants from the video conferencing software: meeting time is considered using video conferencing link and the calendar start and end times are ignored.
- For participants who responded "Yes" but attend the same event offline and not via the video conferencing link: since these participants responded "Yes" to the event, the meeting time is considered from the start and end times from the Calendar event.
- For participants who are not on the calendar event, but get pulled in to the meeting via the video conferencing software: their meeting time is considered via the video conferencing software APIs.
- Calendar events to which the person responded 'NO' will be omitted regardless of whether they attend via the video conferencing link or offline.
Using and attending via video conferencing links is more accurate. Here's why: If the scheduled meet was for 1 hour, but if it ends in 20 mins or extends to 70mins, Hatica identifies this using the video conferencing software APIs
Non calendar events: Events that are not on the user's calendar, but are scheduled on Zoom, are identified using the Zoom API.
Calendar events with only 1 (self) participant: Events with only 1 person is considered focus time that was blocked for work - so it is not considered as meeting time.
Work hours:
- Meetings outside of working hours are not considered for maker time.
- Meetings which partly lie outside working hours are capped to working hours. For example, if working hours are from 9am to 6pm, and a meeting occurs between 5pm and 7pm, the meeting time would be considered from 5pm to 6pm.
All-day or Multiple day events: Hatica ignores these events, since the most common use case for all-day or multiple day events are to mark oneself as Out-of-office (OOO)
Offline meetings: Hatica recommendation is to have a Google Calendar invite and invitees responded as Yes will be accounted as having attended the meeting.
Meetings conducted directly via video conferencing tools without a calendar event:
- Maker time: We consider the start and end meeting times from these tools for the maker time metric. If the meeting extended beyond office hours, point 2 under work hours heading applies.
- Meeting time breakdown: For this metric alone, we do not consider these non calendar video conferencing events.
Here's how to read the maker time graph.
The total hours spent working is the innermost ring, labelled as "Work Hours", which can be divided into hours spent in meetings and non-meetings, a.k.a. Focus time.
Now, there can be meetings spread throughout the day, making this focus time fragmented. Time spent in such context switching is termed as Fragmented time, and the remaining hours (a continuous stretch of 2 hours or more without meetings, etc) is considered as Maker time - which is generally the most productive hours of the day.
All hour calculations are localized to the particular users' timezone.