The evolution of hubs – from Wes to Wordpress

by jbreazeale on February 10, 2010

Rusted Hub
Image by Thomas Hawk via Flickr

Anytime you’re trying to organize, coordinate, and communicate with more than two people over more than a few days, you’ll realize that relying on email (or Facebook, or Twitter) to carry the burden will drive all of you crazy. Someone’s going to miss a message, the “right” people won’t be cc’d or (worse) everyone will be cc’d. On every message. Good times.

After a few of these “I can manage the whole thing via email” disasters, hopefully you’ll start to realize that a centralized “hub” for your team / project / organization might just save your sanity.

A Brief History of Hubs

Then came the “quality” movement and its efforts to quantify and codify the information available from the Wes’s of the world. “Sure, you could go talk to Wes, but we can’t all talk to Ted at the same time, so let’s just write down what Wes said and then we can go back to that the next time we have a question.”

Note: This would have been a great time to buy stock in three-ring binder companies. Especially the really, really big three-ring binders.

And, just as everyone was becoming comfortable with their bookshelf o’ binders, along came the internet and widespread use of personal computers. In the (ultimately futile) quest to become paperless offices, documents were scanned into “document management systems”, we created our “shared drives” and uploaded files to our corporate “intranets” and suddenly all workers had access to all the information they needed, right?

Not quite.

Now, not only had the information been separated from its human hub (which could interpret context and apply judgment), we’d added more layers of bureaucracy and abstraction. A two-minute call to Wes had been replaced by “where’s that #!@* procedure on the intranet? … No, not *that* version, the *new* version…. What do you mean I have to send it to X to get it approved so that Y can post it? … Never mind, I’ll just find that email that A sent me, I think that was the current version…”

Ceramic unicorn

Unicorn (via ffffound)

So, if bureaucracy was the problem, then the solution must be self-service, right? Enter the wiki. Now everyone can create their own content and make it available to others who can then edit and improve and contribute and then, in the magical land of unicorns and rainbows, we’ll have a dynamic and robust source of institutional knowledge and tribal wisdom and we’ll all live happily ever after….

Well, I don’t know about you, but I haven’t seen too many unicorns lately.

The great wiki experiment has had some notable successes (um, Wikipedia anyone?), but outside the realm of technologists and large organizations (who have lots of those technologists), I think the usefulness of wikis has peaked. If I want to share information with my friends, I use Twitter or Facebook. If I’m working collaboratively, I can use Google Docs (or perhaps Google Wave), or a variety of 37signals products. And, if I’m going to organize, coordinate, and communicate with a specific group of people, I’m going to use Wordpress.

Coming soon: From Wiki to Wordpress (why we’re making the switch)

{ 1 comment }

The power of simple

by jbreazeale on October 7, 2009

Enso, the Zen Circle.

Image via Wikipedia

I added a Contact page and form to my blog last night. (It’s a work in progress, but feel free to stop in and say Hi!)

I’ve been meaning to add one for awhile and had played around with a form or two, but nothing seemed to stick. So, what finally got me moving?

Four sentences from a blog post:

So, I went to Google Docs and started a new form. File>New>Form. I put in the categories that you see when you see my contact form. Then, I save the form with a template. Finally, I wrote a new WordPress page called “contact” and embedded the form into it (copy/paste level of difficulty).

In ~50 words, I know what steps to take, how many steps there are, an approximate level of difficulty, and therefore about how much time it would take.

The result? One hour later I had a live, working form on my site.

When faced with an unfamiliar task,  we’re often presented with either an obsessively detailed checklist or a hopelessly vague idea – both of which inspire a distinct feeling of dread and almost always cause preventable delays.

What are you doing to find the middle ground?

{ 0 comments }

A few tips for those outside of the "enterprise"

by jbreazeale on January 27, 2009

Skyscrapers, Tokyo, Japan

I’ve worked for companies with various ranges of accessibility to “The Internet”, but my recent tenure in the uber-locked-down-enterprise-financial-services realm has been a real eye-opener. And if you’re working with people (customers, clients, or even friends/family) who are in the enterprise realm, here are a few things to consider:

1. Not everyone has webmail.

If you’re working with your client on a project for their organization, then by all means, use their business email. These centralized systems are often setup and maintained for a variety of regulatory purposes, so use them. For side projects or personal communication, stick to personal email addresses just realize that it may take longer to get a response.

One more thought on this… For all of you with a “contact us” form that generates an email from the user (as opposed to a fill-in form), not everyone can or is able to use work email systems for non-work purposes. So, when that blank email pops up, you may have just lost that customer. Better to give multiple options for contact, even if they eventually lead to the same place (contact form goes to jane@janedoe.com, or email to jane@janedoe.com).

2. Not everyone has Google.

<gasp>

Ok, I don’t actually know anyone who doesn’t have access to Google’s search functionality, but many people may not have access to Google’s services such as Gmail (see webmail note above), Gcal, Reader, etc.  Keep this in mind when creating “shared” calendars or project files that involve enterprise workers.  You may have the best “Church picnic planning list” in history, but if you’re sharing it on Google Docs, not everyone will be able to see it as quickly as they might have if you used a different service.

3. Not everyone has an RSS feed reader.

I know, there are lots of enterprise services out there – some you might even be able to install without going through tech support hell – but who wants to maintain two (or more) sets of readers? Google Reader for home, Attensa for work? Nah, too confusing and too time consuming to keep them in sync. This means that, for those of you who blog, add an email subscription option for your feed! It’s free and easy.

4. Not everyone has an easy way to share non-work info.

As far as I can tell, delicious.com still works behind the firewall and it’s a great option for maintaining your own bookmarks or sharing with other users who are actually using delicious.comTwitter’s another great option for sharing with users who are actually using Twitter.  Same with Digg, FriendFeed, Tumblr, etc. How are you enabling users to share your content? Can they email as well as using the common social services to share info?

Coming soon: Enterprise-friendly applications for those in lock-down

{ 0 comments }