A broader, better BlogHighEd.org

When Matt Herzberger and Brad J. Ward launched the higher ed blog aggregator BlogHighEd.org way back in February 2008, there weren’t a lot of blogs to pick from. Matt and Brad wisely limited the original list to a sweet 16.

They would add a new blog to the site every now and then, always with the buy-in of existing members, but as more higher ed types got into the blogging game in the months to follow, and as other, already aggregated sites languished due to their authors’ lack of interest, and as Matt and Brad got busier with other pursuits, it became more of a chore for them to keep the site current.

All of that changed this week, however, as Matt and Brad expanded BlogHighEd membership to 29 high quality higher ed blogs. They also weeded out the inactive blogs and updated their application guidelines to spell out minimum guidelines for member blog activity.

I’m very happy to see this expansion. Bigger isn’t always better, but with the higher ed blogosphere expanding (relatively) dramatically in recent years, I think it’s good for an aggregator site like this to incorporate more perspectives. The addition of new voices adds more value to BlogHighEd, keeping it fresher and giving blog readers more reason to visit that site on a regular basis.

Also, the way Matt and Brad run the site, consulting with existing members about new applicants, this aggregator also serves a curatorial role, offering a feed of what I and my fellow BlogHighEd members consider to be the best of the higher ed blogosphere.

So, welcome aboard, new BlogHighEd members. And if you haven’t paid a visit in a while, today would be a good day to do so. Also, don’t forget to follow @bloghighed on Twitter.

The Amazon cloud crash’s silver lining

When Amazon’s data center in Virginia began experiencing some problems last week, it resulted in a major outage for many online businesses and services that rely on Amazon Web Services (AWS) — or “the cloud,” if you will — for their data storage. This is the first major widespread failure of cloud storage, and plenty of tech bloggers have been analyzing the incident and trying to figure out what went wrong.

Over the weekend I thought about the Amazon cloud collapse in the context of a recent lecture I attended on our campus about success and failure in engineering design. The lecturer, Henry Petroski, a professor of civil engineering and history at Duke University, approaches failure from an unusual perspective, since he is both an engineer and a historian. In the talk, Petroski described the paradox of failure:

  1. Anticipating failure leads to success. But …
  2. Successful designs evolve into failures. That’s because we tend to become overconfident in our successful designs (or programs, or models, whatever is working at the time).

The cloud computing model of data storage has chugged merrily along for years. Amazon’s approach seemed to be the best model around. Foursquare, Hootsuite, Reddit and Netflix all put their eggs in the AWS basket, because it seemed like a good thing to do, and Amazon guaranteed the service. No doubt Amazon’s designers created what they thought was a fail-safe system, with multiple availability zones. The thought was that, even if one of those zones failed, others would not. But the concept itself didn’t work. More than one availability zone failed.

Back to Petroski: One of his examples was the infamous failure of the Titanic, a ship that was supposed to be unsinkable. We all know what happened to that vessel.

But Petroski posed another question: What if the Titanic hadn’t struck the iceberg? Then transatlantic voyages would have continued status quo, and more shipping companies would have followed the paradigm of the Titanic designers, and perhaps an even greater tragedy, or multiple tragedies, would have occurred later. Instead, ship designers learned from the Titanic failure and re-designed their vessels with double hulls and taller bulkheads in an effort to prevent a duplication of that disaster.

What lessons will we learn from the crash of the Amazon cloud? More pertinent to those of us in marketing, what can we learn from our own failures?

The value of failure

Last summer, after reviewing Charlene Li’s wonderful book Open Leadership (affiliate link), I riffed on her thoughts on failure in a blog post called The value of failure. I quoted a question from Li that is relevant to higher education:

In your organization, how important is it for people to be risk takers, to be innovators? If initiative and innovation are key to your future success, then you need to take a long hard look at how you personally create trust and approach failure, because it will be reflected back in the culture that you create.

“Colleges and universities tend to be mainly conservative, cautious institutions,” I wrote back then. And nothing has changed. We’re still conservative and cautious. “Not many of our leaders got to where they are by taking huge risks in their careers. And so, the culture that rewards a cautious approach is not likely to reward risk takers — especially if they fail.

“So where,” I asked, “does that leave us who fall in the middle of the org charts and who aspire to be the open leaders Li talks about? ”

I think it leaves us to take risks and give those who report to us as many opportunities to take risks as we can. We should not discourage risk-taking simply because we are in a culture that rewards caution. Moreover, we should learn to practice the art of forgiveness. To those in our organizations who take risks and fail, we should ask: “What did you (we) learn? How can this help us in the future?”

We should also take a cue from Google, which has a motto — “Fail fast, fail smart” — that would be a nice one to adopt in higher ed.

So where’s the silver lining in Amazon’s cloud fail? It’s in the lessons we learn from it. After all, we’re in the learning business, right?

* * *

Update, 11:40 a.m. CDT: This post about lessons from four famous marketing failures, via Laura D.’s Marketing for Higher Ed, provides relevant insight from the marketing realm and reminds us that not all disasters are related to engineering and technology. Sometimes marketers blow it — and blow it big-time.