COMMANDDOC
(UX MVP Overview)
A single, secure platform to manage, track, and execute all COOP plans and recovery activities for maintaining critical public safety functions
MVP Overview
COOP: Continuity of Operations
COOP: Continuity of Operations is essential for maintaining critical public safety functions.
Goal
Develop a single, secure platform to manage, track, and execute all plans and critical functions.
The Problem: Scattered Information, Slow Response
Fragmentation
Plans are scattered across Word, PDFs, email, and shared drives.
Outdated Data
Key contacts and resource lists are often inaccurate.
Slow Updates
Plan revisions after exercises or incidents take too long to circulate.
Lack of Visibility
Command staff lack a quick, real-time view of critical function status.
Compliance Burden
Reporting and audits require extensive file digging.
Goal: A Single Platform
Consolidate and Simplify
Bring all COOP plans, people, assets, and responsibilities into one centralized location.
Focus
Make it easier to track everything required before, during, and after an incident.
The MVP Goal
  • Create a single, secure web platform.
  • Manage COOP files, updates, and responsibilities in real time.
  • Eliminate the need to search through multiple folders or conflicting versions.
  • Improve readiness and response speed.
Key MVP Features: Content Management
1
File Repository
Centralized platform for all COOP files by department.
2
Audit Log
See a history of changes, and version control
3
System Control
Push new templates, lock sections
Key MVP Features: Tracking & Visibility
Status Dashboard
Quick, real-time view of which departments are open, in progress and completed
Task Tracker
Assign, track, and close COOP-related tasks (e.g., plan updates, training).
Audit Log
Version control and history of changes
Users: Who Benefits
Executive Admins
Needs operational visibility into COOP readiness across many departments
View Details
Administrators
Responsible for keeping their department's plans current, accurate and compliant
Editors
Edits, updates and actively completes tasks in order to support compliance.
Impact: Compliant. Ready.
Clarity
Eliminate confusion over which plan version is current.
Speed
Faster updates and streamlined reporting for compliance.
Accountability
Clear ownership for every COOP section and task.
Situational Awareness
Stronger visibility for critical command decisions during an incident.
The UX Process
The UX Process: Building for the User
User-Centric Design
Our UX approach ensures the platform is built around how officers and staff actually work in high-stakes situations.
Operational Focus
Key design priorities are usability, clarity, and speed to support effective decision-making under operational pressure.
Guiding UX Principles (Our Mission)
Guiding Principles: Built for the Field
Clarity Over Complexity
Data must be visible in seconds, not clicks. The platform remains simple and usable even during high-pressure incidents.
Consistency
We ensure a uniform look and flow across all screens and devices to significantly reduce user training time.
Accessibility
The platform must work seamlessly on desktops, tablets, and mobile devices, ensuring field accessibility at all times.
COMMANDOC Platform – UX Approach
Our UX approach is designed to build a platform that directly matches how personnel manage COOP plans—simple, clear, and fast under pressure.
1
Discover
This phase defines core user needs for the MVP.
User roles & responsibilities matrix
User flow diagrams
Pain point summary sheet
MVP requirements checklist
UX success metrics
2
Build
Quick, low-fidelity blueprints and prototypes to test usability with customers
  • Low-fidelity wireframes
  • Interaction notes / usability hypotheses
  • Clickable prototype
  • Design feedback log
3
Pilot Testing
An interactive prototype is deployed to a small group. This validates workflows for uploading, assigning, tracking, and reporting, collecting crucial feedback on usability and data visibility.
4
Launch
The platform rolls out to all units with concise training. We gather in-app feedback, adjust features as needed, and maintain a steady cycle of updates and refinements.
Next Steps: Moving Forward
Discovery
  • Map workflows
  • Determine metrics of success
Build (local POC)
  • MVP requirements
  • User flow diagrams
  • Low-fidelity wireframes
Technical Plan
  • Technical Architecture
  • Hosting platform
  • Cost analysis