Home »Archives for Steptwo

January
2

Some intranet to begin reporting year

Some small signal to begin the new year (these reports are also useful to me to warm up the muscles on this blog, I've gone for too long time because of problems with my new condition Campagnola - provided material and spiritual condition - and not add other).

- Rebecca Rodgers, of StepTwo, talks about testing with users within the intranet project ( "some testing is better than 'no-test'"), it is true that often these blessed tests do not make them do with all the trappings, but in any case also lead some investigations "cooked and eaten" is better than not condurne all.

- In an old article from 2004 talks about Paul Chin promotion techniques to launch the intranet, an issue often overlooked and that goes hand dealt with seriously and with a modicum of creativity. Note that in this case Paul need to clear the content entertaining and non-working on behalf of the visibility of the project.

- StepTwo released its intranet innovation 2009, with a number of very interesting cases, including for example that of the Russian group ChTPZ, which created a very sexy application for sending SMS messages to mobile employees via an option in the pager.

chtpzgroup_mobile_04_edit

Another case ineressante is localized and Saber, and its application (SabreTown) microblogging for questions and answers between the employees (mooooolto interesting).

sabre_New_hub

The report is a fee, but you can download a free rich synthesis (hence the link to the PDF of the summary of intranet innovation from 2009 to 4.3 Mb).

- Speaking of stuff to download, you can give a look matrix intranet Toby Ward, which lists the characteristics of good intranet compare with those of "very good" intranet. Nothing special, but it's worth giving us a look (you must register to download).

- Finally, Oscar Berg has published a list of 12 (twelve) free reports on Enterprise 2.0, caught from various sources such as KPMG or consultancy McKinsey.

For the moment we are okay so ... hello hello and that you will achieve what, esplcitamente or obscure, by choice or by necessity, have meditated for this year that comes.

October
29

the 7 (or eight?) Role of the intranet home page

Steptwo has published a very interesting article on the prevalent use of the home page on the intranet (and the best practices associated with them).

James Robertson identifies 7:

- To highlight the news

- To make access to inland

- To highlight the key applications

- To highlight key information

- To promote the internal culture

- The internal marketing

- For collaboration tools

Then shows an example for each role (but below two):

Display of new on the homepage, including a featured story. Screenshot courtesy of Verve Energy.

Key tools can be directly included on the intranet homepage. Screenshot courtesy of EUMETSAT.

I find the comments very good article, but I forgot to another role, namely to the collector of contributions coming from the community: the home page it can accommodate the latest in automatic things produced within the different spaces for sharing .

Omitting this role is to forget that the intranet is based partly on a number of features for sharing and collaboration that is good to highlight as emergent behavior.

On no?

April
29

Moderate (or no) internal forums and blogs

Very interesting one of the latest articles Steptwo this time dedicated to the theme of moderation of the discussion on the intranet. The subject is close to my heart, as you know, and I have written many times about it.

The article is in highlighting some key points and to propose alternatives in the approach to the theme of moderation.

In summary, here are the points that Alex Manchester puts the spotlight:

- Policy: Every company has its characteristics and its own internal dynamics, for which there is no universal approach, but the guidelines are nevertheless always prepared, and the article link different sources (perhaps the most interesting is the policy of BT, downloadable in pdf)

- Identity: Each contribution should esserfe associated with a clearly definable, avoiding discussions anonymous. The names should always appear vicnio contributions (and I would add, make up your personal profile)

- Single Sign On: to reduce stress and improve the user experience user, the authentication mechanism should rely on more general single sign-on procedure, so you do not have to continually re-enter UID and password

- Moderate: The article proposes between choices:

  • self-restraint
  • moderation "light"
  • moderation "full"

Identifying for each risk and opportunity. I personally believe that there is no sharp boundary between these three choices: I believe that things will change much with the passage of time (usually more than passing control to less control) as well as I think that sometimes the full moderation on some aspects (eg technical issues) living with self-restraint in other respects.

In any case, the list of factors critical to the success of a project for discussion I would like to add some features not listed in the article:

- Report abuse: add this item to any contribution you can loosen the reins, leaving the community the task of making a first filter, as well as give a clear signal about the fact that not everything is permitted

- Rate contribution: it allows to bring out content deemed best, feeding a virtuous cycle

- Ease: The whole system must be easy to use. Simply. If it becomes yet another cumbersome application to use people ritrarranno or do not even consider the height to be able to participate ( "the Hood")

- Keywords: keep a nice list of key words "hot" and let him get a warning each time they are written. This reduces the need for precise control but still be placed in the situation

- Black List and Gold List: the people will end up in the "black list" or the "gold list" depending on their behavior, condition differences in access privileges.

Anything else?

February
20

Customized? And as customize the?

We mark one of the articles Utlimi Step Two, which examines the difficult issue of customization of the CMS intranet, and in particular the problematic relationship with the individual applications that are typically constructed, built or assembled inside the environment.

As usual the pictures are illustrative. I tell you immediately that the three solutions I have always supported the first, but lately I rather change my mind about the subject, and where I can try to work with the two solutions, although they are always so many variables to consider.

The article examines in depth the pros and cons of each solution.

image from the site steptwo cms customization

image from the site steptwo cms customization

image from the site steptwo cms customization

February
16

Forums crews on British Airways

Last year, Nielsen reported they had been in his report. This year saw the gold prize of Steptwo (Intranet Innovation Award). In short, this forum of the British crew really depopulated.

Here you can listen to the voice of the intranet manager, Allen Huish, which tells the story of this initiative.

October
24

The British Airways community

In this video, Allen Huish, the intranet manager of British Airways, said the experience of internal forums for the crews of the company (17.00 people).

This case, as well as winning one of the awards intranet Innovation Award is finite even in the report Nilesen best intranets of 2008 (for once Septwo Nielsen and are in agreement).

It 'a case is really interesting when you consider that the forum is really utilizzatissimo and that the crews do not have a PC, but connecting from public locations in airports.

Allen has recently opened a blog that is worth keeping an eye.

April
21

User centered intranet

I've said many times, and I repeat: to design an intranet slap must look primarily to the needs and processes effectively agitate the people. Be careful, because look at the needs and processes:

- Does not mean a half hour interview for the head of IT;

- Does not mean to guess why so much, we know the company well;

- Does not mean abstract from market surveys or general trends and then approach her to apply as automatons in a specific organization;

- Does not mean the blog or wiki because it's cool to do so;

- NOT signifca (only) to go to lunch with the AD to be told what are the priorities.

In these two presentations, the smooth James Robertson gives us some more methodological element.

Some time ago the good Albert, in the brewery, I would say roughly this: "But damn it, we give us to use these methodologies with users to external sites, and you that people you have in the ufifci do not do . But why? "
Yeah, why?

February
12

Inside the hive

Very concerned the first part of this paper, just published by StepTwo, dedicated to the methodology of implementation of intranets and significantly entitled "Exploring the Intranet Hive (part 1)"

6 describes the components to manage in prgetto, giving 6 tips for each component (the Americans have it on his 10, while the Australians, with 6. We Europeans, given the greek-Judeo-Christian influences, we are still afffezionati to 3. From Aristotle to Hegel. closed brackets).

The components identified are:

  • Strategy
  • Design
  • Contents
  • Changes
  • Technology
  • Team

We carry a significant piece

Intranets are never finished

An intranet is always a work in progress. Although initial intranet builds reasonably linear path to follow, once implementation has taken place there is no single path forward and the next steps will depend on a combination of Largely organizational imperative and the constraints the team is operating under.

From the same site will also point out the recent article devoted to the time needed to select a CMS. Hey, I understand that there are some essential steps (and I'm usually cautious), but I still take a while if the 'easy, you say? ;-)

November
15

What do innovative intranets look like?

In this presentation you will find a few more details on the motivations of the awards' s intranet innovation awards, sponsored by Steptwo. There are also some beautiful screens (the presentation is not downloadable, but you know amme ...)

October
16

Cooperate or share? Problems (almost) philosophical

It has a nice saying about the importance of collaborating, sharing knowledge, encouraging participation. These things I have listed are not synonyms: let's take a step back and look better with this issue.

Suppose you create a group on Lotusnotes, or on Teamsite Sharepoit, or a project team on yoo +, or even a closed group on Google Groups. Have you created a space for collaboration for a small group of people within the organization. Now multiply this by 10, 100, 1000 groups: you have got a fragmented organization in clusters of interest, or in working groups.

But at the same time, you have also created functional silos, (although informal) that do not allow knowledge to flow smoothly between different groups.

But this knowledge can really flow?

This is an interesting subject (one of the most interesting in recent times about this, indeed, that is: how much collaboration is a barrier to sharing?

In other words: what is necessary in an environment to enable an understanding to move? It 'obvious that a document or information which have their own history, tied to a context of trade between a group outside of this context are particularly relevant. If you then take a document drawn up within a TeamSite and take him outside, available to all, information becomes insufficient and insignificant.

In short, while within groups occurs largely conscenza tacit, difficult to transport, open spaces (such as a space for the forms or manuals) are sharing explicit knowledge, readily de-contextualization, but do not have a history of collaboration behind (at least in visible form). It therefore appears that the degree of cooperation is inversely proportional to the degree of sharing possible: if the information was a history and context, this story becomes a dense set and not easily explainable.

What are the solutions to this problem? The debate is open, and I can only give my point of view.

Groups which develop tacit knowledge have always existed, and the creation of closed groups only serves to take note of this situation, providing a suitable environment for collaboration. But at the same time, there are practices of boundary are those that enable groups to learn in their internal knowledge to carry out. There is always the figure that connects, which passes from one group to another, the innovator, who attended the "boundaries" of communities. These are figures that form the cognitive bridge to knowledge produced locally (Mario arrives in his group in the office and says, hey, the ones downstairs are doing something fichissima. It may be useful. When I go to my friend who works there and I do explain ....).

In an intranet-respecting should live these different practices related to knowledge: closed groups that produce collaboration and tacit knowledge and contextual, open groups that allow the explicit knowl-ring (think of a forum on domestic issues in Excel, in which case the conoscneza is less contentuale), and finally, a practice of "work on the borders" allowing participation in different figures to different device groups closed, so you can be a bridge cognition.

Moreover, it is said that the tacit knowledge and context derived from the collaboration can not, at some point, be transformed into explicit knowledge: some end-products may be available to everyone because they have reached a level of explicitness that can be shared. In this case the collaboraizone becomes a sort of incubator listing for sharing.

All this (or almost) is discussed in this article, published by StepTwo.

Happy reading (and good riflesisone).

April
12

I'll you downloaded?

And 'the only thing free of the types in Australia (who started me out with some' on bales). To me it's worth (with the appropriate customizations).

One document states to examine and evaluate all aspects of the process of developing the project. You download from here ...

Tues
4

Strategy? Better to see you soon

Also on site steptwo has just published an interesting paper (but paid) on strategies for implementation of the intranet. The golden rule (at very least share) is that, given the nature of the project, the better the strategy is short term, with half-step after which the entire review process.

In short, the project must be treated in digestible bites. Do not ask: "Where are we heading in 5 years?" But: "What we want to produce in the next six months?"

Schema_semestrale_della_metodologia_steptwo

April
13

Intranet blogosphere

In this period are very engaged, even if I do not know by what (in short, is a period of anxiety with no name ...) so I have the strength and courage mail only posts miniature. However I must point out, the beautiful site tramitre Australian Steptwo (in particular the section Column Two), an updated and full list of blogs on the intranet. As you can see we are not alone in the world (I say more to myself ... eh).

January
28

Internet and intranet: What is the difference? Systematic approach

Begins with an article that appeared last year on Steptwo (when the Australians there is at least a foot in the field of knowledge management ...), edited by James Robertson, who tries to address the issue intranet / internet trying to identify, systematically the differences in approach, the project, in the results. The article has the merit of groped a taxonomy of features that enable optimal design of two environments too often treated as the only hat conceptual "web" or, Instead, vaguely differentiated without a clear decline.

Are compared Intranet and institutional sites, but what matters in this case, the method that is more merit.

Objectives, Audience, refresh rate, size, familiarity with the environment, consistency of display media, content, layout, artwork .... Are all key issues, which have a considerable impact in the design space

In these respects, however, they add, that the author does not specify but which could rightly be added to the list. I'm going to list them:

  • Services: functional type of site - predominant
  • Community: functional type of business - an integral part of the project
  • Learning curve: average rates, remain constant - average, high, decrease with time
  • Navigation structure: it may be too deep - Extended rather than profound
  • Documents and materials: possible - Necessary and integral part of the project
  • Interaction: marginal - very thorough
  • Processes: not much influence - much influence

I believe that these elements are themselves very characterize and contribute very strongly to qualify an area intranets.