Concentration

Black and green. I mean: green IBM3270 font on a full screen whole black background; no browser, no feeds, no email. Just the black background, your text and you. A cool parenthesis of concentration.

Distractionless writing with Writeroom

I miss that word so much in my last weeks life: we delivered the most complex release of the Oracle Enterprise One ERP at Gabetti early in December which kept us REALLY concentrated on making all the amount of old data take their right place in the new system (and also fixing some errors inserted in the old systems during years which made OE1 simply mad).

And then there’s the 2008 budget planning, Second Life, analysis to be made and data to be properly understood. And, wow, this is the end of an overwhelming year dude!

On the personal side of life we’re hitting the start of our new house renewal: discussions with the architect, choosing the right pool, planning the suite bathroom (I replicated it on Second Life to help my wife understanding my ideas better), choosing the doors, the windows, managing all the papers…

I’m tired. I’d like to have more time to manage all the things. Need to slow down. Just a little bit. And that’s also why posts lacked here in the last weeks.

Oh… and thank you writeroom for these 15 mins of distractionless writing.

UPDATE Alberto, while back linking this post, discovers a bond I sincerely have bypassed: the concentration feeling you experiment Writeroom donates you follows the same path Ev highlighted in his LeWeb3 speech: it really seems that innovation, more than from making software more complex, arise when you try to make it simpler. Thanks Alberto!

Enterprise 2.0

Let me first of all say I’m really sorry to simply have dropped last Friday post, ahem, story but both me and Barbara were busy in the final phase of our new home (more on this soon); on aoperation that really took most of my spare time and that helped inspiring next Friday topic (stay tuned).

These few lines to say I’ll be at the presentation of “Community Management“, a cool book about enterprise 2.0, that will be held this evening at the SIAM 1838, Via Santa Marta18 in Milan starting at 6pm. See you there.

Live notes

FRANCO VILLANI (Commercial Director bTicino)

+400 sales men in Italy. They created the internal community because of their role in the market: they need innovation to preserve their leadership.
In their commercial area there’s a lot of old style sales style, but they try to differentiate from the rest of the arena: they have young engineers as salesmen who love their own job. They’re passionate about their business.

But as the company was growing both in its dimension and complexity the needed something to make simpler the communication between the centre and the sale network and vice-versa. They also needed an excuse to gain attention on this new opportunity.

The community was the answer.

In the meanwhile they bought two different companies that really brought a huge expansion in their sales network, and the tool was fundamental in the integration of the new colleagues.

6/7 months from idea to delivery. They’ve chosen a strongly mediated approach in order to have the people to exclusively speak about their business and avoid abuses of the software (such as complains about not having supa cool company cars :-) .

GIUSEPPE SCARATTI (Università Cattolica)

Great potential: organizations need people that correctly interpret company philosphy and translate them in organizational methodologies that support company business. Practice bonds people, technologies and behaviours together.

Wenger says that people learn by entering as novices in practice communities.

EMANUELE QUINTARELLI (Web 2.0 expert)

Companies are already using knowledge management tools to aggregate peoples knowledge and help colleagues to have their work done. But technology seldom is successful (44% of people thinks that itranets really improve their works, IDC in 2006 found that 25% of our time looking for informations).

KM is the past.

Every company is a babel tower: multiple applications, silos, UIs; rigid central management and configurations; long change cycles by the IT department.

Enterprise 2.0 is the usage of social software platforms within companies, or between companies and their customers/partners.

Interaction between people stands visible and durable as time goes by. Enterpise 2.0 change our intranet in an ever-changing structure lead by users: enterprise level tagging, wikis, blogs, etc. (Microsoft Sharepoint)

Why adopting these 2.0 tools? Efficency gain (RSS feeds), competitive pressure that oblige you to continuously innovate.

Informal organization brings strong advantages: business efficency, reduced operational costs, improved customer satisfaction and company morale.

MARCO VERGEAT (FIAT CORPORATE UNIVERSITY CEO)

He cited Bravo and 500 FIAT cars cases where customers where strongly involved in the product projects (millions customers’ ideas to create the new 500 minicar).

Collaborative learning: learn by by the knowledge exchange between networks of people;
Informal learning: non intentional learning that represent the main quota of the learning on the job.

Self development: training the managerial skills of each one; huge quality levels of the participants is the assurance for a correct collaborative learning.

Too late. Really gotta go, hope to find the rest of the seminar backed-up online. And – s**t – cannot listen to Luca De Biase’s speech.

Creating the helpdesk experience

We all have, sooner or later depenging on how you feel lucky, a frightening story about helpdesks: labyrintic menus, looping hold-on messages, and ultra-dumb helpdesk guys (ever felt that strange experience when every guy you talk to asks the same identical question before passing your call to the next one?).

Believe me, I’ve always been kinda unlucky with helpdesks. Unfortunately. So I was happy my first day at Gabetti to discover I would have worked shoulder to shoulder with a small helpdesk team serving our 1000 agencies on IT related problems.

Back in June 2006 the only way to contact the helpdesk was to give a call to a phone number behind which laied an exchange that took care of the call forwarding to the first free operator. In other words the process was something like

  1. call the number
  2. stay at least 15 mins (if you’re the lucky boy) on hold
  3. explain your problem to the operator (other 15 mins, at least)
  4. wait until the IT team solves your problem

A syncronous helpdesk is a waste of time for everybody: for who has the problem and for those who solve it.

Then we started innovating the technology and the processes below the IT helpdesk; our keyword was “asyncronous”.

The first step was to provide the support team and our users with a web interface, with proper problems sections, to communicate and manage tickets. We’re really really happy with the open source software OTRS which could be managed both via email and web and is plenty with personalizations.

That was an important shift from syncronous to asyncronous assistace which brought some interesting features to our helpdesk structure:

  • Our clients wouldn’t have to wait for a free operator to communicate their problems anymore
  • We have the power to simultaneously close a large number of tickets in the very moment (that is to say make more users happy in less time)
  • We can prioritize problems (both basing on the quantity and quality data of our users’ problems)

With just this change we obtained a huge (nearly half an hour) speed up of the ticket opening. Not bad, huh?

But the we moved fast forward both from the technology and process points of view: we rolled out Gabi, our Virtual Assistant, back in July to manage the whole help desk front-line and, more recently, we choosed to prioritize our asyncronous tools (such has gabi itself and the online helpdesk) by cutting the telephone helpdesk times from 8 to 3 hours a day.

Even if this strong move towards the asyncronous life style hasn’t already showed its entire potential the results are huge: the mean life time of each ticket is now something less than 1.5 days and the monthly helpdesk performance has gained full 44 man hours (which is something more than the Italian equivalent of the work week).