You just introduced a phrase I don't think we've shared with the community before, "user story". Can you give a vague example of what a user story would be?

And this, I think, is actually something really simple that a lot of people kind of overlook, but there's some real power in it. So a user story is kind of a building block of Scrum. Everybody knows these things. Essentially, it's a way of describing what you want to do. So an example of this would be, for the character customizer: as a user, I want a character customizer so I can customize my character in the Persistent Universe. That would be a big user story. And basically what that means is, as a user, so as a player, I'm speaking as a player, I want this feature so I get this benefit. Versus saying "character customizer" and having it as a task. Now, a character customizer task makes a lot of sense to people who are on the design side, but it doesn't necessarily make sense to everyone who has to touch it. It kind of goes back to part of why we love production, because we get to interface with so many people. So if we have a user story, "as a user, I want a character customizer so I can customize my character", it seems like you're overstating things, like, why are you doing that? But imagine this. As we start working on that user story, we start breaking it down into smaller stories. So imagine if you said, "as a Star Marine player, I want my character customizer in Star Marine so it matches my PU character." That makes a whole lot of sense, right? But if we were going to write that as a task, it would be like "transfer PU character customizer to Star Marine", right? That could be how the task was written. That doesn't tell you the intent or what the player wants to get out of it in the end. And when we come into the office and we're doing all this work, it's not just to get tasks done. Nobody on the stream, nobody playing the game says, oh yeah, they're working on even more tasks than last month. No, it's about the objectives we can deliver. So by writing a user story, you make sure that everyone working on it sees what the objective is, and we're all working towards that goal. We're doing that whole user story about Star Marine so that people's PU character matches their Star Marine character. So whenever it's in QA or it's in art or in any of the disciplines that it's in, we all know the goal, and we're working towards the same goal. So that's why you would write a user story. You also write it to annoy Chris, because he doesn't always love them as much, but he's coming around, I feel.

And just to confirm, folks, he was using the character customizer in Star Marine as an example. This is not him sitting here confirming that we're bringing that to Star Marine.

Not confirmed. I'm using that as an example.