So, they were able to add a few features fairly easily. The Challenge: Build a native app on top of an existing platform.įor the tiny, but mighty team at T-Mobile working on digital transformation, it was obvious what Clips’ big phase 2 feature needed to be-podcasts. Some pain points Madsen recalls were difficulty navigating to specific episodes or continuing to play when the screen goes dark-all things T-Mobile employees expected when using Clips on their mobile devices. However, on mobile devices, the experience of audio is totally different. While Clips has a YouTube-like interface, Eric Madsen, learning technology architect at T-Mobile, attributes a large portion of the platform’s success to its integrations.Ĭlips was deployed to not only be a central repository for learning media, but also to serve content to T-Mobile employees through various channels like Adobe Experience Manager, Microsoft Sharepoint, Cornerstone, and more.īut as the team quickly found out, it was their audio content that needed a more native feel, something that was a bit more intuitive to mobile devices.Ĭlips was fine for long-form videos and presentations because most employees were viewing those on a computer.
Today, the platform has over 4,000 pieces of content and gets on average about 100,000 hits per day. That is where the five-person team developed and deployed their content management platform, Clips.Īfter T-Mobile and Sprint merged, the team saw widespread adoption of Clips throughout the company.
TMOBILE CORNERSTONE SOFTWARE
Prior to joining T-Mobile Human Resource, Stanci Soderstrom and Eric Madsen led a small software development team at Sprint. T-Mobile Digital Transformation: Giving Voice to Employees with a Mobile Podcasting Appĭiscover how a small-but mighty-team from T-Mobile Human Resources was able to build on an existing content management platform and create an app that feels native to mobile devices.
0 kommentar(er)
