Iterative design
Out of context: Reply #13
- Started
- Last post
- 13 Responses
- ninjasavant0
Hi all, good discussion goin on here. A little background on what my thoughts are on the process.
Yes, it would be ideal to get the specs and the functionality and go off and start creating with those guidelines. This increasingly isn't the case with our development cycle. For better or worse visual design is brought in very early during planning phases. What has happened is that our designers kill themselves to turn around an entire UIs worth of design, a complete package, during the beginning stages. Throughout the cycle changes are made to the software, changes are made in the UI, then some dev manager decides he stopped liking any of it and tells the developer to just come up with something and throw away our months of work that was tested and validated.
We need a way to fit in with this development process. We can flame all we want about how development should get their heads from their asses and start playing ball (and we have) but its just not going to happen.
I want to define a process whereby the design of the UI happens at the same rate as the whole program (or learn about one that exists). During the research phase we design and deliver wireframes, at the next phase identify color palettes, next phase icon style, etc etc. These are the realities of corporate design teams. Not ideal, but an interesting challenge.