A white-collar employee does not automatically “pay for themselves” by being busy or by adopting a productivity tool. The business case becomes credible when employees help improve a process and the organisation can verify what their effort changed: fewer defects, faster service, additional completed work, lower avoidable expenditure or reduced operational risk. A useful distinction is between producing more activity and producing more value.
On 7 October 2026, SAP’s Future of Work Research Lab warned about a productivity trap: organisations may be improving efficiency while leaving the more important question of work redesign unanswered. Its reported research draws on monitoring more than 500 external resources and mixed-method work involving 2,718 employees, 500 C-suite leaders, 60 HR executives and founders of AI-native companies (SAP News Center, 2026). SAP is also a commercial technology provider, so its recommendations should be considered alongside its commercial context.
Time saved is capacity, not yet a return
Consider a hypothetical team of 20 knowledge workers, each recovering 20 minutes a day after reducing duplicate data entry. Over 20 working days this amounts to about 133 hours of capacity. That is an illustration based on arithmetic, not a measured study outcome. If the time is lost to extra meetings, it may create no financial return. If it helps the team clear an existing backlog with fewer errors, the change can create a meaningful customer and operating benefit.
Nor should 133 hours automatically be multiplied by salary rates and reported as cash savings. Payroll usually remains unchanged. Cash savings require an actual reduction in avoidable expense, while capacity improvements require demonstrable redeployment to valuable activity. When leaders call all released time “savings,” they confuse a promising process measure with a realised business result.
SAP reports that 72% of surveyed C-suite leaders thought many organisations describing their AI work as transformation were largely automating existing jobs faster. Its related work-redesign research also found that many employees experiencing AI-related job changes did so without meaningful guidance. These are perceptions within the research; they do not establish that a particular company’s redesign or technology investment has succeeded or failed.
The continuous improvement opportunity is in the workflow
For a finance, HR, procurement, sales operations or administration team, useful improvement often begins with a service rather than a software feature. Trace a supplier invoice, employee onboarding case or sales quotation from request to completion. Record waiting time, rework, information searches, handoffs, approvals and exception routes. Identify which steps are necessary to meet a customer, regulatory or control requirement, and which exist because nobody has questioned the sequence.
Then test one improvement with a clear baseline. A procurement team might standardise the information received at intake before automating the approval. An HR team might shorten repeated employee queries by clarifying a confusing handoff between payroll and benefits. A customer service team might reduce repeat contacts by resolving an underlying information gap. The interventions differ, but the discipline is consistent: understand the problem, change how work is done and compare results.
One of SAP’s proposed shifts is to judge work by impact rather than output. For process improvement, that translates into two measurement layers. Operating indicators may track turnaround time, first-pass quality or work-in-progress. Outcome indicators track whether the change improved customer access, released scarce capacity for higher-priority work or avoided a specific, documentable cost. Both layers matter because a faster internal task can still create a worse experience downstream.
Build an improvement workforce rather than a suggestion box
The most valuable employee contribution is not always a spectacular invention. It may be noticing why a recurring exception exists, quantifying how often it occurs and working with colleagues to remove its cause. People who understand the operation can help distinguish genuine constraints from apparent ones. They still need defined time, permission, data, problem-solving skills and a leader willing to act on evidence.
A sensible improvement routine asks each team to maintain a small register of observed problems, choose one worth solving, measure its baseline, try a contained countermeasure and review outcomes after implementation. Ideas that fail to deliver are recorded as learning rather than celebrated as savings. Ideas that work should become the standard way of working, with an owner and an expiry or review point. This is continuous improvement as an operating habit, not a one-off employee campaign.
Where training fits. Professionals who want to learn how to define problems, analyse processes, design changes and demonstrate value can explore STEP Bootcamp. Employers seeking to build those capabilities in their own processes can enquire about tailored STEP Corporate Training. Explore STEP Bootcamp or enquire about STEP Corporate Training.
A workforce can contribute returns far beyond its job descriptions, but the proposition has to be demonstrated—not assumed. The relevant question is not whether every employee can be assigned a fictional savings target. It is whether people are equipped to find the right problems and whether the organisation converts credible improvements into observable value.
Sources and references
• SAP News Center | Spoiler Alert: The Future of Work Is Already Here | 7 October 2026 Related OES reading: Scaling AI Through Process Improvement: What Gartner’s Latest Survey Changes
Leave a Reply