Department KPI Weighting: Why One Productivity Formula Doesn't Fit All
Why a single productivity formula misjudges different teams, and how configurable, per-department KPI weights make the score fair for engineering, finance, HR, sales and more.
Most workforce analytics tools apply a single productivity formula across an entire organisation. Every department is measured the same way, with the same weighting on task completion, the same penalty for time spent in meetings, and the same definition of what "good" looks like. The result is predictable: teams whose work is naturally meeting-heavy or compliance-driven score poorly, not because they are underperforming, but because the formula was never designed for them.
WorkforceIntelligence365 (WI365) takes a different position. The composite productivity score is configurable per department, so the way you measure an engineering squad is not the way you measure an HR advisory team. This article explains why departments differ, how the weighting works, and how changes to weights are governed.
Why departments are not interchangeable
Productivity means different things in different functions. Applying one rubric across all of them produces unfair comparisons and, worse, drives the wrong behaviour.
Consider four common functions:
- Engineering is project and sprint-based. Output is best captured through weighted task delivery and the steady clearance of a backlog. Engineers also need protected focus time, so heavy meeting loads genuinely erode their effective output.
- Finance is compliance and deadline-driven. On-time delivery against statutory and reporting deadlines matters far more than raw task volume. A late close is a different category of problem from a late internal ticket.
- HR is meeting-intensive and advisory by design. One-to-ones, grievance handling, hiring panels and stakeholder conversations are the work, not a distraction from it. Penalising HR for time in meetings measures the wrong thing entirely.
- Sales is delivery-focused. Pipeline progression and the completion of committed activities are the signal; some meeting load is expected and productive.
If a single formula penalises every hour in a meeting, HR and Sales look chronically unproductive while heads-down functions look exemplary. That is a measurement artefact, not a performance insight. For a fuller account of how the score is constructed, see our productivity score methodology.
How the composite score is built
The WI365 composite productivity score is a weighted blend of four components, computed weekly from Microsoft 365 metadata (Microsoft Planner tasks and Outlook/Teams calendar events — metadata only, never message content):
| Component | What it measures |
|---|---|
| Task completion rate | Completed tasks against assigned tasks |
| On-time delivery rate | Tasks completed on or before their due date |
| Weighted task output | Task volume adjusted for priority and weight, so strategic work is not outweighed by trivial tasks |
| Meeting-load penalty | A deduction based on the meeting load index (meeting hours relative to work hours) |
The composite is, in effect: task completion plus on-time delivery plus weighted task output, minus a meeting-load penalty. What distinguishes WI365 is that the relative weight of each component is set per department rather than fixed globally.
The meeting-load penalty deserves particular attention. WI365 classifies meeting load using transparent thresholds — under 30% of work hours is healthy, 30 to 50% is moderate, and over 50% indicates overload risk. For a heads-down engineering team, a heavier penalty above those thresholds is appropriate because meetings displace the focus hours their work depends on. For an advisory function, the same penalty is counterproductive. The mechanics of meeting load and focus time are covered in more depth in our guide to meeting load and focus time analytics.
A worked example: HR should not be penalised for meetings
Take an HR business partner who spends 22 hours a week in meetings out of a 40-hour week. Under a global formula with a flat meeting-load penalty, that 55% meeting load lands firmly in "overload risk" territory and drags the score down sharply, regardless of how much advisory work was actually delivered.
Under a department-weighted model, the HR profile reduces the meeting-load penalty weight and increases the weight on task completion and weighted output. The same 22 hours of meetings — which represent core HR delivery — no longer distort the result. The score now reflects whether the partner closed cases, met deadlines and handled their workload, which is what HR leaders actually want to know.
The same logic runs in the other direction. For Engineering, you might keep a meaningful meeting-load penalty precisely because protecting focus hours is part of healthy delivery, and for Finance you might raise the weight on on-time delivery so that meeting statutory deadlines dominates the score.
How weights are stored, defaulted and versioned
Department weights are not buried in code. WI365 stores them in a dedicated department_kpi_weights configuration, seeded with sensible defaults for common functions — Default, Engineering, Sales, Finance, HR, Operations, Marketing and IT — so the platform produces fair scores from day one without bespoke setup.
From there, weights are fully configurable. People-analytics teams can work with system administrators to adjust the blend for any department through the portal's KPI Weights administration screen. Because departments are derived from Microsoft 365 Groups mapped to your Azure AD org structure, the weighting follows your real reporting lines rather than a parallel taxonomy you have to maintain by hand. For more on how that organisational data is collected, see how WI365 uses Microsoft Graph workforce data.
Crucially, weighting configuration is versioned by effective date. When you change a department's formula, the previous configuration is retained and the new one applies from its effective date forward. That means historical scores remain explainable against the rules that were in force at the time, and you can see exactly when and why a department's measurement basis changed.
The governance of changing weights
Changing how a department is measured is a consequential act, so WI365 surrounds it with the same governance posture that applies across the platform.
- Role-restricted access. Editing KPI weights is an administrative function, available to system administrators through the Admin area. It is not something individual managers can quietly adjust to flatter their own teams. Visibility and editing rights are enforced at the query level and in middleware, in line with the platform's wider role-based access controls.
- Audit trail. Every change is captured in the
audit_logwith who made it, when, and the before-and-after values. There is a defensible record of every adjustment to a department's formula. - Effective-date versioning. Because changes are versioned rather than overwritten, you retain a clear lineage of how a department has been measured over time.
- Transparency and human judgement. Weighting is part of a wider governance framework built on metadata-only analysis, transparency to staff, role-based visibility and mandatory human-in-the-loop review. Scores inform conversations; they are not used for automated decisions, rankings or discipline.
This combination — sensible defaults, configurable per-department weights, effective-date versioning and a full audit trail — lets you tune the formula to reflect how each function genuinely works, while keeping the change process accountable and explainable. If you would like to see how it applies to your own departments, you can book a demo or talk to our team.
Frequently asked questions
Can each department have a completely different productivity formula?
Yes. The composite score uses per-department weights for task completion, on-time delivery, weighted task output and the meeting-load penalty. You can raise on-time delivery for Finance, reduce the meeting penalty for HR, and keep a stronger focus-time penalty for Engineering, all from the same KPI Weights configuration. Defaults are seeded for common functions so you get fair scores before any tuning.
Does WI365 work without configuring weights at all?
It does. WorkforceIntelligence365 ships with seeded defaults for Default, Engineering, Sales, Finance, HR, Operations, Marketing and IT, so the platform produces reasonable, department-aware scores out of the box. You can refine the weights later as your people-analytics practice matures, with each change versioned by effective date.
Who can change KPI weights, and is it auditable?
Editing KPI weights is a system-administration function performed through the Admin area, not something line managers can alter. Every change is recorded in the audit log with the user, timestamp and before-and-after values, and configurations are versioned by effective date so historical scores remain explainable against the rules in force at the time.
How does WI365 know which department someone belongs to?
Departments are derived from your Azure AD organisation structure and Microsoft 365 Groups, synced via Microsoft Graph. Because the weighting attaches to those real groups, it follows your actual reporting lines and stays current as people move between teams. To see how the wider platform fits together, read the complete guide to workforce intelligence.