MoodleNet/Design Sprint: Difference between revisions
Doug Belshaw (talk | contribs) (Added link to blog post and Bryan's images from Day 1) |
Doug Belshaw (talk | contribs) (→Agenda: Added photo of Martin) |
||
Line 23: | Line 23: | ||
=== Agenda === | === Agenda === | ||
Outlandish | Outlandish's overview of the Design Sprint: | ||
[[File:MoodleNet_Design_Sprint.pdf]] | [[File:MoodleNet_Design_Sprint.pdf]] | ||
[[File:design-sprint-day-1.jpg|Martin Dougiamas at the Design Sprint|thumb]] | |||
==== Monday ==== | ==== Monday ==== |
Revision as of 05:29, 22 May 2018
MoodleNet Design Sprint (May 2018)
Overview
A place to curate everything related to the MoodleNet Design Sprint at the offices of Outlandish, 21st-25th May 2018, from 10:00 - 17:00. More coming very soon!
Aim(s)
- Martin Dougiamas: "For me, it's a visual prototype that is good enough for anyone to quickly understand what MoodleNet does and how it could look and feel."
Location
3rd Floor
149 Fonthill Road
Finsbury Park
London
N4 3HF
Agenda
Outlandish's overview of the Design Sprint: File:MoodleNet Design Sprint.pdf
Monday
Focus: Collect
Morning
- Introduce ourselves and define roles
- Data gathering and analysis
- Exercises:
- a) Activity analysis
- b) Process / journey mapping
- Target User work
- Plot the user scenario
- Create the user Point-of-View statement
Afternoon
- Outcome focused session
- Identify risks and mitigations
Outcomes
Tuesday
Focus: Explore
Morning
- Idea generation
- Worst possible idea
- How might we...?
Afternoon
- Challenging assumptions
- Decision time
Wednesday
Focus: Prototype
Morning
- Wireframe user journey
- Sitemap creation
- Wireframe screens
Afternoon
- Outlandish designer creates a low-fi prototype with team
- Content and UX writing
- User testing script & prep
- Decision on whether or not we will focus on a more developed build on Frida
Thursday
Focus: User test
Morning
- User test
- User testing with five teachers and the team observes
- User testing with technical architect
- A tech review to identify technologies that could be used, opportunities for best development
- Creation of a user testing report, based on:
- Behaviours
- Expressed likes
- Usability issues and failed tasks
- Feature requests from users
- Questions
Afternoon
Gather our user testing evidence and pool our observations
User test participants
- 11:00 - Andrew Field
- 12:00 - Miles Berry
- 14:00 - Mary Cooch
- 15:00 - Christian Turton
- 16:00 - Jess Gramp
Friday
Focus: Iterate
Today has flexibility, but in short it’s about iterating the wireframe. At the end of today Moodle will walk away with a prototype that’s been tested AND iterated, so there is some evidence-based confidence in it as a solution.
Today involves:
- Wireframing UX solutions, based on user testing
- Wireframing new functionality, screens etc, as needed or requested by user test subjects
- Detailed content writing
- Producing the expanded and improved-upon clickable XD prototype
At the day’s close Moodle will walk away with a prototype and evidence-based confidence in taking it forward as a product.
Data
The following contains sensitive data, so shared on a need-to-know only basis. Please ask for access if required and appropriate.
Useful links
A dumping ground for things on this wiki and elsewhere that may be useful during the week. Unordered.