IT Management Practices: Involving the Team

I have an experience that I feel may be useful to share. Till date, I have worked on two excellent new product development projects and it has been a wonderful learning experience. However, each team had its challenges. Since I do not want to name the companies or the managers, let us say I am talking for company Alpha and company Beta.

Both companies are technically very strong. However, company Alpha had to put together a team to develop a rich Internet web application when RIA as a concept was pretty new. This initially led to ambiguity in terms of experience and possibilities, but the manager ran a tight ship and delegated responsibility. The whole team was encouraged to develop skills and participate very closely at every stage - including interviewing, requirement gathering and architecture. This ultimately led to technical skill development, team bonding, growth of all team members and decent execution of the project. The stress and responsibility were evenly divided, but there was no doubt on who was leading the pack. Leadership was inclusive and far-sighted.

Company Beta, on the other hand, had significant experience with web applications and RIA was relatively known by this time. So they could hire the people with right skills and there was less ambiguity to start with. But the structure was more hierarchical and the manager less keen on sharing "power" across the board, giving less influence to team members on requirement gathering, designing or interviewing. Of this, for me, the most difficult part was not being included in requirement gathering. Working with a requirement document may be the norm in big companies, but for entrepreneurial setups it is absolutely critical to be involve the team closely. This can save a lot of time down the line lost to bugs resulting from misunderstood requirements. Moreover, such involvement creates more urgency, creates an aura of responsibility and gives additional perspective to the whole process. This can be critical in long term.

Ultimately, both companies managed to launch a good product. Nevertheless, Alpha is playing for the long term - trying to nurture second rung of leadership - while Beta will increasingly get dependent on one row of leadership with a big vacuum below. In the long run, it may indeed make a difference between great and good, and would be another testimony to Jim Collins.