Home > Uncategorized > From Enterprise1.0 to Enterprise2.0 way of working

From Enterprise1.0 to Enterprise2.0 way of working

PathOur days are filled with tasks of identifying/raising issues and develop intelligence for solving them. We work together, we talk together, we meet together to find the best solutions.

Sometimes we find that the tool set we’re using and the way they make us work/think does not make us effective in reaching these objectives. When we want to work on a document, it is locked; Trying to find info dispersed in some email boxes or hidden away in a data-silo;  Groups meeting to work together on a document with too large scope and related issues/documents, etc.

Working effectively as a group to solve complex problems have been the issue for many great thinkers through the years. In fact in our days the ideas of these thinkers precursor-ed the creation of the Internet and the World Wide Web (see: this presentation)

There is a new way of thinking and doing things, called the Enterprise 2.0, which introduces a much simpler more intuitive tool set to make the knowledge worker truly effective, with the ability to draw more on the resources of the individual and the team.

In Enterprise 1.0 we live in a world of dispersed tools like email, MS-Office documents, Intranet tools, Document Management Systems (DMS) and different other Archiving solutions. We fuel the Intranets and different web pages using a centralised Content Management System (CMS) and we gain access to information via a central Access Management System (ACS). These tool set require a complex infrastructure and support org to keep going. This Enterprise 1.0 world has proved to have certain challenges in achieving an effecient knowledge worker environment – especially with regards information/content development, handling and retrieving. We experience information silos (can’t find data due to access rights), document lock-ups, hampering access restrictions, etc. To be fair, this is also partly caused by erroneous use of tools, eg. email used for information storage/retrieval.

In Enterprise 2.0 we live in a more unified collaborative workspace, with few and simple tool set based on Hypertext model (associative linking) which is the basis for and original idea for the creation of the Internet and WWW. We suggest that the internals of a company work more like the World Wide Web. Let’s see what this can give us.

In the following we will show that going from a Enterprise 1.0 world (described above) to an Enterprise 2.0 world will massively simplify the tools and infrastructure needed to achieve the same functionality developing content, follow an issue, etc., with hopefully improved user experience

Related posts:

–> towards collective intelligence in the collaborative space

Enterprise 1.0

Expert or “the one” focus


TOWARDS
–>

Enterprise 2.0

Collective Intelligence

Scenario 1:

  • The Leader ask the “expert” to write a suggested recommendation in a document
  • The Leader and the group comment on the document
–>
Scenario 1:

  • The Leader puts some headlines (scope) out on the collaborative space and invite the group to develop comments/content on each item
  • The content emerges and improves as the group collectively work on the Information Items
  • The Leader observes the development and can direct/correct/adjust accordingly.
Scenario 2: –> Scenario 2:


Meetings:

Enterprise 1.0


TOWARDS

–>

Enterprise 2.0


Very dependent on lots of physical meetings –
need to get together to discuss in plenum
–>


A meeting can be 100 times more effective when members have met, discussed, dealt with issues, contemplated and prepared before the meeting. The physical meeting is just an extension of the electronic meeting place constantly in operation –> see this interview with Stewart Mader – author of “Wikipatterns
From Document Focus –> towards Information Item Handling

Enterprise 1.0

Print-centric documents (how do I look focus)


TOWARDS

–>

Enterprise 2.0

Content-centric information item handling

Print-centric documents

  • focus on whole document,
  • how it looks/prints, formatting, etc
  • difficult to address/link to sub-items in the document
  • home is usually file servers or document management systems
  • when one edit document, whole document is locked
–>


Content-centric information item handling

  • focus on collaborative development of information  items
  • development of content is primary, the look and print-out secondary
  • compound, associative, interactive
  • home is usually wiki spaces
  • Collective development of Information Items
  • When presenting or print-out: Collect desired information items and run through a presentation engine (eg a pdf-generator)

From EMAIL-focused work –> Collaborative Workspace

Enterprise 1.0

Living in the email, document/DMS, central AMC and centrally fed/controlled CMS world

Enterprise 2.0

Living in the Collaborative Space

