Five apps. One Webex.
Cisco Collaboration had accumulated five distinct applications across a decade of acquisitions and parallel BU initiatives — Webex Meetings, Jabber, Cisco Spark / Webex Teams, UC-One (Broadsoft), and Webex Calling. I led the strategy for a phased, framework-driven convergence that shipped as the Unified Webex App at Webex One in December 2020.
The bet
You can't consolidate by shutting things down. Each of the five applications had real customer adoption in differentiated markets. UC-One served service providers. Jabber had enterprise premise deployments. Webex Meetings was Cisco's flagship. Cisco Spark / Webex Teams had its own user base.
A "pick the winner" consolidation strategy would have shed users, revenue, channels, and acquired technology investment. The strategic answer had to be different: a phased, framework-driven convergence that aligned the five applications at the experience level before consolidating them at the technical level.
The diagnosis
If I had to compress it: You can't consolidate until we have alignment on the need for it across the org, then by framework, then by app. Each stage is a precondition for the next.
Alignment first — organizational alignment across the BUs on why consolidation is needed. Framework second — a modular UI framework that could serve differentiated channels on a shared technical foundation. App third — the technical consolidation through the Unified Client Framework (UCF), staged across multiple releases.
The non-obvious call
Align UI before consolidating tech — not the other way around. Customer-visible momentum well before Phase 2 shipped. Cross-BU alignment momentum that didn't depend on technical consensus. The UI alignment work built the organizational consensus that made Phase 2 framework convergence achievable.
What we shipped
Phase 1a — Alignment. Visible UI alignment across UC-One, Jabber, and Webex with the Webex design system. UC-One: a fragmented multi-pane interface transformed into a Webex-aligned modern collaboration interface.
Phase 1b — Differentiated offerings on the modular framework. UC-One shipped service-provider-branded. Cisco Webex Calling shipped Cisco-branded. Both on the same modular UI framework — proof that consolidation didn't require channel uniformity.
Phase 2 — Technical convergence through UCF. Executed in stages across multiple releases. Each release moved more capability onto the shared framework, with the four legacy apps progressively converging into the single Webex app.
Without his relentless emphasis on addressing and improving the underlying software frameworks in order to achieve the best experience, we would never have started the journey of unifying our application portfolio. This has in turn helped Cisco save millions in R&D investments as well as helped our customers be way more productive with modern, ubiquitous and intuitive designs. Hakim Mehmood — VP/GM, Cisco Collaboration
The longer arc
What this work became: the critical driver of consolidation across the many capabilities the Collaboration group had built across its BUs. The framework set a precedent for how Cisco approached subsequent platform consolidations. The relationship between UI alignment and technical convergence — which we sequenced deliberately rather than collapsing into one step — set the pattern for later consolidations.