Kara Wang
All Projects
OnePipeline
An enterprise application that provides a frictionless way to generate and manage CICD Pipelines for our developers
UI Design
UX Research
Service Design
Internal Tooling
From Problem → Research → Design → Impact
TL;DR
Developers were wasting hours configuring pipelines manually. We designed an internal tool to streamline CI/CD setup, reduce friction, and bring clarity to the build lifecycle.
Includes:
Project scope
Stakeholders
Goals + metrics
Project Overview
From Problem → Research → Design → Impact
TL;DR
Developers were wasting hours configuring pipelines manually. We designed an internal tool to streamline CI/CD setup, reduce friction, and bring clarity to the build lifecycle.
Includes:
Project scope
Stakeholders
Goals + metrics
Project Overview
From Problem → Research → Design → Impact
TL;DR
Developers were wasting hours configuring pipelines manually. We designed an internal tool to streamline CI/CD setup, reduce friction, and bring clarity to the build lifecycle.
Includes:
Project scope
Stakeholders
Goals + metrics
Project Overview
What We Learned from 15 Engineers
TL;DR
We interviewed devs across teams to map their workflow pain points. The biggest issues? Alert fatigue, lack of visibility, and fragmented tools.
Alert fatigue
Lack of visibility
Fragmented tooling
Includes:
Empathy Interviews
Key Findings
UX Competitive Analysis
Journey Maps
Click diagrams below to zoom
Overview
What We Learned from 15 Engineers
TL;DR
We interviewed devs across teams to map their workflow pain points. The biggest issues? Alert fatigue, lack of visibility, and fragmented tools.
Alert fatigue
Lack of visibility
Fragmented tooling
Includes:
Empathy Interviews
Key Findings
UX Competitive Analysis
Journey Maps
Click diagrams below to zoom
Overview
What We Learned from 15 Engineers
TL;DR
We interviewed devs across teams to map their workflow pain points. The biggest issues? Alert fatigue, lack of visibility, and fragmented tools.
Alert fatigue
Lack of visibility
Fragmented tooling
Includes:
Empathy Interviews
Key Findings
UX Competitive Analysis
Journey Maps
Click diagrams below to zoom
Overview
Designing the Solution
TL;DR
We went from service blueprint to wireframes to high-fidelity UI, all while stress-testing developer needs. Here’s what we explored and iterated on.
Group these inside:
Service Design
User Flows
Wireframes / UI Screens
Design Decisions
From Diagrams to Prototypes: Designing OnePipeline
Designing the Solution
TL;DR
We went from service blueprint to wireframes to high-fidelity UI, all while stress-testing developer needs. Here’s what we explored and iterated on.
Group these inside:
Service Design
User Flows
Wireframes / UI Screens
Design Decisions
From Diagrams to Prototypes: Designing OnePipeline
Designing the Solution
TL;DR
We went from service blueprint to wireframes to high-fidelity UI, all while stress-testing developer needs. Here’s what we explored and iterated on.
Group these inside:
Service Design
User Flows
Wireframes / UI Screens
Design Decisions
From Diagrams to Prototypes: Designing OnePipeline
UX Strategy + Constraints
TL;DR
We were building for developers, under tight timelines, inside a legacy system. Here’s how we balanced ambition with reality.
Includes:
Timeline
Technical limitations
Team roles
Constraints that Shaped the Design
UX Strategy + Constraints
TL;DR
We were building for developers, under tight timelines, inside a legacy system. Here’s how we balanced ambition with reality.
Includes:
Timeline
Technical limitations
Team roles
Constraints that Shaped the Design
UX Strategy + Constraints
TL;DR
We were building for developers, under tight timelines, inside a legacy system. Here’s how we balanced ambition with reality.
Includes:
Timeline
Technical limitations
Team roles
Constraints that Shaped the Design
Outcomes + Learnings
TL;DR
The tool launched to 4+ dev teams. Usage jumped, false alerts dropped, and we validated a scalable internal design system. Here's the impact — and what we'd do differently next time.
Includes:
Metrics
Feedback
Next steps
Reflections
What Shipped and What We Learned
Outcomes + Learnings
TL;DR
The tool launched to 4+ dev teams. Usage jumped, false alerts dropped, and we validated a scalable internal design system. Here's the impact — and what we'd do differently next time.
Includes:
Metrics
Feedback
Next steps
Reflections
What Shipped and What We Learned
Outcomes + Learnings
TL;DR
The tool launched to 4+ dev teams. Usage jumped, false alerts dropped, and we validated a scalable internal design system. Here's the impact — and what we'd do differently next time.
Includes:
Metrics
Feedback
Next steps
Reflections
What Shipped and What We Learned