Designing Rules ~ IA Summit 2009
Upcoming SlideShare
Loading in...5
×
 

Designing Rules ~ IA Summit 2009

on

  • 8,866 views

In designing transactional and content-rich web sites, rules provide an underlying structure that governs the experience: what is displayed, when it’s displayed, and how it responds to user actions. ...

In designing transactional and content-rich web sites, rules provide an underlying structure that governs the experience: what is displayed, when it’s displayed, and how it responds to user actions. Web design today is at an important crossroads: more complex technologies offer a greater range of features and functions, which permit more elaborate experiences.

The depth of these systems means that information architects no longer design structures with specific pieces of content in mind, but instead have to design structures around classifications, categories, and abstractions. In conjunction with these so-called “objects,” information architects must consider the rules that govern their appearance, display, and response to users.

This session introduces a framework for thinking about rules, providing a vocabulary and taxonomy of rules where none has previously existed.

Statistics

Views

Total Views
8,866
Views on SlideShare
8,688
Embed Views
178

Actions

Likes
53
Downloads
322
Comments
1

7 Embeds 178

http://librarianlikeme.wordpress.com 145
http://www.slideshare.net 20
http://bnunnally.tumblr.com 5
http://www.scoop.it 4
http://bradsramblings.com 2
http://localhost:8888 1
http://webcache.googleusercontent.com 1
More...

