When to Shut Down a Mobile Game Project

by tmhr consulting

Share it now!

At tmhr consulting we have been hard at work researching, designing and developing mobile games and apps. It has been hard work and we are just starting to see the results from all this hard work.

We have learned a number of very important lessons along the way but one we are still trying to get better at is knowing when to shut down a project.

lessons learned during mobile game developmentHard Lesson Learned

We just learned another hard lesson from one of the latest mobile games we just published. It is called Tunnel Space Fighter and I can honestly say that this game is in some respects an embarrassment. Now not all of the aspects of this game are bad but it is just not up to our usual standards.

Our Project Mistakes

So where did we go wrong but will not let this happen again?

  1. We let the game project continue longer than it should have.
  2. We believed that the developer was doing a great job and would produce a great game.
  3. We did not insist to continually review game design and progress.
  4. We did not insist to review the game on test flight apps before it was uploaded to iTunes Connect.
  5. We believed that the final version of the game play and obstacles would be much better than the initial versions we reviewed.

So now we have a published game that will need to be pulled – reskinned and redeveloped before it can be published again.

Now how do we plan on making sure this does not happen again?

Our Project Fixes

There are a number of project check points that we have already implemented to prevent another run away but also bad game from being published under our brand.

  1. Insist on continual and frequent updates of the graphic design images.
  2. Providing feedback on the graphic design and insist on the required updates.
  3. Insist on having the game available on test flight apps before it is setup in iTunes Connect.
  4. Provide continuous testing and feed back of the game.
  5. Only use development resources that truly do work as a partner with you instead of just a consultant or employee.
  6. Shut down any project that is not following 1-5.
  7. Shut down any project that does provide a good ‘gut feeling’.

The final decision will also be determined if the project is an internal one or one being done for a client.

Dont Wait Too Long

So the bottom line is that if a project is not providing a good warm and fuzzy feeling and it does not seem right – it is better to stop the project. Review the project and then make the decision as to what needs to be done to either right the project, pass it to another resource or just leave it shut down.

Let us know what has been your experience with ‘bad’ projects and what have done to fix them or not let them happen again.

Come back for our next blog when we talk about a problem we had with a run away design project.

Share it now!

Leave a Comment

Previous post:

Next post: