Social Intranet – The Intersection Diagram

February 25, 2011

Often in SharePoint 2010 implementations we see Portals, Team sites and Social sites being treated as separate conceptual entities. Although they have their own merits and add specific value individually, it is in “the intersection” where we find the ideal balance of flexibility, context and business alignment for open collaboration. Furthermore, in the intersection, the user experience allow us to easily flow between the different spheres and levels of formality.

Related post: Collaboration Atmosphere  – chart


Social networks require the right balance to come to life – Collaboration Atmosphere

February 21, 2011

 

In the analogy, think of how the high gravity that exists closer to the sun and how it affects movement. The closer to the center the more rigid and formal everything is. By the same token, the further from the center, the more loose and disconnected things are.

  • Rigid: portals managed centrally, typically by the communications department. Although too rigid for collaboration, they make for a good top down (tightly managed) communication channel where central control is important.
  • Formal: departmental sites, managed in accordance to corporate structures. At this level, collaborations is structured and based on pre-defined groups. Mostly used to share managed documents at the departmental level. Regulated by the department and policies.
  • Right Balance: not too structured not too loose. Governed by an evolving culture and guidelines. Although flexible to allow for non-anticipated types of collaboration and innovation (open collaboration), it is still connected enough to the enterprise goals and existing processes to produce tangible business value. This balance varies for each enterprise or organization.
  • Loose: collaboration groups or initiatives that are still forming (emergent) and may flow towards mainstream by finding the “right balance” or drift towards the disconnected oblivion.
  • Disconnected: so loose that it becomes disconnected. This includes the sprawl of collaboration sites that are disconnected from each other and at times from the organization as well. Although benign in small scales when it grows it aggravates problems such as data duplication, data quality and collaboration silos. Typically no policy, no guidelines and no visibility.

Related posts: Content Management Formality Spectrum & Social Network – The Intersection Diagram

 


Enterprise 2.0 – SLATES Model

December 9, 2010

I am enjoying reading Andy McAffe’s “Enterprise 2.0” book. Here is a bull-eye type chart illustrating the SLATE concept (Search, Links, Authorship, Tags, Extensions, Signals) that summarizes what he calls the “Emergent Social Software Platforms” (ESSPs).


Content Management – Formality Spectrum

December 7, 2009

Related post: Collaboration Atmosphere


Enterprise 2.0 Implemenation Framework

December 6, 2009


Vacation appreciation

August 30, 2009
With adhoc vacations days, appreciation for freedom stays high. This is why I love taking vacation days sporadically… or work sporadically during my vacation.

Cloud Computing Paradigm Chart

August 4, 2009

After reading the NIST working definition of cloud computing, which made things more objective to me, I created this chart to provide a visual representation of the different concepts.

Maria Spinola’s white paper, “An Essential Guide to Possibilities and Risks of Cloud Computing“, does a great job covering the major points and is a great reference.

[Update – Feb 2011] A modified/updated version of my chart has been included in the NIST – Presentation on Effectively and Securely Using the Cloud Computing Paradigm v26 (thanks @petermmell).



%d bloggers like this: