Thursday, May 18th, 2006
As will the first list, this list is by no means a complete account of every reason why a web app might fail. There are countless reasons, Iâ€™m sure, and most are part of a failing strategy and donâ€™t do the damage all by themselves. I have focused on reasons made prominent by the current situation we find ourselves in: with extremely low barriers to creation alongside an explosion of social web applications. This combination is interesting and weâ€™re seeing the evolution of social software in near real-time.
This time, the list includes:
- Theyâ€™re never built.
- They donâ€™t plan for change.
- They donâ€™t think holistically.
Each of the items has a bit of explaination below them, mentioning what it means to the end-user and to the foundation of the company creating the application. I’m not completely sure about all of them in the list (like the “they dont charge money” one), but there are some very valid points made. People still have some of that “if you build it, they will come” idea in their heads to really think sanely when developing their sites. They think that if they put this incredible thing out there, everyone will realize it for what it is and flock to it.
Too bad it doesn’t work that way, huh?
Posted by Chris Cornutt at 7:22 am