Echosec

An OSINT threat-intelligence dashboard: design system, alert model, and inbox triage so analysts act faster.

Type
Product design · Cybersecurity
Scope
System, alerts, inbox
Role
Design lead
Echosec OSINT dashboard results

Introduction

Echosec needed one product language before an investor event. Notification, alert, and event detection were used interchangeably. There was no filtering, and no system holding the screens together. The work ran 12 weeks, discovery through prototype.

Echosec threat-intelligence results dashboard

Twenty interviews. Four flows validated. Eighty percent of testers said the platform finally felt like one product. One hundred fifty components, more than 100 pages, in 12 weeks.

80%said it felt like one product

Inbox triage
Dashboard
Map view

The problem

Analysts had no shared language
for what reached them.

Alert, notification, and event detection meant different things on different screens. There was no filter, so everything arrived at the same weight. Features were built in isolation. The inbox slowed down as media arrived.

System

A foundation before more features

Establishing the Echosec design system

The design system came first so a multi-product OSINT suite could share tokens, components, and a single reading order.

Alerts

Condition, threshold, alert, notification

The model named each layer. Color-coded severity and predictable thresholds replaced interchangeable labels.

Defining the alert model
Color-coded persistent alert modal
Time-based non-persistent notification

Inbox

Triage in the card, depth in the side panel

Echosec inbox
Inbox side panel
List view

The card carries enough to decide. The side panel opens depth without leaving the queue. List and grid views cover different analyst habits.

Find

Filtering and event detection in one place

Search and event detector
Event detector
Map view

Analysts control what reaches them. Search, event detection, and map sit on the same language as the inbox.

Echosec main dashboard

System

One product language for OSINT work

Figma · FigJam · Prototyping · User interviews

Outcome

The outcome

  • 20User interviews
  • 4Flows validated
  • 80%Felt like one product
  • 12Weeks, discovery to prototype

For the first time the inbox, the map, and the alerts felt like they belonged to the same product.

Analyst interview · Echosec · 12-week engagement
Next Step

Building something
ambitious?

I partner with Web3, fintech, and SaaS teams to design flows that actually ship. Book a discovery call. No slides, just a conversation about your product.