Wargaming Engine

When Studio Alpha was shut down, the simulation project it had been supporting toward the end, Stormbreaker, transferred over to Microsoft Federal. Myself, the rest of the creative team, and some of the engineers moved with it. My responsibilities stayed largely the same: UI/UX and Unreal Engine design work for the simulation half of a project being built for military planners.

Due to the project being under a limited NDA, every artifact on this page has been recreated for this case study to align with the publicly available JP 5-0 documentation that Planners work from. The feature focus is also narrowed down to some interaction designs and a variation of the SmartCard I brought over from Studio Alpha.

Military planners have worked with pen and paper and disconnected third-party tools for decades. The process is well established: plans are built in PowerPoint, presented in PowerPoint, then printed and stored in binders on a shelf. That makes reviewing, cataloging, and referencing past plans harder than it needs to be, and wargaming one could take upwards of 16 months to organize and run. Stormbreaker's goal was to digitize the JP 5-0 process and drastically streamline the whole experience.

These are mockups of proposed solutions, validated either internally during exploration or directly with customers.

The SmartCard came over from Studio Alpha: a customizable, data-driven card carrying the information relevant to the plan being built, drawn from what the planner had already set up in earlier steps.

A planner could drop one SmartCard onto the grid and build a hierarchy of objects from it. The card offers the correct object types depending on which side tab is used. Each object card can be customized further if a planner needs more or less data.

Custom areas were something planners kept raising, so the work started on a napkin while a customer talked me through how they do it now and what they wished they could do instead.

This interactive Figma prototype creates two SmartCards. The first is created vertically, below the existing card; the second horizontally, to its right. The point of a prototype like this was to demo the interaction to potential users and get their feedback. This version carries a text hint to give direction from the start.

Best viewed full screen. It doesn't work on mobile at the moment, since the interaction relies on hover.

Placing objects is the main action when setting up a scenario, and these objects usually come in groups. The below motion study shows a group of objects being placed at once from the left nav. After which one single object can be selected and moved independently.

Embedding objects into other objects was something planners would do countless times throughout the creation and testing of a plan. On a map holding hundreds or thousands of objects, selecting one or more and embedding them into a location had to be painless and intuitive. Locations holding embedded objects show the count in a signifier at the corner, and hovering over a location pops up a window listing everything inside, for quick access.

SMX pulled the project from Microsoft Federal and brought it entirely in house. That ended my Allovus contract at Microsoft, along with the rest of the team's. A month or so later, the previous director of Studio Alpha, who had since joined SMX as project director to continue Stormbreaker, hired me and the two other designers to carry on the work.