Constructing and Evaluating Your Design Solution - Data Visualization: A Successful Design Process - page 164

You see, this is the part of the design process where stresses and strains emerge—the
ill-timed bugs, dataset problems, functional failures, unwanted interference. During
this stage it is important that you keep your cool and see your tasks through as
efficiently as possible.
As you work through the construction process, it is important to focus on getting the
functional elements of your solution working first before spending too much time
achieving your desired aesthetic or incorporating technical flair. It is always very
tempting to spend too much time, too soon on things that shouldn't really be given
such priority. Just remind yourself that there is no point running out of time trying
to make something look good when it doesn't yet function. Remember, it will be
easier to make something that is functional, beautiful, than it is to make something
beautiful, functional.
As we mentioned earlier in the topic, you will rarely create a worthy project without
the need for iteration. While we have to present the sequences of the methodology
in this topic in linear fashion, there is always going to be movement forward and
backwards between stages. This is something that should be accepted but also
embraced—it is part and parcel of any creative process. While a methodological
approach to this challenge gives you structure and a neat framework of concerns
to work through, iteration gives you the creative breathing room to allow different
ideas to blossom and influences to take hold. It is something that you should be
prepared to do and plan for.
You clearly want to avoid long iterative cycles but smaller ones can really help
you explore, clarify, and refine your potential solutions. It may be that you end up
following two or three parallel options to quite an advanced stage and then see
which emerges as the strongest. Indeed, some clients will state a need for evidence of
alternatives before committing themselves. For these client-based projects, you need
to maintain open dialog throughout to avoid any inconsistency in interpretation
from either party. Do your absolute best to eradicate the possibility of last minute
surprises about a solution not matching requirements or expectations. That is a sting
in the tail nobody wants!
As you work through your construction stages, in particular, there will be points
when you recognize a need to make certain sacrifices. There may be things you
intend to include but can't justify them. Trade-offs are a constant necessity caused by
time or resource constraints.
Some of the things we find hardest to drop are the most irrational. We often find
ourselves in a sense of denial. This may come from a desire to include features that
you have slaved over or become overly precious about.