Patch Data: From trigger boards to comprehensive observability

Patch Data is a data pipeline observability platform for enterprise software companies. When I joined, the product was CLI-only and stakeholders had a fixed brief: build trigger boards for event notifications. I led the design effort that reframed the problem entirely, shifting the product from reactive alerting to comprehensive observability. The company raised $3M in pre-seed funding and was acquired within a year.

The original assumption was that users needed better notifications for pipeline events. But the real issue ran deeper. Engineers had no visibility into how end users interacted with data pipelines. PMs and account executives relied on delayed insights from BI tools and CRM integrations, creating blind spots in product strategy and customer success. Cross-functional teams were context-switching constantly, and troubleshooting was fragmented across disconnected tools.

I paused development to clarify the actual problem space, securing buy-in from engineering leadership to run research first. I observed behaviour across three personas (data engineers, software engineers, PMs/AEs) and ran think-aloud sessions with 10 high-engagement users. The trigger board assumption fell apart quickly. Users who received alerts fell straight into the same broken workflow: switching tools, chasing context, pulling in engineers for status updates. The real gap wasn't notification speed, it was consolidated visibility and shared understanding across technical and non-technical teams.

I led the team away from trigger boards toward a comprehensive observability platform. I benchmarked against existing tools to leverage users' existing mental models, then designed a unified interface with clear data visualisations, intuitive source and dataset management, and a shared visual language that worked across roles. I validated through competitive analysis, wireframe co-creation, and prototype testing, keeping iterations lean and grounded in real user behaviour.