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.
Along with design and development work, research efforts need to be represented in an Agile backlog to enable teams to focus on continuously learning about users throughout the project.
Agile development teams that struggle to keep track of UX work in the product backlog can utilize a separate backlog for UX. This method can help siloed teams where UX and development aren't in direct communication. Separate UX backlogs do have pros and cons, which are discussed here.
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.
Feedback during design critiques can be filled with hypothetical scenarios and unactionable suggestions. The right facilitation techniques help stakeholders and team members stay on track while still feeling heard.
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?
A general technique that's helpful in many kinds of UX workshops and design ideation is to first have team members work independently to create diverging ideas and solutions. Then, as a separate step, everybody works together to converge on the final outcome.
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.
In 2020, the most typical researcher–to–designer–to–developer ratio reported was 1:5:50. Beware, however, of using role ratios alone to measure teams’ maturity or impact.
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?
Will the UX field value people who change careers from another field and want to become user experience professionals? Will the field still value them if they're a bit older, and how do they compete with fresh graduates?
3 quick game-like activities you can use with participants in a UX workshop to get the team energized and ready to be creative and productive before turning to the real work of the meeting.
Design and development projects are highly multidisciplinary with team members with a variety of skills and vocabulary use, sometimes with conflicting definitions of terms. A kickoff meeting can make sure everybody is on the proverbial same page regarding all the team members' skills and responsibilities.
Anybody who's already a good UI designer and can make great screens, has a big head start to becoming a good UX designer, but more is required to excel in this expanded role.
To maintain focus in a UX workshop, set aside ideas in a "parking lot" if they diverge from the stated agenda. Parked ideas should be discussed later when they won't slow the team's momentum in addressing the meeting's main topic. Here are 3 guidelines for making the most of a parking lot.
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.
Use the affinity diagramming method with stakeholders and members to efficiently categorize then prioritize UX ideas, research findings, and any other rich topics. Work together to quickly develop a shared understanding among your team.
How can you determine whether your organization is doing UX right? One tool is to estimate the UX maturity: high (set up for systematic success) or low maturity (mostly fail, and ship bad design, unless you're lucky). This video presents the main signs of low UX maturity.
Trade-off scales are a tool that UX practitioners can use to visually prioritize user needs and project dimensions to focus resources on the most important ones.
What to do when a UX team becomes too popular and too many projects want UX help with their designs, overwhelming the available capacity to do good work.
Workshops are a useful tool in the user-experience design process, but mistakes are common when the workshop facilitator didn't prepare right, causing the team to waste time.
Flip-charts, post-its, markers, stickers, and even fake coins are common ingredients in a UX toolkit. Though they may appear to be frivolous art supplies, these materials serve a crucial role in supporting team engagement, creativity, and focus.
There are clear benefits and drawbacks to doing UX work as part of a UX team or a product team. Knowing and addressing these can help you grow the organization’s UX maturity, improve awareness about UX, and hone your craft.
Tips to help clarify the role of UX and how to navigate the relationship dynamics between UX and the rest of the team within an Agile development process.
UX professionals often receive poorly defined design requests. When saying no is not an option, a more productive way of addressing the request is to focus on the outcome goals and the Return On Investment (ROI) of proper UX effort.
Along with design and development work, research efforts need to be represented in an Agile backlog to enable teams to focus on continuously learning about users throughout the project.
Feedback during design critiques can be filled with hypothetical scenarios and unactionable suggestions. The right facilitation techniques help stakeholders and team members stay on track while still feeling heard.
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.
In 2020, the most typical researcher–to–designer–to–developer ratio reported was 1:5:50. Beware, however, of using role ratios alone to measure teams’ maturity or impact.
Product design principles (or, in short, design principles) are value statements that frame design decisions and support consistency in decision making across teams working on the same product or service.
In a survey of 557 design and UX practitioners, organizations only did 22% of recommended DesignOps efforts, did not have DesignOps-dedicated roles, and had low DesignOps maturity overall.
Practitioners define DesignOps based on the value it provides for their team or organization. Most practitioners think of DesignOps as a way to standardize and optimize processes, enable and support designers, or scale design.
Even though in-person UX sessions are typically ideal, sometimes budget or travel restrictions necessitate remote UX work. This article presents guidelines for remote user research, UX workshops or presentations, and collaboration.
Meetings are for sharing information; workshops are for solving a problem or reaching an actionable goal. We compare the differences in purpose, scope, length, structure, and preparation time for workshops and meetings.
Design and user research usually report to either a centralized UX team, a product team, or a hybrid of these. There are clear benefits and drawbacks to each model.