Thursday, February 18, 2010

Technology Projects and Organisation Culture

Over my years of experience in creating/implementing technology projects for non-profits, i was intrigued by both success and failure of technology projects in NGO's.

Initally I and my team was elated of the success of the projects and it's contribution to the organization innovation and growth. On the personal front comes recognition, promotions, salary raises etc. - i was also was very much disturbed when technology projects didn't take off as resources went waste in a shoe-stringed technology budgets of an NGO and also risking which is primarly donor's money.

Many of the technology projects (particularly software projects) don't take off across all sectors (not only in NGO's). Some statistics of various surveys conducted are there in this link.

Conclusion by IT Cortex
       Technology project is more likely to be unsuccessful than successful
       About 1 out 5 IT projects is likely to bring full satisfaction
       The larger the project the more likely the failure



Many attribute this failure to due to various reasons like Poor Project Management, (Didn't do pareto/water-fall analysis!) Vendor Selection, Technology selection, Scope etc. Don't appoint consultant (particuarly from another company or person who is engaging in developing software) to tell you where your software projects went wrong!

Though i partially agree to some of it mentioned above - i felt during my working experiences that culture of both individuals and organisations - also plays a major role with either success or failures.

I would look at people characteristics such as fairness, collaboration with others, enthusiasm for the job, trust from individuals and organisation characteristics such as risk-taking, information-sharing, compliance, team-work, meticulousness,innvoation at the market place.

If i look back of all my previous success and failures on the above characteristics mentioned, following are some pointers:

High level of only organisation characteristics leads to
More of top-down/autocratic decision making style leads little contribution from individuals or groups. Success/failure rate are high, but information and success/failure are with 'few' individuals. Typical technology projects will be of what's the pressing needs - mostly operations which are tedious and time consuming are implemented, so there could be high level of success rates. Most of the projects will be on time and tested platforms and softwares. Technology projects are owned by functional people or few individuals in IT.

High level of only people characteristics leads to
Participation from individuals are high. Most of the time - technology projects are on a committee basis - typical technology projects involves from cross-functional teams, expert consultants looks at integration aspects between systems. Long projects duration for creation or implementation, Technology transition is invitable. Ownership is neither with technology or functional team! - If there is no considerable organisation characteristics - then the projects will remain only on paper or success/failture will be 50:50.

High Level of characteristics from people as well organisation leads to
Ideally, the project will be co-owned by both function and IT where high levels of maturity would be seen. Maturity on both functional and technology design will be seen. There will be functional and technology champions. Both success and failures will be shared jointly. Some of the characteristics of both people and organisation will manifest are:
    People Characteristic - Inter-dependence and Trust
    Organisation Characteristic - Team-orientation, flexibility, documenting information flow

What could be attributes of software failures in terms of culture?
     People Characteristic - Indepedent and mis-trust
     Organisation Characteristic - Lack of Co-hesion, information which is closely held and lack of risk-taking

If you have created/implemented technology projects in an NGO and experienced it - could you share what are the learnings from both - success and failures of technology projects?

No comments:

Post a Comment