Core work vs. non-core work: a better way to understand workforce allocation

Two different employees can both have  a fully productive day, and they can spend it in completely different ways. And while productivity data can tell you what websites they visited or specific tools they used, it cannot tell you how those contributed to each one’s role.

Suppose both of them are developers. One writes code for six hours and spends two in meetings. The other one codes for two hours and spends six hours coordinating projects and keeping things moving.

Does that mean one is less productive than the other?

It doesn’t. Both are putting in real work, and neither is slacking. What’s missing from the equation is an understanding of core work and non-core work.

Core work is what a role exists to produce, while non-core work is everything else that sustains that production. Both are equally important.

At scale, that difference decides whether teams are spending their capacity on the work they were hired to do or losing it to everything else.

Core work is work directly tied to a team member's primary responsibilities and the outcomes that role exists to produce.

Non-core work is everything else required to make that production possible. It isn't the team member’s main output, but the role requires it to function.

Those are two of three categories used to classify how work gets done. The third is unproductive work, and it's a different thing from non-core.

• Core work is activity connected directly to a team member's primary output. It's the reason the role exists in the first place.
• Non-core work is supporting activity that keeps core work possible. It's necessary, but it isn't what the team member is measured on.
• Unproductive work is activity that doesn't meaningfully contribute to outcomes at all. It sits apart from both. Non-core work still serves a purpose, unproductive work doesn't.

The same activity can be classified differently depending on who's doing it. A meeting that's core for one team member can be non-core for another.

Here's how that can play out across a few common roles:

Suppose an employee spends an extended stretch of time on nothing but non-core work. That’s typical, not a red flag because non-core work is still part of a job.

A person can be productive and non-core at the same time, because non-core work is still part of the job. It doesn't automatically mean the work isn't contributing to the team. It only means the contribution isn't the role's primary output.

There are different types of work that fall under three measurement dimensions:

There is no universal definition of core work across an organization.

If only one type of work counted as important regardless of who's doing it, most employees would appear as if they're underperforming.

Different roles produce value differently. That's why what counts as core has to reflect:

• Role and job function. A developer’s core work is very different from a project manager’s. One produces code, the other produces collaboration.
• Department and team context. The same task can mean different things on two different teams. A client call is core work for account management but not for engineering.
• Primary responsibilities and deliverables. Core work should be defined by what someone is accountable for, not by what they do most.
• Expected outcomes for the role. Two roles can have similar day-to-day tasks, but they can still have different definitions of core work. Outcomes define the role, not the activity.
• Project or client context, in some cases. Core work can shift depending on the engagement. For instance, a consultant’s core work on one project can be non-core on another.

Role-appropriate measurement starts with role-specific classification. If the classification is wrong, then the measurement built on top of it will be wrong too.

Core and non-core work may look like a basic classification on the surface. But it's a building block for a much bigger system that shapes how an organization allocates its capacity as it scales.

Work classification is built from activity and productivity monitoring data. It's what effective workforce allocation (and the workforce capacity planning and operational decisions built on top of it) depend on. Once work is classified appropriately, leaders can start asking better operational questions:

• Is supporting work crowding out core responsibilities? Meetings, admin, and internal coordination all consume capacity. Is that capacity coming out of time that should be going toward role-specific output?
• Are certain roles carrying a disproportionate administrative burden? If one team is buried in process work relative to peers doing similar jobs, that's a signal. It might mean you need to redesign a process or automate something repetitive.
• Are teams with similar responsibilities allocating their capacity differently? Two teams with the same mandate shouldn't necessarily look the same on paper. But when they diverge sharply, it's worth understanding why output between them varies.
• Is organizational growth increasing coordination overhead? Scale adds meetings, reporting, and approval layers. While they don’t show up as line items, they eat into capacity all the same.

Suppose a leader is deciding whether to hire another engineer or fix a broken process instead. Without classification, all they have is a sense that the team feels stretched.

With it, however, they can see if senior engineers are spending their time on architecture and code review or if coordination and status updates are burning through the hours supposedly for core work. From there, they have more options other than “just add headcount.”

Or, let’s say a different leader is trying to figure out why two account management teams post similar productivity numbers but very different client outcomes.

