Breaking The Wheel

A screen grab from one of Justin's GDC17 sessions

GDC17 Feedback and Responses

GDC 2017 was my first GDC ever. So, I figured “Why not be an asshole about it?” and signed up to give two presentations. 6’ish months later I found myself at GDC, sweating bullets and shitting bricks. I should also mention that the longest presentation I’d ever given was about 10 minutes, and had signed up for a total of 90 minutes of speaking time. Anyhoo, both presentations went well and nobody died. And then, a month and half’ish later, my compiled speaker feedback arrived. It was largely positive. But, of course, there were a few people (4 in each session, based on the reviews) who took umbrage with ol’ Justy. And some of the negative comments bothered me. Not because people disagreed with me (that’s to be expected, after all) but because I couldn’t respond. But then I realized that not only could I respond (having a blog and[…]

Read More »
A picture of a bottleneck, because auteurs bottleneck stuff

Bottlenecks and Hindsight: Why Auteurs Make Horrible Economists

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.

Read More »
A scientist looks at some fluid in a beaker because root cause analysis

Root Cause Analysis: The Five Whys – Game Planning With Science! Part 15

On January 28th, 1986, seven astronauts boarded the Challenger for its tenth launch into space. Its previous missions had included the first space walk and, at various times, the first American woman, African-American, Canadian and Dutchman in space. 73 seconds after lift-off, the Challenger broke apart, killing the entire crew. Why? Because the fuel tank exploded. So, the solution, of course, is to send the next shuttle up with a fuel tank that doesn’t explode, right? Only if you assume that the exploding fuel tank was a 100% isolated incident, completely unrelated to any other events. If that sounds fishy to you, it should. And this is where root cause analysis comes into play, a practice colloquially known as “the five whys”.

Read More »
A picture of scientists because heijunka is a sciency thing

Heijunka: Why Batching Is Not Your Friend – Game Planning With Science, Part 14

A commonly held belief is that it’s best to batch work – to handle similar tasks in large, consolidated chunks. The notion makes intuitive sense. It allows you to focus on one activity at a time and avoid so-called switching costs of switching activities. But as with so many other instances of unverified intuition, this particular notion is flat-out wrong. Batching may avoid switching costs, but it greatly protracts flow time, which, in the long run, can end up being far more expensive. Which is why the Toyota Production System introduced the concept of heijunka – “leveling”.

Read More »
A picture of scientists who hate muda. Trust me.

The Muda of Defects, Or: Finding Freedom Through Discipline – Game Planning With Science! Part 13

One of the more interesting characters I’ve encountered in my wanderings through the internet is a man by the name of Jocko Willink. He’s the author of Extreme Ownership and a business consultant. Oh, and an ex-Navy SEAL and a black-belt in jiu-jitsu. So, the man knows a thing or two about getting shit done under arduous circumstances. And his personal mantra is “Discipline equals freedom.” And the more I study operation science and the more I learn about software development, the more I see his point. So, in this post, I’m going to walk you through a multi-step process for testing code and how a little QA discipline can avail a lot of freedom.

Read More »
A picture of a scientist because jidoka and gin and tonics.

Jidoka: Putting The Robots To Work – Game Planning With Science! Part 12

As a developer, you’re almost perpetually flat to the boards. There is always too much to do, too many fires, too many needed fixes. You can’t create more time in the day, or more days in the week. But you can do the next-best thing: eliminate repetitive tasks using automation. Welcome to the wonderful world of jidoka.

Read More »
A picture of a scientist, because kanban is scientific!

Kanban: The Counter-Intuitive Value Of Pull-Based Production – Game Planning With Science! Part 11

The word “kanban” sometimes comes up in software and game development circles. But, when it does, it’s usually within the context of agile and scrum. And the interpretation of the term usually begins and ends with “It’s like scrum, but without sprints.” This is a massive oversimplification. You see, when I was a freshly minted scrum master, I often told folks that I was all about scrum, but I would happily kick it to the curb as soon as I found a better framework. Kanban is that framework.

Read More »
I picture of a scientist. Poka-Yoke falls under the realm of operation science. So it fits.

Poka-Yoke: The Fine Art of Mistake Proofing – Game Planning With Science! Part 10

You remember that time you plugged your HDMI cable into your PS4 upside-down and fried it’s video card? Or that time you clamped your ski-boots into your skis backwards and almost killed yourself on a black diamond slope as a result? Or that time you put a k-cup into a Keurig machine sideways an sprayed hot coffee all over the kitchen? No, you don’t. Because you can’t do any of those things. Those products are all designed so that they can only be used in the proper manner. The grooves on the HDMI connector, the specific clamps and catches on skis and boots, and the tapered design of Keurig k-cups mean that the proper application of the product is as obvious as its improper use is impossible. Welcome to the world of poka-yoke (poh-kah yo-kay).

Read More »
A bunch of scientists. Featured image for a post on lean development

Lean Development for Games – Game Planning With Science! Part 9

1947. Japan, still reeling from the Second World War, lies in economic ruin. And a little company called Toyota finds itself in a highly undesirable strategic position. It’s headquartered in a nation in tatters, and competing with companies in the world’s newest economic super-power: ‘Merca. How could it possible compete against companies with such amazing access to capital, resources and cash-rich customers? Well, necessity, as they say, is the mother of invention. And the necessities of Toyota’s strategic realities gave birth to one of the most remarkable feats of management ever achieved: the Toyota Production System. Or, more generically, “lean” development.

Read More »
Informal Power featured image of a rusty gate

Informal Power, Or: Why It Always Pays To Be Polite

The Merriam-Webster dictionary defines power as (among other definitions) “possession of control, authority, or influence over others”. Nothing terribly shocking there. But it’s worth digging into how power induces that influence. There’s the obvious, overt “Do this thing because I said to do the thing.” We’re all familiar with that one. But there’s also a different form of influence that comes not from influencing people, but circumstance. And on any given day, this informal power is far more likely to cause you grief.

Read More »
%d bloggers like this: