"SharePoint The Reality Series 4: Benchmarks for success" by Marc Solomon

KMWorld.com HomeBack in May, I posted about a couple of articles on “SharePoint: The Reality Series” that Marc Solomon had written which included some quotes from a discussion I had with him back in January.  Marc was kind enough to ping me today about a new installment in the series.

Marc Solomon

This installment is entitled SharePoint The Reality Series 4: Benchmarks for success and includes more from that January conversation, or as Marc called it today, “the interview that keeps on giving”. I must have kept my lips flapping pretty fast if he got all of this from the one conversation!

Once again, I sort of like what I said, so here are some snippets.  Of course, there’s lots of other good stuff there, so read the whole article.

First of all, here’s what not to measure. According to Marc Anderson of Sympraxis Consulting, it’s not about documents. It’s about accomplishing goals in a better way and evidencing SharePoint as a catalyst. “It’s one thing to have a mission and a goal structure. It’s another thing to create a welcoming climate for breaking old habits,” says Anderson. “Some of this is sound engineering. Most of it is cultural.”

Storytelling is more powerful than setting mandates. Anecdotes count. Colleagues, otherwise siloed, reach out to each other—not to be social but to jumpstart a project. “Was SharePoint an enabler?” asks Anderson. “If they both say it was a factor, it counts.”

 

One important metric worth minding is how well SharePoint-hosted content travels over local and wide area networks. According to Anderson, SharePoint does not have a good story to tell as a global software platform: “It can crawl long before it learns to walk over a global LAN or VPN,” cautions Anderson. SharePoint is not replicated all over the world. It lives behind the firewall and can bury a server on an underperforming network with a ballooning database. Documents are the common language of SharePoint, and SharePoint doesn’t make them any smaller.

 

Ironically it’s a simple thing to make SharePoint available through authentication through a secure IP address. The holdup comes from a misplaced insecurity about the crown jewels (access to SharePoint-hosted intellectual capital). The absurdity for Anderson is this: “Your firewall blocks Twitter and YouTube but everyone has a Blackberry. What did that accomplish? It takes longer for people to do their jobs!”

 

The ultimate power of SharePoint stems organizationally from what Marc Anderson terms that “one version of the truth thing.” 

“SharePoint: The Reality Series” by Marc Solomon

KMWorld.com HomeI was just vainly searching myself on Google (in the context of playing with https://vizibility.com, so it’s not that bad), and I ran across two articles by Marc Solomon at KMWorld.com  that had quotes from me.  I had talked to Marc back in January, and pretty much had forgotten about it. Marc is very active in the Boston area knowledge management community and I seem to run into him in one context or another every few years.

Marc Solomon

The two articles are SharePoint: The Reality Series: On the hook: the SharePoint ownership imperative Part II and SharePoint The Reality Series: Laying the foundation for your next SharePoint deployment

If I had seen them before, I’m totally blanking on it, and I sort of like the quotes from me that Marc ended up using.  Read the articles for the full context, but here are the snippets.

From SharePoint The Reality Series: Laying the foundation for your next SharePoint deployment:

To Marc Anderson of Sympraxis Consulting, the first misstep is refusing to walk the walk. “The guy who gets religion needs to start practicing it,” he says. Deploying SharePoint successfully means rolling out metrics and measuring your people against them, so that every arrow and line points from pre- to post-implementation. “I’m behaving differently because I see the benefit,” Anderson says.

Architects by nature have to see the bigger picture. The problem with putting IT administrators in charge is that they miss the real workflow between organizations. They look at SharePoint and see a top-down hierarchy. “If your project manager is more concerned about full disks than empty sites, you’ve got the wrong guy in charge,” Anderson maintains.

and from SharePoint: The Reality Series: On the hook: the SharePoint ownership imperative Part II:

“If you look at SharePoint as software, you’re asking for rejection,” says Marc Anderson of Sympraxis Consulting (sympraxisconsulting.com). SharePoint happens to be an ECM tool, but it’s also a work environment. “If it was as simple as flipping a switch, then everyone in the organization would remove e-mail from their company-issued computers and go live on SharePoint,” says Anderson. “Who’s ready on day one for that release?”

But that transparency takes vision. Architects by nature have to see the bigger picture. The problem with putting IT in charge is that they miss the real workflow between organizations, says Anderson. They look at SharePoint and they see a top-down hierarchy. What they miss is its silo-busting potential for routing requisitions and managing critical tasks that falter from one unit to the next. Business managers who route job postings through HR provide a good example of where SharePoint, not e-mail, is the better choice to handle cross-unit tasking.