Accessibility

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • thanks
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Documentation survey <br />
  • <br /> <br />
  • What you should and should not do. <br /> What kind of person you should be <br /> Means for living with other humans. <br /> <br /> <br />
  • Authors like: Doctorow Gaiman <br /> Subjects like: Human behavior, Small business <br /> Toys like: Thomas trains <br /> Not that it picked things I’m interested in, but of all the things I’m interested in, it picked these. <br />
  • Authors like: Doctorow Gaiman <br /> Subjects like: Human behavior, Small business <br /> Toys like: Thomas trains <br /> Not that it picked things I’m interested in, but of all the things I’m interested in, it picked these. <br />
  • Authors like: Doctorow Gaiman <br /> Subjects like: Human behavior, Small business <br /> Toys like: Thomas trains <br /> Not that it picked things I’m interested in, but of all the things I’m interested in, it picked these. <br />
  • Authors like: Doctorow Gaiman <br /> Subjects like: Human behavior, Small business <br /> Toys like: Thomas trains <br /> Not that it picked things I’m interested in, but of all the things I’m interested in, it picked these. <br />
  • <br /> <br /> <br /> <br /> <br /> ▼ <br /> What is a rule? <br /> <br /> plainview.files.wordpress.com—moses1.jpg <br /> <br /> <br /> •Wireframe: what goes on the screen <br /> •Rule: how the screen changes in different circumstances <br /> •CORE IDEA: <br />
  • ▼Enginewww.drivingenthusiast.net—MAZDA3_engine_HR.jpg <br /> •Not quite: while rules are crucial for \"driving\" the user experience, they aren't the heartbeat <br /> or the central nervous system. Rules also are not a single cohesive system with lots of <br /> moving parts. Rules are applied here and there as necessary. <br /> Rules make use of the language of a web site without defining it. <br /> <br /> <br /> <br /> <br /> <br /> <br />
  • ▼Recipeslh4.ggpht.com—p0002180.jpg <br /> •Not quite: while rules provide direction, rules aren't linear instructions -- they feel more like <br /> mechanisms for selecting ingredients <br /> Rules must apply in specific situations with clear criteria regarding presentation. The metaphor breaks down quickly. <br /> I can use the same recipe when I want to make a dish. <br /> Different circumstances call for different rules. <br /> Doesn’t help us understand rules. <br />
  • ▼Editorwww.hadesign.net—WTVI QC room.jpg <br /> •Help us make choices about what's seen and how we see it <br /> •Director: overall experience <br /> •Actor: content itself <br /> Editor crafts one aspect of the experience: within the format of the medium and the parameters of the director’s vision, we get the editor <br /> <br /> <br /> <br /> Editor: starts with piles of footage, pulls out the stuff that works best <br /> <br /> <br /> <br /> <br /> We’ll consider some other metaphors later <br /> <br /> <br /> <br /> For now, let’s see how rules fit into IA <br /> <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • ▼A new-ish definition (more like a description) of IA, in decreasing tangibility: <br /> •Templates: How content is arranged on the screen <br /> •Navigation and classification: How people find content <br /> •Content Types: set of content structures that give us a meaningful language for talking about the range of information on the site (functional content types vs. format content types) <br /> •Rules: they're what stitch the experience together, like an editor <br /> <br /> <br /> <br /> <br /> ▼Why IAs should care about rules <br /> •Rules are germane to the user experience <br /> •IA work gets more abstract: talking about contnet in terms of it’s type <br /> •IA needs a way to integrate real-world \"instances\" into abstract structures <br /> •Rules are, in a sense, a structure that governs the implementation of content, that bridge the gap between the abstract structures we create to form context (Hinton) and the way those structures are populated <br /> •They describe how everything fits together <br /> <br /> <br /> <br /> Small amount of literature on this stuff: I struggled to find any thinking on the mechanisms behind the display, as related to user experience. <br /> <br /> <br /> <br /> Rules govern different aspects of the user experience: Content. <br />
  • ▼A new-ish definition (more like a description) of IA, in decreasing tangibility: <br /> •Templates: How content is arranged on the screen <br /> •Navigation and classification: How people find content <br /> •Content Types: set of content structures that give us a meaningful language for talking about the range of information on the site (functional content types vs. format content types) <br /> •Rules: they're what stitch the experience together, like an editor <br /> <br /> <br /> <br /> <br /> ▼Why IAs should care about rules <br /> •Rules are germane to the user experience <br /> •IA work gets more abstract: talking about contnet in terms of it’s type <br /> •IA needs a way to integrate real-world \"instances\" into abstract structures <br /> •Rules are, in a sense, a structure that governs the implementation of content, that bridge the gap between the abstract structures we create to form context (Hinton) and the way those structures are populated <br /> •They describe how everything fits together <br /> <br /> <br /> <br /> Small amount of literature on this stuff: I struggled to find any thinking on the mechanisms behind the display, as related to user experience. <br /> <br /> <br /> <br /> Rules govern different aspects of the user experience: Content. <br />
  • ▼A new-ish definition (more like a description) of IA, in decreasing tangibility: <br /> •Templates: How content is arranged on the screen <br /> •Navigation and classification: How people find content <br /> •Content Types: set of content structures that give us a meaningful language for talking about the range of information on the site (functional content types vs. format content types) <br /> •Rules: they're what stitch the experience together, like an editor <br /> <br /> <br /> <br /> <br /> ▼Why IAs should care about rules <br /> •Rules are germane to the user experience <br /> •IA work gets more abstract: talking about contnet in terms of it’s type <br /> •IA needs a way to integrate real-world \"instances\" into abstract structures <br /> •Rules are, in a sense, a structure that governs the implementation of content, that bridge the gap between the abstract structures we create to form context (Hinton) and the way those structures are populated <br /> •They describe how everything fits together <br /> <br /> <br /> <br /> Small amount of literature on this stuff: I struggled to find any thinking on the mechanisms behind the display, as related to user experience. <br /> <br /> <br /> <br /> Rules govern different aspects of the user experience: Content. <br />
  • ▼A new-ish definition (more like a description) of IA, in decreasing tangibility: <br /> •Templates: How content is arranged on the screen <br /> •Navigation and classification: How people find content <br /> •Content Types: set of content structures that give us a meaningful language for talking about the range of information on the site (functional content types vs. format content types) <br /> •Rules: they're what stitch the experience together, like an editor <br /> <br /> <br /> <br /> <br /> ▼Why IAs should care about rules <br /> •Rules are germane to the user experience <br /> •IA work gets more abstract: talking about contnet in terms of it’s type <br /> •IA needs a way to integrate real-world \"instances\" into abstract structures <br /> •Rules are, in a sense, a structure that governs the implementation of content, that bridge the gap between the abstract structures we create to form context (Hinton) and the way those structures are populated <br /> •They describe how everything fits together <br /> <br /> <br /> <br /> Small amount of literature on this stuff: I struggled to find any thinking on the mechanisms behind the display, as related to user experience. <br /> <br /> <br /> <br /> Rules govern different aspects of the user experience: Content. <br />
  • ▼A new-ish definition (more like a description) of IA, in decreasing tangibility: <br /> •Templates: How content is arranged on the screen <br /> •Navigation and classification: How people find content <br /> •Content Types: set of content structures that give us a meaningful language for talking about the range of information on the site (functional content types vs. format content types) <br /> •Rules: they're what stitch the experience together, like an editor <br /> <br /> <br /> <br /> <br /> ▼Why IAs should care about rules <br /> •Rules are germane to the user experience <br /> •IA work gets more abstract: talking about contnet in terms of it’s type <br /> •IA needs a way to integrate real-world \"instances\" into abstract structures <br /> •Rules are, in a sense, a structure that governs the implementation of content, that bridge the gap between the abstract structures we create to form context (Hinton) and the way those structures are populated <br /> •They describe how everything fits together <br /> <br /> <br /> <br /> Small amount of literature on this stuff: I struggled to find any thinking on the mechanisms behind the display, as related to user experience. <br /> <br /> <br /> <br /> Rules govern different aspects of the user experience: Content. <br />
  • ▼A new-ish definition (more like a description) of IA, in decreasing tangibility: <br /> •Templates: How content is arranged on the screen <br /> •Navigation and classification: How people find content <br /> •Content Types: set of content structures that give us a meaningful language for talking about the range of information on the site (functional content types vs. format content types) <br /> •Rules: they're what stitch the experience together, like an editor <br /> <br /> <br /> <br /> <br /> ▼Why IAs should care about rules <br /> •Rules are germane to the user experience <br /> •IA work gets more abstract: talking about contnet in terms of it’s type <br /> •IA needs a way to integrate real-world \"instances\" into abstract structures <br /> •Rules are, in a sense, a structure that governs the implementation of content, that bridge the gap between the abstract structures we create to form context (Hinton) and the way those structures are populated <br /> •They describe how everything fits together <br /> <br /> <br /> <br /> Small amount of literature on this stuff: I struggled to find any thinking on the mechanisms behind the display, as related to user experience. <br /> <br /> <br /> <br /> Rules govern different aspects of the user experience: Content. <br />
  • ▼A new-ish definition (more like a description) of IA, in decreasing tangibility: <br /> •Templates: How content is arranged on the screen <br /> •Navigation and classification: How people find content <br /> •Content Types: set of content structures that give us a meaningful language for talking about the range of information on the site (functional content types vs. format content types) <br /> •Rules: they're what stitch the experience together, like an editor <br /> <br /> <br /> <br /> <br /> ▼Why IAs should care about rules <br /> •Rules are germane to the user experience <br /> •IA work gets more abstract: talking about contnet in terms of it’s type <br /> •IA needs a way to integrate real-world \"instances\" into abstract structures <br /> •Rules are, in a sense, a structure that governs the implementation of content, that bridge the gap between the abstract structures we create to form context (Hinton) and the way those structures are populated <br /> •They describe how everything fits together <br /> <br /> <br /> <br /> Small amount of literature on this stuff: I struggled to find any thinking on the mechanisms behind the display, as related to user experience. <br /> <br /> <br /> <br /> Rules govern different aspects of the user experience: Content. <br />
  • <br /> <br />
  • ▼Govern the display of content: Content Rules <br /> •Conditional Display Rules -- Whether to show the box <br /> •Filtering Rules -- What content to show in the box <br /> ▼Responsibility -- who controls the content <br /> •Editorial Guidelines vs. Application Logic: rules followed by humans vs. rules implemented <br /> by a system <br /> ▼Examples <br /> <br /> <br /> • <br /> <br /> <br /> cooksillustrated.com <br /> <br /> <br /> Strong editorial influence here. Decisions that in other media might be left up to humans, we leave up to the machine, But we provide a set of guidelines to make sure it chooses wisely. <br /> <br /> <br /> <br /> For cooks, you can imagine the range of considerations: latest, magazine, theme, categories <br /> (Aside: tools for helping content editors do their jobs better) <br />
  • ▼Govern the display of content: Content Rules <br /> •Conditional Display Rules -- Whether to show the box <br /> •Filtering Rules -- What content to show in the box <br /> ▼Responsibility -- who controls the content <br /> •Editorial Guidelines vs. Application Logic: rules followed by humans vs. rules implemented <br /> by a system <br /> ▼Examples <br /> <br /> <br /> • <br /> <br /> <br /> cooksillustrated.com <br /> <br /> <br /> Strong editorial influence here. Decisions that in other media might be left up to humans, we leave up to the machine, But we provide a set of guidelines to make sure it chooses wisely. <br /> <br /> <br /> <br /> For cooks, you can imagine the range of considerations: latest, magazine, theme, categories <br /> (Aside: tools for helping content editors do their jobs better) <br />
  • Perhaps a little more obscure, a little more meta <br /> Rules that govern how people experience the information <br /> Imagine you could say, in rooms of this type, always show 3 exits <br /> <br /> <br />
  • ▼Govern the range of experience: Navigation Rules <br /> •What menu options to display/facets <br /> ▼Examples <br /> <br /> <br /> • <br /> <br /> <br /> reviews.cnet.com—mp3-players <br /> <br /> <br /> <br /> <br /> • <br /> <br /> <br /> reviews.cnet.com—digital-cameras <br /> <br /> <br /> <br /> <br />
  • ▼Govern the range of experience: Navigation Rules <br /> •What menu options to display/facets <br /> ▼Examples <br /> <br /> <br /> • <br /> <br /> <br /> reviews.cnet.com—mp3-players <br /> <br /> <br /> <br /> <br /> • <br /> <br /> <br /> reviews.cnet.com—digital-cameras <br /> <br /> <br /> <br /> <br />
  • ▼Govern the range of experience: Navigation Rules <br /> •What menu options to display/facets <br /> ▼Examples <br /> <br /> <br /> • <br /> <br /> <br /> reviews.cnet.com—mp3-players <br /> <br /> <br /> <br /> <br /> • <br /> <br /> <br /> reviews.cnet.com—digital-cameras <br /> <br /> <br /> <br /> <br />
  • Facets are the same, but the values vary <br /> Clicking one yields the same result <br /> Rules help select appropriate values <br /> Highly mathematical/algorithmic <br />
  • Facets are the same, but the values vary <br /> Clicking one yields the same result <br /> Rules help select appropriate values <br /> Highly mathematical/algorithmic <br />
  • Not really editorial, not really about navigation <br />
  • <br /> Kind of rudimentary example, but illustrates exactly what I’m talking about. <br /> <br /> <br /> This is a foaming attachment for my Krups I bought recently. <br /> <br /> <br /> Crucial information that might vary in different circumstances. <br /> <br /> <br /> <br /> <br /> <br /> <br /> ▼Govern the rendering of information <br /> •Business rules around calculating price/shipping <br /> •Business rules about options available to users <br /> •Business rules about login/account information display <br /> ▼Filtering infinite information space <br /> •Search results <br /> •Flight searches <br /> ▼Example <br /> •Offering different shipping options depending on destination <br /> •Calculating shipping charge based on supplied ZIP code <br /> <br /> <br /> <br /> ALSO: Decision Points <br />
  • <br /> Kind of rudimentary example, but illustrates exactly what I’m talking about. <br /> <br /> <br /> This is a foaming attachment for my Krups I bought recently. <br /> <br /> <br /> Crucial information that might vary in different circumstances. <br /> <br /> <br /> <br /> <br /> <br /> <br /> ▼Govern the rendering of information <br /> •Business rules around calculating price/shipping <br /> •Business rules about options available to users <br /> •Business rules about login/account information display <br /> ▼Filtering infinite information space <br /> •Search results <br /> •Flight searches <br /> ▼Example <br /> •Offering different shipping options depending on destination <br /> •Calculating shipping charge based on supplied ZIP code <br /> <br /> <br /> <br /> ALSO: Decision Points <br />
  • ▼BUT: things are getting ambiguouswww.checkout.org.cn—platypus3_h.jpg <br /> •The taxonomy here can not address every situation <br /> •Products are becoming more complex <br /> Some things in common: <br /> Criteria for selecting behaviors or responses within the context of a presentation <br />
  • ▼BUT: things are getting ambiguouswww.checkout.org.cn—platypus3_h.jpg <br /> •The taxonomy here can not address every situation <br /> •Products are becoming more complex <br /> Some things in common: <br /> Criteria for selecting behaviors or responses within the context of a presentation <br />
  • <br /> <br />
  • ▼Patternsfarm4.static.flickr.com—3267227227_660b6ab4f4_b.jpg <br /> •Generalized approaches to common problems <br /> •BUT: rules expressed as generalizations (choose latest content) without specific <br /> applications <br /> •AND: a pattern can describe the kinds of rules needed <br /> •Example: developer.yahoo.com—pattern.php <br /> <br /> <br />
  • <br /> <br />
  • ▼Componentsfarm3.static.flickr.com—2314610838_beecd46647_o.jpg <br /> •Layout of content specific to a design system <br /> •BUT: one component can support multiple rules <br /> •AND: a component can specify the kinds of rules needed <br /> •Examples: www.sun.com—g39.html <br /> <br /> <br />
  • <br /> <br />
  • ▼Ruleswww.gutenberg.org—p1.jpg <br /> •For a specific area of a specific interface, rules describe what content is to appear <br /> •Rules use the language established for a specific web site: content types, metadata, <br /> components <br /> How do we structure rules? <br /> What do we need to think about for each rule? <br /> <br /> <br />
  • For any given rule, there are five things you need to think about. <br />
  • Show/Display <br /> <br /> <br />
  • Which content type <br />
  • How select content from content type? <br /> Separate from content type because dependency between filter and content type <br />
  • How many items are you going to show? <br />
  • What fields of the content will you show? <br />
  • What’s the default? <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> http://www.flickr.com/photos/jamesjordan/2226419650/sizes/o/ <br /> <br /> <br />
  • <br /> <br />
  • Which category will serve as the navigation mechanism? <br />
  • How will users select value? (menu, slider) <br />
  • What are the upper and lower limits? <br />
  • How does changing the value affect the display? <br />
  • Can users see all content within the category? <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • Chooses content meaningful to the user <br />
  • Leads to specific choices <br />
  • Leverages existing IA parameters <br />
  • Clear on how rule is enforced <br />
  • Addresses all possible scenarios <br />
  • Has a good default <br />
  • Rules may not govern how we interact with people, but they do govern how our products behave relative to users <br /> Another possibel metaphor: if not the soul of the product, then certainly its frontal lobe <br />
  • <br /> <br />
  • <br /> <br />

