One of the keys to a successful system launch seems to be directly correlated to its ability to provide a quality user experience from its inception. While the technical side is the key to making the program work, its overall success is based on the system’s ability to engage the user and provide a useful service.
After reading the “System Development Life Cycle” it seems clear that by analyzing the development models normally used by a developer, outdated plans such as the waterfall methodology are not effective when being used by “knowledgeable workers.” The waterfall model has seven key steps, but they mainly focus on the ability to create effective and bug free coding. The users experience is not a main priority, and I believe this became more of an issue in the late nineties when computer programs became part of the everyday lives of most people. Prior to 1991, computers were mainly used for specific tasks, while the personal computer made them a more main stream tool starting around that timeframe.
Models such as rapid prototyping (sometimes called rapid application development) prioritize the user experience, even before the back end code is really written. Initial launches in rapid prototyping allows end users to test the programs usefulness, and this will create a more successful end product.
“System Development Life Cycle” also makes a strong point when acknowledging that program development successes hinge on delivering a quality product on time. This is not unique to this line of work, as delivering any product on time is crucial to its overall success. However, the article acknowledges that large, successful organizations such as Microsoft and Netscape managed a timeline by “scaling back product features rather than let[ting] milestones slip” when the deadlines got close.
From a marketing management perspective, I find this interesting because I would have initially thought that if my organization were to build a proprietary digital product that I would have needed to manage around the creativity and timeline of the software building team. Now, if I were to facilitate the creation of something like a proprietary CRM or internal software, I would prioritize a draft of the program for my internal clients to try, and create clear deadlines after consulting with the creative team about what was feasible to create in that timeline.