One Step to the Epiphany

Meeple-Development

The Player Development Cycle?

During a quarterly goals check-in with Andrea, I talked over the status of several Flightless projects, and she asked a question I didn’t have a ready answer for. “Who exactly are your customers for each of these?”

I had a vague idea who I was designing for in each case, but no clue on specifics. “Erm, gamers who like… games… about… things?” Basically some bullshit that would never fly in the startup world where I spend my days and earn my living. Yet somehow I had failed to apply that same type of rigor before spending time developing and iterating on game designs.

Andrea went on to talk out how this could be a valuable tool for deciding who to reach out to about projects, what to include when writing about them, and making sure that my designs were scratching my prospective players gaming itches, so to speak. She, too, was flabbergasted that this had never occurred to either of us in any of our previous goal sit-downs. She said she felt like she’d had ‘an epiphany’. So that became the joke. I added “Andrea’s Epiphany” to my to-do list, which when I later broke out into “develop steps for Andrea’s Epiphany”, made that record-scratch noise in my head. The canonical work on this exact piece of building a business is literally called “The Four Steps to the Epiphany“. I revisited this notion (more specifically via the work’s more-digestible little brother: “The Entrepreneur’s Guide to Customer Development“) and am working to design a model of customer development for tabletop games (…and maybe more).

I’m not ready to show it yet, as I want to run through several cycles of experimentation and revision before releasing, but if you’re interested in this concept applied to tabletop gaming, please email me at woodardj@gmail; we can talk over your experiences, and I’ll share the early phases of my research with you.