Nachdem wir nun schon seit Jahren den Begriff des IT-Business-Alignment brav vor uns hin kauen und es dabei immer schwerer fällt, dem Impuls zu widerstehen, diesen mittlerweile geschmacklos gewordenen Begriffsklumpen auszuspucken (bzw. immer noch auf den Geschmack warten), sorgt Tom Austin (im Bild) von der imageGartner Group nun wieder für etwas Aroma: In einem Interview auf fast company stellt er eine völlig neue Job-Beschreibung für IT-Experten in Aussicht und meint, dass der ITpro der Zukunft mehr ein Sozialwissenschaftler sein wird als ein Technologe.

Ein durchaus überzeugender Ansatz bedenkt man, dass die größten Hürden beim Einsatz neuer Technologien oft sozialer Natur sind. Austin:"A new species of Information Technologist is emerging from the primordial ooze of Web 2.0 -- social scientists and humanists who focus on human behavior more than software code."

Hier einige Ausschnitte aus dem Interview:

The problem with IT today is there are too many engineers and not enough social scientists. Look at the numbers of features and controls we put on how things are done. That's an engineer's approach, versus some of the free form approach of Enterprise 2.0 and social networking.

Why do you call social networking and Web 2.0 the "primordial ooze?"

The idea is to allow behavior patterns to emerge from that ooze from an evolutionary point of view rather than trying to predict how things should be run and controlled ... There's a recognition that if you relax some controls -- not all -- you're probably going to get more creative behavior out of the individuals than if everything is locked down. The organization gets far more flexible as well. I remember a discussion I had with the CIO of a mid-size manufacturing firm where I was explaining the value of an open wiki where employees could contribute ideas and edit each other's ideas. One of my points was, make sure you don't allow anonymity so people will be rewarded socially or punished socially for inappropriate behavior. The CIO said, "You know, I really get this." Then she went on to explain how she would have to put in place workflow review and approval for everything before it gets posted to the wiki, which led me to realize I'd done a bad job of explaining this whole notion.

posted by Wolfgang Tonninger