Re: [agile-usability] Re: principles for UI architectures
>I'll just respond to a small part of your post.
>So, I'm wondering what would happen if we just did the
>interface work as required by the feature we're working
>on. Why can't we approach UI design like we do
>evolutionary code design?
>What forces resist evolutionary interface design?
It likely depends on the type of product that you have, but with
applications that people use as part of their core job (i.e. spending
the majority of their workday using the app), changing the user
interface significantly decreases productivity as users try to forget
the old layout and learn the new. The outcry is usually terrific.
We try to design for what is coming in the future so that we don't have
to modify the interface drastically and make our current customers mad.
If we designed for only this release then refactored the interface on
the next release, we wouldn't have any customers left. I think that is
the force that resists evolutionary design. :-)