Back

Designing a Mobile Gamified Training System for Real-World Decision Making

The result is a scalable training system that uses game design principles to improve real-world decision-making under pressure.

Summary

Designing a Mobile Gamified Training System for Real-World Decision Making

Rather than relying on points, badges, or leaderboards, this system uses interaction-driven gamification to train law enforcement officers in high-stakes, real-world scenarios.

Designed for field use — officers could complete training between calls, requiring fast interactions, minimal friction, and mobile accessibility.

Context

In 2013, Colorado Senate Bill 13-226 mandated additional training for law enforcement officers encountering dogs in the field. A multidisciplinary taskforce — law enforcement, animal behavior experts, legal advisors, and training professionals — was formed to define and implement a statewide solution.

The requirement wasn’t just to create content. Departments needed an interactive digital training system they could deploy independently to meet compliance standards.

The Core Challenge

The primary challenge was translating diverse — and at times conflicting — stakeholder perspectives into a structured training system that:

• Met legislative requirements
• Reflected operational realities in the field
• Scaled across departments
• Could be deployed inside strict government IT environments

While the goal was training, much of the work ended up being systems design — structuring content, logic, and progression in a way that could hold up under real-world use.

Constraints & Environment

• Legislative compliance requirements
• Stakeholder disagreement on best practices
• Government IT deployment restrictions
• Limited development resources
• Long-term maintainability concerns

“We both agree on the value of training law enforcement on ‘dog encounters’ and we both understand that there is a big difference between a pet that may be barking and one that ‘poses an imminent danger of attack.’”
— Taskforce stakeholder (name omitted)

Members of the taskforce brought different constraints and pressures to the table. While officers agreed on the value of safer outcomes, they were also mindful of the time and resource burden additional training would place on their departments. The system needed to be practical, defensible, and simple enough to earn adoption — not just satisfy legislation.

At the time, many law enforcement and government environments operated under strict software approval processes. Adobe Flash applications were already certified within many of these environments, which allowed the training to be deployed without undergoing lengthy security review cycles.

So many of our design decisions were shaped by what would realistically get approved and installed inside precinct and department systems.

The initial system was built in Flash/Flex using an XML-driven content structure — prioritizing deployability and institutional acceptance over long-term platform flexibility.

My Role

I partnered closely with the lead engineer and the multidisciplinary taskforce to structure the training experience end-to-end.

My responsibilities included:

• Translating stakeholder input into structured course architecture
• Designing interaction patterns within an XML-driven framework
• Modeling learning flows and progression logic
• Ensuring the system could operate independently across departments

The ownership was collaborative, but I focused on translating complex — and sometimes conflicting — requirements into something officers could actually move through and complete without facilitation.

Key Design Decisions

1. Modeled training as reusable interaction systems
Rather than building static slide-based content, the course was structured around repeatable interaction types — scenario-based decisions, matching exercises, hotspot analysis, and video-driven branching — defined within XML. This allowed consistency across modules and made future updates more manageable.

2. Facilitated stakeholder alignment through synthesis
There were real disagreements among stakeholders about best practices in the field. Through structured one-on-one and group sessions, I translated those qualitative discussions into standardized interaction logic that could be defensible and teachable.

3. Designed for independent departmental deployment
The system needed to function without instructor facilitation. Clear progression states, feedback loops, and completion tracking were built into the architecture so departments could demonstrate compliance when required.

Revised HTML-based training interface showing structured interaction modules and progression logic.

Tradeoffs & Design Tensions

Legal Precision vs Practical Usability
Content needed to remain legally defensible while still reflecting realistic field conditions officers would encounter.

Stakeholder Alignment vs Delivery Timeline
Building consensus required facilitation and iteration, but the training also needed to be delivered within mandated timeframes.

Platform Constraint vs Longevity
Flash solved the immediate deployment problem, but we knew it wasn’t a forever solution — and eventually that tradeoff caught up with us.

Interaction Design & Core Gameplay Loop

Because departments controlled access and officers completed the training on their own, the system needed clear onboarding states, visible progress, and challenge and evaluation loops that could stand up to scrutiny. I mapped predictable transitions—invitation, registration, login, module selection—and designed feedback so officers knew where they stood while administrators could confidently track completion.

Invitation and authentication flow modeling access states and administrative control.

Early wireframe exploring feedback visibility, scoring, and progression within challenge and evaluation loops.

Platform Migration & System Evolution

When Adobe deprecated Flash and the original hosting contract expired, the project was brought in-house under Emersive Systems to preserve statewide continuity.

I partnered with the lead engineer to translate the structured XML-driven course architecture into HTML/CSS, maintaining the learning logic while modernizing the interface.

As departments continued using the system over time, some architectural limitations became obvious — especially in the administrative tooling and how identity was structured. In the second-generation implementation, administrator accounts were coupled directly to email addresses as primary keys. When personnel changed roles or departments, this created friction and required manual intervention. We also encountered reliability issues in certificate generation that exposed weaknesses in the underlying structure.

Administrative dashboard introduced during the HTML migration, used by departments to manage users, track completion status, and generate certificates.

Working through those issues changed how I think about identity and administrative systems. It’s not enough to design for launch — you have to design for personnel turnover, policy shifts, and long-term maintenance.

Applying Game Design Thinking

While not a traditional “game,” the system applies core game design principles:

• Player = Officer in training
• Core loop = Observe → Decide → Act → Feedback
• Failure is safe, repeatable, and instructive
• Difficulty scales with experience
• Engagement comes from interaction, not rewards

Gamification Strategy

Gamification Through Interaction Design

No points. No badges. Just better decisions under pressure.

• Instead of traditional reward systems, we focused on engagement through meaningful interaction:
  Officers reviewed real-world environments and identified visual indicators of a potential dog presence under time constraints.
• Officers reviewed real-world environments and identified visual indicators of a potential dog presence under time constraints.
  Users tapped or clicked elements within a scene—similar to hidden-object or investigative gameplay systems.
• Immediate Feedback Loops
  Each interaction produced:
  • Correct identifications
  • Missed signals
  • False positives
• Progressive Complexity
  Modules increased in difficulty, simulating the unpredictability of real-world encounters.
• Behavioral Learning Through Iteration
  Repeated exposure reinforced pattern recognition and decision-making—similar to skill acquisition in games.

Mobile-First Evolution

Transitioning to Mobile Learning

Designed for real-world use: officers could complete modules between calls, in vehicles, or during downtime—requiring fast load times, simple interactions, and minimal friction.

The original system was built in Flash, which limited accessibility on mobile devices.

As mobile usage became essential for in-field training, we rebuilt the platform using HTML/CSS:

• Enabled training in short, on-demand sessions
• Supported field-based usage during downtime
• Improved accessibility across departments and devices
• Maintained structured progression and interaction models
• This shift transformed the system from a desktop training tool into a portable learning experience aligned with real-world workflows.

Outcomes

• Deployed statewide to support compliance with SB 13-226
• Enabled departments to independently meet mandated training requirements
• Preserved continuity of training through platform migration
• Continues to be used to train officers in Colorado

Ongoing Modernization

We are currently modernizing the administrative architecture to address accumulated technical debt and improve scalability. This includes:

• Decoupling identity from email-based primary keys
• Improving certificate generation reliability
• Rebuilding the administrative dashboard using a modern stack (Lovable, Supabase)
• Simplifying admin workflows to accommodate personnel turnover

Modernizing the administrative layer also gives us the foundation to adapt the framework for other states — and potentially build additional training programs on top of the same system.

Back