"Productive time" is the number most managers look at first in an activity report. It is also the one most often misread. It does not measure effort, talent or value. It measures how much active computer time was spent in apps and websites you have labeled productive. Once you understand that, the number becomes very useful.
How the number is built
Three measurements stack on top of each other.
- Screen time or work time. The period the computer is on and the person is signed in during the day.
- Active time. The part of that time with keyboard or mouse input. CyberWall Insights records that input happened, never which keys were pressed. After a few minutes without input, time counts as idle.
- Productive time. The part of active time spent in apps and sites categorized as productive for that person's company, team or role.
The rest of active time is split into neutral and unproductive. Neutral covers things that are neither clearly work nor clearly not, such as a search engine or a general news site. Unproductive covers sites and apps you have decided aren't part of the job.
Why categories matter more than anything else
Because productive time is defined by category, a bad category list produces a bad number. A few examples:
- If your line-of-business app is new to the system and still uncategorized, an entire day of real work may land in neutral.
- If YouTube is unproductive for everyone, your trainer who watches product videos all day will look idle.
- If LinkedIn is productive for everyone, a job search will look like hard work.
Spend time in the first week reviewing the pending-classification queue and adjusting categories for each team. Insights lets you set categories at the company level, override them for a team, and override again for one person. That last level is how you handle the one marketing person who lives on social media for legitimate reasons.
What productive time can't see
Be honest about the gaps. These all show as idle or neutral, even though they are work:
- Phone calls away from the computer.
- In-person meetings and conversations.
- Reading printed material or reviewing documents on paper.
- Thinking. Some of the best work involves staring at a whiteboard.
This is why goals should be set per role and checked against outcomes. A role that is mostly phone-based will never hit the same computer-productive number as a data-entry role, and it shouldn't have to.
Why eight hours is the wrong goal
An eight-hour schedule includes breaks, lunch, a few short conversations, bathroom trips and the time it takes to switch from one task to the next. Even very focused people don't spend every minute of a workday in productive apps with their hands on the keyboard. A goal equal to the full schedule guarantees that every report looks like a failure, and people stop paying attention to reports that always say the same thing.
How to set a realistic goal
1. Measure first
Run the system for two to four weeks without a goal, or with a placeholder goal you don't act on. This gives you a baseline that reflects how your team works today.
2. Look at your steady performers
Find the people in each role whose output you are happy with. Look at their average productive time across the baseline period. That range is a realistic target for the role, because you already know it is compatible with good work.
3. Set the goal per role, not per company
Create schedules and goals that fit the job. A customer service team, a bookkeeping team and a sales team will each have a different pattern. Insights lets you assign schedules and productive-hours goals to the right people so each report compares like with like.
4. Set over and under thresholds
Goals are more useful with a band around them. Someone far under the goal may need help or may have spare capacity. Someone consistently far over it may be overloaded. Insights uses over- and under-utilization thresholds so both ends show up in reports.
5. Revisit quarterly
Roles change. New software, a new client or a seasonal rush can all shift the right number. Check whether the goal still matches what your steady performers do.
How to read the number once you have a goal
- Look at the trend. A person whose productive time slides over six weeks is more informative than a person who had one slow Tuesday.
- Look at the mix. If neutral time is high, check categories before drawing conclusions.
- Look at the team. If everyone dips on the same afternoons, look for a shared cause, such as a slow system or a weekly meeting.
- Check it against outcomes. If the work is getting done well, a lower number may simply mean the role is less computer-heavy than you assumed.
Turning time into capacity
Once goals are realistic, productive time becomes a planning tool. If a team of six averages well under its goal, you may have room to take on more work before hiring. If a team is consistently over, you may need help sooner than you thought. The workforce cost analysis report turns the gap between goal and actual into untapped capacity measured in full-time equivalents, and puts a dollar figure on it.
Summary
- Productive time is active time in apps and sites you've labeled productive.
- Categories decide the number, so review them early and by team.
- Offline work shows as idle, so goals must fit the role.
- Set goals from what your steady performers already do.
- Read trends and compare with outcomes.