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.

Students of Rules

November 12, 2013

Those who make rules ought to be students of rules. We mean this in at least the two ways this posting and the next will address.

First, rule makers should know the essence of the existing body of rules which they will be responsible for upholding or modifying during the necessary ongoing review of those rules. These rule makers should have a general awareness of when and why each rule was first adopted, how it might have evolved, how it is now applied and what the major compliance problems have been in the past or may be in the future.

This first requirement is as important for those who prepare the rules for the contests – the playing rules – as for those who promulgate the rules that establish the minimum eligibility standards and the maximum limits for competition. In the face of any proposal to eliminate or greatly modify any rule, rule makers must ask what problems may return if they remove the rule that solved those problems.

Dov Seidman writes in how:  Why HOW We Do Anything Means Everything:  “Rules, of course, don’t come out of thin air. Legislatures and organizations adopt them usually to proscribe unwanted behaviors but typically in reaction to events. They lower speed limits after automobile accidents become too frequent, regulate pit bulls after a series of dog bites, or institute new expense-tracking procedures after someone is caught trying to get reimbursed for their new iPod. Rules have been established for a reason, but most people are out of touch with the rationale and spirit of why. They don’t read legislative histories and so have a thin, superficial relationship to the rules . . .”

That is not acceptable for those who write, review and revise rules. They have to know where each rule has come from. This is why for the rule makers and for those in our member schools responsible for applying the rules day in and day out, the MHSAA keeps current “The The History, Rationale and Application of the Essential Eligibility Regulations High School Athletics in Michigan."