Showing posts with label Business. Show all posts
Showing posts with label Business. Show all posts

Wednesday, November 24, 2010

SharePoint Adoption

Economics of Information noted a recent survey showing business users by and large ignoring Microsoft’s structured file sharing service, SharePoint.  They ask why people still use email to collaborate, despite its nominal inefficiencies.  Here are my thoughts based on my experiences in the finance industry:

  • Disclosure matters.  Having a simple, understandable-by-a-judge document that says A sent X to B on such and such date is critical on a number of levels.  It can prove whether a contract was respected or violated or whether or not a department or employee did it’s job correctly or incorrectly.  And yes, intra-company conflicts are no less bloody or consequential even if lawyers are not involved.  SharePoint nominally accomplishes this, but with more ambiguity.  Say a file changes, how do people know what changed and whether it’s pertinent to them?  How do you set policy so that you even know whether everyone knows that a file changed?  Unless you are very, very careful in how you set policy you lose knowledge about disclosure.  Most managers don’t have time to figure that out and won’t take the risk in adopting something could reduce their control of process.
  • Collaboration in the creation of office documents is over-rated.  Most technical documents have a two step life.  An analyst level person creates the document and a manager reviews and makes changes as necessary, and it’s done.  When I have seen manuscript type documents where you need multiple managers reviewing/editing a single document, it’s almost always a formal sign-off process where you need documentation that everyone reviewed and approved.  I could imagine SharePoint doing that but again you’d need a lot of policy work to automate the documentation, this time cutting across departments.
  • Another note on collaboration- I’ve had SOX auditors tell me they don’t like seeing office documents involved in material financial calculations at all.  I can’t imagine them being comfortable with something that introduces even a shred of additional ambiguity.  SOX compliance is another reason managers are probably reluctant to change process.

All of this is to say that you need a lot of policy work to control notification and documentation of such.  That can be done but requires an investment of time by managers, and the payoff compared to using email doesn’t cut it.

If I were running a startup I’d demand people use a structured file system with lots of opportunity for markup information (what is this, what does it pertain to etc.) and I’d expect businesses that use it to have a considerable advantage down the road (how much time do you spend trying to untangle the work of predecessors?)  I would not expect established businesses, especially big ones with lots of history, to lead the charge.

Sunday, October 3, 2010

Bad Documentation = World of Pain

Just when you thought the real estate market couldn’t get more screwed up along comes this.  And it’s corollary, this.  Managing documentation is not rocket science.  It’s kind-of sort-of legally required when it comes to numbers through Sarbanes Oxley.  So why is it that big companies still get caught with their pants down like this?  Sound business processes- don’t leave home without them.

Saturday, April 19, 2008

Excellent Cringely column/podcast

Cringely has an excellent column and associated podcast up dated 4/18.  His thesis in a nutshell:  Most IT consultants don't know what they're doing, and trusting such people can destroy a company.  What he doesn't say is that many internal IT departments are no better then consultants. 

The fundamental problem is businesses that don't know what they're doing.  What is the average duration of employment for someone with a given organization, maybe 5 years?  How long does it take to understand all the nuances and tricks, to know what is real and what is merely label?  One year, at a minimum. 

Now add a level of complexity:  how long does it take to gain sufficient mastery to be able to explain these intricacies to someone else?  It's the difference between being a student and being a teacher.  I'd say another year, easily.

So in a given company, at least 20% of the people don't know what they're doing, and another 20% are probably doing the right thing but couldn't tell you why.  Throw in the fact that most of these 40% will not self identify, and it's no wonder requirement gathering sucks! 

Cringely cites a successful consultant, Christine Comaford-Lynch:

A key part of her success was her requirements gathering process. She turned it into a very effective collaboration effort involving the key people who would use the software.

Sounds to me like she was good at separating the wheat from the chaff.