Group items tagged

Gartner has identified seven properties that differentiate emergent architecture from the traditional approach to EA: 1. Non-deterministic - In the past, enterprise architects applied centralised decision-making to design outcomes. Using emergent architecture, they instead must decentralise decision-making to enable innovation. 2. Autonomous actors - Enterprise architects can no longer control all aspects of architecture as they once did. They must now recognise the broader business ecosystem and devolve control to constituents. 3. Rule-bound actors - Where in the past enterprise architects provided detailed design specifications for all aspects of the EA, they must now define a minimal set of rules and enable choice. 4. Goal-oriented actors - Previously, the only goals that mattered were the corporate goals but this has now shifted to each constituent acting in their own best interests. 5. Local Influences: Actors are influenced by local interactions and limited information. Feedback within their sphere of communication alters the behaviour of individuals. No individual actor has data about all of an emergent system. EA must increasingly coordinate. 6. Dynamic or Adaptive Systems: The system (the individual actors as well as the environment) changes over time. EA must design emergent systems sense and respond to changes in their environment. 7. Resource-Constrained Environment: An environment of abundance does not enable emergence; rather, the scarcity of resources drives emergence.

low readiness for change high risk-aversion preference for hierarchy and processes to create knowledge over personal freedom to collaborate and share individual preference for position power and legitimate power over referent powerand expert power

Driving successfully web 2.0 into the enterprise

A lot of companies are currently planning their web 2.0 strategies and are discovering the opportunities as well as facing the challenges of adopting these technologies in the workplace.

The business case, system adoption and issues around fragmentation are typical pain points that companies are dealing with as far as Enterprise 2.0 implementation is concerned.

Looking to spur wiki adoption? Want to grow from 10 users to 100, or 1000? Applying patterns that help coordinate people's efforts and guide the growth of content, and recognizing anti-patterns that might hinder growth - can give your wiki the greatest chance of success

Social Tagging

69 percent of respondents report that their companies have gained measurable business benefits, including more innovative products and services, more effective marketing, better access to knowledge, lower cost of doing business, and higher revenues. Companies that made greater use of the technologies, the results show, report even greater benefits.

We found that successful companies not only tightly integrate Web 2.0 technologies with the work flows of their employees but also create a “networked company,” linking themselves with customers and suppliers through the use of Web 2.0 tools. Despite the current recession, respondents overwhelmingly say that they will continue to invest in Web 2.0.

When we asked respondents about the business benefits their companies have gained as a result of using Web 2.0 technologies, they most often report greater ability to share ideas; improved access to knowledge experts; and reduced costs of communications, travel, and operations. Many respondents also say Web 2.0 tools have decreased the time to market for products and have had the effect of improving employee satisfaction.

These concerns about SharePoint’s ability to be an effective Enterprise 2.0 platform is one I hear echoed a lot with practitioners I talk to. In spite of this, I correspondingly hear that SharePoint is in fact what most organizations are planning on using when it comes to 2.0-style collaboration and knowledge management. Why the apparent disconnect between the perceived suitability (which we’ll dissect in a moment) and actual use? Part of it is SharePoint’s stunning penetration in the software business. T

In other words, SharePoint is already in most organizations today:

In fact, this is a central lesson in Web 2.0 design, that complexity is the enemy of ease-of-use and adoption; most 2.0 products are almost brutally simple in their user experience.

The problem? The growth of the collective intelligence site so far largely has been fueled by early adopters and enthusiasts, according to Rasmussen. About all those who would have joined and shared their knowledge on the social networking site have already done so. If the intelligence agencies want to get further gains from the site, they need to incorporate it into their own formal decision making process, he contended. Until that happens, the social networking aspect of Intellipedia is "just a marginal revolution," he said.

Established in 2005, Intellipedia, now managed by the Office of the Director of National Intelligence,  has approximately 100,000 user accounts. Open to anyone with a government e-mail account, it has social bookmarking tool, a document repository, a home page for each user, and collaboration spaces.

For true change to occur, other agencies must use Intellipedia as their official conduit, at least for some functions, Rasmussen said. Otherwise, it is just creating additional work for contributors.

Islands of Me — the beginning of organizational use of personal computers in which there was a culture of protectionism within facets of an organization; One-Way Me/Enterprise 1.0 — coworkers ask each other for information, but still only on a "need-to-know" basis; Team Me — employees understand their own individual power within their work community, but it does not expand enterprisewide; Proactive Me/Enterprise 1.5 — the ability to always be connected as workers could be distributed globally; Two-Way Me — communities are explicitly and purposefully created, and collective intelligence is beginning to surface -- albeit not in an automatic way; Islands of We — focus is on a larger team level and explicitly looks at how networking and community development can drive benefits to the entire organization; and Extended Me/Enterprise 2.0 (still in the early-adopter phase) — utilizes different information systems in order to foster transparency, has developed a participatory and engaged community, and has the agility to quickly adapt to changing environments.

14 per cent use it at some time to access social networking sites. Usage is significantly higher among younger workers with 32 per cent of 16-24 year olds and 23 per cent of 25-34 year olds reporting frequent or occasional use. 20 per cent said their employer blocked access to social networking sites while 57 per cent said their employer allowed it (23 per cent did not know). 76 per cent of workers who use the Internet at work could see a benefit to their organisation in allowing access to social networking sites believing it showed: - trust in employees (68 per cent);  - gave people a break from day to day work and kept them fresh (48 per cent); and  - allowed them to better network with other employees, customers and suppliers (40 per cent). Among those who use social networking sites, 91 per cent saw a benefit to their organisation from the activity. In general, younger workers were more likely to see these benefits than their older counterparts. 16 per cent overall said an employer’s policy re on-line social networking would influence their decision to join one employer over another. This view was particularly strong among 16 to 24 year olds, with one in four saying it would. 91 per cent say that they use the Internet appropriately at work, with only 1 per cent admitting to frequent inappropriate use.

1. It is about the architecture

2. Capture inputs

3. Create relevance

Integrate the wiki as one of several important tools in an organization's IT collaboration architecture.Understand the wiki "rules of conduct" and ensure they are monitored and enforced.Optimize the use of wikis for collaborative knowledge creation across geographically dispersed employees, and for crossing divisional or functional boundaries, in order to gain insights from people not previously connected.Assign a champion to each wiki and have that champion observe contributions that people make to the wiki; the champion will help foster employees who adopt the important "shaper" role within the wiki.Recognize that the most difficult barrier to cross in sustaining a wiki is convincing people to edit others' work; organizations should ask their champion and managers to help with this.Recognize that a significant value of wikis comes from embedding small software programs into the wiki that structure repetitive behavior. Some include organizing meeting minutes, rolling up project status or scheduling meetings. Ask wiki participants to keep watching for repetitive activity to evolve and enhance wiki technology.Understand wikis are best used in work cultures that encourage collaboration. Without an appropriate fit with the workplace culture, wiki technology will be of limited value in sharing knowledge, ideas and practices.

Comment passer de 10 à 100 puis à 1000 membres ? Ce site propose des "patterns", des stratégies d'action permettant de faire croître le contenu d'un wiki . Mais il ne s'arrête pas là : s'il détaille des stratégies d'action, il décrit aussi des stratégies contre-productives ou "anti-patterns" qui peuvent, elles, constituer des facteurs d'échec ou de ralentissement.