sociallayer - Bertrand Duperrin on Diigo

Mar

15

2012

Enterprise Software Architecture: a Network of Services, Not a Layered Stack - Forbes

"Social networks are a hot topic in the enterprise these days, despite being only one type of network deployed in a networked business. Many individuals and companies are talking about creating a ‘social layer’ in the enterprise and how that layer needs to be ‘woven’ into the ‘fabric’ of the enterprise. I’m not exactly sure what that means, but I do know that layers is the wrong metaphor for enterprise software, especially for front-office categories such as social software."

www.forbes.com/...f-services-not-a-layered-stack

- Preview

socialnetworks sociallayer socialintranet socialmedia socialsoftware software

Layers of anything are hierarchical. A layer can only interact with the other layers on either side of it. A software user interface layer can’t directly integrate or interoperate with layers below the one upon on which it sits.
7 more annotation(s)...
- Network architecture, on the other hand, eliminates the need for middleware and other intermediary layers. Any application or functional service can directly connect and interoperate with another through open APIs and standard protocols. Network architecture is more efficient and flexible, as well as less expensive, than traditional stacked enterprise IT architectures.
- Because of its hierarchical design limitations, the layer metaphor has never been successful in the marketplace for enterprise software. In the early 1990s, workflow software providers collectively positioned their offerings as an orchestration layer in which business analysts could sequence the interactions with the multiple back end systems business people used to do their jobs.
- The pure-play vendors that survived repositioned their offerings as workflow ‘engines’ that could integrate with any platform.
- This pattern repeated itself a decade later, when the enterprise portal software market rapidly consolidated despite predictions of robust future growth.
- Enterprise social software will largely cease to be packaged and sold as applications and suites, unless those are offered by platform providers as part of their broader range of integrated software solutions
- Think of each bit of enterprise software functionality as a service node in a network. Multiple services (functions) can be combined to create a purpose-built application that addresses a targeted use case, aiding a worker in a specific role to perform his job, or helping a customer or business partner to carry out a specific interaction with the organization. Many different, tailored applications may be created by connecting different nodes of functionality residing in the same network.
- it is time to stop talking about enterprise software layers. Instead, we should think in networked business terms and treat software functionality like networked nodes that may be fluently, even dynamically, related to each other

May

17

2011

Making An Intranet More Social

"Offering a handful of limited social tools in a corner of the intranet is missing not only the more significant opportunity to unleash the untapped potential of enterprise intranets, but it will likely be soundly rejected on the ground by a growing percentage of today's workers. Instead, organizations should be planning for a fundamentally social intranet. "

www.ebizq.net/...ng_an_intranet_more_social.php

- Preview

intranet socialintranet adoption intranet2.0 sociallayer

They realize it can enable self-service and unleash an organization to share knowledge and work together in powerful new ways. It also makes it very easy to connect the organization's knowledgeable experts to those that need to know, while using what I've started calling stored collaboration to ensure that this process scales and is highly time and resource efficient..
5 more annotation(s)...
- Even better, the concerns about trust and control over social media, particularly internal use, continue to fall by the wayside.
- Now the question that I'm seeing asking more often is how to go beyond social media lip service and integrate it more deeply into the fabric of a modern intranet.
- 1. The core intranet based on a social suite. Legacy Web-apps located elsewhere on the network with lightweight integration
- 2. The social intranet is divided up into two social platforms that each have unique functions and strengths.
- 3. The social intranet is delivered via a social business suite with all or most intranet apps running within it

Jan

5

2011

Enterprise 2.0: A Transition From Destination Site To Platform Services

"Detail: In general, the first wave of Enterprise 2.0 was arguably tool-based (e.g., stand-alone blogs, wikis). The second wave of Enterprise 2.0 focused on enabling an enterprise-wide destination (e.g., a “Corporate Facebook”) which acted as a community and connectivity hub for employees. More accurately, we might describe this type of platform as a social network site (Reference Architecture For Social Network Sites). The third wave of Enterprise 2.0 is moving in two directions virtually in parallel to each other."

