Feeds:
Posts
Comments

Posts Tagged ‘Adoption’

Over the last few weeks there’s been some interesting exchanges around mandating the use of social tools (in particular blogs) within an organisation as ‘reflective’ tools for sharing and learning (see Abraham, Leberecht, Leyden and Cornelius). Those exchanges dovetail nicely with another weighty debate around tailoring the functionality of tools like ‘Facebook’ and ‘Twitter’ to suit the enterprise context, and more particularly, whether their use should be given a top-down or other informal nudge to ensure contributions are sufficiently work-related. The former is now moving through a spectrum of mandating -> encouraging contributions and the latter is focusing on channeling or containing them.

Moving away from a ‘they just must‘ perspective, we can instead observe how people are communicating and with whom, and why in other instances they are not. We also have the opportunity to consider how to channel ‘twittering’ behaviour to help us work in a more fun, informed and effective way.

The working paper “Communication (and Coordination?) in a Modern, Complex Organisation” by Adam M Kleinbaum, Toby E Stuart and Michael L Tushman (Harvard Business School, First Look, 29 July 2008 ) provides some extraordinary insight into the structure of communications in a modern organization. In other words, who is communicating, how often and with whom? To answer the following question, the study analysed millions of electronic mail messages, calendar meetings and teleconferences for thousands of employees in a geographically dispersed, multiunit enterprise:

What is the role of observable … boundaries (i.e. business unit, office location, gender and tenure in the firm) between individuals in structuring communications inside the firm?

The salient findings include:

  • The extraordinarily high similarity and parallel relationship between email and face-to-face/social networks within the firm.
  • The striking relationship between e-mail activity and hierarchical level; the average executive (members of the top four salary bands) in the sample sent and received more than twice as many e-mails as the average middle manager who, in turn, sent and received more than twice as many as the average rank-and-file employee.
  • That women, mid- to high- level executives, and members of the executive management, sales and marketing functions are most likely to cross the company’s social structure gaps and participate in cross-group communications.

What we don’t know is whether (and if so the extent to which) other communication/collaboration technologies were available within the firm. Of course the authors warn against generalisations based on results from a single organisation, but given well-known issues associated with email overuse, abstinence from traditional ‘above-the-flow‘ KM/collaboration, and the need for buy-in from management, I think the study supports some principles which can guide behaviour in other instances.

If social tools are thrown into the mix, any adoption strategy should look to the participation of the groups identified above, who are key information/social networking nodes and would be invaluable to any social software pilot. But engaging the high-level executives (in particular) could be a very large mountain to climb. Whilst that group has a considerable amount to gain from ‘above-the-flow’ activities and slight changes to behaviour (like micro-blogging instead of emailing), they usually have well established preferences for face-to-face, email or phone communications, and need to cope with a variety of political/power dynamics. And as for a “they just must” approach with this group: forget it!

Simply articulating the value to be obtained from experience will clearly not be enough, even if people are being given the time to take up the opportunity. Instead, barriers to the participation, reflection and learning processes need to be lowered. Amongst other ways, that can be achieved by giving people the means to capture their thoughts on a platform in a more informal conversational way – whilst they are working (i.e. more ‘in-the-flow’ of daily operations). Whether that be through micro-blogging, sticky notes or commenting, status updates or wall-postings, the process should reflect people’s preferences for technology and communication style. As we are seeing, that means enabling ‘twitter-ing’ quick-fire style exchanges during people’s work, which can be rapidly embellished and/or responded to by others.

And rather than defining the scope of the tools (like “please use this for client and not social purposes”), use tags, aggregators and RSS to manage/channel the flow of content. Having started the debate, McAfee on further reflection notes “… norms and policies might not be the only ways to make a tool like Twitter work well for enterprise purposes”. The idea is to “tag” the tweet, perhaps by prefacing it with characters (like @FM) corresponding to a client or contract. In that way, it would be possible to categorize and organise the flow of information.

In fact, that may be one use case for PagesPlus (which Paolo Valdemarin from Evectors very kindly demostrated to everybody at Headshift yesterday morning!). Since the core of PagesPlus is an aggregator, it can digest any form of RSS/Atom and use tags to organize everything it aggregates. Because the aggregator supports tag schemas not only can it distinguish between a topic-tag and a category-tag, but it also allows you to create your own schemas to address specific needs. With the WYSIWYG application allowing users to easily create content at the front end, it would be a small step to continually auto-save the content and for the system to recommend to the user tags based on an analysis of the text being typed (and other tags applied in the past). That content could be pushed out to the categories and pages corresponding to the tags, and to the users who are subscribing to feeds from those categories.

Essentially, designing the tools around people’s preferred styles of communication and collaboration will help to support behaviour rather than control or mandate it – a poor counterpart. People may then filter content and functionality depending on their style and preferences, and then hook other people and content into the process by creating actions and feeds out of their activity. All up, that approach should help to get people on board and keep them there.

