 Thank you. Better. Okay. Hello. Yeah, I have to do this. Okay Stage career pending Okay, so we talk a lot about openness innovation and opportunity on the web in Missila and and we do care a lot about this And as you guys know work with us for years It has to be like a key part of everything we do. We can't do anything alone We're simply not big or strong enough But the realities of day-to-day life is that when the teams are shipping code and things need to be fixed Sometimes this aspect of openness can seem like it gets more tedious than it gets effective But we can't stop there that can't stop us in creating open code and it can't stop us in working in open ways And so we really wanted to understand how we create a better experience And that's a better experience of people who want to contribute to Missila's mission and the stuff that we do But it's also a better experience for the people who are working at Missila and who want to work in an open way And one of the ways we do this in design in UX world is that we start off by understanding people's needs So there are motivations. Why do they do something because when we understand that we can design better experiences for them So that was the ground kind of idea of this project It's really how do we create a better experience for contributors who want to help with Missila's mission around the world a Really good way of starting to understand people's motivation is to ask them. So we had a lot of interviews 26 in in total that were Between an hour and an hour and a half Across the world some people in this room that we talked to as well We talked to people in person and San Fran in London under an OSFAS But we also talked to a lot of people remotely over Skype and video calls So the people we talked to ranged from a lot of different open source networks We didn't focus just on Missila open source contributors because we wanted to understand how other open source communities doing this What are people getting out of being part of those other open source communities and what can we maybe do better? So we talked to primarily technical Contributors from different projects range of different ages the projects ranged from open source hardware projects such as the V-Volvo project platform, which does bionic arms and robotic arms for people who Anything and then but we also talked to people who were part of like open source hacker spaces across different areas So there was a lot of breath in the in the group of people And I want to say before we go further is that it's not like it was me and Brian and a few others doing this on our own And we worked a lot with the community as we went for it and through conversations and small kind of group intercessions But also through some really big co-creation sessions One in London where we had about 40 participants But also one in Shanghai where we actually had over 70 persistent and the way we did this was we Basically presented the findings and the things that we saw and then we asked the teams and the groups there like what does this mean? What are the things that come out of this and that was a huge part of like building the recommendations that I'm gonna talk to you about today? So what did we find we found a lot about what motivates contributors funnily enough The way that we did these interviews is that we focused on their stories So it was a lot about getting them to tell us stories so that we could understand How they first got involved What was the things that kind of motivated them to get involved? But also telling us stories about when things have been really good like what were the things that were happening when this was really good What were the things that were happening when this is really bad? From a kind of social science perspective, we do that because once we get people to story tell we can normally better hear the tacit motivations as well as the known motivations that they have So the stories ranged From a lot like obviously we got a lot of information out of this But one of the stories that I thought was was really interesting was an 18 year old student who was volunteering for the Xperia Android fork and he had Started at a very very young age But he'd found himself totally immersed in this project and he was now one of the kind of not leads But one of the second in commands in the project and it was a huge part of his status and how he moved forward in his career there's also stories such as a An office assistant who felt that making sure that everyone had access to the internet and understood What was on the internet had kind of driven her to start a local community in her own little local village and Are still driving a huge part of the localization forward from a seller today So very different people very different areas. I'm going to talk a little bit about Some of the motivations that we saw Learning being one of them. I'm going to talk about these on a high level The report is public and I'll see other link afterwards and you can go into detail But each high-level motivation area has kind of forked into these under Kind of lower level of motivations that we saw which are a bit more specific But for today, I'm just going to kind of quickly brush through them. So learning I think is pretty obvious Everyone who's participated in open source knows that the learning curve especially when you start is pretty steep And it continues as you go through the the project and this was definitely the main motivation for a lot of people to To join one of the things that we heard from one of our interviews was it's like having a constant update of what matters Like I know when new things hit. I just know it comes up on our see through chat through other things It's like having this kind of push metaphor. We thought about it internally as like a kind of news feed That was created for you Community it was another one a lot of people were attracted to the community for the unity and for being part of something and A big part of it was taking part in something that was bigger than themselves and also just belonging to a social group That was important for them and there was a real belief in obviously the power of these communities So we heard things like the community is the engine like we can't work without the engine But also how community helps us keep going so this idea that it's your personal blackmail When I say that I'm gonna do something I've promised that to my friends and so I will do it because otherwise You know, I will let them down And it was interesting that even for those who work with a comfort entity within the open source project such as Mozilla or Android or Cyanogen mod This is still a huge factor for them The other one was calls and calls as I put here can be a lot of different things It can be and the cause of doing something better moving something forward changing the life for others But for most people it was this pure concept of just open source the way of working that we do an open source and the way We share knowledge that hopefully we all believe first is innovation in some form and having that as as a key reason for Continuing working on these things were also important fourth and second last is recognition and So a key part of why people really stay is the ongoing recognition that happens and again, this can be Very different as we've talked about here For starters when you're just starting out like something like a sticker or swag can be immensely Important to just show your relationship But once you get a longer term contributors and longer term Relationships it really is about the kind of tacit recognition that happens within the group and within the community as well And a story I thought was interesting here as well is was one of the guys who talked about who was an expert on a really specific fork Of an open source project said that it was quite nice You know when you go to conferences and they introduce you as that guy when you go on stage You know there's something about having that feeling of really being an expert on something That's that's a huge part of this as well and the last one that I once quickly cover is tangible goals So most people are also there because they want to see impacts So whether that is for the junior developer who wants to be able to see their code actually ship in a larger project Or whether it's for the more experienced developer who just want to be able to kind of drive where technology is going Where development and focus is going and also work on new technology and interesting projects So This is not brain science, right? I think if I had talked to any of you guys you could have told me those five things were pretty important for every contributors But what we do in design and what we do when we when we do X is that we really focus on the need and designing those experiences for that need and One of the ways we do that is that today we can't design for every single individual yet I may change that and I may be out of a job But so far that is not where we are and so the way we make sure that we Look at these different motivations is that we cluster them We pull them together in things that look alike and this is complex, right? Like it's not like one person is just inspired by learning and the other person is just inspired by recognition so the way that we try to kind of minimize the complexity in this which is a In social science what we call a little bit of a finger-in-air exercise, but tends to work Is that we took each of the individuals we talked to and on each of the scales of these five motivations We gave them a score from one to ten So what is most important what is least important for them and that helped us build like a profile that we could then actually cluster on Which we did and luckily the clustering exercise led to four distinct Kind of groupings coming out. So these are the four design personas that I want to talk about today I want to talk a little bit also about before going to them what we use design personas for So as I said, we really focus on needs and the motivations when we design these experiences because that's just how things move best for us and Personas are key in this because it allows us to put a face and a person behind things that sometimes are a little bit tangible Now if I just say learning to you and like 10% recognition and 50% something else That's really hard to build for but if I present you with a person that has specific needs and a story It's much easier for us to design experiences for them and that's why we use design personas a lot I'm sure most of you who have seen these from your UX partners in the fields Well, so I'm gonna quickly go through each of these again. They are they are online if you want them and The first cluster we saw was a cluster. We've called the independence the pictures here are fake By the way, because we really want to keep people who pad took in this study Kind of anonymous. So this is just a flicker picture that was on creative comments license So the one thing you saw in this cluster of people we'd interviewed was that they were all quite young They had the obviously common characteristic of being high in recognition and tangible goal as many motivations But they were all very young in their career and they're often focused on a really specific output, right? This is the tangible outcome for them. They're there because Things we heard was like my teacher had said you need to be part of deaf communities and this young female had no idea What that meant and so she googled that communities and open source came up and hence she got involved and has now been like a contributor for five years So sometimes it's it's fairly random kind of ways that they get into it but mainly it's so that they can build up their skills their networking and Get things that they can put on their CV and show and move their careers forward with however, they stay in open source because they get Enticed by the community and they get enticed by that recognition and status that they can get when they actually successfully ship something and get it put into code The second group we saw was we called the leaders The reason we called them the leaders is that they all had the same characteristic that they had been contributors for a longer period of time So it's not exactly a fancy name for them But they obviously were quite on the other end of motivation spectrum So they scored fairly high in recognition fairly high in calls, but really what matters to these people is the community That's what's keeping them there. That's what's keeping them really engaged This is also where we heard the the community is my personal black male comment And heard things like you know for one of the Mozilla contributors we talked to They said that there's you know this great feeling about being able to say I am the expert of Mozilla in my country that is like me as the go-to person The third and second last group that I want to talk about is we called the fixers We called them the fixers because there was this great quote from from one of the guys I was in this that said that you know, I have a fixer mentality I just want to fix things if they're broken. I can't leave them broken and they are Scoring really high on kind of tangible outcomes, which is obvious from this quote But also learning and so they are really there because they have a specific problem They often join because they have an own project they're working on or they want to work on a project That's relevant to one of their own things and open source is a way for them to get that done quicker with more people or collaborate on that problem But they stay because this is really an ongoing source of learning for them They feel like they can keep like up in the pulse is that I don't know how you say that But they can keep up to date and they can learn new things and this is like their continuous learning development program for them So lastly is the citizens and we actually call them the activists to start with I don't know quite why we changed the citizens But but we did sounded better. Maybe They are really high in cause and communities Again, they span ages. We can't say anything specific about age groups They were most of them all professional and they are really there because they care about the cause And this is like whether it's open source or a literacy or whatever it can be that they're working on some of the people We talked to from the revolver community really cared about, you know Enabling people with disabilities to move to work to engage and hence they spend a lot of their free times building and open source Bionic arms But most of what we heard from these people is that it's not about getting paid or necessarily Just being able to do this full-time. It's the satisfaction I get from contributing my time and my knowledge and seeing this area move forward All right, so in the last five minutes I want to talk a little bit about what this means because Having designed personas is great But like how do we move from there to the actual experience that we want to build and this is an ongoing journey for us at Missile We're by no means done and this project is still happening But one of the first things we did is that we sat down with the community and we sat down with the internal people Some of the internal people we're not done with this process either Who work with volunteers and we talked about what does this mean for you? Like what are the things that you do different knowing this that we can do different knowing this internally in Missile So this is very Missile-focused so apologize for this, but I think that there are some general trends that pretty much every open source Community can can utilize So one of the recommendations that came out was this idea of showcasing the value exchange I'm used a very businessy word in you value proposition But the reason that we've used that is because it's super important One of the key things that we saw when we talked to people is that in the beginning of their engagement with Any of the open source communities? They didn't really understand the benefits to the full extent that they do when they're involved So when they start they maybe think okay, this is great I can do some code I can learn some code and once they've been involved longer the benefits are so much more than that It's the community. It's the network It's all of these more tacit benefits that you can't really put your your finger on It's ensuring that we're better at communicating those up front when people start We also help them overcome some of that hurdle of getting involved first time Which we all know can be can be hard if you don't necessarily know anyone in the community Reinforcing infrequent communication on how to get involved. This is the big hurdle of how to get involved Now this workshop was done with some of the people from our open design community as well And so there's a lot around like how can we also visualize this like can we use visualization as an aid for this? So this is some of the things that we're working on now to try and figure out how we do So we wanted to communicate and visualize an onboarding process that gives them a sense of where they are in the process This is obviously a really hard problem, but one that we're really committed to working on We also want to visualize Missila and what we're about that's everything from like the projects We're working on and to the things we're doing some of the projects that are tapping into this It's like the pulse project if you haven't heard it. You should check it out. I'm still a pulse school search We'll probably get you there Where some of our foundation people have built the site that basically pulls out all the small projects that are happening across Missila and gives people a better an idea of what can I like contribute to what can I work on? the last thing we thought about doing which is Work in progress was creating a content and contact map of Missila So this is kind of the idea of creating a heat map across to see where people are that you can get in contact with from the different projects Third recommendation show how you can make a different for the mission And this is basically focused a lot obviously on the kind of citizen group that we talked about But this idea of highlighting that Missila is obviously about the open web But we do a lot of other things like web literacy Like to work on them projects to connect with women In India and all these other things that are kind of happening with our community and around our community We also wanted to do a we have the Kind of get started bug list We wanted to do something similar for people who are more interested in the cause right? So what are the easy things that people can get involved with and kind of start off straight away? We also talked about building a culture of positive recognition I think this is pretty obvious for anyone who's an open source So I'll kind of let you read it, but this idea that recognition is really important for us We also think that connecting to the communities early is really important now at Missila This is a something that the community themselves manages And if you don't get through the right place or you're not contacted through the 100% right person This can be a little bit of a thing where people fold through the cracks But we know that once you have that personal connection once you have feel like you're part of that community That's really what makes you stay and that's really what makes you feel like this is a worthwhile use of your time Lastly and this is for the more kind of experienced contributors We wanted to foster co-ownership and what we mean by co-ownership is that Things go bad and things go well and obviously as Brian said, you know This has been a turbulent year from Missila, but it's important not to be like this is all good and we're all happy It's important to own this both good and bad days together and giving people that co-ownership and Pulling them into both the hard times and the good times is really what makes us a joint community And hence we also need to be more transparent in the way that we're working And that's ongoing work both from the leadership side, but also from us working with volunteers on the ground So you can kind of look at these recommendations There are many more in the document that's online, but I've tried to kind of look at how we're looking at these as we think About how people engage with us across their experience with Missila and where we're focusing in so as I said It's online. It's it's open-source If you want to go have a look how we clustered how we did this you can do this here. It's 250 pages. Good luck But you know if you really interested so next steps that this work continues so this is a Project we started last year as I said, but we've actually partnered now with Howard University Who's really interested in understanding more about open source as well and therefore like looking further into this So we're still looking for people to interview we're looking for existing contributors for all open source communities We're looking for people who've left we're looking for people who maybe have thought about it But aren't really convinced. We're also doing a survey. You'll see some posters around here And again, this is run by Howard, but we would love if you could take part of it And we also just want your feedback anything that you have questions input. We'd love to hear Malika is from Howard and I'm our Jensen if you have any questions or comments That is where to go sorry She is not she has a newborn baby and so she's stuck, but she's hearing You take some questions Okay, so really probably the best be the best timekeeper of all the speakers all day So we have loads of time for questions. Let's take five minutes. So I will ask two things We only got one working Mike unfortunately, so ask your question really loud I mean, I would ask you to repeat the question on the mic. Please. Thank you So this is not a quaint project. This is what we call a qualitative project. So having us that decision look at 26 Sorry repeat the question Jesus it's right now He asked have we had a statistician look at this both from the point of view of the methodology and from how we recruited the Participants and so this is not a quaint project It's a core project. And so it's a different way of gathering information What we're trying to do with Howard is to add that quantitative part into it And that's part of what we're trying to do with the survey And so the way that we look at this in social science is that these are ways for you to gather information You can't quite can help you understand how and what but it will never help you understand why So we're using this to understand the why and then we're using the quants to go back and look at the how and can this actually be Replicated on large scale. Can we see this back in a survey? And that's how we're doing that. Yes So the survey and everything that we've sorry Thank you Jesus He asked if we had tools that other people can use in other open source Projects to kind of replicate and these surveys and using their own projects. So everything's online If you email Malika, she can tell you where it is. It's on Howard website tomorrow that I actually can't remember on my Kind of feet right now, but if you go there, she will talk to you about the if you email I shall talk to you about the methods she's using She can talk a little bit more about how she's looking into this from a statistician point of view as well And she will give you the survey and and the background everything to use in your own projects as well So the question was if this was a particular Missilla project or general open source communities So the first round of interviews that we did was definitely Hierated on Missilla because it was a Missilla question. The partnership that we've started now with Howard is general open source So that's why Malika is still looking for interviews and it's gonna do more of these as well Yeah So the question was if we've looked into the negative blog posts around add-ons to understand more about how the community is Feeling right now and the answer to that is that Malika is also running some Like basic content scraping to understand sentiment analysis online. So we'll probably appear in that But again, I would reach out to her to understand more about how she's doing that. I couldn't Let me see if I got that right It reminded you of a project that I didn't know about and did you ask what inspired us to get involved or So we did in the beginning of this speech out to quite a few different open source communities because we wanted to talk to people from different areas The feedback we got from the ones we talked to was that they weren't doing anything But I should also say we haven't reached out by any means to all of them And that is probably something that we should consider but we haven't done that The slide with the The URL