WCRC Analysis
Ricoh's technology-adoption survey, released on 21 October, describes a gap between management confidence and employee experience. In its company-issued findings, 91% of business decision-makers expressed confidence that AI investments were delivering expected value, while 53% of employees said AI created friction or additional work.
September fieldwork covered 2,017 full-time workers in the US and Canada: 1,511 employees and 506 business or IT decision-makers. This is vendor-sponsored, self-reported evidence. The groups should not be treated as matched pairs from the same organisations, and the percentages do not establish a measured loss of productivity. Trade publication dates on 22 October should not obscure the original release date.
Follow a task through the gaps
WCRC's analysis is that the complete task is a more useful starting point than the individual application. A tool can perform its assigned step adequately while leaving considerable work between that step and the next one.
Consider a hypothetical request that moves from a shared inbox into a case-management system and then into a reporting file. Someone may have to interpret the original message, enter the same details again and check that the record remains consistent. The processing time inside one application would capture only part of that work. This example illustrates the proposed analysis; it is not an observed Ricoh case study.
A practical review follows a small number of real tasks from beginning to end, with the appropriate permissions. It records where information is found, what gets entered more than once and who handles an exception. The employee doing the work should be able to correct the resulting account. Otherwise, the process map may describe the intended system while missing the working method.
Establish a baseline before claiming a saving
WCRC would separate time spent completing the task from time spent managing the tools around it. Search, correction and waiting should be visible where they can be measured reliably. That makes it possible to judge a proposed change against the actual burden it is meant to reduce.
The comparison needs care. A quicker case may simply be an easier case. A new tool may initially require more learning. A review should record those conditions and compare similar work over a suitable period before treating a difference as a dependable saving.
This avoids another measurement problem: a reduction in one team's workload can create additional checking for another. A process-level result should include the work transferred downstream. Otherwise, an organisation can report several successful departmental projects while leaving the total task largely unchanged.
Examine workarounds as evidence
When an employee creates a parallel spreadsheet or uses a different route to finish a task, the response should begin with understanding the problem they are trying to solve. That does not make every workaround appropriate. It does help identify why the approved route is being avoided.
A manager should be able to distinguish a missing capability from a training need or an unclear instruction. Each calls for a different response. The review should also account for the information handled and the controls that apply, rather than treating convenience as permission to move data anywhere.
Employees need a credible way to describe these difficulties. If reporting friction is interpreted as failure to adopt technology, the organisation loses information it needs to improve the process. Feedback should lead to a named owner who can investigate and respond.
Ricoh's survey gives that investigation a current news peg, not a universal verdict on workplace technology. WCRC's proposed test is to ask what happened to the complete job after a tool was introduced. If repeated entry, correction and coordination still surround it, the next useful investment may be in how the work connects. That question can be answered through observation and a fair comparison, rather than confidence alone.