We use and teach teams better ways to create user experience documentation.
On the face of it, the “doc system” is a set of templates. But it’s actually much more than that.
Process RESET!
BEFORE SYSTEM
Designer starts project, finishes analysisDesigner authors wireframes from scratch, reinventing already existing componentsGroup reviews design, extensive commentsDesigner reworks wireframes, gradually narrowing to existing design systemGroup approves design (finally)Designer delivers wireframes in PDF; retains source files in proprietary format
IT gets wireframes; deep analysis reveals many components w/o HTML/CSS/codeGroup scrambles to reconcile design ideas vs what’s actually possibleDesigner continues to revise wireframes
IT creates new but realistic HTML & CSS
$ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $
DON’T FORGET THESE BENEFITS TOO!
MORE PORTABILITY: Group not constrained to use same designer for updates since source files are reusableLESS REINVENTION: Other designers don’t reinvent nearly so many new components due to the common approach
WITH SYSTEM
Group trains designer on doc system (once)
Designer starts project, finishes analysisDesigner uses client’s doc system
Group reviews wireframes, fewer comments
Designer reworks wireframes faster
Group approves design
Designer delivers PDF AND source files
IT assesses familiar systems faster
IT extends component HTML/CSS
$ $ $ $ $ $ $ $ $ $ $ $ $ $ Courtesy Martin Hardee, Cisco Systems
“ Creates formulaic design and removes creative potential by reusing existing elements.”
“ Creates formulaic starting points and focuses creative attention by reusing existing elements.”
“ Deliverables are not be a place to stand out from the crowd . Be creative with your designs.”
Creating a System for Teams 1 2 3 Interviews Survey Doc Reviews Planning Discovery Analyze Templates Assets Samples Packaging Pilot Assemble Documentation Training Demos Coaching Reviews Adopt
DELIVERABLE
Creating artifacts to communicate user experience, from concepts to comps
Markers automatically added to layer you can hide but trace reusable bits back to the library.
Element Libraries
Yahoo Patterns
iPhone Symbols
Wireframe Components
A component is a reusable page chunk.
Pages
Some teams even have
standard page types.
They are built from components, of course.
Wireframing Conventions
C’mon, who wants to fight?
A wireframing system must have a consistent visual language, so you have to make decisions like:
Long live gray scale. But minimize or remove gray.
Use Arial. Only Arial!
Blue for interactivity. Orange for annotation. Red for errors. No more color.
X for images.
No visual embellishments. Rounded corners, gradients, stroke weights only if it conveys meaningful structure.
PUTTING IT ALL TOGETHER
Piecing together modular bits to tell a story, or lots of different stories
Components in a Page
A Component Across Pages
A Component in Deliverable
Wireflows
Copy in Wireframes?
Target your audience Design Strategy Editorial Guidelines Design Spec Product Manager Site Strategist Publisher Engineer QA AUDIENCES DESIGN DELIVERABLE What do they need?
Reuse All Over the Place!
If Adobe Isn’t Your Thing
TOOL
Why is the first question always “What tool do you use?”
@mckayp says:
Does Nathan Curtis get a kickback from Adobe?
@carlrice says:
indesign is an entirely unacceptable [tool] to present interactive content.
@nathanacurtis response? yeah, sometimes, you are absolutely right
Sometimes You Get Real...
...Other Times You Don’t
What do I design? Visual Designer Content Strategist Information Architect
So, Why InDesign?
Our surveys reveal that Visio and Omnigraffle are the two most popular tools in the IA community. We work in InDesign because:
0 comments
Post a comment