Activity data alone won't explain it, but classification might: one team could be spending capacity on core client work, while the other is buried in internal reporting that looks productive but doesn’t move the account forward. With that workforce analytics context, the leader now knows that the solution is to cut the reporting load, hand it to someone else, or automate it.

Since both core and non-core work are necessary, employee performance shouldn't be measured by how much of one or the other someone does. People don't choose that split on their own, and neither do teams.

A team spending 75% of its time on core work isn't inherently better than a team at 55%. The right mix depends on:

• The role and its seniority level. A senior hire spends more time on decisions and less on hands-on output than someone earlier in their career.
• Organizational structure and team size. Smaller teams absorb more coordination per person, simply because there are fewer people to spread it across.
• Project type and current workload. A team mid-launch looks different than a team in maintenance mode, and both are doing exactly what the moment calls for.
• Business model and operating context. A services company runs on client coordination in a way a product company doesn't. The difference isn't a flaw in either one.

Take a senior engineering leader, for instance. They might spend far less time writing code than an individual contributor on their own team, and that's not a problem. Mentorship, decision-making, and coordination is the job at that level. Less code doesn’t mean less value.

Core and non-core classification is, ultimately, a diagnostic tool. It's not a scoreboard. Its job is to help leaders spot patterns and the story behind them. It should never be used to rank employees or teams against each other.

Data like this only becomes useful with context attached. A percentage on its own says nothing. Work classification stripped of role, seniority, and circumstance is just a data point sitting in a vacuum.

You’ve read about how classifying these two types of work can support operational decisions. To get there, you need clear answers that tell you what’s going on and where to go next.

And to get answers, you need to ask questions. Start with these:

• Are our highest-cost roles spending enough capacity on the work only they can perform? Senior talent is expensive precisely because of what only they can do. If that capacity is going somewhere else, you're paying premium rates for work someone else can handle.
• Is administrative work increasing as we scale, without a proportional increase in output? Growth should buy more output, not more overhead. If admin work is climbing faster than results, something in the process is eating up capacity it shouldn't.
• Are meetings crowding out role-specific, high-value work? Every hour in a meeting is an hour not spent on core output. That's not to say you should cancel meetings, but it’s a valid reason to know what they're costing and decide which meetings are necessary or not.
• Which teams are carrying the greatest coordination burden, and why? Some coordination work is unavoidable. However, if one team carries far more than a comparable team, you might have a process problem on your hands.
• Could repetitive non-core work be automated, delegated, or redistributed? Non-core work is necessary. That doesn’t mean it needs to be done by your most expensive people.
• Are process changes actually giving teams more time for core work or just shifting where non-core time goes? A new tool or workflow can look like a fix, but it could just be moving the same hours somewhere else. Classification will help you identify the difference.
• When a team's productivity metrics look strong, what is that productive time actually being spent on? Strong numbers can hide a weak allocation. The score may say the team is working, but it doesn’t say what they’re working on.

Answering these questions puts you in a position where you can make decisions with a reliable view of where capacity is going, the value it’s producing, and what’s consuming it.

Traditional activity data can show that someone spent three hours in Slack. That's insufficient.

The relevant question is: what does Slack represent for this person's role?

Raw activity numbers don't answer that. They show that something happened but not what it meant.

What does answer that is workforce analytics, which can classify work by role and business context instead of treating every app and every hour the same way.

Hubstaff is a time tracking platform that adds role-specific context to productivity data by helping organizations distinguish between core, non-core, and unproductive work. This way, leaders can identify where capacity is going and investigate whether or not it's aligned with business priorities.

Here’s how Hubstaff makes that context visible:

• Work time classification turns raw hours into core and non-core categories, so a flat number becomes a picture of where a team's time goes.
• Utilization data shows that picture at the team level, where a pattern like coordination crowding out core work becomes visible.
• Focus time and meeting cost data narrow the same question down further: how much workforce capacity is going to meetings, and does that match what the role needs.

Productivity tells you that work happened, but it doesn't tell you what that work was for. Core and non-core classification fills in the rest, not to rank one category over the other, but to show whether the balance between them still makes sense.

At scale, that's the real question underneath the productivity number: not whether people are working, but if the teams are spending time on the work that moves the needle for the business.

Book a demo to see how Hubstaff can help you allocate your workforce toward growth.