Login    /    Register



Tony Collins suggests that you can't implement something centrally and expect it to be adopted locally. Here’s an example: A UK local fire service had no interest in supporting the new central system, which they saw as being foisted upon them. It’s critical to get approval and support from end users in advance for a new IT system to work. Think about it: from the end user's point of view, this is theirsystem. If they want it to work, they will make it work. If they don't—count on it, they'll surely make a mountain out of a molehill.

Ken added: How can you argue with the thoughts in this article. There are many projects, applications and even companies that no longer exist because they didn't get the most important opinion for a product - the end user. Either an easy to use application that missed the need or an offering that met exactly the requirements but was too difficult to interpret or use can mean your effort was wasted. And it can have devastating results. Someone else usually comes along, takes your concept and makes it usable and becomes very successful. Or even relatively successful applications can be replaced by bigger and better, you also cannot rest on your success. You have to keep improving but always with the end user in mind (and hopefully involved).

  |     |     |     |     |  

Subject Matter

User Involvement

About the Contributor:

Attributed Author

Tony Collins

Tony Collins writes a blog for ComputerWorldUK and is freelance writer. Tony co-founded Campaign4Change. Tony worked as editor and writer for Computer Weekly. Tony co-wrote a book of IT project management case studies called Crash (Simon & Schuster).
Jim JohnsonJim
Keith KerrKeith
Stijn Van LooyStijn
Van Looy
Pascal de HaanPascal
de Haan
Dave  BatsDave
Joseph PuthenpurackaJoseph

The Standish Group News

The Standish Group Events

The Standish Group Blog

CHAOS Tuesday Podcast

The Dezider