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.

The Subjunctive

January 3, 2014

As a frequent traveler to foreign lands and also as a college English major and high school English teacher, my ears perked up when a speaker said recently that there are some languages that, unlike English, do not have the subjunctive verb mood or mode. I love the subjunctive!

That’s the mood of what might have been, the speaker said. For example, “Had I studied harder, I would have received a better grade.” And “If I were you, I would have studied much longer.”

The subjunctive can also be the mood of excuses, I thought. For example, “If the official hadn’t made that traveling call, we would have won the game.” But I digress.

The subjunctive verb mood is used for the hypothetical. This makes it most valuable as a mindset before taking any action. It helps one think of unintended consequences.

But the subjunctive mood is also useful for the remedial: “If we had done this or that differently then, perhaps the result would have been better.”

Thinking in the subjunctive mood as we plan before initiatives, and then also as we evaluate after plans have been rolled out, are the one-two punch of effective project management.

What we must avoid, however, is thinking of the subjunctive as the mood of regrets. “If only I had . . .” And then doing nothing to try to change the future.

As we think about the year just past and about the year ahead, let’s use the subjunctive mood for its better purposes – planning and evaluation, not excuses and regrets.