Compliance and Enterprise 2.
0 - For the right reasons
Burton Group analyst Mike Gotta writes Compliance Doesn't Sell E2.0 … But It Should in his personal Collaborative Thinking blog.
Can an enterprise leverage collaborative software like blogs, wikis and microblogging platforms and retain compliance? It can, if collaboration platforms are built in-house from selected technologies, as opposed to an all-in-one suite from an Enterprise 2.
0(E20) vendor. Enterprise 2. 0 compliance, in other words, is something best baked in from day one?
"The enterprise is tougher than consumer environments because of so many contrived regulations.
There should be higher expectations of the enterprise 2. 0 vendors to prioritize the features that will help enterprises manage compliance. "
When asked if E2.
"Nope, not yet.
It may be overkill, but spending 10 minutes with enterprise content management vendors or the IBM collaboration group exposed how little E20 has attended to this. "
I certainly agree that Enterprise 2.
And I'll claim that Traction Software really "gets" compliance for reasons that accept, but go beyond regulatory requirements.
An ad-hoc wiki used solely within an IT department may not need much more than the basics.
Boundaries that make sense, WebDAV file versioning, Page /
It's great to have wiki pages open for general editing wherever possible.
But it's also important to be able to distinguish pages that represent an agreement at a specific time - the approved budget, product specification, reseller agreement in a way that can't be confused with casual work-in-progress (or prankish) change.
People who want to be able to use wiki pages for reliable reference to the current approved budget, specification etc need to be able to distinguish the "last stable /
Traction TeamPage has permissioned activity streams - for tag clouds, search results, email digests, RSS/
"Baking in" support for these capabilities makes it possible to support wide open draft collaboration as well as "latest stable version" publication in the same collaboration space, as well as permission boundaries that disappear when you have permission to cross them but act as secure and reliable barriers when privacy counts.
Try to do this by slapping separate Social Software and ECM products together and you'll likely end up with something that works like JFK's description of Washington DC: "A city that honors the traditions of Southern efficiency and Northern hospitality.
We didn't go to all this work just to satisfy checklist requirements - I honestly believe it's what's necessary for widespread use and adoption of Enterprise 2.
For more on related TeamPage features, see:
Boundaries that make sense - Patterns of collaboration.
Permissioned activity feeds - Including tag clouds, search results, email digests as well as rss /
Moderation and work-in-progress collaboration - Enabling collaboration on content where consensus - or binding agreement - counts.
Audit Trail - Edits, tags, names, email and more.
And where this comes from Traction Roots - Doug Engelbart