 Hi everyone, my name is Candice and thank you for joining me in this 4.0 roadmap update. The UX lead for the Moodle design team and as you can see the team are spread across different products within Moodle. So we've got LMS, mobile app and workplace. We also extend our design team out to our external stakeholders. So we work really closely with our partners, MUA and the Moodle community itself, that means developers, students, teachers and administrators. So they're also really important as part of the design process. So we're at with 4.0 so far as we've just completed vision and prioritization phase where we actually went and did some discovery on what would be the great user stories to set us up for 4.0's delivery. So we're in delivery now, we've just kicked off and we're preparing all the design solutions so that we can build that as part of 4.0's release next year. Just to go back a bit about that phase one, really we had two key objectives. One was to establish ourselves on Moodle.org so we could make contact with the community and a place for us to share our thoughts and our research and our process as well as also define those 4.0 projects for the roadmap. Those two key activities that we did during that discovery phase to actually define the roadmap was a survey that we sent out to our users and also we ran a series of workshops. The survey itself was very interesting. We got a lot of great feedback from our users over 770 results and you know the key thing that we were looking for from the data was from the question we asked which was what's the one thing that challenges you the most on a day-to-day basis when using Moodle. So as you can see probably here in the top 10 categories you've got on the diagram you know really what stood out was courses and student experience. So the teacher created courses and student experience as well as some technology issues, activities not working as well as they showed the mobile app and components. So when we put all that information together and categorize them and rank them by severity again we got this focus area on the key problems around the teacher course experience. Teachers not being able to easily duplicate, reuse and move course content around so the system not being as flexible as it could be. Students not finding their way around the system that easily as easily as they should know the interface giving the users a lot of options so just making it a bit difficult for them to complete some common tasks. Activities as well as quiz and assignment standing out as quite severe issues on the setup processes and workflows as well as components. So grade book needing some help with some you know improving some of that the manual workflows and being able to yeah link better that student enrollment flows to the grade book workflows as well. So we also delved into delved into this research during some workshops and we run the ran these over a couple months we had 12 workshops in total about 40 participants and again we ran these internally as well as externally so we had teachers participate students and our dev community we really focused on what the vision was for 4.0 who's our target audience and who what are their pain points what do they need we looked at looked at that over the user journey map so to understand that in the real world context of them you know through their life cycle then we went into some fun bits of ideation where we said how can we solve some of these problems together so those results from the user journey map actually was what we extracted the data from in terms of what are all the issues that our users are having while they are moving through the system at different phases of their life cycle so again we got some key themes back around the teacher journey map saying was difficult difficulty around navigating between courses at speed again moving content around more easily grading activity the resources and quiz also coming up as some friction areas through their processes as well as the student journey map highlighting to us that also navigating between courses wasn't as easy as possible and that students really just need to know what to do next especially from you know place where they would expect that to happen in their dashboard and also just making the assignment and grading process progress a lot clearer and intuitive for them so ultimately we put that back together from all of this information and discovery phase and we came up with three key objectives for 4.0 and that was to you know make sure that we're optimising the UX for the most critical user tasks, Relative Design and New Language System for LMS and really modernise Busts Interface theme interface and then while we're doing this we're obviously going to do this very user-centred and make sure we're really embedding a user-centred framework and everything that we do so just to focus again on those key theme areas for the optimisation of the UX journeys we really want to focus on navigation that was called out for the teacher and the student experience, the teacher create a course, workflows, student do a course, UX needs to be improved, the teacher-student dashboard with there's some work to be done there and some further work around teacher assignment and gradebook experience. So how did we actually make sure that we were choosing the right things for this process? Well we had all that list of user problems that we extracted through the discovery and then we went through a qualifying criteria process where we said if you're a teacher and a student well then you know and it's an issue that you're facing then that passes through as a problem that we want to deal with then again we looked at these key areas and said if it's part of navigation create a course, do a course, dashboard, assignment or gradebook then we give you a thumbs up you can definitely come through to 4.0 because we know that these are the key areas that are causing people the most issues and then we go through to prioritisation where we look at it with our development team and we actually say how big is this problem versus the value that we're going to get from actually investing the time and effort to build it. Ultimately where we want to get to is obviously create those cool user stories so we can start building and designing a solution. I'm not in scope for 4.0 things like quiz forum, enrolment, feedback, messaging, etc so it doesn't mean we're not going to do those things it just means they're not a priority right now and as soon as we complete those really critical stories for create a course and do a course etc the next issues that have come that have bubbled up in those themes will be looked at immediately straight afterwards. So all together how that looks like over the next 12 months is we've got three project streams led by our designers who are working with our development and product teams and our first stream of work is again that how going into that key theme area of navigation and solving the problems in there within the menu and the breadcrumbs etc and then towards the end of that stream being able to pick up the teacher assignments set up in grading issues. Second course stream was all about that teacher create a course UX so being able to edit and move content around more easily we've put in there a bit about onboarding but we think we're hoping that we would have solved a lot of those problems in the first phase and yeah we're just banking on that we're making them interface a lot more intuitive and won't really rely that need to rely that much on onboarding but we're keeping it in there because it did come up in the research as a as a thing that people really needed. The teacher and grade book a setup and editing stories will then follow after that and the third stream is picking up the pieces of the teacher dashboard UX and of course that student UX around doing the course and the dashboard so just improving those user flows around their timeline and you know their to-do lists. So new design language for LMS Boost theme as we said we want to create something that's scalable sustainable and no something that's focusing on universal design language which is meeting our highest usability and accessibility standards and we do have to focus on unifying LMS with our app experience because obviously they are the same product used by the same users but we also have to bear in mind that we have some common workplace UI components that we may not want to incorporate into into our system as well. So ultimately what we want to achieve is you know starting to build out that new design system with the foundation aspects and the UI components and pattern library which looks a little bit something like this so we've got a long way to go and we still need to find a home for our design system so that we can create this library and this common toolkit for everybody to have access to. So how are we doing it is obviously we're going to be working an agile with our development team we're working two weeks sprints we can do a lot of you know clearing up what's the user problem making sure we're honing on the right scope and really getting in through to that estimate to that ideation phase where we can quickly rapidly ideate design and test some of these solutions and work lean with our product and development teams and of course with yourselves out there our community our partners and MUA to make sure that we are getting you know closer to the right problem together and everybody's aware of the direction that we're taking. So we have set off we're currently in the second sprint so please do keep updated on noodle.org UX team and you'll see all of our projects up there in different streams where you can see the workflows and updates every day of what we're doing we do have one major update that we'll do every fortnight so at the end of the sprint but there are more frequent updates that we'll do as well and particularly around recruiting for research and getting involved in some of our activities which we'd really like you to be part of so things like ideation workshops or just some usability testing or interviews and just sharing our prototypes and getting feedback on that so there's a lot of stuff that's going to be coming your way to please stay tuned and please get involved and please give us your feedback really want to hear what you think of the roadmap and any suggestions that you have and yeah look forward to working with all of you on 4.0 cool thanks