Momentum is UniGroup's first design system, built to bring consistency and speed to a fast-growing portfolio of QDivision apps.
The
Problem
I'd advocated for a design system since early in my time at UniGroup, having seen firsthand how inconsistent components, typography, and spacing slowed teams down. Without buy-in, I maintained a personal system, Momentum, on my own for years.
The
Speedbump
As QDivision scaled and new apps launched in rapid succession, the lack of shared standards went from inconvenient to unsustainable. Teams were rebuilding the same components independently, and the pace of new products made the need for a real design system impossible to ignore.
The
Solution
So when strategic planning for Converge came around, I finally had the platform to make the case, arguing that a shared design system would speed up development across it, and proposing Semantic UI as its foundation after evaluating it against other frameworks. Once Converge was approved, so was Momentum, but budget constraints ruled out a dedicated team to build it.
Fortunately, that didn't have to stop us. We took Momentum directly to the organization, presenting it company-wide and asking for volunteers to help build it during their allocated innovation time. I led the UX foundations, principles, and accessibility guidelines while our Software Architect handled the shared component structure.
The
Foundational Pillars
The
Outcome
That volunteer effort paid off. I released Momentum 1.0 in early December, and involvement kept growing from there, eventually reaching over three dozen contributors across design and development. It became one of the most actively supported initiatives in QDivision.
By the time I handed it off, Momentum had become the foundation for every UniGroup app, along with marketing, product voice, and document templates. It cut development time for new features by a third and helped accelerate Converge's build time, directly contributing to the DOD contract win.













