Skip navigation

Brainstorming: Structuring the RHoK-GWoB relationship for fun and profit

This Group is archived. You may not add or alter any of its content.

Brainstorming: Structuring the RHoK-GWoB relationship for fun and profit

On today's call, I heard a few ideas about how to improve our process. I think I have an idea that could address a lot of our concerns. Please comment and help me see whether there's anything to it?

I heard that we would like to consider several things: champions for each application, business model descriptions, mentoring teams up for a second try at funding later, one-page profiles of the applicants, pre-application interviews, separating team from concept rankings, make better use of teams who contribute multiple times, and trying to push a presumption of project durability rather than transience.

So what if we made a literal game of it? As I understand, there exist game mechanics engines which will reward people for doing the things that need to be done to accomplish a goal. What if we laid out a very detailed map of how to grow an idea into a company, and used the RHoK weekends to attract players? Done well, we could coerce the scoring system to any conclusions that we choose and therefore the framework could support any process that we determined was meaningful.

We would be something like a game publishing house that manages lots of little studios and helps their work to get into the hands of users. Then each project would be like a game title, worked on over time by a series of people. Their performance ratings could come from daily contribution, RHoK participation, forum posts and responses, etc. Each project would then have a staff role of champion, so that continuity could be maintained as the people rotate through. Then, from among the list of participants who connect to a project, the one with the highest ranking or score in the Project Contribution Game would be offered the lead role. The champion would mentor the lead until the lead is ready to submit for funding assistance; a threshold that would be embodied in the Project Maturity Game.

Anyway, that's the meat of the meta idea.

PS: One of the projects that comes to mind is the Project Game Project.

Comment viewing options
Select your preferred way to display the comments and click "Save settings" to activate your changes.


Riley, I really like this idea - it's something that came up during GameSave. RoarEngine would be an easy game mechanic engine to plug into the backend to make all the other parts work well, and they're already big propoents of the stuff we do.

We'd have to worry about the front end - what does it look like? Do we know people who can make the pretty parts plug into the functional parts?


I would also open the system for education credits. Learning programming at universities usually involves solving little and isolated problems. That is not what you do in real life later. You often contribute to an existing codebase & have to collaborate in a team. If people contribute a significant amount of work to a software project, they could get credit for it in (university) education (thanks to the bologna process at least in europe). If RHoK/GWOB just spits out some sort of certificate (indicating the contribution and workload), it could help catching coding talent which is not interested in starting a company (now). They could get credit for their work and skip courses. No fancy front end needed, just a (pdf) template.

Need help?


The blog lets your team communicate by posting updates and discussing issues. It is a great place for sharing progress, discussing challenges, and exploring ideas.