Let Them MAKE Cake

Submitted by Holly on Tue, 02/13/2007 - 3:15pm.

Jason Z over at Democracy in Action has a great post today about RSS and how it works. (If you're loking for more info, we just did a great webinar with Alex Samuels of Social Signal.) Jason says in his post:

It's come to the point where nonprofit staff who aren't using RSS aren't really doing all of their job.

Jason - I agree wholeheartedly.

But what I think goes unsaid in his post is this: organizations that aren't using RSS are operating on the old model. The old model works like this. I will call this the "Let them Eat Cake" model:

Let Them Eat CakeLet Them Eat Cake

The premise behind this model is that we, as nonprofits, are special messengers. We have IMPORTANT information that NO ONE can get ANYWHERE else. You want to know what's up with the baby seals in Alaska? You come to OUR SITE. (This probably has very little to do with the actual context of the Let Them Eat Cake event, but I don't care. It made for great stick figure art). And while you're at it, give us money. After all, we are the ONLY place you can get this information, and we're the only ones who can tell you what to do about it.

The problem with this premise is that it just doesn't hold true anymore. The revolution in online publishing has meant that there are literally hundreds of thousands of web pages about baby seals. So you need a new model. One where you provide the cake recipe, and let your constituents do the baking - preferrably with their choice of kitchens and sous chefs.

And that's what RSS is all about. It allows us to mashup content from everwhere and let our stakeholders create their own experience with it.


Submitted by Jason Z. (not verified) on Wed, 02/14/2007 - 9:03am.

... for the shout. I think what you've said here is a really good way to position the higher-order issue involved, with potentially some pretty far-reaching implications for organizations. Obviously the difficulty is always getting more groups into that conversation because RSS adoption is so sluggish.

Poor as it is, I'm hoping a very basic explication of the ROI to adopt it for existing business processes convinces/cajoles/browbeats someone -- maybe someone coming to our page to log into their CRM who just bumps into it -- into stepping onto the slippery slope.