IBM COMMUNITY RADIO
TL;DR: I co-founded and branded IBM Community Radio, a side–project–turned–platform for critical thought, culture renewal, and good music. I prototyped the initial front–end player/schedule interfaces, co-ordinated formative on-air content, and educated folks on how to get up and running quickly on the network. I also, in typical fashion, guerilla advertised the hell out of the first live broadcasts, and earned us our initial notoriety.
As of November 2016, IBM Community Radio has been cited as reaching “...between 5,000 and 6,000 people [within IBM] daily.”, according to Fast Company.
A quick demo of beta functionality as of November 1, 2015:
Throughout 2015, Miroslav Azis and I had been bouncing back and forth the idea of emancipating our fellow designers from the shackles of our hyper-corporate day-to-day at IBM. Manifesting through a series of community-organizing projects which fizzled out one after another, we codenamed our efforts 'Grand Unification Projects'.
One day, as we mused on other ways to self-organize within a massive corporation, Miroslav mentioned something along the lines of “Building an NPR for IBM”, and we knew, at that moment, what had to be done.
Miroslav had been able to quickly coordinate the aquisition of a physical server in Raleigh, from which we installed a general-purpose streaming software, and admin interface to queue music. We had the engine, and a method of queuing tracks, but there was no interface whatsoever that represented the content being delivered, or what the heck the entire operation was at all. I remedied this quickly, by spinning up a static page in our enterprise Github and linking it to the server–serving–music. It looked like this:
As indicated by the copy, I was clearly in need of some help. A friendly developer, Devan, helped us out with a rapid v2 that switched out my static link into a play/pause button:
Devan also introduced a horrifying gradient at this time, but I was okay with this — our radio was still in its infancy, and we were moving fast. I spent a good chunk of time soon after Devan's additions playing with some interfaces I thought would set us in a good direction. All the while, we were revolving through a small set of DJs (ourselves included) who were interested in broadcasting over many lunches, to test our systems. It was soon after our latest version that I began to explore methods of branding out our work, and giving further character to it.
I was heavily inspired by the twisting of our existing design language — up until this point, the efforts of distinguishing IBM's visual design were very much in flux, and it wasn't exactly kosher to fuck around with the elements sanctified by our Global Branding teams, our logotype included — I was drawn to the extending of the 8-bars that constituted the “I” in “IBM” and turned them on their side, representing them as EQ bars. It was around this time that I had begun to plug static designs into prototyping tooling (Framer primarily) and give them life.
While extending the functionality of designs was nice, I felt that what we most needed at the time was an actually usable front end for our radio, so I began the task of dusting off my abilities and prototyping the radio interface of my dreams in Codepen, which was much more responsive and design friendly than editing static files in Github. I ended up with this:
Soon after this prototype was completed, our tiny radio admin team was bolstered by the efforts of 5 full time developers, who had been hunting around the Austin studio for a hack project they could finish up in a week. More quickly than we had ever imagined, our radio began to take form, and was soon equipped with the ability to log into the player itself and provide set/track titles, which were then archived.
As we reached a proper “Version One”, we managed to secure funding for the purchasing of the broadcasting software for other IBM Radio stations around the world, and had begun to structure out how radio programming would operate. Soon after these initial