Service ownership, feature state, content readiness, and QA progress were difficult to compare.
Back to projects
Case study 03 / Service management
Zero gives product teams a single map of services and feature readiness.
A service and feature management system for product managers, content teams, and QA, designed to clarify ownership, dependencies, status, and release confidence.
Overview
A service and feature control layer for product, content, and QA teams.
Product managers, content managers, QA teams, operations, and feature owners.
Product architecture, workflows, dashboard design, interaction patterns, and UI system.
A shared workspace for service visibility, readiness checks, dependencies, and launch confidence.
Challenge
The system had to align different teams without flattening their workflows.
Product, content, and QA teams look at the same feature from different angles. The challenge was creating one system where each team could see its own work while still understanding the broader release picture.
I designed around status clarity, ownership, filtering, and readiness signals so teams could move from scattered updates to a single operational view.
A shared control surface for release readiness.
The main board turns service status into a working model: teams can compare environments, detect blockers, inspect ownership, and move from high-level health to specific deployment evidence.
Flow in motion
Operational flows that connect service status to the work needed before release.
Deployment evidence
Connect service cards to Jira-level context.
The flow shows how operators can move from service health into related deployment work without losing the board view.
QA automation
Expose automation as a clear operational action.
The QA flow keeps automation state, ownership, and next steps visible so teams can act without switching tools.
Process
From fragmented status tracking to a clear product operations model.
01 / Research
Mapped team responsibilities, release blockers, repeated checks, and visibility gaps.
02 / IA
Defined services, features, ownership, readiness, dependencies, and QA state hierarchy.
03 / Flows
Designed paths for service setup, feature review, QA approval, and launch tracking.
04 / System
Created reusable cards, status chips, filters, checklists, and operational detail views.
05 / Prototype
Validated scanability, empty states, role-based views, and dense dashboard behavior.
One service model
Created a shared structure for features, owners, content state, QA state, and release readiness.
Role-aware views
Designed views that support different teams while keeping the same underlying product truth.
Readiness over reporting
Shifted the UI from passive status reporting into actionable next steps and blockers.
Final experience
Screens that make service health, feature progress, and ownership easy to scan.
01 / Deployment evidence
Keep service health connected to the work behind it.
The Jira deployments drawer lets teams move from a service card into linked tickets, status, summaries, and related work without losing the broader board context.
02 / State comparison
Make environment changes explicit before they ship.
A focused state modal compares active and alternate services so release owners can review what will change, select the right services, and confirm with confidence.
03 / Feature inventory
Turn feature rollout into a matrix teams can scan.
The feature table maps feature names, groups, environments, values, and scheduled variants so product and content teams can see rollout differences at a glance.
04 / Configuration model
Expose complexity without making setup feel chaotic.
The feature configuration view organizes type, status, values, dates, expired states, and environment rules into repeatable panels for faster review and updates.
05 / Geographic targeting
Make regional rollout decisions visible and reversible.
The location selector pairs a country list with a world map so teams can understand mixed states, selected regions, and value assignments before updating an environment.
Impact
A cleaner operating model for shipping service-heavy products.
Improved team alignment by giving PM, content, and QA a shared view of readiness.
Reduced ambiguity around ownership, dependencies, and next actions across feature work.
Created a scalable interface language for complex product operations and QA workflows.
Next case