iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Simpler enterprise software can reduce the time and effort employees spend correcting errors, relearning interfaces, asking for help, and working around inaccessible or poorly fitting workflows. The business case for human-centred design (HCD) is to identify those costs in real work, improve the tasks that cause them, and measure the change against a local baseline—not to assume every redesign delivers a fixed return.
What human-centred design means for enterprise software
HCD is a lifecycle approach: understand the people who use or support a system, design around their needs and context, then evaluate the result and continue gathering feedback. It is not simply a visual refresh or a usability test at the end of a project. Digital.gov describes HCD as an iterative practice, while ISO 9241-210:2019 sets out requirements and recommendations for HCD principles and activities across the lifecycle of interactive systems.
That standard’s scope includes off-the-shelf software and custom office systems. ISO says the 2019 edition was reviewed and confirmed in 2025, so it remains current as of that review. It provides a process framework, not a guaranteed savings figure or ROI formula.
Where simpler software can create business value
Usability problems generate costs through several connected pathways. NIST’s IUSR overview describes overhead from correcting errors and relearning interfaces, and identifies reduced errors, training and maintenance costs alongside greater productivity and user satisfaction as plausible benefits of improved usability. NIST notes that the page is no longer being updated, so it supports the general mechanisms—not a current numerical estimate.
#1 Best Overall
- Used Book in Good Condition
- Errors and rework: unclear labels, confusing sequences, or poor feedback can lead to incorrect entries, corrections, duplicated work, and abandoned tasks.
- Repeated learning and training: people may need longer onboarding, refresher instruction, or colleague help when common tasks are difficult to remember.
- Support demand: recurring questions and avoidable help-desk contacts consume time for both employees and support teams.
- Task time and workflow friction: extra navigation, workarounds, and unnecessary handoffs can slow routine work or add workload elsewhere.
- Accessibility and adoption: barriers can prevent employees from completing tasks efficiently, especially when software does not work with their needs or assistive technologies.
- Lifecycle costs: maintenance, support, accessibility remediation, and transition work all belong in a comparison—not just purchase or implementation cost.
Accessibility can be relevant to efficiency as well as compliance. Section508.gov connects accessible tools with productivity, operational efficiency, service delivery, and lower remediation or legal risk. Its guidance addresses U.S. federal obligations and organizational cases; other organizations should apply the mechanisms in their own legal and operational context.
How to measure the case in your organization
Start with a specific workflow and the people who perform and support it. Define the problem before selecting a redesign or procurement option, then record a baseline so later changes can be compared with the work as it actually happens.
Rank #2
- 57 clear-to-use design methods
- Case studies of process in action
- Practice worksheets
- Choose representative workflows and users. Include the roles and user groups affected, plus support staff where their work is part of the friction. Capture important differences in task frequency, context, and accessibility needs.
- Record baseline measures. For the targeted tasks, measure completion time and completion rate; error, correction, rework, and abandonment; onboarding or training time; repeat questions and help-desk contacts; accessibility barriers and time spent resolving them; and adoption by role or group.
- Include the full cost picture. Account for maintenance, support, remediation, implementation, and transition costs. A change that makes one screen easier but increases workload or support elsewhere may not improve the overall process.
- Set a realistic adoption assumption. Distinguish mandatory from voluntary use and estimate how many people are likely to use the improved workflow. Report assumptions clearly rather than treating projected uptake as certain.
- Compare outcomes after the change. Reassess the same workflows and user groups using the same measures. Separate observed changes from projected benefits, and note relevant changes in volumes, staffing, policy, or other conditions.
- Translate results into organizational value. Apply local transaction volumes and labor or service costs. Distinguish cash savings from capacity freed for other work; do not count the same time saved as both unless the organization can actually convert or redeploy that capacity.
The UK Government Digital Service’s Digital and Data Benefits framework offers useful benefit categories, including productivity, user experience, channel shift, and reduced failure demand. It is government appraisal guidance, not enterprise-software ROI evidence. It warns that take-up, productivity, and savings assumptions are uncertain and recommends scenario testing to reduce optimism bias. Build low, central, and high cases from your own data rather than importing public-sector estimates as expected returns.
How to compare software options fairly
Vendor claims about ease of use are hypotheses to validate with your users and tasks. Compare options against the same representative workflows, user groups, and conditions so that a short demo or a polished interface does not substitute for evidence about everyday work.
Rank #3
| Comparison area | What to assess |
|---|---|
| Task performance | Task success, completion time, errors, rework, and abandonment on representative workflows. |
| Accessibility and user fit | Whether people with different needs can complete tasks, including with relevant assistive technologies. |
| Learning burden | Training and onboarding effort, learning curve, repeat questions, and help requests. |
| Workflow fit | Integration with existing work and whether changes remove friction or shift/add workload. |
| Lifecycle burden | Support, maintenance, remediation, implementation, and transition costs. |
| Benefit confidence | Adoption assumptions by role or user group, evidence behind projected gains, and uncertainty across scenarios. |
Who to involve, and when
Bring in the people who do the work and the teams that train, support, maintain, or oversee the system. Digital.gov’s design guidance recommends involving participants and stakeholders in discovery and checking whether a proposed solution changes workflows or adds workload. Include affected users early enough to identify the real task and its constraints, then return to them when evaluating whether the change helped.
This is especially important when a local efficiency gain could create extra work for another role, when accessibility needs differ across teams, or when software adoption is mandatory. A design decision should be evaluated against the whole workflow, not only the screen or team that initiated it.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What the available figures do—and do not—show
The 2026 UK Digital and Data Benefits framework reports £9.48 returned for every £1 invested in digital skills across its benefit streams. That figure concerns digital-skills investment, not HCD or enterprise UX. The same framework cites an estimated £1.5 billion in annual potential savings from full digitisation of government services by reducing offline channels; its estimate uses a Monte Carlo simulation based on existing take-up and transaction-cost data and assumes a maximum 90% digital uptake. Neither is an enterprise-software ROI benchmark.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →The framework also reports a 35% drop in call volumes in a Telford and Wrekin Council case involving a 24/7 AI chatbot. That is a service-specific case, not evidence that HCD alone caused a general productivity gain. Its cited 88.9% completion rate for the 2021 Census is context about digital-service uptake, not an estimate of software-design impact.
Best Value
No cited source establishes a controlled, general causal estimate for the financial return of HCD in enterprise software. The defensible case is therefore local: identify measurable friction, document the baseline and assumptions, test an intervention, and calculate the resulting value using the organization’s own volumes and costs.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
