Gamasutra: The Art & Business of Making Gamesspacer
View All     RSS
November 1, 2014
arrowPress Releases
November 1, 2014
PR Newswire
View All
View All     Submit Event

If you enjoy reading this site, you might also want to check out these UBM Tech sites:

Escaping the Indie Shame Spiral
by Ethan Levy on 03/20/14 01:27:00 pm   Expert Blogs   Featured Blogs

The following blog post, unless otherwise noted, was written by a member of Gamasutra’s community.
The thoughts and opinions expressed are those of the writer and not Gamasutra or its parent company.


On the second day of GDC, I presented Escaping the Indie Shame Spiral as part of the Indie Soapbox session at the IGS. I wanted to expand on the information I presented it in the talk and share it beyond those developers who could afford to attend GDC.

Defining the Indie Shame Spiral

When I left EA after a 4 year stint at the company I had two goals. One was to found a start-up and the other to finally build and release some of the art game concepts I had been mentally developing for years. The start-up goal was realized, but after a year and half we shuttered our doors after failing to secure funding via the venture ecosystem or Kickstarter. My indie game aspirations quickly fell by the wayside as opportunities to consult presented themselves. I have been lucky enough to build a business as a monetization design consultant and my initial savings have been largely untouched thanks to freelance work over the past two years. I have contributed to a lot of games and have traveled the world to speak at conferences on the topic of F2P design. Yet the longer I go without filling my dream of completing one of my art games, the more regret I feel.

When the start-up failed, I began pouring my time and energy into indie game development. I started working on a game called Some Day You Will Die, a narrative mediation on the inevitability of death. Although initially filled with passion, verve and a deep sense of purpose, I began falling into what I call the indie shame spiral. As I talked to other independent developer friends I learned that my situation was unsurprisingly common among solo game developers.

Each Monday I would wake up and excitedly make a list of all the things I wanted to accomplish that day. This included development on Some Day You Will Die, freelance work, work on a match-3 game I was developing with a former colleague and chores like shopping for groceries, running and calling Mom. By the end of the week, I would look at my list and despair. I was lucky if I accomplished half my Monday goals. Not only that, the tasks I did complete after making rent always seemed to be the least critical.

Despair over lack of progress drained my motivation. Flagging motivation resulted in even less momentum on my game. Creating more despair. Draining more motivation.

I was getting less and less done and feeling worse and worse about it. I wanted to abandon my game and start prototyping that shiny, new art game concept I felt genuinely excited about. I was trapped in the indie shame spiral.

Escaping the spiral

Thanks to my background as a game producer, I had some tools to help me get my project momentum back on track. The critical first step to escaping the shame spiral was to start running a personal scrum as though I was leading a team back at EA. I fired up Pivotal Tracker and started populating my backlog (alternatively I could have used Trello or a Google Spreadsheet). I like Pivotal because it is an opinionated piece of software; using it forces me to embrace points instead of hours, and the product tracks my momentum and gives me an honest estimate of what I can accomplish in a one week sprint.

Pivotal only allows 1, 2 or 3 point tasks. I decided that a 1 point task was anything I could do with 1-2 hours of concentrated work. 2 points was for 1-2 day tasks and 3 points was for anything that would take half a week (or a lot of effort in short bursts over a long period of time). Any task that would take longer was broken down into component tasks that fit my point system. Chores were critical tasks I had to do that would take 15 minutes or so, such as answering key emails, paying bills or sending and checking up on client invoices. I did not allow my backlog to fill with more than 3 sprints worth of work; backlogs get stale quickly and anything further out was unlikely to stay relevant.

Since I was running a one person scrum, I tracked important personal tasks as well. I created chores for morning meditation and assigned points to incentivize easily skipped personal tasks like running and weekly allergy shots. I used labels to separate personal, freelance and development tasks to ensure I was not artificially boosting my momentum by working on myself while neglecting my games.

