Friday, July 26, 2019

Digital Director - now dating again...

I started with 91.3 WYEP as Digital Director in December, 2015.

Coming from a Product Management and Web Development background, working at this radio station has been a rewarding challenge and a joy. I've been a part of a team that has moved the needle substantially in several facets of WYEP's digital needs. Here are some of our accomplishments:

  • In the first 5 months: Streaming increased 200%, Web traffic increased 70%
  • 2016-2018: increased Instagram following 200%, Facebook engagement increased 565%, Twitter Clicks, Retweets, Likes and Replies increased 200%
  • Drove improvements in productivity and communication processes, including the adoption of Slack for both WYEP and WESA.
  • Introduced lean development practices and trained staff to analyze digital metrics.
  • Identified minimum lovable product for iOS, Android and Alexa apps; Rapidly developed and successfully launched.
  • Designed and executed in-house digital video production processes for events and marketing, including design and training on best practices.
  • Created and hosted WYEP Hackathons
  • Increased streaming an additional 20% in 2018 via Alexa Skill
It's been real fun... check out this video from our Summer Music Fest: https://www.youtube.com/watch?v=HnG-5JKpaac

Or Buffalo Rose: https://www.youtube.com/watch?v=uWkniJUj4uA

Or really any of the 100s of videos on the WYEP YouTube channel. Great times with great music.

Although it's time for me to move on, I am very proud of our work, and I hope that it has set a foundation for the future success of the station.

I've got several technical articles I'd like to share, in the hopes that other non profit stations or folks with similar needs can benefit. There's more about Streaming, Headless CMS (Gatsby/Drupal), Social Media, and probably a bit about Product Management, the Voice of the Customer, and Agile Development I'd like to talk about here. Subscribe, and hit me up with any topics you would like to have me cover.

My plan going forward is to do some consulting (so feel free to hit me up). I'm also have feelers out to join an Agile product team that could use someone with my skills and background.

Friday, July 21, 2017

Ionic 2 & Exoplayer for Android

This last week I got to experimenting with Ionic 2, and the Cordova ExoPlayer plugin for Android.

The working example is posted here: https://github.com/spyderboy/ionic2Exoplayer

Monday, July 3, 2017

2017 Summer Music Fest Sizzle Reel

This year we had a lot of fun at Pittsburgh's WYEP Summer Music Fest.

Using our DJI Osmo handheld steady-cams, we shot a bunch of 4k footage.  Showing off the beautiful day, great music, and an energized crowd, this short video really gives you an idea of what it was all about.


Big props to our Digital Media intern, Owen Hipwell for capturing the essence and producing this Sizzle Reel!

Digital Technology group for nonprofit music stations

Maybe you have a problem I've already solved.  Maybe you have a solution that I could benefit from...  

Here's a public Slack group for those of us working with digital technology:

Let's talk about:
Streaming
Analytics
Apps
Video
Content Management Systems
Collaboration Software
Content Creation Software

... and more




So you want an Alexa Skill for your radio station...

Two days after my new Amazon Echo Dot arrived, I had our new Alexa Skill for WYEP working, submitted, and accepted by Amazon.

 Get the skill
It's basic.  It plays our live stream (AAC), and will tell you what song NPR Digital's Composer thinks we are playing (not always accurate, in part due to humans)

Want one for your station?  It's up on GitHub: https://github.com/spyderboy/WYEP-Alexa-Skill

Monday, June 6, 2016

WYEP's successful fundraising featured in The Current Magazine


WYEP just had a record fundraising day, thanks to our combination of on-point messaging, teamwork, and a creative digital strategy that leveraged social platforms for maximum effect.  See the article by The
Current's April Simpson HERE.

Sunday, April 24, 2016

913 Songs, 913 Tweets (almost) - Buffer/Zapier/Twitter: what worked, what didn't






Aka "How to Countdown 913 awesome songs and tweet about, with photos, from a spreadsheet."