Living in an email environment Living in the collaborative space
You raise an issue/question, request an action, inform, etc. by writing an email content You raise an issue/question, request an action, inform, etc. by writing an Information Item in the collaborative space
You address people by sending the email to their email inboxes You address or get the attention of people by:

  • marking the content with tags that make them appear in certain spaces or raise an action
  • people may also be notified via email, sms, etc.
The content and development of the issue resides in multiple email boxes, siloed, not “globally” accessible – dispersed/redundant and not uniquely referenced – can not address individual elements of the content The content and development of the issue resides in one place , not siloed, “globally accessible, uniquely addressed – the whole thing of it and/or the individual Information Items it consists of
Responding/Developing – you respond by sending a reply to all or reply to some. In doing so, you also expand/develop on the content of the matter. Several members may reply simultaneously. There will be different copies and versions of the content of the whole thread – some will only see parts of the content history/development. Responding/Developing – you respond by commenting on the paragraph/Information Item you need and/or by modifying directly in the content of the wiki (usually also with a moderation function). Still the changes reside with the issue in one place. Any such changes are automatically notified to involved parties
Storing and Retrieving – you can search in your email boxes/folders (one at a time) on what you have received and sent. However there may be limitations on the size of your email boxes, resulting in the content either goes into an archive or DMS or simply erased – leading to the loss of content/intelligence Storing and Retrieving – there are no imposed silos. You can search for desired content across all spaces of the collaborative workspace. Subscription content will continually be fed to you. Important issues/tasks you are currently working on will be displayed right there on the front page of the collaborative workspace.
Presenting or printing: You can print/present the whole (or the copy you have) of the email article/thread. Combining articles/threads or parts of several articles/threads is not possible except with a copy/paste operation Presenting or printing is just a matter of collecting the desired Information Items and sending them to a PDF or printer rendering engine

….

From DOCUMENT-focused work –> working with Information Items

Enterprise 1.0

Living in the email, document/DMS, central AMC and centrally fed/controlled CMS world

Enterprise 2.0

Living in the Collaborative Space

Living in an document/DMS environment Living in the collaborative space
You start content development by creating a MS-Office document You start content development by writing an Information Item (HTML-based) in the collaborative workspace
You store the document file locally (private draft) or you can share it / publish it by storing to a common folder on a file server or DMS (Document Management System) You store private drafts or publish the Item to be accessible to others
You mark the document in the DMS in pre-defined fields. Easier to find, generate views based on these metadata fields. Only whole content/document can be marked, not individual elements in the document. You mark the content with tags to categories and to make them appear in certain spaces or views or to be notified by certain people or processes. Each element/paragraph of the article can have their own tags
Marking and tagging in the DMS to pre-defined categories Marking or tagging can be user defined and structure can emerge as the project progresses
Only whole document can be addressed and referenced to. Comment on word level possible Granularity down to paragraph level can be individually addressed and referenced to and commented on.
Locking/simultanous editing: When one is modifying the document, the whole document is locked for others to modify. “Document”/Article consists of small parts (Information Items) that can be modified individually without locking. They bundle together to forms the whole document.

CENTRAL ACCESS MANAGEMENT, GROUPPOLICIES

Enterprise 1.0

Living in the email, document/DMS, central AMC and centrally fed/controlled CMS world

Enterprise 2.0

Living in the Collaborative Spac

Living in a ACM, GROUP POLICIES environment Living in the collaborative space
I don’t see this content because I’m not part of that group (anymore). Content locked in information silos. Cross-space access not based on group belonging. Open if not restricted policy. User or Information Item owner decides what to restrict. Can be specified down to paragraph level

CONTENT MANAGEMENT SYSTEM

Enterprise 1.0

Living in the email, document/DMS, central AMC and centrally fed/controlled CMS world

Enterprise 2.0

Living in the Collaborative Space

Living in a CONTENT MANAGEMENT SYSTEM environment Living in the collaborative space
Appearance on the space is controlled by a one-way feed CMS, usually centrally controlled. Publishing content is not instant. The user control what’s appearing on his space. May be coupled with departmental or central feed. Publishing is instant.
Advertisements
Categories: Uncategorized
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: