In a recent conference call, I was accused of 'hiding' behind the user. During the call, it was demanded that we go ahead and make assumptions about the user to ensure the project time line was met. My response was that 'this is dangerous at best' because as a user expert, I was trained that I am not my user and any assumption may inject bias.
This is symptomatic of the gap between the status quo of the software development life cycle and the iterative approach of the user centered design process. Where the SDLC fails, is that it doesn't account for iterations... in other words, you repeat the SDLC in versions. UCD assumes that you will pass through it several times and is designed that way. So, the challenge lies in assimilating an iterative and qualitative approach within a quantitative serial cycle.
Some solutions are to integrate a system of user based checks and balances within the current SDLC. This maintains the process that the development organization requires to function while not being solely dependent on UAT findings to fill the need.
No comments:
Post a Comment