Unify Design & Deliverables
•Download as PPT, PDF•
21 likes•2,606 views
The document summarizes a presentation about creating standardized design documentation systems ("doc systems") to improve efficiency. It outlines how using common templates, components, and processes allows designers to focus on creativity rather than recreating basic elements. Teams that adopt such systems can more easily hand off and update projects between designers. The presentation also discusses specific tools like InDesign that can be used and provides resources for learning more.
Report
Share
Unify Design & Deliverables
- 1. UNIFY DESIGN & DELIVERABLES DC REFRESH - JUNE 2009 Prepared by Nathan Curtis © EightShapes LLC
- 2. Thinking Systematically 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.
- 3. 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
- 4. “ Creates formulaic design and removes creative potential by reusing existing elements.”
- 5. “ Creates formulaic starting points and focuses creative attention by reusing existing elements.”
- 6. “ Deliverables are not be a place to stand out from the crowd . Be creative with your designs.”
- 7. 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
- 8. DELIVERABLE Creating artifacts to communicate user experience, from concepts to comps
- 9. Deliverables http://semanticstudios.com/publications/semantics/000228.php Plus: Contracts Proposals Placards Tri-folds Offers House Rules
- 19. Starting a Deliverable Choose your page size & orientation (order by frequency of use): 1 Letter Landscape 2 Legal Portrait 3 Letter Portrait 4 Tabloid Landscape
- 20. The “Blank Canvas” Every deliverable is born with two measly pages. Page 1: Cover Page 2: Interior
- 21. What’s In A Template? In the Template: Metadata as Variables Grids Chapter divider Color palette Styles (type, object, tables, TOC) NOT In the Template: Sample content Symbols (like markers) Sample page layouts Template moral: Keep it light, Keep it flexible
- 22. Getting the Basics Right DOCUMENT METADATA PAGE TITLES
- 23. Getting The Basics Right Cover Chunking Chapters TOC Change History Clear Objectives Briefs Wireflows Specs Plans
- 24. Symbols Do you get the standard symbol stuff? Absolutely. Markers Callouts Frames Site Maps People Flows (thanks JJG!) Project Plans Reviews
- 25. Speed Up with Dynamic Markers
- 26. Deliverable Reuse: Page Layouts Coming Soon: Isometric Site Maps Sketching & “Design Studios”
- 27. Panacea Deliverables Are Not Assignment: Annotate three screenshots provided, using 1-2 deliverable pages. Results: Wildly different layouts, editorial style, details, and assumed audiences. For our unfortunate readers, it’s empathy time. But there’s hope! Massive frame? A table! A table! Art in middle? Specs by element
- 28. WIREFRAME Standardizing user interface design to be more efficient, consistent, and founded on patterns & components
- 29. Design ≠ Deliverable Units / Size Typography Grid Purpose Depict what a screen looks like Combine pictures & words to document a design
- 30. Lightweight Template Setup Styles Layers Layout Grids 1 Page
- 31. Layers :: Grid Descriptions
- 32. Layers :: Fold A band from 590px to 610px down...
- 33. Layers :: Component Markers Markers automatically added to layer you can hide but trace reusable bits back to the library.
- 35. Yahoo Patterns
- 36. iPhone Symbols
- 37. Wireframe Components A component is a reusable page chunk.
- 38. Pages Some teams even have standard page types. They are built from components, of course.
- 39. 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.
- 40. PUTTING IT ALL TOGETHER Piecing together modular bits to tell a story, or lots of different stories
- 41. Components in a Page
- 42. A Component Across Pages
- 43. A Component in Deliverable
- 44. Wireflows
- 46. Target your audience Design Strategy Editorial Guidelines Design Spec Product Manager Site Strategist Publisher Engineer QA AUDIENCES DESIGN DELIVERABLE What do they need?
- 47. Reuse All Over the Place!
- 48. If Adobe Isn’t Your Thing
- 49. TOOL Why is the first question always “What tool do you use?”
- 50. @mckayp says: Does Nathan Curtis get a kickback from Adobe?
- 51. @carlrice says: indesign is an entirely unacceptable [tool] to present interactive content. @nathanacurtis response? yeah, sometimes, you are absolutely right
- 52. Sometimes You Get Real...
- 53. ...Other Times You Don’t
- 54. What do I design? Visual Designer Content Strategist Information Architect
- 55. 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: Cross platform (think: big teams, vendors, etc) More than sufficient for vector-based drawing Most modular (snippets, linked files like PDFs) Style dominance (type, objects, tables, TOC, etc) UX “designers” include more than just IAs!
- 56. Combining Tools WIREFRAMES Illustrator WIREFRAMES InDesign DELIVERABLES InDesign COMPS Photoshop PROTOTYPES Fireworks Or WIREFRAMES & COMPS Fireworks COPY InCopy
- 57. Tools by Discipline Visual Designer Information Architect “ Design” Content Strategist (Wireframes) (Comps) (Copy) Deliverables Same Templates! Same Styles, Grids, etc..
- 58. EIGHTSHAPES UNIFY What you can download from unify.eightshapes.com
- 59. Deliverables and Wireframes Deliverables Templates Elements Pages Pages Elements Templates Components Wireframes
- 60. Deliverables and Comps Elements Pages Comps Components Deliverables Pages Elements Templates Templates
- 61. So, if you are interested...
- 62. Monthly 1/2 Day Workshops DELIVERABLES WIREFRAMES Friday June 26, 2009 August 2009 Register for $188 at www.eightshapes.com ...
- 63. The Book For designers thinking about reuse in design and deliverables using components (or patterns) during projects or for building a design library. Due July 2009 (hint: you can pre-order)
- 64. Thanks! Nathan Curtis EightShapes LLC [email_address] @nathanacurtis | nathanacurtis on most networks This presentation on slideshare.net/nathanacurtis/