Critical to running successful sprints was ending each sprint with an unflinching post mortem. It is necessary to call out bad behavior, review previous areas for improvement to see if I was in fact getting better and detailing new areas for improvement based on recent failures. After cathartic self-flagellation over my transgressions (and celebration of my accomplishments) I would refresh the backlog, set my new priorities and start a fresh sprint with a clean slate.

I quickly learned how much work I could actually get done in a regular week. Unsurprisingly it was significantly less than my previous Monday morning productivity fantasies. Running personal sprints forced me to accept my limitations. With that acknowledgement the despair began to subside. I was no longer haunted by the demons of unattainable perfection.

Commitment devices

The second critical step to clawing my way out of the indie shame spiral was to use a commitment device. A commitment device is “a means with which to lock yourself into a course of action that you might not otherwise choose but that produces a desired result.” For me, this meant buying a table to showcase Some Day You Will Die at the Good Game Club event in San Francisco even thought I did not have a playable build of my game at the time I wrote the check. The event forced me to curb my procrastination and get things done.

By running a scrum and having a clear, hard deadline to show off my game, I started making true progress. I was coding right up to the last minute before the doors opened on the event, but when they did I had a playable demo that allowed me to collect real feedback from real players.

We are lucky to develop in a time where there are plentiful commitment devices available. Submissions to IGF, IndieCade or PAX showcases, Ludum Dare and game jams, local meet ups and demo nights with other developers in your area can all create milestones to drive towards. You can set up a devblog on TIGforums and commit to updating with a demo once a week or set up a newsletter and commit to sending out a playable demo once a month. Every week you have the opportunity to share your game and get feedback from other developers in the r/gamedev Feedback Friday post on Reddit. There are plenty of possible deadlines to commit to either publicly or privately to force yourself to escape the indie shame spiral and make real progress on your game.

My commitment

When I started the talk, I asked the packed room of game developers how many had 5 or more prototypes, demos, design documents or half-finished games on their hard drives. I was met with a sea of hands. My call to action to the Indie Games Summit, and to you if the concept of the indie shame spiral sounds familiar, is to choose a commitment device and show off your game. I am personally deep in the shame spiral – for weeks I let my process fall by the wayside and have been completely focused on freelancing and a match 3 game. I haven’t opened Game Maker even just to fix bugs in the Some Day You Will Die code for too too long. My pledge at the summit was that on March 28th I will show off my game on r/gamedev’s Feedback Friday. It won’t be pretty and it won’t be complete, it might not even be any good. But it will be playable and I will have to make true progress to get there. I hope to see your game on the thread too, so that I can give you feedback and congratulate you on making progress towards completing your game.

Related Jobs

Forio — San Francisco, California, United States

Project Manager / Producer (Games)
Infinity Ward / Activision
Infinity Ward / Activision — Woodland Hills, California, United States

Senior Sound Designer - Infinity Ward
Treyarch / Activision
Treyarch / Activision — Santa Monica, California, United States

Multiplayer Level Designer - Treyarch
Petroglyph Games
Petroglyph Games — Las Vegas, Nevada, United States



Jon Day
profile image
Excellent post. Might have to give all this a try, sounds like what I need to do. And maybe I'll join you on reddit next Friday, who knows.

this comment is sounding quite relevant to the post..."might, maybe, who knows" yeah I need use a task tracker like pivotal or trello or whatever and make some commitments

Ethan Levy
profile image
Thanks, Jon. Glad you enjoyed the post and I hope it helps you commit to your game.

Curtiss Murphy
profile image
After starting Gigi Games, I quickly fell into the shame spiral. Until one day, my wife tapped my shoulder and said, honey, "You need to release something. Build something in 6 weeks and get it on iOS, no matter how simple!' It seemed impossible, so I countered, "8 weeks!" and in the end, it took 9.

Since then, I've released 4 more products that have reached 180,000 users. The modest income and massive 1300 reviews keeps me going - I'll release another this week, and have major progress on a 7th. All Indie's should take the "12-week challenge" (link below), whether professional or hobbiest. My wife made me do it, and as usual, she knew best.

The 12-week Challenge:

