The Problem
Templates Existed in a Vacuum
Templates were the starting point for validation, but they stopped being useful once an assessment launched. Users had no connected place to understand outcomes over time.
Cymulate templates are curated collections of attack scenarios grouped by use case. They define what teams test, but the old experience surfaced only metadata and forced users to stitch their validation story across multiple screens.

No feedback loop
Users couldn't see assessment results from the template they originated from. Templates were a one-way launchpad.
No trend visibility
Comparing results over time for the same template required navigating across three separate pages.
No coverage signal
No way to tell at a glance which templates were actively tested, scheduled, or sitting untouched.
Process
From Catalog to Validation Hub
The core insight was simple: templates are not a static library. They are the unit teams use to track whether security posture is improving.
01
Research
Mapped existing user journeys and identified the disconnect between templates and assessment results.
02
Strategy
Defined the template-as-hub concept: every template becomes a self-contained view of its validation history.
03
Design
Designed new card components and a multi-tab drawer with assessment results, insights, and MITRE coverage.
04
Iteration
Refined the adaptive UX for tested vs. untested templates based on internal feedback and edge cases.
The Solution
Two Layers of Improvement
I led both product strategy and UX execution: redesigning cards for immediate clarity and introducing a detail drawer for deep, contextual analysis.
01
Status-Rich Cards
New template cards show testing status, assessment count, schedule frequency, and contextual CTAs that adapt by state.
02
Template Drawer
Clicking a template opens a resizable drawer with assessment results, insights, MITRE coverage, and exposure data.
03
AI Analysis
Vero AI summaries are placed in the overview tab so teams can quickly understand what changed and why.
04
Adaptive States
Drawer structure changes for tested and untested templates, always surfacing the most relevant actions first.
Deep Dive: Feature 01
The Template Drawer Overview
The overview tab answers the primary question immediately: how is this template performing in my environment?
Assessment results at your fingertips
- Latest assessment score with prevention and detection sparklines.
- Vero AI analysis summarizing results in plain language.
- Prevented vs. not-prevented scenario breakdown.
- Quick actions: Replay, Schedule, or Generate Report.

Deep Dive: Feature 02
Insights and Analytics
The insights tab surfaces systemic exposure gaps, not just single-run results.

Identify systemic gaps
Teams see prevention and detection ratios, drift over time, and prioritized ATT&CK problem areas in one place.
- Prevention and detection ratios as donut charts.
- Prevention and detection drift counters.
- Top not-prevented ATT&CK techniques ranked by volume.
- Top not-prevented ATT&CK tactics ranked by volume.
Deep Dive: Feature 03
MITRE ATT&CK Coverage Heatmap
Coverage moved into template context, so teams no longer jump across pages to reason about kill-chain health.
Designed for quick scanning
- Color-coded cells from green (81-100%) to red (0-20%).
- Each cell shows technique ID, name, and prevention rate.
- Not-tested techniques are visually distinct.
- Direct links to the full ATT&CK MITRE dashboard.

Deep Dive: Feature 04
Assessment History Table
Every assessment launched from a template becomes part of one searchable historical record.

The complete historical record
- Full search and multi-filter support.
- Security control icons for quick identification.
- Progress bars for prevention and detection ratios.
- See in Assessments link for full workflow handoff.
Design Detail
Adapting to Template State
The drawer layout changes based on whether a template has prior assessments, ensuring value for both first-time and repeat users.


Outcomes & Impact
Closing the Loop
Users can now move from "what should I test?" to "how am I doing?" to "what should I fix?" without leaving template context.
TBD
Increase in template engagement
TBD
Assessment creation from templates
TBD
Reduction in navigation to Assessments page
The project is in early rollout. Qualitative signals from internal stakeholders and early adopters show that teams no longer piece together validation outcomes across disconnected pages.
SOC Manager, Mid-Market Customer
This completely changes how I think about templates. I used to treat them as a launcher. Now it is where I go to check if we are actually improving.
Reflection
What I Learned
The key lesson was information architecture. Most required data already existed, but it was fragmented across disconnected pages and workflows.
Choosing a drawer over a full page preserved browsing context while still giving power users deep access through a resizable detail surface.
Leading both PM and UX accelerated decisions, reduced scope risk, and helped ship a practical improvement instead of an overbuilt system.