I'm working on web interaction testing project and I was hoping to
enlist the help of IxDA members. Help a brother out by taking a few
minutes to fill out this 9 question survey, via the link below, on
your typical design process. Next week I'll share the results on
this discussion thread. Thank you all in advance!
This has been on my mind a lot lately. I feel like our process is
very fast and accomplishes the right things, but I don't have much
to compare it to. It'd really mean a lot to me to know your
company's design process and to gather any feedback you have on the
process I outline below. I'm looking for ways to improve what we
So here's how we do design at onegreatfamily.com:
We are a small company, we have 8 developers. We consider ourselves
an "Agile/Scrum" shop. We have 2 designers, one assigned to the
windows app and one assigned to the website.
What's your company's process/pipeline/set of tools for delivering
and communicating designs (and associated visual design assets) to
your dev team?
*[Addressed particularly to "innies" in software development orgs
though anyone's insights much appreciated]*
TO be clear: I'm NOT asking the "Visio vs Illustrator vs Fireworks
etc" conversation. I'm asking what happens *after* the design team
has determined (at least a first cut of) both how the app should
work, and how it should look.
Ok, so this turned into a three-part diagram, not two, and what I
thought were the "characteristics" in part-two turned into the
"principles" of part-three, but whatever, design is iterative
right? I'd really like to stress-test this again - comments please!
Can anyone recommend a persuasive, unquestionably authoritative
presentation on why a formal design process, characterized by
progress toward increasing precision -- for hardware AND software --
makes good business sense?
I've got a VP that doesn't have the time or patience to read
anything too lengthy, who's an electronics engineer, struggling to
understand the needs of the burgeoning software department under
Too much design jargon will be a turn-off.
Perhaps a presentation on slide-share? Something by the CEO, or Chief
Engineer of an electronics manufacturing Fortune 500 maybe?
I'm having trouble with our design process. It seems like it isn't
working, we are falling behind schedule. What I'd like to know
What is your design workflow? Do you do low-res mockups first, or
start with an existing design? (This is in the context of creating a
new application to fit into an existing suite of apps, so the visual
style is already set)
How long does your design process take? If you had to do say a dozen
screens, would you expect going from nothing to handing it to a
developer to take 2 weeks? 4 weeks?
Earlier this week at the local Utah IxDA meeting and over the last
while at various places I've heard the topic of how to deal with
developers come up. I was thinking about it and realized I had a lot
to say about it. Sorry for the length :)
I currently work at a very small company, less then 20. But compared
to the other stories I've heard lately from Interaction Designers
like myself in Utah, our company gets surprisingly consistent results
from our developers in regards to design.
We're on the verge of starting a new-ish project (some work done
already, but that's another issue).
The system is to be built using an SOA approach, which, it seems,
means that it will be be highly dependent on business process analysis
practices in order to define the Services. (In theory, there will be a
BPA and a UX person on the team...although we're both actually
interaction designers and will be covering both roles.)
Have you successfully integrated business process analysis practices
with interaction design practices?
In hjis book, Hugh Dubberly <http://www.dubberly.com/author/hugh/> have
collected over one-hundred descriptions of design and development processes,
from architecture, industrial design, mechanical engineering, quality
management, and software development.