Give the Organization Its People Back
Too many organizations buy technology to reduce labor when the real constraint is capacity. The better question is not how many hours technology can eliminate, but what the organization can finally accomplish when those hours are returned to its people.
There is a sales conversation I have watched play out far too often, particularly with labor and membership organizations.
The technology vendor explains how much manual work the software will eliminate. Hours saved. Tasks automated. Fewer people required. Somewhere in the deck, those hours become dollars, and the dollars become the ROI.
Across the table sit leaders whose people are already carrying more work than their available capacity can absorb — and, in many labor organizations, whose own staff are themselves union members, who often are overburdened with the multiple responsibilities that come with maintaining their own jobs while also administering union duties.
The conversation may remain polite. But the vendor has already diagnosed the wrong problem.
This is not simply a messaging mistake. It reflects a deeper assumption embedded in decades of enterprise software thinking: that efficiency means doing the same work with fewer people. For many organizations, especially those operating with lean staffs and expanding obligations, that is precisely backward. The real opportunity is to give capable people enough capacity to do the work the organization exists to do.
Efficiency and Capacity Are Not the Same Problem
An organization can be inefficient. It can also be underwater. From the outside, the symptoms can look remarkably similar. The remedies are not.
An inefficient organization is spending time on work that should not exist: duplicate activity, unnecessary handoffs, redundant approvals and avoidable rework. The remedy is subtraction.
An organization with a capacity problem is different. Its people are doing necessary work, but too much of their time is being consumed by administration, reconciliation, disconnected systems, manual reporting and workarounds. Important work gets postponed because urgent work keeps winning. The remedy is not fewer people. It is more capacity.
Most enterprise software has historically been sold against the first problem. In the organizations we work with, I increasingly see the second.
Labor organizations make the distinction particularly visible. Revenue models have been pressured. Administrative burdens have increased. In some states, long-standing dues collection mechanisms have been disrupted by legislation. At the same time, expectations around member service, reporting, organizing, communications, governance and compliance have not become smaller.
From inside the organization, this rarely looks like waste. A membership director loses two days assembling a report because the numbers live in systems that do not agree. A local officer enters data at night. A staff member reconciles information manually because two applications have no common operating context.
None of those people look idle. Quite the opposite. They are busy enough that the strategic work — member engagement, organizing, relationship building, planning and service — is the work most likely to be deferred.
The Cost of Diagnosing the Wrong Problem
This matters because a bad diagnosis does more than produce an awkward sales meeting. It produces the wrong transformation agenda.
If the organization buys technology to solve “labor cost” when its actual constraint is capacity, the implementation will optimize for the wrong outcome.
The evaluation centers on tasks eliminated, steps removed and hours saved. Those are useful measures, but they are incomplete. The more consequential question is what happens to the capacity that was recovered.
Does a field representative spend more time with members? Does a membership team resolve issues faster? Can leadership finally see information that used to require days of reconciliation? Can the organization take on work that had been deferred for years? Can the same staff serve a growing membership base without creating another administrative layer?
Those are not soft benefits. They are operating leverage. And the same distinction matters beyond labor. Many SMBs live with a similar constraint: institutional knowledge is concentrated in a handful of people, administrative work expands faster than headcount, and disconnected systems force employees to become the integration layer. For them, “saving labor” is often the wrong objective. Creating capacity is the growth strategy.
Why the Old ROI Model Persists
The reason cost reduction remains the dominant software story is not difficult to understand: it is easy to put on a slide.
If a task consumes 2,000 hours and the loaded labor cost is $50 an hour, someone can put a $100,000 benefit into a spreadsheet. Procurement can compare it. A board can remember it. A salesperson can defend it.
Recovered capacity is harder because the value depends on what leadership chooses to do with it. Two thousand returned hours can disappear into more meetings and more administrative work — or they can become member engagement, faster service, stronger retention, better organizing, improved compliance, additional customers or a project the organization previously lacked the bandwidth to undertake.
That makes capacity a management question, not merely a technology metric.
Measure What the Organization Can Now Do
I would rather be approximately right about the outcome that matters than precisely right about a metric that does not.
Before an implementation begins, establish the baseline. How are people actually spending their time today? Which activities consume capacity without advancing the mission? What work is routinely deferred? Where do handoffs, reconciliation and disconnected systems consume the week? Most importantly, if that time came back, where would leadership deliberately redeploy it?
Then measure the change. Not only hours saved, but capacity redirected: member contacts increased, cases resolved faster, administrative backlog reduced, new initiatives undertaken, growth absorbed without proportional headcount, decision time shortened and service levels improved.
Those measures require more thought than counting automated tasks. They also tell a board, an executive team — and an investor — whether technology actually changed the economics and effectiveness of the organization.
There is a practical lesson here: take the baseline before the system changes anything. Organizations routinely implement technology and ask a year later whether it worked, only to discover that nobody documented what “before” looked like.
If you are planning a transformation, spend the time up front to understand where organizational capacity is going. It may be the least expensive part of the project and one of the most valuable.
Our View at Arrayworks
This perspective has become important to how we think about the role of technology at Arrayworks.
We are not interested in helping an organization become a slightly faster version of an operating model that is already consuming too much human capacity. The more meaningful opportunity is to orchestrate the work differently — connecting data, workflows, applications and increasingly AI so that routine coordination happens through the operating system rather than through people acting as human middleware.
That matters even more as organizations enter the autonomous age. If AI simply automates isolated tasks inside fragmented processes, it may create activity without creating capacity. But when the organization has shared context, governed workflows and an orchestration layer capable of moving work across systems, AI can begin to absorb the coordination burden that consumes so much human attention. The objective is not to remove the human from the organization. It is to remove unnecessary work from the human.
What Comes Next
I expect the efficiency narrative to persist. It is familiar, measurable and deeply embedded in the way enterprise technology has been bought and sold.
But I believe the more important question for the next generation of technology is changing. Leaders should ask not simply, “How many hours can we eliminate?” but, “What higher-value work becomes possible when we give those hours back?”
That is a much better test of whether technology created value.