mikeg.typepad.com/...site-to-platform-services.html

- Preview

enterprise2.0 applications platform services socialnetworks businessapplications integration processcentricity workflow sociallayer

The initial direction is to support social applications hosted on the social network site itself. The most common examples I’ve seen so far are innovation/ideation solutions but organizations will likely want to construct their own community-like applications on top of their social network site as well.
This horizontal trend is the second direction within this third wave of Enterprise 2.0 implementations. Social networking services will enable organizations to take social data within the social network site and surface that information contextually within another system (e.g., productivity suites, collaboration tools, enterprise portals, business processes, and mobile applications).
1 more annotation(s)...
- The recent discussions within the Enterprise 2.0 community have indicated that E2.0 should have greater process-centricity (e.g., integration with CRM, ERP, supply chain, etc). This type of pragmatic approach is more doable as vendors in this space prioritize API's to integrate "social" into the flow of work and adding a social layer as many have argued.

Dec

20

2010

More On The McKinsey Study: Integrating Into Workflows May Pay Off The Most - Rawn Shah - Connected Business - Forbes

"Yet, Fully networked organizations achieved substantially more benefits–a mean of 27%–compared to 15% for Externally networked, and 12% for Internally networked.

What makes Fully networked organizations drive almost twice value of the other two networked organizations despite having very similar demographics?

The only driving factor that I can see from the second table in their report is the level of integration into the various day-to-day tasks of the constituents in each category"

blogs.forbes.com/...workflows-may-pay-off-the-most

- Preview

networkedorganization process workflow integration value socialbusiness enterprise2.0 socialnetworks sociallayer

70% of Fully networked organizations indicate that Web2.0 is integrated into their day-to-day tasks, compared to 53% for Externally and 49% for Internally networked organizations. I
Long story short: the degree of how social business is integrated into the workflows of your organization may be a strong driver of business benefit and the success of your Enterprise 2.0 effort.
4 more annotation(s)...
- This raises an interesting debate: should collaboration technologies be a separate vertical stack of tools with links to and from existing tools? Or, should they be an integrated horizontal layer directly within the enterprise applications?
- As a vertical add-on, you can keep discussions and tacit information separate from the repositories of the enterprise applications. Employees then paste in links or referencing identifiers to content on the enterprise apps.
- Integrating collaboration as a horizontal layer into the enterprise app incorporates new data types such as conversations, tags, comments and other collaboration content into the enterprise app itself. This complicates the app, but creates a tighter link between the two where the user doesn’t have to know two different applications at all—it becomes part of their workflow naturally.
- However, the greatest value seems to lie in a fully networked organization applying social business both inside and outside, and perhaps a key determinant of its success is in integrating social business directly into the workflow of employees

Jun

27

2010

Social Needs To Be Layer, Not A Feature

"
By making social a layer, we (the vendors) can create solutions that bridge the gap between islands of applications, allowing you (the customers) to work in a far more efficient and effective way. We're (the industry) just starting to make this happen, but I hope that by working together we can avoid the integration issues that have plagued enterprise applications for decades. In my next post I'll discuss the standards that are being put in place to make this vision a reality, and how we're using them to develop Socialtext Connect. "

www.alanlepofsky.net/...eeds-to-be-layer-not-a-feature

- Preview

enterprise2.0 sociallayer silos socialsoftware integration

Bertrand Duperrin's Library tagged sociallayer → View Popular, Search in Google

Enterprise Software Architecture: a Network of Services, Not a Layered Stack - Forbes

Making An Intranet More Social

Enterprise 2.0: A Transition From Destination Site To Platform Services

More On The McKinsey Study: Integrating Into Workflows May Pay Off The Most - Rawn Shah - Connected Business - Forbes

Social Needs To Be Layer, Not A Feature

Selected Tags

Related Tags