Charles Zapata
profile image
Great post. I've just stared my own indie studio, and though I've only been in the indie dev world a short time I can understand what you are going through. I'm using the same sort of commitment devices as well.

I can also speak to the specific challenge of working solo. I have previously co-founded a VC backed startup with two other founders, and I can definitely say there were days where it helped to have other people their cheering you on and helping pick you on days when you don't feel fully committed to the cause. Finding someone equally committed to your game to help out in some capacity, no matter how small, may yield significant returns (it's one of the many reasons I'm bringing on a cofounder.)

Charles Zapata
profile image
[pick you on] == [pick you up on]

Bhasker Hariharan
profile image
@Ethan : Loved this talk at GDC. Enjoyed your presentation.

Ethan Levy
profile image
Thank you. I'm just glad the crowd laughed and didn't throw any tomatoes at me.

David Abraham
profile image
Thanks for this post, I've been going through a similar funk. Actually, I am working on a match-3 puzzle RPG at the moment (surprise), but the game I *really* want to work on, and have been working on for a couple of years now, is in a state of disrepair and has been on hiatus for some time.

I've committed myself to finishing the puzzle-RPG, releasing it on the Apple Store, and then returning to work on my "main" game. However, I have not yet set a concrete deadline. Progress has been slower than expected and I often lose motivation and go on video-game-playing binges.

I used Trello for a couple of weeks, making task lists and setting dates. I then proceeded to ignore my Trello page completely, having been bummed out that very few of these tasks were completed on time. Maybe I will try Pivotal and make more of an effort to keep up using it.

I don't have these problems at work, where I have set hours and I have set deadlines when the games have to be completed by. Definitely what I need is a "commitment device" of some sort. I'll look into local events I can show the game at, or perhaps try one of these 12-week challenges or something of the sort.

Tarcisio Rezende
profile image
Great article, hope to get out of my spiral of shame , thanks for the tips!

Craig Timpany
profile image
I find it hard to stick to a schedule of work days and leisure days when working solo. I found it really helpful to mark whenever I'm taking a rest day on a calendar. This is a useful reminder of when I've inadvertently starved myself of relaxation. The worst thing you can do is get stressed about being behind schedule and try to work every single day. After a while you end up spending days that are neither productive nor refreshing. Frequent periods of slacking off and web surfing aren't nearly as good as giving yourself a proper day off. Go outdoors now and then!

Bug trackers and task trackers are by their nature depressing (but necessary!). Pivotal encourages you to measure your work in terms of user-visible features and initial estimates, which is excellent for scheduling, but it's a poor indicator of how much effort you're putting in from day to day. I wrote myself a script that turns my commit log into iCal entries in the same calendar as above, so I have an overview of when I'm productive. It's good for when you find yourself thinking, "Man, what have I even gotten done this month?"

Luis Blondet
profile image
Thank you for this article. I'm personally spiraling back up slowly after years of descent into desperation.

Ethan Levy
profile image
You are welcome. Keep on climbing upwards and onwards!

andreas grontved
profile image
I have around 40 prototypes. And i've been so sad about, but i've come to realize that they are just part of our individual path to something that makes more sense.
Also it can be quite depressing that "everyone" around you has profound ideas and seems to have plenty of time to produce them.

Christopher Totten
profile image
Thanks for this great article. I'm running a Kickstarter right now and while I'm normally able to keep myself pretty upbeat about game dev, it's starting to take its toll :-(

Ethan Levy
profile image
Thanks much, glad it is helpful. Keeping spirits up during a Kickstarter could be it's whole separate article! Best of luck with your campaign.

Tom Kail
profile image
Absolutely spot on. Something I've found massively helpful in my case is working as a pair. As soon as one person beings to fall victim to the spiral, it's the other person's job to pull them out. Oftentimes simply having a second perspective that directly relates to your experience is enough.

Ethan Levy
profile image
Definitely. Having a partner (on other projects) has made things easier for sure. Although 2 man development also has its host of challenges.

Caio Marchi
profile image
So precise that I felt it need to be spread. So I translated it to Portuguese. Thanks for posting.