Our listeners voted on the top 913 songs, which we then scheduled to play throughout the week as a countdown.

A while back I set up a twitterbot to tweet out songs that are now playing on-air.  WYEP DJ Joey Spehar hit me up on Hipchat, and wanted to know if we could adjust the tweets to include the countdown #:
'Here's my thinking for the countdown tweets: '#374 The Flaming Lips "Race For The Prize" || #913Countdown'

Simple request...

The thing is, our twitterbot is a hacked together mashup.  A prototype really.  It pulls information from an NPR Digital Composer playlist feed.  Our Drupal CMS ingests the feed, and posts to Twitter.

Unfortunately, the place in the countdown isn't included anywhere in that pipeline.  What to do?

When I got the countdown list from our Programming Director, it looked like this:



I have pretty much all the info I need.  I added "for the song title in column F, and added a concat function:
=CONCATENATE("#",E2," ",C2," ", F2, D2,F2,"  || #913Countdown")

Which gives me the output:
#913 Grateful Dead "Casey Jones"  || #913Countdown

How do I get these tweets scheduled for Twitter from my spreadsheet?
As it turns out, there is a great tool called Zapier, which can connect a Google Spreadsheet to your Buffer account.

The gist of our Zapier setup:
The Trigger: When a row is updated in the Google Spreadsheet
The Action: Add to Buffer Schedule

The text source is the column containing the results of my concatenate function above.  For the schedule template I used the two columns to build a human readable date: Wed 04/13/2016 10:01am -1h

The -1h (minus 1 hour) was necessary to get the time right... not sure why since the timezone was set to East Coast. (don't forget to keep a space before "-1h")

And presto... 913 songs scheduled to tweet!  Only... our level of Buffer account only allows 200 scheduled at a time.  Also, anything over 99 sends you an email to confirm that you want to do such a large job.

But how did you get all those photos in there?
I later noticed that you can add photos based on a column in your spreadsheet.  There was a quirk though... and I don't quite remember what it was.  For some reason, just adding a URL in the column wasn't working.  Instead, I wound up building the url in the Zapier template.  We used: http://bit.ly/(google sheet column).

Our awesome interns then proceeded to curate photos and enter appropriate bitly codes into the spreadsheet.

This mostly worked!  
What didn't work:  Tweets with photos larger than 3mb would fail.  There was no email notification that they failed, so I didn't notice until I checked into Buffer.  It would have been really great to get a notification when the tweet was scheduled, instead of waiting for it to fail.

Also, nearing the end of our countdown we got the sad news that Prince had died.  There was no way we could carry on counting down without taking a moment to celebrate the musical force that Prince was.

It was the last day of the NAB Show, and I was just getting ready to check out of our hotel.  But first, I thought I would check in on the countdown, and finish up the scheduling.

Our marketing coordinator mentioned something in Hipchat about preparing messaging about Prince, just in case.  What?  Eeek.  Not Prince!  I looked up the info... AP had verified that Prince had died.

I tuned into our stream, and we were playing Purple Rain.  Odd... Purple Rain was indeed on our countdown, but it wasn't at this spot.  Oh no... we are going wall to wall Prince.  I mean awesome, I love Prince. But...

Must. Stop. The. Tweet. Train.
Deleting, editing, or rescheduling a tweet in Buffer is relatively easy.  Deleting 200 tweets is not.  It requires a hover, click, confirm for each.  Man, would checkboxes be nice.  I found a bit of a shortcut, where I could tap my touchscreen where the delete button would be, and it would jump to the confirm dialog which was always in the same spot.  It was like a Twisted Candy Crush.

We managed to only publish a couple of countdown songs ahead of their actual playtime, and were able to resume the countdown without too much trouble.

All in all, the tweet scheduling was a success.  There was a big increase in impressions and engagement through the countdown.  This was a good way to provide an additional level of digital content to WYEP listeners, allowing them to share in a sense of community and conversation celebrating music.