Five Relay Points Where Activation Slips Away — and the Named Owner Each One Needs
Photo: business team handoff relay baton office collaboration, via wallpapers.com
Software does not usually go unused because someone made an error. It goes unused because a series of reasonable people each completed their own portion of the work and handed it onward, and at every handoff the responsibility for the next step became slightly less clear. The purchase was approved. The contract was signed. The accounts were created. The email was sent. Each of those statements is true, and the software still sits idle.
This is a control-design problem, not a personnel problem. Five relay points account for most of the loss, and each one has a specific owner who should be holding the baton.
Handoff one: procurement to IT
What disappears. The purchase order closes. A deployment ticket may or may not open. The entitlement quantity, the activation deadline in the vendor's onboarding terms, and the business unit that funded the purchase are recorded in the contract system, which IT does not read.
The tell. IT learns about the new tool when a user submits an access request, or when the first invoice arrives.
The fix. Require a structured handoff record at purchase completion: product, quantity, business sponsor, intended population, target go-live date, and vendor onboarding contact. No purchase closes without it. This is a small process change with an outsized effect, because it converts a contract into a deployment obligation.
Owner. Procurement operations, with the sponsorship of the business unit that funded the purchase.
Handoff two: IT to security
What disappears. Time. A security review, an architecture assessment, or a data processing review sits in a queue while the commercial clock runs. Software procured in the fourth quarter is frequently procured at a discount precisely because the vendor's fiscal year is ending; that urgency is not matched by review capacity on the customer side.
The tell. Accounts are provisioned weeks after the contract start date, and the vendor's onboarding window for assisted configuration has expired.
The fix. Pre-clear categories rather than products. A standing security pattern for, say, a SaaS application storing only internal-classified data removes thousands of individual reviews. Where a full review is required, set an internal service-level target tied to the contract's activation deadline, not to the general queue.
Owner. Security and architecture leadership, jointly with IT service management.
Handoff three: security to the business manager
What disappears. Assignment. Access is approved, but the decision about which employees receive seats belongs to a manager who was not part of the purchasing conversation and may not know the tool exists.
The tell. A large block of provisioned licenses is assigned to a single administrative group, or the vendor reports an activation rate well below the licensed quantity with no corresponding complaint from the business.
The fix. Make the manager's allocation explicit and time-bound. At handoff, the business sponsor supplies a named population and a confirmation date. Where the sponsor cannot name the population, the purchase should be reconsidered rather than deployed.
Owner. The business sponsor who approved the spend.
Handoff four: manager to the individual employee
What disappears. Attention. The activation email arrives in a crowded inbox. It contains a link, a temporary credential, and a deadline that the recipient does not know exists. If the employee never opens it, no system records a failure — only an absence.
The tell. Registered accounts lag provisioned accounts by a wide margin, and the gap persists well beyond the first month.
The fix. Treat activation as a managed task rather than a notification. A short assignment with a stated purpose, a fifteen-minute onboarding session, and a single follow-up at day seven recovers most of this loss. The vendor's automation is designed for volume; your organization's problem is individual.
Owner. Line managers, supported by a named enablement contact rather than a general help desk.
Handoff five: first use to actual capability
What disappears. Value. The employee logs in, sees a default configuration, and uses the product at its most basic level — or opens it once and never returns. The features the business case was built on remain dormant. This is where the largest share of unrealized spend accumulates, and where it is least visible, because the account looks active in every report.
The tell. High login counts alongside low adoption of the capabilities cited in the original business justification.
The fix. Measure capability activation, not account activation. Identify the two or three specific features that justified the purchase, define what first meaningful use looks like for each, and report against that definition. Route the resulting data back to the business sponsor, who can then decide whether the tool needs better enablement or a smaller footprint.
Owner. The business sponsor, with product or functional enablement support.
Making the relay explicit
Individually, each of these fixes is modest. Together they form a control chain that most organizations have never drawn. A useful exercise is to write it down: five stages, five owners, and one measurable signal at each boundary — purchase closed with a deployment record, review completed before the contract activation deadline, population named and dated, registered accounts reconciled to provisioned, and capability use reported to the sponsor.
That register changes the nature of the conversation. When software goes unused, the organization no longer asks who failed. It asks which boundary lacked a signal, and which owner had no way to see the baton leaving their hand. Most of the time, the answer is that the boundary was never defined at all.