Tools SIG

Perhaps not all of these apply to you, but every game studio I've seen has had one or more of the following problems.

1. Design as you go
All too often, game companies are in too much of a hurry to allow proper upfront design of tools. As a result, programmers end up designing the tools, anyway. Unfortunately, since they have to continually show progress, the tools are designed as they are coded, which doesn't really save any time at all, and leads to a host of problems. As tool development gains inertia, the earlier code becomes more and more difficult to change without breaking the entire system. When given a choice between rewriting and creating a workaround, the least expensive of the two (in the short run) is generally preferred. Major changes to support new features or a more desirable workflow become more and more difficult as the code becomes too brittle to support it's own weight.

2. The system model of design
When programmers design interfaces, they tend to expose the underlying data structures directly. That is the most logical method, since they understand how the system works. The end user has a different view of the system is based on his own goals. He doesn't need to know the underlying implementation details, just the result. The system model can give the desired effect, but may seem illogical to the user, making the tool difficult to understand.

3. Leveraging the wrong technology
A lot of us, especially with engineering backgrounds, cringe at the thought of “reinventing the wheel.” Recreating something that already exists somewhere else goes against everything we've learned, but taking a tool designed for one thing and turning it into something it was never destined to be, will cost more time in the long run than just writing a new tool from scratch.

4. Complicating the interface
“The simpler, the better,” should be every tool designer's motto. The more interface the user has to deal with, the more difficult the tool will be to use. Focusing on the goals of the end user, should make apparent what interface items should be readily available, and which should be hidden away in a menu somewhere.

5. Extraneous features
Often, the tool designers aren't communicating with the tool users, which always leads to a handful of features that just aren't used. They probably seemed really important during design, but wasted time spent on these features should have been used to improve the commonly used functionality. They just end up cluttering the interface or adding additional steps to a process that should have been much simpler.

6. Designing for advanced users
Let's face it, there are some people in your company that are more technically skilled than others, and I'm not talking about programmers. Often, the more technical designers (the ones with scripting or programming backgrounds) are the ones who are able to use the internally developed tools more effectively, leaving the rest of the design staff to struggle. This is also true of other disciplines, but design has it the worst, in most cases. Game development tools should target the average user, with advanced functionality neatly tucked away where the more technically savvy users can find it, if necessary, while the more common functionality should be out in plain sight, easily accessible and understandable.

All of these issues lead to one overarching problem -- low usability. Tools that are unusable, do little good to anyone, and higher usability leads to happier and more productive employees. Every minute that an employee spends fighting with the tools is a minute that could have been spent making a better, more polished game, something every game company struggles to achieve, by addressing problems like the ones above will help tremendously. I'll talk more about these and other issues more in-depth in future blog posts.