Leveraging Lean UX in Drupal
0 likes546 views
The document discusses leveraging Lean UX principles in Drupal development, emphasizing a faster, more iterative approach that focuses on user experience rather than traditional wireframes and specifications. It highlights the importance of user stories, success metrics, and agile methodologies in fostering collaboration between designers and developers. An example is provided with the Mukurtu project, showcasing improvements in user experience and functionality through smart design and open source development.
Leveraging Lean UX in Drupal
- 1. Leveraging Lean UX in Drupal Drupalcamp New Orleans March 28, 2015
- 2. Typical UX Approach Wireframes, site maps, flow diagrams,content inventories, taxonomies, mockups and of course, the ever-sacred specifications document Image source
- 3. Results of the Traditional Approach ● A front heavy development process ● Design and front end visual goals often compromised ● Harder to make changes along the development path ● Bonus: solid ground to stand on!!
- 4. Lean UX The practice of bringing the true nature of our work to light faster, with greater focus on the actual experience being designed.
- 5. At the Start Key Success Metrics ● What is the value being created ● Goals and success metrics become a guiding light
- 6. Lean UX is not a shortcut ● Very short, iterative, low-fidelity cycles, with regular feedback ● Speeds up delivery with knowledge sharing greatly enhanced between Designers, Coders and end clients Image source
- 7. Lean UX Concept > Prototype > Test Internally > Externally Validate > Learn from User Behaviour > Iterate
- 8. Where to Start? User Stories User A, wants to accomplish goal X so they will find the Feature B which results in Outcome Y.
- 9. User Story Example Mary Jane, a social scientist, wants to report bees in her backyard so she will find the ‘add a count’ tool to post the observation type, time and location.
- 10. What’s next? Functional Requirements ● User based acceptance criteria ● Access matrix defining user roles and permission ● Define content types with fields/ taxonomies
- 11. Appetite for Agile Very Important! You must be comfortable with the rough edges Your client needs to understand the process You need a very clear vision and focus on the core value
- 12. ● Sprint Planning ● Do the Drupal! ● Drop in base theme ● Test the functionality ● Determine what wireframes / design are needed First Really Early Prototype
- 13. What About Wireframes? ● Would a wireframe help define the functional spec? ● Would click through wireframes help define the workflow? ● See the reality of field length, content and functionality, the wireframe the necessary pages
- 14. Big Win for Drupal Do what comes naturally!
- 15. Example: Mukurtu Mukurtu (MOOK-oo-too) is a grassroots project aiming to empower communities to manage, share and exchange their digital heritage in culturally relevant and ethically-minded ways.
- 16. The Challenge Improved UX with Dashboard Wizard & Assisted Workflows Upgrade Organic Groups? Multirole, Content Segregation Media Management One Click Install Agile Project, Fixed Budget
- 17. Mukurtu
- 21. Kanopi Studios To create value for our clients through smart user experience design & skillful open source development. Talk to me! anne@kanopistudios.com