 Okay, so I'm very excited to be here to talk about learning on demand and how it's coming to Moodle workplace. This is huge for us, and I'm very excited to be here and see a lot of familiar faces. So let's get started. So about me, first, you probably don't see me there, but I'm this guy, just sitting beside Martin, which means that for the next year, I will be in a lot of marketing materials, so you'll see my face. So I managed to sit beside him, but a couple of things about me, I think I need a mic. So I'm a long time Moodleer, I think since 2008, sorry, that I was working with Moodle. I'm a product person and I'm a product manager at heart, even before it was a thing for me, I didn't know that that was a title, but I was a product person. I'm a product solver, I'm optimistic, probably. So you can see that, oh, okay. It's not a glass of whiskey, by the way, but I couldn't find a glass of water. So I'm one of these persons that sees the glass full, half full, and not half empty. I'm proud of that. I'm getting married this Saturday, and I love this Moji for no reason and I use it everywhere. Okay. Okay, so let's talk about something completely different, the learning catalogue. So what is the learning catalogue? So what is the catalogue? So you probably have seen catalogue all around. So when you're accessing Udemy, edX, Coursera, you're actually using a learning catalogue and something that basically lets you to choose the learning you do want to take, some things that are interesting to you, and basically decide what you want to learn. So this is what we want to have in Muro Workplace. It will take us a while to get there, but we're working on that. So for us, a learning catalogue will mean that we will be unlocking the learning on demand way of learning, because right now in workplace, we focus on the prescribed learning use case. Basically, it's someone else deciding what you need to learn, but because that's a huge use case in workplace, we have certifications, we have compliance training, and things like that. And of course, it's not that workplace is not really for the learning on demand use case. There's a lot of products out there that do this. There are catalogues that they can be integrated with workplace, our partners use them all the time, but there wasn't any built-in solution for this. This is something essential, so that's why we are adding Muro Workplace. And it was, in fact, one of the top priorities, the topmost priority when we ask partners what is the feature they wanted to have in workplace. So let's go back to the start, a little bit, so it doesn't go so fast, because if not, it'll take 10 minutes only for my presentation. So let's go back to the promise that we want to solve with this. What uses me? So for learners, they want basically to choose their learning and access it anywhere, anytime, find the best learning for the better price, and discover new courses that are available to them. This is basically what learners want to do when they are looking for a catalogue. Managers, which is a user persona for us, is very important. They want them to learn and improve by allowing them to choose their own learning. This is key. And also by recommending learning 30 minutes. It's not the same thing recommending something to someone done, basically assigning them to the learning. Also developers, which are very important for us, because linking with what I said yesterday, Muro Workplace is more at least both a product, a platform, and a solution. So as a platform, for us, it's very important that developers have a building catalogue and e-commerce functionality embedded into Muro that they can customize and extend. So there are a lot of keywords here. It has to be embedded into Muro, has to be a building solution, and obviously it must have e-commerce functionality so they can customize it and extend it. And organizations, they want to help improve their employees' skillset, increase their work power and therefore their benefits, but also, most importantly, promote and monetize their learning. All these things are different users from the catalogue. But you will be wondering why now or why we waited for so long to introduce the catalogue. So the first thing is that we didn't wait for so long. We have been working on this for a long time, but before we could build a catalogue within Workplace, we needed to have some things embedded into the platform that they didn't exist before 4.0. So we took the opportunity, before 4.0, to start designing the UI and the user workflow, having the catalogue in mind. So the introduction of the MyCourses pages was essential for us, because, as you know, apart from courses, we have also other learning entities, programs and certifications. So this was in place where we could show the users all the learning that was assigned to them. In fact, this is like their personal learning catalogue. So this was the first step towards that. With this, we introduced their course cover page, which is basically the details page on any catalogue. You will see, if you don't have access to the course, but you can see what is this course about, the dates and all the relevant information. You can imagine that if you had a by-mouton in there, you'll have half of the functionality of the catalogue. So we introduced the course cover page, and we also have the same four programs with the program page. So when we introduced all these elements, we had the catalogue in mind. So that's why. So what are the goals we want to achieve with the catalogue? This is very related, of course, to the pain points. So with the catalogue, we want to empower learners to take control of their own learning journey. This is basically learning on demand. We want to enable organizations to curate, promote, and monetize their learning natively in motor workplace. And we want to make it easy for developers and partners to add custom e-commerce features to motor workplace using this flexible and scalable, built-in catalogue solution. So they're very ambitious goals, and the catalogue alone could be like a different product, because it's very big. So how we approached the design, what was our approach to design with this? Because we had to make sure that we designed this in a way that we could test it as soon as possible and learn from it, because it's massive. So we moved working on this for, I think, one year, maybe. So everything started with the benchmarking. So we were looking at how all the solutions, what problems all the solutions were solving, how they solved them, and what we could do to add similar functionality. And with this, we continued the research to really dig into this aspect and everything to prepare like a very big workshop with our partners that took us like one month to prepare this. We got all the PEG partners in a room, in a virtual room, and started discussing all the things that we could add to the catalogue, but what were the priorities. And the mirror was so massive that I couldn't include it even in 10 slides. But with this, we didn't want to have a very detailed roadmap that it would probably be outdated six months after. But we really wanted to know what was essential for them so we can build the very first person of the catalogue. And on top of it, we could evolve it and add the rest of the feature. So we did the user storm mapping with them. I'll get into this in a sec. And we sliced the two first relations that we wanted to do not to be very ambitious. And then we started with the prototype look, which means that we started creating prototypes from very high level ones just to test our assumptions, test them with real users, refine the prototypes, and do this again. I think we did like three or four looks with this until we got to a prototype. But we really thought it was great. And it had exactly what we wanted to have. And then we started with the development. So what's the release plan? What will be in the catalogue? So first thing that we do is that we took the essential functionality and we split it into two releases. So in this case, with other features, we always had this approach, this incremental approach to add features in workplace. But with other features, we used to create like very big MVPs, which means that we could be working on something for six months, something obviously not so big like this. Only to realize that we put that in the house of the partners or that real users start using them, we found things that maybe we could have done differently. But we didn't know because that was the first time our users used that. So with the catalogue, we thought that we should do something different. So we should have a shorter feedback loop. So the MVP for us was basically something that could value to some users, only to some users, but that we could test. So if we could get something for the next major release, put it in the hands of the user, validate it, our hypothesis, do user testing with the real product, we could learn from it and decide with partners what is the feature that we wanted to add next. So for the first, this is like first release, and then in the second release, we just decided to add the sensor to function ID. So in release one, we implemented a course catalogue and release two could be the MVP for the learning catalogue. I'll go with that in a second. So this is what we were planning to do, and this is what we're really doing. So the course catalogue, in the first release of Mural, in its first release, which is Mural WordPress 4.4, it will basically have the same functionality of the slash courses catalogue in Mural. It will effectively replace it in WordPress. So if you enable it, you will get to our catalogue instead to the Mural LMS standard catalogue. So we will have the same functionality. People have courses that can be made public through the catalogue. Users will be able to find learning in there to purchase courses the same way they will do in Mural, and set the catalogue as set home. So basically we'll cover the same functionality, obviously adding some bits and, and as you can imagine, changing everything underneath and under UI, but the functionality will remain the same. This way, we can set that for the user, for our users that are using only courses that really need course catalogue functionality, they can start testing this and help us to validate our hypothesis. What we're going to do is just developing what is essential and relying on Mural in these first releases for everything that Mural already does. So we're not going to reinvent the wheel with the way Mural has to, for users to buy courses. So we will support enrollment plugins, there will be the payment gateways, natively and everything to ensure that users can buy courses with a catalogue. In the next release, in the following release, what we will be doing is adding our learning entities to this mix. So once we have the foundation, we'll add programs and certifications with exactly the same capability, which means that we need to implement a way of users to self-register to progress certifications, which is also a big feature. And once we have that, we can call it a learning catalogue then it can add value to all of our users who want to use a catalogue. And that will be the foundation is done. And from there, we will learn, we will test things and we will decide with our partners what's the next step in the journey. So let's have a sneak peek into the learning catalogue. So this is the catalogue learning page, landing page, sorry, so this is basically a homepage for the users in the catalogue, this is the first page that we see. And this is where all the advanced functionality in the catalogue will hook in because if there's some plugins to recommend courses to the users based on different criteria, they will add blocks to this page. If there's a rating feature for courses, it will also hook into here. Maybe you'll see the most top rated courses. Courses that your two mates are taking that might be interesting for you. All this feature might hook in in this page. Obviously this page can make publics, this can be public. And then users can either browse their categories, which is a challenging winner because it's unlike other catalogue solutions, we have to be generic. So we need to support very different use cases with just a few categories or hundreds of them. And users can find their learning by browsing the categories with filters. You will notice that this is a different view. We'll have a car view in the landing page. Here we have more like a tile layout. And users can search, find things in the catalogue, and refine the search. It might look simple and vanilla, but that was intentional, because for us, the learning catalogue and everything in workplace is like a white canvas that then our partners and developers in general take to create customized solutions for the customer. So it has to be white, clean, it has to be something that they can customize. But you'll notice the UI and the navigation is very slick and it's, and we think that it's very usable because our testing is what it demonstrates. So this is the learning catalogue. As I say, it might look simple, but there's a lot of work under the scenes because we have to basically create new functionality to replace the existing MuralLMS functionality and connect the dots and bring all the features in here so we can have the full learning journey just by adding the essential features. So the catalogue will, as I said, will be available, the cross catalogue will be available in 4.4. This is what we're working towards. Development is going very well. In fact, there are some things that are already added to the product, but they're not shown in the UI. So you'll be able to test it soon. So this is about the catalogue, but it's not the only thing I wanted to talk about. So we're releasing Mural Workplace 4.3 one month after MuralLMS, because after the MuralLMS major release, we do our QA and upgrade, and then we're ready to release. So in Mural Workplace 4.3, we have two important features that we have many features that are added, but I want to highlight two of them. The first one is this. The name is not perfect, but the other name we have for this is Tarek Manager. It was bit misleading, it was basically that. So it's a manual-assigned manager feature. It basically helps organization do better integrated HR systems with Mural, because centralize the reporting lines management to make HR manager life easier, and it streamlines a whole team creation. Because it just adds another way to define reporting lines in workplace, that is, at the same time, it's simpler for the user, and also is what all the systems use when defining reporting lines. This is basically the ability to define one person being the manager of another person. This is a data management relationship, no departments and positions involved. So a part of this, or thanks to this feature, we took the opportunity to refactor organization extractor. The way that reporting lines, the U.S. will define reporting lines works and better, because as it is today, it's maybe too close to the extractor in the database, and it's not so functional. So in the manual-assigned manager, the new feature what we're doing is that we'll have a people tab where HR managers can see everybody, all the employees in the tenant, with all the just, I'm from there, they can just get to the base, to a base where they can see all the related information for individuals, such as the jobs that have assigned so they can know all the positions they have. Because of those positions, there are some people reporting to these persons or they report to all the persons. So they will see in the same place what are the jobs this person have, who this person reports to, and everybody reporting to this person from the same place, they will be able to add new jobs, add managers manually, or add people managing to this, basically creating ad hoc teams from here, and really loud. It's a more intuitive way of browsing the organization extractor, and this is something that also helps organization with massive number of users or with a very complex organization extractor, and we have quite a lot of them. But at the same time, one of the main benefits of this is that it will simplify integrations with all the systems because this way is simpler to integrate with systems that already use this approach. So the other functionality I wanted to talk about is the public custom pages. So with this feature, we can create public landing pages natively in more workplace and expose this content and functionality to external users. For those of you who don't know what a custom pages are, basically functionality in more workplace that allows creating pages like dashboards are in blocks, like you would add them in the dashboard and then make these pages available to specific audiences in workplace. So this is the, and about our space, this is how it would look like, and you make them accessible to specific users by defining audiences. So these audiences could be, this page is only available to people in the sales department, or as we introduce now, this page is available to guests and non-authenticated users, which means that it's effectively a public page. And you can do this from workplace, natively. So I want to spend a bit of time talking about the roadmap and the new features that we will deliver in the future. And I'll take this opportunity to make an announcement. So to announce something, we're working on the accessibility accreditation, the level AA accessibility accreditation. This is the first time we get it and for more workplace, for some reasons why we couldn't do it before, but we're doing now at the same time as more LMS. Which means that hopefully in the next major release, we can, or before the next major release, we can just say that motor workplace is accessible with the AA level, which is a huge milestone. So yeah, thank you. I know the people that are expecting are looking forward to this, so yeah, it's not that exciting for all of us, but I think it's a great selling point of workplace and something that we really have to do to take all kind of uses and diversity into account. So I think this is key. So from all these features that we have in the roadmap, there are, okay, or not? Oh, okay, you cannot see them, sorry. It's not, the context is not very well. So very good. So in this feature in no column, you'll notice that, so you see that the public custom basis already completed will be delivered in 4.3. Maniles and manage is about to be finished, so it will be also in 4.3. The accessibility of it is in progress and the course catalog, of course, will be available in the next release. And for the other four features, we have already started exploring them. The most relevant and probably the most important is from the ones that we have started working on is starting report builder. So we started exploring this feature and so we can start with the design during the next increment. I don't think we can deliver something for 4.4, but we'll see because we still have to define the scope. So we might be able to split something into the release, but that's also another big feature that is commonly work place. So, okay, that's great because I just got to the end. So thank you so much. And if you have any questions, I think we have five minutes. Hello. One question you mentioned in the course catalog that organization needs other, and sometimes organizations want to buy entire catalogs of other companies like LinkedIn, Skillsoft and so on. Would that be a possibility to integrate one's catalog with another's? That's a very good question, by the way. Look, with the catalog, we don't want to, we will probably not add all the e-commerce features and all the features that these specific solutions have because it wouldn't make sense to do it, build it in more, because there are especially solutions that can do that and they do it very well. So what we're doing is the basic functionality. This is something we need to explore with the PEG. We need to decide together how far we can get on this. But of course it will be a room for all of these solutions to either to use them instead of the catalog, the client, if the user really needs this specific functionality, or also to be integrated with our learning catalog to augment our functionality. So we see an ecosystem where all these products will continue adding value to workplaces, not that we want to replace them at all. We just want to provide a built-in solution so users can have some capability within workplaces. It's great to see the courses and programs and certifications integrated into catalog. Are there any plans to go beyond that? For example, just resources or a video or a page or I'm kind of getting at kind of basic LXP type functionality? As I said, that's a very good question indeed. I see that they could be added to the catalog but it's too early to say anything about that because we need to decide with partners what to do. And probably we will add all the features first that other than this because this is like a going level farther, which complicates everything that we are. But yeah, I see it as an interesting feature, so we'll see. I cannot say anything about that, sorry. Hello. One of our biggest struggles is that whether we like it or not, our clients like to prioritize style over functionality. And my question is in terms of how easy is it going to be to customize those cards on the catalog on the dashboard? Probably was to, I don't know, with Weston, yeah. That's great. I was expecting all these questions. So it was too small in the screenset but I don't know if you noticed that in our user story map, we had one user persona that was developer. So we took that into account and in the development we're doing everything so you guys can customize it, cards, templates, and everything. So that's the intention. We took that very into account. And that's why we made it very vanilla so you could customize it this way.