Lean public agencies are usually described in terms of budget: too little money, too many mandates. But the constraint that quietly does the most damage is rarely the budget line. It is administrative capacity, the finite hours of a small team. When a platform capability the agency already pays for sits switched off, the work it was meant to do does not disappear. It falls to that small team to do by hand, and sometimes a second tool is purchased to help. The agency ends up funding one job three ways, and the most expensive of the three is not the software. It is the team’s time.
What follows is a public-service agency that had, without ever deciding to, built its entire operating model around compensating for capability it had already bought.
A public-sector service agency with roughly three hundred employees, funded through a mix of state, federal, and local sources across many cost centers. It runs on a tight administrative team. A single HR lead carries most of the workforce function, supported by one platform specialist whose knowledge is deep but who has no backup to call on.
The agency moved onto UKG Ready a few years ago. The platform was successfully deployed and the essentials went live. What never followed was the bandwidth to continue activating the capabilities that came with it. Modules the agency pays for as part of its subscription stayed dormant, not through any fault in the rollout, but because the same small team that would switch them on was fully consumed running the agency day to day. The gaps filled with manual effort and a few pieces of separate software, and the agency settled into paying for capability it owned while continuing to produce the outcome by hand.
The assessment began as a review of dormant platform capabilities and ended as a review of organizational resilience. That shift was the finding. The modules were not dormant because the agency lacked technology or had implemented it poorly. They were dormant because the same two people responsible for running the workforce function were the only two who could improve it, and running it consumed everything they had.
The agency had built, without ever deciding to, a closed loop. What looked from the outside like an optimization backlog was, underneath, a resilience problem wearing a software costume.
The two people who could fix the operating model were the same two holding it together. Every hour they spent compensating for a gap was an hour they could not spend closing it. The agency was not short on software. It was short on the only resource that could put the software to work.
The question was never really about modules. It was why a workforce function of this importance had come to rest on the willingness of two people to keep absorbing the difference.
The review combined stakeholder interviews, workforce-management process reviews, UKG Ready configuration analysis covering which modules were active versus dormant, and a mapping of the separate tools and manual routines filling the gaps. The objective was not simply to find unused features. It was to understand where the agency was spending money and effort to reach an outcome the platform it already owned was meant to deliver.
That distinction is what surfaced the finding. A feature audit would have listed the dormant modules. A software review would have listed the extra tools. Only by tracing each workflow from platform capability to manual workaround to who actually owned it did the real pattern come into view. What appeared to be a software optimization issue was, in practice, a resilience issue.
The agency named the gap itself before the review confirmed it: the system is not being optimized. Underneath that plain statement was a clear causal chain, beginning not with software but with capacity.
Putting the full picture in one view made the cost legible for the first time. The largest of the agency’s costs was not a line item at all. It was the recurring weekly draw on scarce HR capacity, and unlike the subscription or the extra tools, it was the only one that compounded.
This is deliberately directional rather than a dollar return. The honest unit is not a precise figure but a shape: hours every week rather than minutes, several workflows rather than one, and a draw on the team that recurred every cycle rather than a one-time cost. For a two-person function, even that directional picture is decision-relevant, because it shows the scarce resource being spent on the very work that keeps it scarce.
For leadership, the concern was not only the wasted spend. It was the difficulty of demonstrating to auditors, boards, and funding authorities why the agency was paying for overlapping capability while critical workforce processes remained dependent on undocumented manual effort held by two people. The function had been quietly mortgaging its own future, spending the very capacity it would need to build a second person, a documented process, or an analytical bench.
The objective was not to deploy more technology. It was to reduce the amount of organizational knowledge that lived only in two people’s heads.
The work was not simply activating modules. Activation, documentation, cross-training, and workflow ownership were treated as one program rather than separate tasks, because the problem was never that a module was off. It was that the agency could not afford to depend on individual effort to keep the function running. Each dormant capability was brought online in discrete, bandwidth-sized pieces a lean team could absorb, and each was documented and handed off as it landed.
The decisive part was not the configuration. It was building a second person’s command of the platform and writing down the reasoning behind each workflow, so that ownership shifted from a person to a process. For a two-person function, that is what removes the single-point-of-failure risk. And as the workflows moved onto the platform, the workforce data they generate became structured and consistent, which is the foundation any reporting or analytics layer needs before it can be trusted.
| Resilience / Workforce KPI | Before | After |
|---|---|---|
| Workflow Ownership | Person-dependent | Process-dependent, documented |
| Platform Administration Coverage | One specialist, no backup | Cross-trained, second person built |
| Critical Processes Documented | Held as informal knowledge | Documented and repeatable |
| Workforce Data Availability | Compiled manually on request | Structured, standing reporting |
| Headcount by Funding Source | Assembled per request | Live view across cost centers |
| Capacity Available for Analysis | Effectively none | Recovered and redirected to mission |
For a lean team, this reporting layer matters most because it removes work rather than adding a tool to maintain, and because it shifts the operation off the shoulders of individuals. When a process is documented and owned by the system rather than a person, the agency stops being one resignation away from losing it. When workforce data is structured and standing, no one compiles it by hand. The value is the dependency that disappears and the questions that finally have answers leadership can take to its board.
The return showed up in three places, and for a public agency the first one carries real weight.
The agency’s backup plan was never a process or a system. It was the willingness of two capable people to keep compensating for every gap. Sooner or later, every organization discovers that people are the most expensive integration layer it owns.