Once you've evolved high-level blueprints and
architectural page mockups, you're ready to collaborate with your
graphic designer to create deign sketches on paper of major pages in the
web site. In the research phase the design team has begun to develop a
sense of the desired graphic identity or look and feel. The technical
team has assessed the information technology infrastructure of the
organization and the platform limitations of the intended audiences.
They understand what's possible with respect to features such as dynamic
content management and interactivity. And of course the architect has
designed the high-level information structure for the site. Design
sketches are a great way to pool the collective knowledge of these three
teams in a first attempt at interface design for the top level pages of
the site. This in a wonderful opportunity for interdisciplinary user
interface design using the architectural mocks ups as a guide; the
designer begins sketching pates of the site on sheets of paper. As the
designer sketches each page questions arise that must be discussed. Here
is a sample sketching session dialog:
Programmer: I like what you're doing with the
layout of the main page, but I'd like to do something more interesting
with the navigation system.
Designer: Can we implement the navigation system using pull down menus? Does that make sense architecturally?
Architect: That might work but it would be
difficult to show context in the hierarchy. How about a tear-|way table
of contents feature? We've had pretty good reactions to that type of
approach front users in the past.
Programmer: We can certainly go with that
approach from a purely technical perspective. How would a tear away
table of contents look? Can you sketch it for us? I'd like to do a quick
and dirty prototype. These sketches allow rapid iteration and intense
collaboration.
No comments:
Post a Comment