Development projects should spend 10% of their budget on usability. Following a usability redesign, websites increase desired metrics by 135% on average; intranets improve slightly less.
To save costs, some companies are outsourcing Web projects to countries with cheap labor. Unfortunately, these countries lack strong usability traditions and their developers have limited access -- if any -- to good usability data from the target users.
Usability is a well-paying profession these days: A usability specialist in California with five years' experience had an estimated cash compensation of $90,118 a year in 2001, not counting stock options or other benefits. This number is at the high end of our detailed survey, which analyzes salary data from 1,078 professionals who attended the User Experience World Tour from November 2000 to April 2001. The survey respondents represent a response rate of 40% of the 2,682 conference attendees. Because we surveyed people at a high-end professional conference, the data probably reflects the salaries of good user experience professionals.
A survey of 1,078 user experience professionals finds that usability specialists make more money than designers and writers in the same field. In all three areas, salaries are highest in the U.S., lower in Canada and Asia, and much lower in Europe and Australia.
Never listen to what people say in response to a survey: asking high-tech employees what will keep them in their jobs provides very different answers than the factors that actually drive retention.
Web project management impacts usability significantly. Mistakes include having site structure mirror your org chart, outsourcing to multiple agencies, generic links from offline collateral, and lack of strategic thinking.
You need to hire someone to design your Web site. What should you look for before signing on the dotted line? Let's look at a few different types of consultants.
In 4 case studies, the median usability improvement was 165% from the first to the last iteration, and the median improvement per iteration was 38%. Iterating through at least 3 versions of a UI design is recommended, since some usability metrics may decrease in some versions if a redesign has focused on improving other parameters.
User interface standards can be hard to use for developers. In a laboratory experiment, 26 students achieved only 71% compliance with a two page standard; many violations were due to influence from previous experience with non-standard systems. In a study of a real company's standard, developers were only able to find 4 of 12 deviations in a sample system, and three real products broke between 32% and 55% of the mandatory rules in the standard. Designers were found to rely heavily on the examples in the standard and their experience with other user interfaces.
Thovtrup, H., and Nielsen, J. (1991). Assessing the usability of a user interface standard. Proc. ACM CHI'91 Conf. Human Factors in Computing Systems (New Orleans, LA, 28 April-2 May), 335-341.
Roadmaps cover future work and vision, but this can be done at different scopes, from everything related to the product to only the UX activities and priorities, possibly narrowed to a sub-specialty of UX.
Dual career ladders are important in user experience. Don't force talented UX professionals to become managers if their growth path would instead benefit from focusing on UX craft.
A roadmap documents upcoming and future priorities for your user experience. The process starts with gathering goals, proceeds through the creation and sharing of the UX roadmap, and never ends, since the last step is to update.
Research with people who are learning Design Thinking shows that they progress in a nonlinear manner through 4 phases of increasing competency and confidence. Understanding these phases helps both learners and educators/managers.
UX staff can be organized in two ways: centralized or decentralized (or a hybrid). The teams can also report into different parts of the bigger organization. There is currently no single best practice for these team-structure questions.
At the beginning of a new project, identify the level of UX effort needed, and the key deliverables you aim to produce. Identify known and missing knowledge about users and tasks to uncover gaps before they bite you.
When stakeholders observe user research sessions, the credibility and acceptance of findings will increase. Since they are busy, make it easy to participate and work on increasing the value they get out of going.
We investigated current trends in design-team ratios, specifically: What's the typical number of designers and researchers in an organization relative to the number of developers?
UX professionals should engage in all Scrum ceremonies. Here are tips for what UX should contribute to stand-ups, backlog refinement, sprint planning, sprint review, and retrospectives.
The user experience field is plagued by vocabulary inflation: repeatedly replacing well-known terminology with new fancy words that cause miscommunication.
Advice on how to balance breadth and depth of skill within the many different subdisciplines of the user experience profession. You can't be great at everything, so how do you choose where to specialize in your UX career?
At the Virtual UX Conference, Jakob Nielsen was asked whether it's best for a UX professional's career to seek a management role or to pursue deeper and stronger levels of expertise.
We asked a group of user experience professionals what makes for efficient UX leadership in their experience. Answers differed, but included a lot of soft skills.
After each sprint, the team should have a retrospective session to identify what went well or not so well. The sailboat metaphor is a nice way to structure such retrospectives.
Great design doesn't just happen. Rather, the organization must build 6 pillars that carry UX to success: capabilities, executive support, teams, resources, process, and schedule.
UX workshops can drive projects forward and build consensus, but are only a valuable use of time when the agenda is defined from the goals you want to achieve. Here's a 3-step process for designing a useful workshop agenda in UX projects.
Create a team mission statement collaboratively with your team. Make sure everybody understands what a mission statement is and abstract the core purpose and value of your team by identifying themes in stories of value about your team.
Our UX-maturity model has 6 stages that cover processes, design, research, leadership support, and longevity of UX. Use our quiz to get an idea of your organization’s UX maturity.
Collaboratively create a UX roadmap in a workshop setting by guiding participants through activities that familiarize them with the project goals, context, and inputs and that identify key roadmap themes and priorities.
A survey of people in user experience and product management shows that these professionals disagree on who should be responsible for many key tasks, like doing discoveries and early design.
UX professionals often work hard to convince stakeholders to support UX research and design efforts. Recognizing who your key stakeholders are and how they impact your work is the first step to building fruitful stakeholder relationships.
To create a roadmap, inputs are gathered and clustered into themes, then prioritized and visualized. This article covers 6 key steps to roadmapping that can be applied to any scope or industry.
Treat your goal to implement DesignOps like a design problem: Collect evidence that demonstrates where the true design-team challenges lie and align DesignOps efforts accordingly.
Our latest research on UX careers looks into specialization, explores unique backgrounds of practitioners entering the field, and details the skills and responsibilities needed to work in UX today.
Because the field is being defined in real time, practitioners often have questions about what Design Operations means, and how to establish DesignOps practices.
UX practitioners associate the term “service blueprinting” with an artifact, framework, or collaborative tool. Those surveyed used service blueprints early on or near the end of the product-design lifecycle.
As part of an Agile team, UX professionals should participate in all Scrum ceremonies in order to maintain open communication, influence product success, and productively contribute to the team.
Retrospectives allow design teams to reflect on their work process and discuss what went well and what needs to be improved. These learnings can be translated into an action plan for future work.
