As software development methodologies evolve, so must the developers themselves. There’s a new set of expectations of what software should be, as well as a new set of expectations for what a developer’s responsibilities should cover.
The times when you could get away with implementing applications with decent-looking screens and calling it a day are fading. Even with small and less visible projects, it’s no longer acceptable if an application has poor User Experience (UX). UX is vital no matter the size or scope of the project.
As Waterfall is replaced by Agile and delivery cycles become shorter and shorter, developers need to champion the end-to-end product. Focusing just on database performance or making the product feature complete doesn’t quite cut it anymore. Developers need to step up and take wider responsibilities even if it involves exploring uncharted terrain.
So, it’s now the developers’ job to go beyond the nuts and bolts of building an app and have a broader perspective over the work they are doing. Sure, UX is not their main focus or their area of expertise, but a well-coded, robust and performant app is just not enough anymore if the user experience is broken.
How do you get those old fashion developers to think differently? You give them a simple checklist on the essential steps they can follow to adopt a new perspective on UX. You help them bridge the gap between their core set of skills and a great application.
This checklist guides you through the most important questions developers must learn to ask and to answer, and shows you why these answers make the difference between developing a decent User Experience, and developing one that’s great.
Follow the checklist to see if your application’s User Experience is on the right track. Use it as reference, print it, stick it on the walls, and make it visible. Always keep in mind that developers are increasingly expected to play a bigger role in the delivery of an awesome User Experience.