All right, so now we get to make mockups kind of, okay? And before we actually start doing the kind of wire framing and those types of things, we need to get a kind of a features list. Okay? What are we gonna include in this new app, this new website, this extra feature? Okay? You might have a core nugget of an idea, but you need the kind of supporting stuff as well.
What other features does it need to have to make it work? Okay? And this is where you do it again as a group team. Okay? So you want to make sure everybody's on board and, and kind of singing from the, um, same song sheet. Now, um, first thing to do is make sure, say you've done, you could do this in one big group.
You could do your personas and then afterwards, maybe after a lunch break, um, come back and do the features list just as a bit of a time so you can kind of adjust the, um, the persona, or you could do it the following week or something like this. So get everybody back together. And then it's just a matter of making sure they've read the personas so they really understand, you know, who the features are for. And then come back and get your post-it notes again. Yay. We'll get to do more post-it notes, okay?
And just get people to yell out features. Okay? Say we are using my, my, my website as an example. Okay? So it's an online training site and delivering videos. Um, you know, and you start at the ball rolling.
It might be, it needs a forum. You write that down, stick it to your wall. Okay? Somebody else might say it needs, uh, you know, a live chat for the trainer. Great. Add that to it.
It needs a pause button and a play button. Okay? It needs, um, it needs some sort of maybe bookmarking or adding notes. And you kind of just get the ball rolling with everybody. And no feature is, you know, bad. Just add them all on there, stick 'em to the wall.
And once you've got a kind of a, um, a group together, uh, you know, a bunch of them together where you've exhausted your features list, you might have hundreds. Okay? You might have 10. There might be, you know, it might be, you know, there might be loads. It might be only a little bit. So group them all together and, and any features that are kind of very similar, you know, stick together on your whiteboard, okay?
Put them overlapping and say that that's kind of the same thing. So cut it down, then remove anything that I like, essential, and for my mind's a video training site. So there's no point talking about the value of having a video on the page. It's the most important. Yes. And that's always gonna win, but it's essential.
And for me, um, mine's a paid subscription site. Okay? So some sort of login is a feature, yes, but can we exist without it? No, the, the, this doesn't exist without some sort of logging in thing for students. Okay? So I remove that off there, get it down to the, um, you know, the kind of the supporting features rather than the core stuff.
Anything that's a bit iffy leave in there. Okay? And you think, oh, maybe we could be without this. Maybe that's arguable, leave it in there. Okay? Then, um, then you need to prioritize.
Okay? You might have a big list. And then what do you work on? Because the developer might be thinking, it definitely needs this thing. Okay? It needs the forum.
'cause that's what his experience, life experience. That's what's gonna be really good for this thing. And the CEO though might be thinking, you know, the whole reason for this thing is to have, you know, I don't want this interaction with students. I want it to be kind of like a, a a zombie website where it goes off and looks after itself. He doesn't want a big support team and people running it. So you gotta get, you know, get all these ideas and then you gotta prioritize them.
Okay? So the way to prioritize 'em, there's a couple of ways, easy ways. You just sit around and do it together, okay? Um, and you, maybe there's the monopoly money way where you all sit down and you buy features, okay? So you go through all the feature lists and try and cut it down to a reasonable amount. If there's some really weird stuff, okay, you might remove it off, okay?
But get it down to maybe 10 or 20. And then you can do stuff, give everybody some monopoly money, and you get them to, you pull up one boost of note, you stick it there and you say, all right, how much people gonna spend on this? Um, you know, what, how, how, how much value do they think it has? And they might get given, you know, a thousand, um, fake dollars. If you don't have monopoly money, you can use anything. You might be trading pens or coins or whatever's lining around the office, okay?
And it, it, it, it makes people a sign value. And in saying that, it makes 'em take a value away from something else. 'cause you can't say that is the top, that is also the top, which people do. They have to be both the top. They can't be, you have to start somewhere. You have to do something.
So you need some sort of ordering. So then you might say, you know, pop a feature and for me it might be the forum. So I think that's really valuable. I might cough up 500 bucks for that one, knowing they've only got 500 to, uh, you know, to go around the other ones and it kind of, you can just pile the money on top and then count it at the end. Okay? Then you've got a priority list.
You start at whoever got the most money and work your way back through that list. And because you've all done it together, it's a really nice way of doing because it means that the developer who had a different idea from that CEO doesn't go, well, my idea's better. Why isn't he doing it? Because they've had that chat. By putting the money down, conversations start happening and you start working out priorities and everybody starts getting on the same page. You might disagree, but, um, it doesn't matter because you've, you've kind of been part of why, you know, you understand the reasoning why these people have gone this way and it might help things like, you know, 'cause often a new idea.
It's the idea for these are kinda locked in people's heads, especially the kind of, um, you know, the owner or the, the people, people initiating the, the, the project. They might have it in there and know what they wanna do, but the other people dunno. Okay? So it kind of e lists all that sort of conversation. So that's one way of doing buying money. It's one way.
Um, problem with that way is in which you can get round is kinda more like a poker version of that exact same thing. Give everybody the money. And what you do is you put the feature out and everybody has to put down at the same time. Okay? 'cause what happens is you get a bit of a boss bias where, um, you know, uh, say there's five of you round the table, the CEO and his employees. What happens is when you do that first example with Monopoly money is that whatever the boss does, everyone kind of like follows along, you know?
And you're like, oh, okay, yeah, me too. You know, just to make sure, just keep everybody happy, okay? Um, whereas if you do more of a poker one where everyone has to kind of be, you tune into a poke, like a poker kind of style thing and you try and make a game outta it. 'cause you don't want people to be caught out or feel bad is it's literally 1, 2, 3 and you put your money down and then you kind of look around. 'cause then there's no boss bias. You know, everyone's just put down what they think rather than kind of just like going around in a circle and just seeing what the boss put down and just kind of covering him.
Okay? So that's kind of a nice way of doing it. Nice and easy. What I find the, um, the the most useful for me when I'm working, I deal with a lot of startups and kind of one man band type things when we're doing UX or a lot of my projects. Okay. Um, is, uh, peer wise comparisons, we'll do that.
I find that's probably out of all of them my favorite that I've ever run. It works the easiest. Um, yeah, it's less gamey than the, the poker stuff. So, and you can do it by yourself as well. It's really handy. Um, so let's do that in a whole new video and we'll show you how to do that as a group.