Sustained Always On

Sustained Always On

Quickly see the state of Always On at your organization and take action. 

Long working hours are important to track — teams might churning out code, but at what cost? Too much work, week over week without reprieve, can lead to unhappy developers and ultimately to attrition. 

Sustained Always On

Sustained Always On is calculated by looking across all of the signals Uplevel has for a given contributor each day. Each activity is assigned a weight, for example, a 30 minute meeting gets 30 minutes of "weight".

Uplevel assumes that the 8 hours with the most activity "weight" are the given contributor's "working hours" for the given day. A contributors "working hours" may change day-to-day as the inputs to their activity weights change.

Anything beyond those assumed "working hours" are classified as "always on" time. 

Use this chart to understand your Always On trends over time.  Levels of Sustained Always On are categorized into Elevated and High. 

  • Elevated: defined as greater than 30 minutes of work a day outside normal "working hours", over more than half of the weeks in the selected time period. 
  • High: defined as greater than 1 hour of work outside of normal "working hours", over more than half of the weeks in the selected time period

Screen Shot 2024-05-07 at 11.01.40 AM

Always On & Not Always On 

These chart looks at those who are or aren't currently experiencing Sustained Always On. It breaks down each group's median time in meetings, deep work, interruptions, and fragments which can indicate the root cause of long hours. These two charts compare the experiences of those who are currently experiencing elevated levels of Always On to those who aren't.

Idea

Tip: if Deep Work looks low, jump to your Deep Work breakdown for a deeper analysis.

AA-NAA

Breakdown by Manager 

Drill down to see what percentage of each team (the number of individuals) have been at each level of Sustained Always On activity over the selected time frame.  Teams with high value have had more individual at a elevated level, for a longer duration of time. 

AA-breakdown

Individual details where appropriate

Always On data is vailable at the individual level, complementing the same details about Deep Work and Meeting categories in order to give a complete picture of teams' working habits.

Visible to who

By default, information at the individual level is provided only to those in the reporting tree - who have context to interpret the data and help support the team.

Specifically, this detail is available to the individual themselves, and their manager and leaders who they report up to. Individual level details are not available about individuals outside your reporting tree who don't report up to you.

Roll-up stats about entire teams are available to everyone, as long as the teams are the appropriate minimum size as chosen by your organization.  This provides org wide visibility to group norms and trends.

Organization experience options

Options are available to configure the experience to match your organization's goals and norms:

  • The minimum team rollup size can be adjusted, which determines the smallest team where rollup information is visible to all.
  • Individual level information about Always On, Deep Work and Meeting categories can be made available based on the org chart reporting tree (the default experience), visible to all (for a totally open organization), or visible to none.

Contact support@uplevelteam.com to review the options and make any changes to these experience options for your organization.

    • Related Articles

    • Uplevel's 2-Week Sliding Calculation Window

      Balancing the tradeoffs between leveraging the latest information and maintaining integrity in reporting. Data from your source systems (JIRA/Git/Calendar/Slack/etc.) is fluid. While a JIRA issue may have been classified as a "story" at one point in ...
    • Pulse Page

      Understanding important changes over time at a glance Metric Trends on the Pulse Page highlight the insights with the largest recent change, to highlight where focus is needed, and where efforts to improve are showing the biggest impact. It's ...
    • How to find low Deep Work time

      Learn how to analyze and improve your organization's deep work. Uplevel categorizes your team's work into two buckets: Development time, which consists of Deep Work and fragments. Optimized development time consists of as little fragments as ...
    • Meeting Classifications

      How are meetings classified? Uplevel's Meeting Classifier takes into account high-level details surrounding number of participants, meeting titles, and the duration of meetings to provide insights around which kinds of meetings take the most of your ...
    • Deep Work

      What is Deep Work? Uplevel categorizes your team's work into two buckets: Development time - consists of deep work and fragments. Optimized development time consists of as little fragments as possible. Non-development time - The various types of ...