In the same way the famously contrasting perceptions of the nature of organizational communities has animated a great debate in organization theory during the past few decades, so too perhaps will the issues discussed here continue to test knowledge workers. Kleinbaum et al cite the study of Hannan and Freeman (1977), which posed the classic question, why are there so many organizational forms, and DiMaggio and Powell’s (1983) rejoinder, why are there are so few. Likewise, I wonder about the levels of diversity of communication and collaboration actually being facilitated in organisations, and why there aren’t more.

Read Full Post »

In my previous post I introduced the idea of using a process framework for managing the wiki implementation. Here’s some more detail about the concepts behind each of the framework’s processes:

Wiki Management Cycle

  • Identify ‘needs’: This requires focusing first on the business needs, collaborative behaviours and capabilities to be developed, then on identifying the technologies which can support those needs/capabilities.
  • Plan: Having identified a wiki as a suitable technology, its implementation and management must be considered. This should balance planned and emergent approaches to foster learning and allow patterns of use and self-sustaining behaviour to evolve over time, whilst providing direction/purpose to co-ordinate and guide efforts towards a shared vision of what is to be achieved. Consideration should also be given to the practical applications and purpose(s) of the wiki, how it will fit with existing technology systems and work processes, and the nature of facilitation (e.g. initial structuring and seeding of the wiki) to support and sustain use.
  • Adopt: Wiki ‘adoption’ refers to the stages through which users typically progress before committing to a new technology, with different adopter ‘types’ progressing through the stages at different times and speeds. Rogers’ Model of Technology Adoption Categories below illustrates the characteristic responses of adopters to technology innovation:

Rogers’ Technology Adopter Categories

Typically, those users become aware of a technology’s potential and then develop an understanding of it, which can lead to testing through trial use, and if successful, to its application in everyday work, before full adoption across the organisation as a key element in work processes. Whilst that path may not be linear, recognising the different stages may help to identify support/transition mechanisms to ensure each user-category is more likely to adopt the wiki, and help avoid its rejection, which may occur during any stage of the adoption process. In particular, the issue here is how to strike the balance between voluntary grass-roots adoption and directive use to encourage participation, raising considerations about the nature of training, teamwork, use of facilitators, support for different communication styles and unlearning of old habits regarding overuse of inefficient/ineffective technologies.

  • Maintain: Closely related to adoption is wiki growth and propagation of good practice throughout the organisation. Issues here relate to managerial support, content management and wikis’ integration with other systems and work processes. Of interest here is whether managers have in fact absorbed the advice from industry and academic literature indicating they should be directly involved in the implementation by leading by example, mandate and reminding, reducing barriers to use, encouraging experimentation with the wiki and monitoring its use for ideas and best practices then propagating them throughout the organisation. Content management is also a key issue. Since wiki content should become more useful, structured and navigable over time if people are updating, linking and tagging, consideration needs to be given to the mechanisms which best encourage that type of behaviour.
  • Evaluate: Of interest here is whether, and if so how, businesses are evaluating their wiki implementations. Such evaluation can be a mechanisms for encouraging feedback and learning from the implementation process, and allowing for revisions to implemenation plans, and wikis’ design, usage and maintenance. Measuring users’ progress through adoption stages and how often people are using wikis will provide some elementary figures on wiki diffusion and infusion in the organisation, and may provide grounds for investigating any barriers to the implementation process. However, more difficult issues relate to evaluation of wikis’ impact on bottom-line performance and development of organisational learning practices. Measurements focusing solely on bottom-line performance improvement in terms of accelerated project cycle times, reduced email overload and search costs may provide some hard data to support ROI, but they do not consider more important effects of wiki management/usage on organisational learning and collaborative capability development. Not only is it more difficult to establish direct causal connections between wiki management/use and improvements here, any evidence would be in the form of people’s opinions/perceptions.

Read Full Post »

The original wiki design principles (Wiki Design Principles) encourage emergent work and do not impose structure, process or rules, contrasting applications characterised by a top-down command-and-control mentality. That can allow people to work together in self-directed ways, encouraging levels of openness, autonomy and knowledge sharing which other systems (i.e. all systems in the organisation including cultural, managerial, structural and operational systems) could not well support. Consequently, a wiki implementation should be viewed as a change process rather than the introduction of a new technology per se.

Since cyclical process frameworks have been suggested for technology management in general – i.e. as means to aid consideration of technology’s role, effects on the organisation and nature of managerial activities/involvement, from existing literature I derived a wiki management framework to help assess how in practice businesses are managing wiki implementations and the utility of such a framework for managing the change process.

That framework includes the following processes: ‘Need’ Identification, Planning, Adoption, Maintenance and Evaluation. During my research I posed a range of questions to interviewees and survey respondents regarding their practices in respect of each of the processes. I’ll be discussing the responses in a later post.

Wiki Management Cycle

Wiki Management Cycle

Read Full Post »

Follow

Get every new post delivered to your Inbox.