Digma · Developer tools · Data visualisation · 2024

Making code observability approachable for developers

Digma finds performance issues at the code level before they reach production. I designed the dashboards, flows and design system that make those insights clear to developers and managers.

Role
Senior Product Designer
Timeline
Feb 2024 – Apr 2025
Team
Product, engineering
Platform
IDE plugin, Web

The challenge

Draft — what was broken, for whom, and why it mattered to the business. One or two short paragraphs is plenty.

Add any constraints that shaped the work: deadlines, legacy systems, regulations or team size.

Research

Draft — how you learned about the problem: interviews, analytics, competitor reviews, support tickets. End with the one or two insights that changed the direction.

Image placeholder — Research artefact
Journey map, affinity board or key insight

Design process

Draft — the main options you explored and why you chose one. Show the messy middle: flows, wireframes, rejected ideas.

Image placeholder — Early wireframes
Wireframes
Image placeholder — User flow
User flow

The solution

Draft — the final design and the details that make it work. Lead with the screens; keep the text short.

Image placeholder — Final design
Final screens

Results

Draft — what changed after launch, and what you learned.

Metric one
00%
Metric two
00%
Metric three
0×

Next case study