(This is the final installment of a four part series. Go back and read Part 1, Part 2, and Part 3 if you need to get caught up with the rest of the class.)

Now that I've given you a look at what it means to incorporate good design practices early in your process, and quite probably scared you into an early retirement by laying out some of the ramifications of not doing it, I'll wrap things up with some tips on what to do to make sure you're staying on the path of design righteousness.

I've already exhorted you to address design early. And I'll keep doing it until you listen. I'm pushy like that, but I assure you that it's for your own good. That's step one.

The next thing: Make sure the people working on the product have visibility and access to each other. Your product can only be made better if business, design, and dev are working together. This keeps them all on the same page and working toward the same goal. Sheltering your developers from the realities of the business and business processes will gain you nothing but grief in the long run. Sadly, it's a mistake that is all too common.

And lastly, get your users involved. In fact, don't just get them involved, keep them involved. Test your product for usability, solicit their feedback, treat them like the invaluable resource that they are. Make sure you're meeting their needs and keeping them satisfied. (I bet you never thought software development was so much like dating.)

Without user satisfaction, you have nothing. Well, nothing except a useless piece of software that you've spent a lot of money to design and develop, and that you'll now spend even more money going back to redesign and redevelop.

Be first to comment this article

Only registered users can write comments.
Please login or register.

Powered by AkoComment Tweaked Special Edition v.1.4.6
AkoComment © Copyright 2004 by Arthur Konze - www.mamboportal.com
All right reserved