In my last post, I talked about critical mechanics and how to use them to prioritize work. In this post I want to talk about an easy way to turn a critical mechanic into a task list using a very simple concept: the use case.
One of the hardest aspects of managing game development is prioritization. And nowhere is prioritization more difficult than in the earliest days of a project. If you don’t know what your game is, how the hell are you supposed to prioritize the work? I’ve struggled with this problem in the past and eventually ended up stealing a solution from the start-up world in the form of something I like to call “critical mechanics.”
One of my favorite quotes revolves around planning. It came from Helmuth Von Moltke, a 19th century German Field Marshall: “No plan survives first contact with the enemy.”1. The implication here is simple enough: the plan that makes total sense on paper quickly falls apart when confronting the entropy of reality. And yet planning is essential for getting a team moving in the right direction. As Dwight Eisenhower said, “I have found that plans are useless but planning is everything.” And thus we arrive at what I like to call the paradox of planning: planning is the act of creating something that is simultaneously infinitely valuable and completely worthless.
Here’s a question for you: is dog-fighting (the airplane variety, not the literal kind) an art or a science? It’s obviously an art, right? Two pilots, and a wide-open sky – the possibilities for maneuvers and counters are positively endless. Endless, that is, except for this funny thing called “physics”. Far from being limitless, a pilot’s options are severely restricted by his altitude, speed, weapon load, and aerodynamic characteristics. The man the world has to thank for codifying this realization is one of history’s great iconoclasts: United States Air Force pilot John Boyd. But Boyd’s gifts to the universe were not limited to the military, and one of his last major labors before he died was a paper and presentation he called “Analysis and Synthesis” or, alternatively, “Destruction and Creation.”
This post is about an empirical issue: the economic cost of being an auteur. When I originally posted this entry on Gamasutra back in 2014 it was not without its detractors. David Jaffe even dropped a line on it, saying he thought it was neat, while simultaneously implying that I was full of shit. Nonetheless, in retrospect, I still feel this idea is worth considering in an industry like ours, one that consists of both public personas and massive-team-based endeavors.
Marketing has the same basic premise as football, judo, and hacking: find the opening and exploit it. In terms of your competition, the opening is known in marketing as the “white space”: the area of the canvas without any color. How does one identify the white space? With a simple exercise called, appropriately enough, a white space analysis.
Sunk-Costs and Ugly Babies: On The Value of The Scientific Method – Game Planning With Science! Part 8
It struck me one day that “Game Planing With Science” has a glaring omission: the value of scrapping a plan. The goal of “Game Planning With Science” is to forecast, not predict. It’s to estimate and understand, but not to codify. You can’t codify the creative process, or the future for that matter. Just as important is the fact that life doesn’t care about your plans. Reality is going to be what it’s going to be. You can’t change reality to fit your plan, so modifying your plan to fit reality is the only path forward. As Dwight Eisenhower, one of the most immensely quotable people ever, once said, “Plans are useless, but planning is everything.”
This post about five forces analysis originally appeared on my old blog and Gamasutra. I find that it’s as relevant today as it was then. Mobile is still a hot bed of both independent and publisher-backed development. And for good reason. There is a massive addressable market and mobile devices have high user engagement. Mobile also supports smaller test launches and rapid iteration, meaning that developers and publishers can treat mobile games less like products and more like businesses. Add to that the lack of any marginal production or distribution costs, and you have a super-sexy platform. And that’s exactly the problem. Mobile is so attractive and so accessible that the market place is perhaps the purest example of “perfect competition”, the yin to a monopoly’s yang.
This post is a bit of a capstone. It utilizes all of the tools to make video games scientifically that I covered in the Parts 1-6 of “Game Planning With Science”. Make sure you’ve reviewed those weighty tomes before digging in here. In this post, I’m going to walk you through how to utilize capacity charts, story points, user stories, variance, and the central limit theorem to forecast development time lines.
There’s a saying in data science: Garbage In, Garbage Out (or GIGO, if you prefer). The most advanced formulas and models won’t provide outputs worth a dead cat if you don’t have high quality inputs. When it comes to something as difficult and uncertain as feature planning and estimation, that’s quadruply so. In this post I’m going to walk you through the system I’ve used successfully, how it works, and why. And it’s all based on the counter part to the story points from Part 5, user stories.