Yet another Bullshit 2.0 presentation (via Bertrand Duperrin).

I used to be kinda okay with this sort of Armanoesque material. But I just can’t anymore : I just find this type of presentations disgusting.

Here is the pitch : there is this emergence of Enterprise 2.0 tools that transform the way we work in the company. These are natural tools for the digital natives but not so natural for the baby boomers. The generation in between (it doesn’t say but I would think 35 - 45) are the knowledge workers 2.0 (blimey !) who can link the two generations together. Innovation … blah blah … collaborative work … blah blah … bullshit … blah blah

Something very interesting : out of the 55 slides, there aren’t so many on the very grounds you build teams on, teams that then become greater than the sum of their parts : trust, transparency, commitment and enthusiasm.

The problem with this type of statement is that the container (mode of communication) replaces the contents (what is communicated) : “use 2.0 tools and you’ll be creative“. This type of colorful demagogy is typical of the marshmallow speech which has been served to the Generation Me, as Jean Twenge depicts it in her book.

In the IT area, you end up having to cope with young professionnals that just get upset because you show them their software have severe performance issues, is not tested properly or is not easily deployable / maintainable.

They also get upset if you’re not happy with their standard of software documentation : a couple of lines in a wiki. Don’t get me wrong : Wiki is cool, but posting crap documentation in a Wiki is just as useless as writing crap Word document.

You then become the villain, the poor old guy who doesn’t understand software innovation (read unfixed level of abstraction and complexity) and who is only interested in the dark and boring side of the industry (read deliver the best possible software on time for it to be used as expected i.e. industrialization).

Now I guess all these consultants have to keep the whole thing buzzing to make a living. Enterprise 2.0 tools definitely can help getting things done but only if they remain the mean not the objective. They can’t replace the principles that rule professional work and teams organization as this type of propaganda tends to make believe.

3 Responses to “Bullshit 2.0 - Propaganda for Generation Me”

  1. Fred Brunel Says:

    Hi Cecil,

    That’s an excellent post and I totally agree with you. Actually, the Web 2.0 and the whole “agile” phenomenon is being totally misinterpreted by then young professionals.

    IMO, agile methods and tools are efficient but only when they’re used by experience people. In the hands of inexperienced people it becomes a complete chaos.

  2. David Says:

    Hi Cecil,

    You’re right, it makes no sense to have a wiki containing crap documentation.

    Like any tool, it requires some time to start bringing value to a group.

    There is no magic with wiki, it needs to be structured, members need to contribute, read, maintain, search information.

    In the end, this is a good mean to get new comers (young or old professionals) up-to-speed, and I think this should be the first goal of any dev team wiki : Ease the integration of new team members by having a kinda “Getting Started” that indicates how to setup a development environment, where are the repositories, what are the processes, coding guidelines, continuous build system, etc…

  3. ceciiil Says:

    Hi David,

    Thanks for your comment. I am not fully convinced to be honest. I guess it really depends on the size of your structure and also your type of activity.

    I am currently doing Support of a industrial software solution and it’s pretty hard to have some people in the team understand that a wiki is not really appropriated for direct customer relationship.

    @Fred - I am planning to write a post on corporate Vs open source project management. We have quite a few programmers here that advocate an open source approache. They probably haven’t read this (http://www.onlamp.com/pub/a/onlamp/2006/02/27/what-corp-projects-learn-from-open-source.html) where the author (who worked on Gimp) says that thorough testing and documentation are the foundations of a sound open source project.

Leave a Reply