L&D Market Signals

A Large HR Platform Refresh Is a Manager Design Decision

Lockheed Martin’s SAP SuccessFactors move is useful evidence for a broader question: are leaders buying a system or redesigning the work that makes the system valuable?

Ravinder Tulsiani, DBAEmerging signal

Lockheed Martin’s move to modernize its HR systems with SAP SuccessFactors shows intent, not workforce transformation. The useful question is what manager work should get easier, faster or disappear because of this change. If leaders cannot answer that clearly, they may be treating system consolidation as operating improvement before they have decided which approvals, exceptions and decisions will actually change.

A common platform can reduce fragmentation in employee data, manager workflows and service delivery. That still leaves the harder issue of how work is set up and who is accountable for decisions. If the same policy exceptions, handoffs and local workarounds remain, the enterprise has mostly bought cleaner administration. Managers can still carry the same coordination burden, with stricter data entry and more visible compliance added on top.

That manager load is part of the operating result. It is not a side issue. When managers are asked to keep cleaner records, follow new routines and resolve more exceptions without clearer decision rights, the cost shows up elsewhere: slower decisions, weaker role accountability and less capacity for actual performance management. A single source of truth can look like governance progress while ownership of the decision is still blurred.

The success test often goes wrong here. A platform rollout can be declared successful because the system is live, the data is cleaner and the process is standardized. None of that tells you whether the work improved. I would look first at a few concrete points in the work: which manager tasks have fallen away or become materially lighter, which approvals or exceptions now sit clearly in the system instead of email or local interpretation, and whether the new workflow is producing better results where it applies, such as faster time to proficiency or more consistent execution. If the team cannot name those changes, the platform is probably organizing information better than it is improving work.

Ownership is usually shared, but the decisions are different. The CHRO has to decide whether manager and employee work is actually being simplified or only moved into a cleaner system. The CIO has to decide whether the platform is only replacing infrastructure or whether the workflow, approvals and handoffs around it are also changing. If either side treats this as a software event, the business can spend money on transaction discipline without getting better workforce readiness or better use of manager time.

The source supports a narrower claim than many readers will want to make from it. It tells us Lockheed Martin announced the modernization and the intended platform direction. It does not tell us how well adoption is going, whether manager effort is lower, whether employee experience improved, or whether the business is seeing productivity gains or return on investment. There is no independent verification here of implementation success or difficulty.

The point is to check whether a platform refresh is changing the work or only making the administration cleaner. I would change my view with before-and-after evidence from early cohorts showing lower manager administrative load, clearer ownership of exceptions and measurable improvement in time to proficiency, decision speed or service consistency.

The signal I’m watching

I would watch whether the first implementation reduces manager work and raises capability readiness, or simply adds system discipline without faster decisions.

What would strengthen this signal

A stronger signal would be a before-and-after view showing lower manager admin load, clearer ownership and faster time to proficiency in the first deployment cohorts.

Sources