1. Executive support
1.1. Backing up projects with more data
1.1.1. Vote
1.1.2. Vote
1.1.3. Vote
1.2. Building awareness for the importance of UX-Design
1.2.1. Vote
1.2.2. Vote
1.2.3. Vote
1.3. Research data that is directly reflected in ROI
1.3.1. Vote
1.3.2. Vote
1.3.3. Vote
1.4. Always back UX-decisions to get Executive Support
1.4.1. Vote
1.4.2. Vote
1.4.3. Vote
1.5. Quantify the business impact of certain UX-Improvements (ROI)
1.5.1. Vote
1.5.2. Vote
1.5.3. Vote
1.6. Building awareness of UX in market/industry
1.6.1. Vote
1.6.2. Vote
1.6.3. Vote
2. UX-focused crossfunctional team
2.1. More research data
2.1.1. Vote
2.1.2. Vote
2.1.3. Vote
2.2. Creating a system that shows a direct corelation between reserach and ROI
2.2.1. Vote
2.2.2. Vote
2.2.3. Vote
2.3. share impact after releases for motivation
2.3.1. Vote
2.3.2. Vote
2.3.3. Vote
2.4. Involve the marketing teams in the UX-Process
2.4.1. Vote
2.4.2. Vote
2.4.3. Vote
2.5. Follow up plan and vision
2.5.1. Vote
2.5.2. Vote
2.5.3. Vote
2.6. Balancing act between feature for experienced users and a dummy variant (eg. 1 click)
2.6.1. Vote
2.6.2. Vote
2.6.3. Vote
3. Project schedule that predicts and supports iterative design and UX research
3.1. Planning more AB tests
3.1.1. Vote
3.1.2. Vote
3.1.3. Vote
3.2. Schedule redesigns or adjustments after release
3.2.1. Vote
3.2.2. Vote
3.2.3. Vote
3.3. do User-Testing- & Onboarding-Sessions
3.3.1. Vote
3.3.2. Vote
3.3.3. Vote
3.4. Binding afterlaunch session after x months to revise functionality and (customer) feedback, as well as reprioritise deferred features
3.4.1. Vote
3.4.2. Vote
3.4.3. Vote
3.5. split big new features
3.5.1. Vote
3.5.2. Vote
3.5.3. Vote
3.6. Monitoring of the required level of detail and whether all detailed settings actually have to be enabled for all customers
3.6.1. Vote
3.6.2. Vote
3.6.3. Vote
3.7. Being able to say "we were wrong" and take the time to do it right
3.7.1. Vote
3.7.2. Vote
3.7.3. Vote
4. Capable UX team
4.1. Continuing education
4.1.1. vote
4.1.2. Vote
4.1.3. Vote
4.2. Enough time for UX-research for each project
4.2.1. Vote
4.2.2. Vote
4.2.3. Vote
4.3. more UX-Input (e.g. workshops) for PMs
4.3.1. vote
4.3.2. Vote
4.3.3. Vote
4.4. Improve analytical skills (qualitative and quantitative)
4.4.1. Vote
4.4.2. Vote
4.4.3. Vote
4.5. Having more research data
4.5.1. Vote
4.5.2. Vote
4.5.3. Vote
5. Adequate UX resources (1 for every 5-9 devs) and budget
5.1. Styleguide accessible for every team member
5.1.1. Vote
5.1.2. Vote
5.1.3. Vote
5.2. ready to use components
5.2.1. Vote
5.2.2. Vote
5.2.3. Vote
5.3. Grow dev team and build UX research team
5.3.1. Vote
5.3.2. Vote
5.3.3. Vote
5.4. Using the right tools for the right purposes
5.4.1. Vote
5.4.2. Vote
5.4.3. Vote
6. Dev process that includes UX (not only coding and QA)
6.1. 1. More communication on the UX decision
6.1.1. Vote
6.1.2. Vote
6.1.3. Vote
6.2. 2. Involve DEVs more in conception phase instead of waterfall process
6.2.1. Vote
6.2.2. Vote
6.2.3. Vote
6.3. 3. Library & Style Guide to follow
6.3.1. Vote
6.3.2. Vote
6.3.3. Vote
6.4. Building a better bridge between IT and UX for a better understanding of UX-Decisions
6.4.1. Vote
6.4.2. Vote
6.4.3. Vote
6.5. Testing prototypes
6.5.1. Vote
6.5.2. Vote
6.5.3. Vote
6.6. First vision of UX-concept should be detached from implementation (don't let devs set borders to early in design process)
6.6.1. Vote
6.6.2. Vote
6.6.3. Vote