New year, new voices.

New year, new voices.

Back in December, we told you about some upcoming changes in our blog.  In the next few weeks, you’ll begin to see some of those changes.  We’re really excited about what the updated blog will allow us to share with you (and vice versa). You may remember that we took a little bit of our new digs to CES this year.  We were blown away by the response we got.  So, we’re going to bring some of that personality to our online presence.


We’ve made a big deal out of our Nashville home.  

More great photos of our booth at CES and the people who made it awesome

The energy, vitality and creativity that have lead to so much of American music’s being created within 10 miles of our offices is reflected in more than 200 Griffinites who work in Nashville or our offices around the world.  We want you to hear from them.

We’ll be introducing a chorus of new voices (yeah, sorry, the bad music metaphors just write themselves sometimes) in the coming weeks.  We’re going to share some of the massive tech wisdom that’s been building in Tech Support for the last twenty years (their wiki is an awesome thing to behold, though rumors of its sentience are somewhat exaggerated).  The conversation gets pretty interesting around here and we’d like you to join in.

The social media landscape is changing fast.  And Griffin’s changing with it.  Since launching back in 2008, we’ve blurred the lines between content, tech support and outreach … the whole task of social media is becoming more widely distributed through the company.  We’ll be introducing a new curator for our online presence and a host of new contributors in the upcoming days. 

We’re proud of the vibrant online community we’ve created over the past few years.  And we’re looking forward to what the new year will bring. We hope you like what you hear.

2 responses to “New year, new voices.”

  1. When it says posted by Web does it mean the Internet wrote this blog post?

  2. D’oh!  We’re rolling out new authors for the blog and Twitter responders over the next few weeks.  We don’t want to loose the juice that our current “griffintech” has and muddy the water with multiple Griffin-related handles, so signing our work with a ^FirstName seems like a good option.  While it won’t be a problem for people like ^Michael or ^Rachel, say, it does seem to point out an issue with me (Web Webster).  Maybe ^WebWebster confuses less?

Leave a Reply