The Social Setting

March 18, 2014

One week last month our local Big Ten head men’s basketball coach blasted Twitter. The following week Iowa’s head coach, arguably the coach with the league’s worst sideline decorum (and that’s saying a lot for a league that’s allowed its coaches to get out of control) said his players are henceforth barred from tweeting.

Between these headlines was one of more significance: Facebook announced that it would be paying $19 billion to purchase WhatsApp. Which means social media is here to stay. And everybody, including big time basketball coaches, needs to deal with it in better ways than merely blasting it and/or barring it.

What it means for an organization like mine is that everything we do needs to be considered in all the usual goals, objectives and strategies progressions, and that at least one progression must have social media as an outcome and almost all progressions must have social media as a tactic.

Just over a decade ago we realized that almost every task we have has an information technology component. We discovered we needed our IT staff in the room when new projects or protocols were being considered, when new policies were being developed, and when all sorts of problems were being addressed. Fail to involve IT personnel soon enough or at all, we learned, and failure of the enterprise was assured.

We are at the same point today with social media. If we neglect the social media component – fail to consider how to use it to the advantage of the project or fail to consider how adverse social media could doom the project – we operate with at least one hand tied behind our back.

Just as the IT staff have needed to be consulted, and listened to, in order for the enterprise to reach its potential, so must our social media staff have a seat at the table and a voice in the discussion of anything of consequence we might think we should do.

This is as true for nonprofit organizations as it is for profit, for small organizations and large, both private and public.

Oyster Stew

November 13, 2015

Jonathan Swift, an 18th Century writer I was introduced to as an English major in college, grabbed my attention and loyalty with the statement, “He was a bold man who first ate an oyster.”

I’ve hated oysters for their look, their texture and their taste; and also because, as a child, oyster stew was the Christmas Eve fare that stood between me and the time when we could begin opening presents under the Christmas tree.

But I have loved Swift’s metaphor.

Imagine the courage – or the desperation – of the first person to eat an oyster … or any other ugly, slimy critter ... raw!

But it is often this person, bold or desperate enough, who looks past appearances to tackle something of such unpleasant prospects, who actually makes the discovery or connects the dots or makes the breakthrough necessary for real progress.

What are the most unappetizing issues before us? Transfers? Football scheduling? Specialization? What unappealing solutions might we be avoiding because they look so awful? Are we bold enough to take a bite out of them?