It’s nearly twenty years ago, now, children. Facebook had only recently burst the bounds of Harvard Yard. Twitter had just slipped the bonds of the digital underground. But web geeks like me still saw “social media” as a continuation of the older digital networks, protocols, listservs, and discussion forums we’d come up using, and not as the profound disruption that, partnered with smartphones and faster cellular networks, they would soon turn out to be.
So when world-renowned CSS genius Eric Meyer and I, his plodding Dr Watson, envisioned adding a digital discussion component to our live front-end web design conference events, our first thought had been to create a bespoke one. We had already worked with a partner to adapt a framework he’d built for another client, and were considering whether to continue along that path or forge a new one.
And then, one day, I was talking to Louis Rosenfeld—the Prometheus of information architecture and founder of Rosenfeld Media. I told Lou about the quest Eric and I were on, to enhance An Event Apart with a private social network, and shared a roadblock we’d hit. And Lou said something brilliant that day. Something that would never have occurred to me. He said: “Why not use Facebook? It already exists, and that’s where the people are.”
The habit of building
Reader, in all my previous years as a web designer, I had always built from scratch or worked with partners who did so. Perhaps, because I ran a small design agency and my mental framework was client services, the habit of building was ingrained.Â
After all, a chief reason clients came to us was because they needed something we could create and they could not. I had a preference for bespoke because it was designed to solve specific problems, which was (and is) the design business model as well as the justification for the profession.Â
Our community web design conference had a brand that tied into the brand of our community web design magazine (and soon-to-emerge community web design book publishing house). All my assumptions and biases were primed for discovery, design, development, and endless ongoing experiments and improvements.
Use something that was already out there? And not just something, but a clunky walled garden with an embarrassing origin story as a hot-or-not variant cobbled together by an angry, virginal undergraduate? The very idea set off all my self-protective alarms.
A lesson in humility
Fortunately, on that day, I allowed a strong, simple idea to penetrate my big, beautiful wall of assumptions.
Fortunately, I listened to Lou. And brought the idea to Eric, who agreed.
The story is a bit more complicated than what I’ve just shared. More voices and inputs contributed to the thinking; some development work was done, and a prototype bespoke community was rolled out for our attendees’ pleasure. But ultimately, we followed Lou’s advice, creating a Facebook group because that’s where the people were.
We also used Twitter, during its glory days (which coincided with our conference’s). And Flickr. Because those places are where the people were.Â
And when you think about it, if people already know how to use one platform, and have demonstrated a preference for doing so, it can be wasteful of their time (not to mention arrogant) to expect them to learn another platform, simply because that one bears your logo.
Intersecting planes of simple yet powerful ideas
Of course, there are valid reasons not to use corporate social networks. Just as there are valid reasons to only use open source or free software. Or to not eat animals. But those real issues are not the drivers of this particular story.
This particular story is about a smart friend slicing through a Gordian Knot (aka my convoluted mental model, constructed as a result of, and justification for, how I earned a living), and providing me with a life lesson whose wisdom I continue to hold close.
It’s a lesson that intersects with other moments of enlightenment, such as “Don’t tell people who they are or how they should feel; listen and believe when they tell you.” Meet people where they are. It’s a fundamental principle of good UX design. Like pave the cowpaths. Which is really the same thing. We take these ideas for granted, now.
But once, and not so long ago, there was a time. Not one brief shining moment that was known as Camelot. But a time when media was no longer one-to-many, and not yet many-to-many. A time when it was still possible for designers like me to think we knew best.
I’m glad a friend knew better.
Afterword
I started telling this story to explain why I find myself posting, sometimes redundantly, to multiple social networks—including one that feels increasingly like Mordor.
I go to them—even the one that breaks my heart—because, in this moment, they are where the people are.
Of course, as often happens, when I begin to tell a story that I think is about one thing, I discover that it’s about something else entirely.
12 LESSONS from An Event Apart San Francisco – ? 1: 
