Our global presence will give you plenty of room to work wi One of the major obstacles to adoption of traditional enterprise software is poor user experience take ERP solutions, for example.
A lot of legacy enterprise technologies just aren’t user-friendly and people won't use something that's poorly designed or complex, and that impacts productivity in a negative way.
When it comes to productivity tools for collaboration, analytics and mobile, we understand and improve the user experience and improve collaboration and productivity.
According to the Institute of Electrical and Electronic Engineers (IEEE)2005 research, Site exit disclaimer roughly $1 trillion a year was spent on IT worldwide, with the U.S. government spending more than $60 billion on its roughly 1,200 civilian IT projects and an additional $16 billion on military IT.
In the Human Factors International (HFI) video, The ROI of User Experience, Site exit disclaimer Dr. Susan Weinschenk notes that of those IT investments, up to 15% of IT projects are abandoned and at least 50% of a programmers’ time during the project is spent doing rework that is avoidable. Following UCD best practices, helps to identify challenges upfront so that a solution can be found early.
Avoiding Common Mistakes by building a skilled team and following best practices, you can avoid several of the top 12 reasons IEEE identified for why IT projects fail:
Site exit disclaimer
o Unrealistic or inarticulate project goals
o Inaccurate estimates of needed resources
o Badly defined system requirements
o Poor reporting of the project's status
o Poor communication among customers, developers, and users
o Use of immature technology
o Inability to handle the project's complexity
o Sloppy development practices
o Poor project management
o Stakeholder politics
o Commercial pressures
HFI recommends following the “10%” rules.The rules of thumb state that 10% of your IT staff should be user experience (UX) professionals and 10% of your budget dedicated to UX. By putting a larger emphasis on UCD principles and practices, you can make iterative improvements and avoid costly large scale rework that does not fit your users or organisations goals.
Weinschenk, in her white paper Usability: A Business Case Site exit disclaimer outlines three useful equations for calculating cost savings related to:
(# of errors) x (avg. repair time) x (employee cost) x (# of employees) = cost savings
Example: (2 errors/week) x (60 mins) x ($30/hour) x (100 employees) = $6,0000/week or $300,000/year
(# of changes) x (avg. hrs/change) x (cost of developer) x (4, if late) = cost savings
Example: (20 changes) x (8 hrs each) x ($40/hour) = $6,400 if fixed early or $25,600 if changed late
(Time saved) x (employee cost) x (# of employees) = cost savings
Example: (1 hr/week) x ($30/hr) x (1000 employees) = $30,000/ week or $15,000,000/year
Defining and Measuring Success
In addition, there are some other ways to define and monitor success related to your goals.You can do so by identifying specific targets for various performance and satisfaction goals: