I attended a seminar by Edward Tufte recently. He said something that really stuck with me: “clutter and confusion are not attributed of information; they are a failure of design”. Tufte also discussed why websites should not be the traditional tree-like hierarchy, but rather a “cloud” of information with many thoughtful, intuitive paths to information.
In other words: why force people through some clumsy hierarchy?
The best example of this that I can think of is Wikipedia. Wiki encourages people to create links to other articles, and the result is anything but a hierarchy; it’s more of an informational “walk in the park” that goes from topic to logically connected topic.
It’s brilliant.
So where does Sharepoint come into this? It doesn’t, except for the fact that I’m doing some Sharepoint training right now, and it’s entirely counterintuitive to Tufte’s methodology (which I happen to agree with very much).
For instance: we create sites within sites. Just getting to the project or group site you’re looking for generally means starting at the top and drilling down, or using the largely incapable search bar that never seems to be ‘tuned’ properly (that’s tech-speak for “we can’t figure out how the fuck to make it work”).
My second beef with Sharepoint is the married-at-the-hip interconnectivity with Microsoft Office. Large corporations who drink straight from the Microsoft teat may see this as an advantage, and the armies of drones (clerks) in accounting departments will love the idea of staying in Excel.
Think about it, though: the whole point of web 2.0 is to cut the umbilical cord connecting us to fat applications like Office. A web application that simply reshuffles the 25+ year old methodology of disparate files created using locally installed application and stored in kludgy, unindexed local file systems is a bit like designing modern cars around the driving paradigms of a Ford Model T.
Yes, it’s comfortable. Yes, the drones all know how to use Microsoft Excel and are very capable of saving things on floppy disks.
And does it move us forward? Not one iota, unfortunately.
Wikipedia allows users to create rich, indexed, hyperlinked content with a simple markup language compatible with any web browser on the planet. True, you can’t create spreadsheets in Wiki, but I’m also guessing that it’s a fairly short leap from Mediawiki-style collaboration to rich web applications like Google Spreadsheets and Writely.
And before you ask about mobile devices that don’t always have network connectivity? I can’t think of a better place to implement an open standard for document exchange - open standards that would facilitate a variety of productivity applications.
We can boil this down to three basic ideas:
On choice: Microsoft not only does not give us choice, but it actually totes the deep interconnectivity between Sharepoint, Office, SQL Server and Windows Server 2003 as an advantage. To that end, none of these products would be considered the best-of-breed in their respective industries; do we really want to weld our methodologies to these non-standards-based proprietary applications?
This smacks largely of FUD - and it works. After all, they certainly didn’t build their multi-billion dollar monopoly on quality.
On enablement: Sharepoint’s rigid hierarchical paradigm is mired by an impossibly incapable search utility (to that point: I’ve yet to see a Sharepoint search bar that actually returns consistently good results. They may exist, but they’re certainly elusive), and a frighteningly archaic adaptation of hierarchical file structures into a pretty web-based front-end. There’s nothing enabling about this, and I can imagine the same endless file repositories kludging up corporate Sharepoint portals that clog up corporate network drives today.
On Lateral Thinking: As I said above, Wikipedia is a remarkable departure from how we manage information in a traditional corporate network, and it works. It has millions of pages and millions of users, and it facilitates the information, the ecosystem and the culture into a wonderfully elegant web application that requires nothing more than a web browser. Writely and Google Spreadsheets take a different approach - leveraging the best of client-side web scripting to replicate the functionality of traditional fat applications in a web browser window - also with decidedly non-exotic technologies on the client side.
These are all examples of thoughtful and resourceful use of the tools - instead of shoehorning old paradigms into a new software box and wrapping it in a thin veneer of web technology that doesn’t work that well in non-IE browsers.
I’m all for innovation and competition and the free-market, but I still don’t get Sharepoint.