Designing Rules ~ IA Summit 2009 Designing Rules ~ IA Summit 2009 Presentation Transcript

  • Designing Rules The Engine of User Experience by Dan Brown, EightShapes IA Summit 2009, Memphis, TN, USA 1 Monday, March 23, 2009
  • 1 Monday, March 23, 2009
  • Please tag with: #rules #ias09 2 Monday, March 23, 2009
  • 2 Monday, March 23, 2009
  • 3 Monday, March 23, 2009
  • Not these kinds of rules 3 Monday, March 23, 2009
  • 4 Monday, March 23, 2009
  • These kinds of rules 4 Monday, March 23, 2009
  • These kinds of rules 4 Monday, March 23, 2009
  • These kinds of rules 4 Monday, March 23, 2009
  • These kinds of rules 4 Monday, March 23, 2009
  • 5 Monday, March 23, 2009
  • What is a rule? 5 Monday, March 23, 2009
  • 6 Monday, March 23, 2009
  • An engine? 6 Monday, March 23, 2009
  • 7 Monday, March 23, 2009
  • A recipe? 7 Monday, March 23, 2009
  • 8 Monday, March 23, 2009
  • An editor? 8 Monday, March 23, 2009
  • 9 Monday, March 23, 2009
  • Defining the Damn Thing 9 Monday, March 23, 2009
  • Defining the Damn Thing 9 Monday, March 23, 2009
  • 10 Monday, March 23, 2009
  • What We Do 10 Monday, March 23, 2009
  • What We Do 10 Monday, March 23, 2009
  • 11 Monday, March 23, 2009
  • What I Do 11 Monday, March 23, 2009
  • What I Do 11 Monday, March 23, 2009
  • What I Do 11 Monday, March 23, 2009
  • What I Do 11 Monday, March 23, 2009
  • What I Do 11 Monday, March 23, 2009
  • What I Do more abstract 11 Monday, March 23, 2009
  • What I Do more abstract 11 Monday, March 23, 2009
  • 12 Monday, March 23, 2009
  • Content Rules 12 Monday, March 23, 2009
  • 13 Monday, March 23, 2009
  • cooksillustrated.com 13 Monday, March 23, 2009
  • cooksillustrated.com 13 Monday, March 23, 2009
  • 14 Monday, March 23, 2009
  • Navigation Rules 14 Monday, March 23, 2009
  • 15 Monday, March 23, 2009
  • cnet.com » mp3 players 15 Monday, March 23, 2009
  • cnet.com » mp3 players 15 Monday, March 23, 2009
  • 16 Monday, March 23, 2009
  • cnet.com » digital cameras 16 Monday, March 23, 2009
  • cnet.com » digital cameras 16 Monday, March 23, 2009
  • 17 Monday, March 23, 2009
  • “Business Rules” 17 Monday, March 23, 2009
  • 18 Monday, March 23, 2009
  • Ecommerce Product Page 18 Monday, March 23, 2009
  • Ecommerce Product Page 18 Monday, March 23, 2009
  • 19 Monday, March 23, 2009
  • Taxonomy Insuficient 19 Monday, March 23, 2009
  • Taxonomy Insuficient Criteria for selecting behaviors or responses within the context of a presentation 19 Monday, March 23, 2009
  • 20 Monday, March 23, 2009
  • Rules are not... 20 Monday, March 23, 2009
  • 21 Monday, March 23, 2009
  • Patterns 21 Monday, March 23, 2009
  • 22 Monday, March 23, 2009
  • Carousel Pattern Yahoo Pattern Library 22 Monday, March 23, 2009
  • 23 Monday, March 23, 2009
  • Components 23 Monday, March 23, 2009
  • 24 Monday, March 23, 2009
  • Accordion Component Sun WebDesign 24 Monday, March 23, 2009
  • 25 Monday, March 23, 2009
  • IA is a web site’s “language” 25 Monday, March 23, 2009
  • 26 Monday, March 23, 2009
  • Content Rules 26 Monday, March 23, 2009
  • 27 Monday, March 23, 2009
  • Content Rules » Action 27 Monday, March 23, 2009
  • 28 Monday, March 23, 2009
  • Content Rules » Scope 28 Monday, March 23, 2009
  • 29 Monday, March 23, 2009
  • Content Rules » Filter 29 Monday, March 23, 2009
  • 30 Monday, March 23, 2009
  • Content Rules » Quantity 30 Monday, March 23, 2009
  • 31 Monday, March 23, 2009
  • Content Rules » Format 31 Monday, March 23, 2009
  • 32 Monday, March 23, 2009
  • Content Rules » Default 32 Monday, March 23, 2009
  • 33 Monday, March 23, 2009
  • Navigation Rules 33 Monday, March 23, 2009
  • 34 Monday, March 23, 2009
  • Navigation Rules » Facets 34 Monday, March 23, 2009
  • 35 Monday, March 23, 2009
  • Navigation Rules » Options 35 Monday, March 23, 2009
  • 36 Monday, March 23, 2009
  • Navigation Rules » Range 36 Monday, March 23, 2009
  • 37 Monday, March 23, 2009
  • Navigation Rules » Eect 37 Monday, March 23, 2009
  • 38 Monday, March 23, 2009
  • Navigation Rules » See All 38 Monday, March 23, 2009
  • 39 Monday, March 23, 2009
  • Documenting Rules 39 Monday, March 23, 2009
  • 40 Monday, March 23, 2009
  • Wireframe Annotations 40 Monday, March 23, 2009
  • 41 Monday, March 23, 2009
  • Wireframe Annotations » Prose 41 Monday, March 23, 2009
  • Wireframe Annotations » Prose 41 Monday, March 23, 2009
  • Wireframe Annotations » Prose If the customerʼs state is nexus, show sales tax. 41 Monday, March 23, 2009
  • 42 Monday, March 23, 2009
  • Wireframe Annotations » Pseudo-code 42 Monday, March 23, 2009
  • Wireframe Annotations » Pseudo-code 42 Monday, March 23, 2009
  • Wireframe Annotations » Pseudo-code Display Conditions • IF state=nexus • THEN display tax 42 Monday, March 23, 2009
  • 43 Monday, March 23, 2009
  • Wireframe Annotations » Table 43 Monday, March 23, 2009
  • Wireframe Annotations » Table 43 Monday, March 23, 2009
  • Wireframe Annotations » Table Area Content Type Quantity Criteria 1 Article 3-5 Latest 2 Comments 3 Most Useful 43 Monday, March 23, 2009
  • 44 Monday, March 23, 2009
  • Wireframe Content 44 Monday, March 23, 2009
  • Wireframe Content 44 Monday, March 23, 2009
  • Wireframe Content Latest Articles • [Article Headline] • [Pub Date] [Summary (160 chars)] more... • [Article Headline] • [Pub Date] [Summary (160 chars)] more... • [Article Headline] • [Pub Date] [Summary (160 chars)] more... 44 Monday, March 23, 2009
  • M996S&!quot;###* M996S&!quot;###+ M996S&!quot;###, Z3*&!quot;#$%&BED&E..GD&=(&0*<*5EG Z3*&!quot;#$%&BED&E..GD&=(&(3* Z3*&!quot;#$%&BED&E..GD&=(&(3*&(5 E))5*00*0&Q1=?13&E&3*12?F(5?(()7 F-1G)132&E3)&EGG&=?*&-31=0&Q1=?137 B(5*&-31=0&Q1=?13&E&F-1G)1327 P?*&F-1G)132&Q(-G)&?E<*&1=0&(Q3 !quot;#$%&E0&Q*GG7 `&OGE2&=?5(Q3&Q?*3 A(B.E3D&3EB*&?E0&F**3 ! B(<*)&=(&E))5*00&G13*&E3) -./0123435quot;6578quot;97:quot;;<=quot;>7?@AB=Cquot;D3A:E03F -0*)&=(&BE,*&BE=A?7 _IEA= quot;O&=?*&E))5*00 .5(<1)*)&BE=A?*0 E=A? *IEA=GD8&=?*&0D0=*B Q1GG&5*=-53&5*0-G= ]X6^ A()*&X67 YD '(B.E3D '(B.E3D&KEB* E..G1*)&E0&O1G=*5&=( B-G=1.G*&BE=A?&G10=7 -G=1.G* quot;O&=?*&E))5*00&AE3 (3GD&.E5=1EGGD&BE=A?8 E=A? =?*&0D0=*B&Q1GG&O1G=*5 5*0-G=0&FE0*)&(3 ]MML%^ A(B.E3D&3EB*7 45 Monday, March 23, 2009
  • M996S&!quot;###* M996S&!quot;###+ Flows M996S&!quot;###, Z3*&!quot;#$%&BED&E..GD&=(&0*<*5EG Z3*&!quot;#$%&BED&E..GD&=(&(3* Z3*&!quot;#$%&BED&E..GD&=(&(3*&(5 E))5*00*0&Q1=?13&E&3*12?F(5?(()7 F-1G)132&E3)&EGG&=?*&-31=0&Q1=?137 B(5*&-31=0&Q1=?13&E&F-1G)1327 P?*&F-1G)132&Q(-G)&?E<*&1=0&(Q3 !quot;#$%&E0&Q*GG7 `&OGE2&=?5(Q3&Q?*3 A(B.E3D&3EB*&?E0&F**3 ! B(<*)&=(&E))5*00&G13*&E3) -./0123435quot;6578quot;97:quot;;<=quot;>7?@AB=Cquot;D3A:E03F -0*)&=(&BE,*&BE=A?7 _IEA= quot;O&=?*&E))5*00 .5(<1)*)&BE=A?*0 E=A? *IEA=GD8&=?*&0D0=*B Q1GG&5*=-53&5*0-G= ]X6^ A()*&X67 YD '(B.E3D '(B.E3D&KEB* E..G1*)&E0&O1G=*5&=( B-G=1.G*&BE=A?&G10=7 -G=1.G* quot;O&=?*&E))5*00&AE3 (3GD&.E5=1EGGD&BE=A?8 E=A? =?*&0D0=*B&Q1GG&O1G=*5 5*0-G=0&FE0*)&(3 ]MML%^ A(B.E3D&3EB*7 45 Monday, March 23, 2009
  • 46 Monday, March 23, 2009
  • What makes a good rule? 46 Monday, March 23, 2009
  • 47 Monday, March 23, 2009
  • Good Rules » User-Centered 47 Monday, March 23, 2009
  • 48 Monday, March 23, 2009
  • Good Rules » Unambiguous 48 Monday, March 23, 2009
  • 49 Monday, March 23, 2009
  • Good Rules » Feasible 49 Monday, March 23, 2009
  • 50 Monday, March 23, 2009
  • Good Rules » Specified Responsibility 50 Monday, March 23, 2009
  • 51 Monday, March 23, 2009
  • Good Rules » Comprehensive 51 Monday, March 23, 2009
  • 52 Monday, March 23, 2009
  • Good Rules » Gracefully Degradeable 52 Monday, March 23, 2009
  • 53 Monday, March 23, 2009
  • Do the right thing 53 Monday, March 23, 2009
  • Thanks! dan@eightshapes.com social networks: 54 Monday, March 23, 2009
  • Photo Credits 3 http://plainview.files.wordpress.com/2009/02/moses1.jpg 6 http://www.drivingenthusiast.net/SD-mazda/products/mazdaspeed3/engine/MAZDA3_engine_HR.jpg 7 http://lh4.ggpht.com/_o456qV7CNhQ/RhyHtSLCToI/AAAAAAAAAWw/__S_7cHPCmk/p0002180.jpg 8 http://www.hadesign.net/images/WTVI/WTVI%20QC%20room.jpg 19 http://www.checkout.org.cn/news/mmg/media/images/platypus3_h.jpg 21 http://farm4.static.flickr.com/3401/3267227227_660b6ab4f4_b.jpg 23 http://farm3.static.flickr.com/2210/2314610838_beecd46647_o.jpg 25 http://www.gutenberg.org/files/16352/16352-h/images/p1.jpg 28 http://www.flickr.com/photos/lencioni/2223801603/sizes/l/ 30 http://www.creativecookware.com/images/measuring%20cups%20spoons.JPG 32 http://www.flickr.com/photos/jamesjordan/2226419650/sizes/o/ 34 http://www.uncg.edu/rom/courses/dafein/civ/nude_no2.jpg 37 http://www.flickr.com/photos/mhartford/69673975/sizes/o/ 49 http://www.meridian.net.au/Art/Artists/MCEscher/Gallery/Images/escher-relativity-woodcut-medium.jpg 50 http://www.flickr.com/photos/dystopos/17007801/sizes/o/ 52 Canʼt find source. If this is your photo, please email me! 55 Monday, March 23, 2009