Human-centred design (HCD) can make enterprise software simpler by reducing friction in the work people actually do. The business case is strongest when an organization measures that friction before a change, tests a proposed improvement with representative users, and tracks what changes afterward. There is no reliable universal return figure for HCD in enterprise software; the financial case depends on local workflows, costs, adoption and results.
What is the business case for human-centred design?
Enterprise software creates costs beyond its licence or implementation price. When employees struggle to complete routine tasks, organizations may absorb time spent correcting errors, repeating work, relearning interfaces, asking for help, or working around inaccessible features. Those costs can also affect adoption, service quality and the workload of support and maintenance teams.
As an Amazon Associate I earn from qualifying purchases.
Human-centred design is a lifecycle approach, not a visual polish pass at the end of a project. ISO 9241-210:2019 sets out requirements and recommendations for HCD principles and activities across the lifecycle of interactive systems, including off-the-shelf software and custom office systems. ISO’s catalogue says the 2019 edition was reviewed and confirmed in 2025, so it remains current as of that review. The standard provides a process framework, not a promised return on investment. ISO 9241-210:2019
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →The business logic is practical: understand users and their work, identify measurable friction, make a change, then evaluate whether the work improved. NIST describes poor usability as creating overhead through error correction and relearning interfaces, and identifies reduced errors, training and maintenance costs alongside increased productivity and satisfaction as possible benefits. NIST notes that its overview is no longer being updated, so it supports these general cost pathways, not a current benchmark or forecast. NIST’s IUSR overview
#1 Best Overall
- Used Book in Good Condition
Which costs and outcomes should you measure?
Choose measures that reflect the specific workflow the organization wants to improve. Record a baseline before redesigning or procuring software, and use the same tasks, user groups and conditions when measuring again.
- Task performance: time to complete representative workflows, completion rates and abandonment.
- Errors and rework: mistakes, corrections, duplicate entry and work that must be repeated or escalated.
- Learning and support: onboarding and training time, recurring questions, help-desk contacts and support workload.
- Accessibility: barriers encountered by employees with different needs, including the time spent finding workarounds or resolving access problems.
- Adoption: use by role or user group, interpreted in context. Mandatory use is not evidence that software is easy to use.
- Lifecycle burden: maintenance, support, accessibility remediation, integration and transition costs.
Pair quantitative measures with feedback from people who use, support and maintain the system. A faster task is not necessarily a better outcome if it increases errors, shifts work to another team or leaves some users unable to complete it.
Rank #2
- 57 clear-to-use design methods
- Case studies of process in action
- Practice worksheets
How do you estimate the return without overstating it?
Translate measured changes into local scenarios rather than importing a headline figure from another organization. Use your own transaction volumes, labor or service costs, affected roles and realistic assumptions about who will adopt the change. Keep the calculation transparent: show the baseline, the expected change, the number of people and tasks affected, the period measured, and the costs of design, implementation and transition.
- Define the problem. Identify a specific workflow and the people who perform or support it. State the friction to be addressed, such as high correction rates or lengthy onboarding.
- Set a baseline. Measure relevant task outcomes and costs before a redesign or procurement decision. Record how the sample and test conditions were chosen.
- Test a change. Evaluate a prototype or configured system with representative users doing realistic work. Check task success, time, errors, accessibility and effects on connected workflows.
- Build scenarios. Estimate conservative, expected and high-adoption outcomes, with assumptions visible. Separate cashable savings from capacity that could be redeployed to other work.
- Track after implementation. Compare the same measures after rollout, accounting for training, transition and other changes that could influence the result.
Take care not to count the same time saved twice—for example, once as a cash saving and again as additional productivity—unless the organization can actually remove the expense or redeploy that capacity. The UK Government Digital Service’s 2026 Digital and Data Benefits framework identifies productivity, user experience, channel shift and reduced failure demand as benefit streams, and recommends scenario testing because uptake, productivity and savings assumptions are uncertain. It is government appraisal guidance, not an enterprise-software ROI benchmark. Digital and Data Benefits framework
Rank #3
The same distinction matters for figures sometimes cited from public-sector examples. The framework reports £9.48 for every £1 invested in digital skills across its benefit streams, not for HCD or enterprise UX. Its £1.5 billion annual potential savings estimate concerns full digitisation of government services and reduced offline channels; it assumes a maximum 90% digital uptake and uses a Monte Carlo simulation based on existing take-up and transaction-cost data. Neither figure establishes a return for a company redesigning internal software.
How can accessibility and employee participation strengthen the case?
Accessibility is both a user need and a potential operational concern: barriers can prevent employees from completing tasks efficiently and may create remediation or legal risk. Section508.gov connects accessible tools with productivity, operational efficiency and service delivery, while advising organizations to use their own data because estimates vary. Its guidance concerns U.S. federal accessibility obligations and organizational cases; the business mechanisms may be relevant elsewhere, but the legal requirements depend on jurisdiction. Section508.gov’s business-case guidance
Involve the people who do the work and those who support it. Digital.gov describes HCD as an ongoing cycle of understanding people’s needs, designing against them, evaluating results and gathering feedback. Its design guidance recommends engaging affected participants and stakeholders, and checking whether a proposed change alters workflows or adds workload. Digital.gov’s HCD guidance and Principle 3: Design for humans
How should you compare enterprise software options?
Evaluate alternatives against the same representative workflows and user groups, rather than relying on a vendor’s general claim that a product is intuitive. Include the people who will use the system and those responsible for support, accessibility and maintenance.
Best Value
- Task success, completion time, errors and rework.
- Accessibility and compatibility with the assistive technologies employees use.
- Training burden and the learning curve for each relevant role.
- Fit with existing workflows, integrations and workload across teams.
- Support, maintenance and remediation needs over the lifecycle.
- Adoption assumptions, including who is expected to use the system and how confident those projections are.
A short, realistic evaluation can reveal trade-offs that a feature checklist misses: a system may accelerate one task but require extra steps elsewhere, or appear efficient for one group while creating barriers for another. The useful choice is the option that performs best for the organization’s actual work and can be supported through its lifecycle.
What a credible HCD business case can claim
A sound case links a defined user problem to a measured baseline, a plausible intervention and outcomes checked after implementation. It can estimate potential value using local data and state uncertainty clearly. The available guidance supports these methods and identifies plausible benefit pathways, but it does not provide a controlled, general causal estimate for the financial return of HCD in enterprise software.
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.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
