Peter Yang - Unifying Three Legacy Products into One Scalable Platform

Unifying Three Legacy Products into One Scalable Platform hero

Unifying Three Legacy Products into One Scalable Platform hero

Traced and unified three fragmented IAs into a single Monitor–Act–Manage structure.

Select a widget to preview the consolidated component set.

Nested grid

Live

	Building name	Campus/Group	Total energy consumption	Average daily equip runtime	% of time within setpoint
	Office complex B	Campus A	18,420 kWh	14.6 hr	114 %
	Willow Creek	Campus A	12,880 kWh	13.1 hr	117 %
	Maple Heights	Campus A	21,055 kWh	15.8 hr	112 %

Office complex B

Entity name	Total zone out of temperature (h)	Time zone too cold (h)	Time zone too hot (h)
V-1040-40	8.2 h	0.0 h	8.2 h
V-1050-50	8.1 h	0.3 h	7.8 h
V-1060-60	8.0 h	0.6 h	7.4 h
V-1070-70	7.9 h	0.9 h	7.0 h
V-1080-80	6.6 h	0.0 h	6.6 h
V-1090-90	6.5 h	0.3 h	6.2 h
V-1100-00	6.4 h	0.6 h	5.8 h
V-1110-10	6.3 h	0.9 h	5.4 h
V-1120-20	5.0 h	0.0 h	5.0 h
V-1130-30	4.9 h	0.3 h	4.6 h
V-1140-40	4.8 h	0.6 h	4.2 h
V-1150-50	4.7 h	0.9 h	3.8 h
V-1160-60	3.4 h	0.0 h	3.4 h
V-1170-70	3.3 h	0.3 h	3.0 h

Modular widgets that carried specialized workflows into one platform.

Platform ConsolidationEnterprise SoftwareUIUX Refresh

Overview

Where I Started

Problem Statement

Three smart building products had evolved independently, creating fragmented workflows, duplicated capabilities, and inconsistent user experiences.
Each product supported a different operational model, from equipment control and automation to analytics and reporting. Consolidation required more than merging features.

Context

The business needed one maintainable platform, while users and product teams needed to preserve the specialized workflows they relied on.
My challenge was to define a shared product structure without flattening meaningful differences between user groups.

What I Did

Responsibilities & Contributions

Set the consolidation strategy: Synthesized research, product requirements, and technical constraints across three products to separate essential workflows from legacy complexity.
Aligned teams around a shared product model: Facilitated cross-functional working sessions that turned competing requirements into a unified information architecture and prioritization framework.
Designed a flexible platform foundation: Defined core navigation, workflows, configurable dashboards, and modular widgets that supported distinct operational needs within one coherent experience.
Improved design-to-engineering execution: Introduced implementation-ready specifications and a design QA process that reduced handoff friction and created reusable practices for other teams.

Impact

3 products to 1 platform

Consolidated fragmented experiences into a shared product foundation.

30% faster task completion

Observed across selected core workflows in limited usability testing.

25% faster feature delivery

Estimated by the product and engineering team after introducing detailed specifications and design QA.

1 shared UX foundation

Established common navigation, workflow, and modular UI patterns across previously separate product teams.

What I Learned

Key Insights

Platform consolidation is as much an alignment challenge as a design challenge. A shared vision gained traction when teams could see how their users' needs shaped the final product model.
Standardization needs intentional flexibility. The strongest foundation standardized navigation and interaction patterns while allowing specialized workflows to remain distinct.

Critical Constraints

Different technical foundations and migration timelines required the experience to support phased adoption rather than assume an immediate transition.
Detailed specifications and close engineering partnership were essential to avoid carrying legacy inconsistencies into the new platform.

View Full Case Study