Adam Polansky Lead Information Architect Travelocity.com A PROCESS BY ANY OTHER NAME… Applying Information Architecture  W...
Some bridges occur naturally
Some bridges occur intuitively
Some bridges extend from their environments
Some bridges augment their environments
Some bridges are purely functional
Some bridges are aesthetic
Some bridges are used for people
Some bridges are not
Some bridges take on purposes for which they weren’t intended
Worse Thing:  Push-back because time needed for artifacts seen as bottle-neck Bad Thing:  Misguided demand for a process b...
Shhhhhh! Matters not…. the process does
Every development process includes three basic areas of activity. The job of the IA is to find ways to close the gaps betw...
So there’s this guy….
Origin Info Vehicle Destination Disposition INFORMATION TRANSFER <ul><li>Look at these elements. </li></ul><ul><li>Charact...
Domain Expertise Institutional Knowledge System Constraints Location of Resources New Development New Technology Mature or...
<ul><li>Annotated Wireframe </li></ul><ul><li>Annotated Mock-ups </li></ul><ul><li>Narrative Document </li></ul><ul><li>In...
<ul><li>IF:  </li></ul><ul><li>The team is small </li></ul><ul><li>They’ve all worked together on the product before </li>...
<ul><li>BUT…  IF:  </li></ul><ul><li>The team is small </li></ul><ul><li>Some of them  worked together on the product befo...
 
 
 
 
 
 
 
It’s not the process. It’s not the tools.  It’s the practitioner. Choose artifacts based upon your understanding of the fo...
 
Upcoming SlideShare
Loading in...5
×

A Process By Any Other Name...: Applying Information Architecture with bridges, cooking & hardware

1,429

Published on

This is my presentation from the 2006 IA Summit in Vancouver, BC. The summary is that the practice of IA is not about artifacts but the thinking that goes into them and the way you assess which artifacts to use.

Published in: Business, Technology
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,429
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
48
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide
  • A Process By Any Other Name...: Applying Information Architecture with bridges, cooking & hardware

    1. 1. Adam Polansky Lead Information Architect Travelocity.com A PROCESS BY ANY OTHER NAME… Applying Information Architecture With Bridges, Cooking & Hardware
    2. 2. Some bridges occur naturally
    3. 3. Some bridges occur intuitively
    4. 4. Some bridges extend from their environments
    5. 5. Some bridges augment their environments
    6. 6. Some bridges are purely functional
    7. 7. Some bridges are aesthetic
    8. 8. Some bridges are used for people
    9. 9. Some bridges are not
    10. 10. Some bridges take on purposes for which they weren’t intended
    11. 11. Worse Thing: Push-back because time needed for artifacts seen as bottle-neck Bad Thing: Misguided demand for a process based on artifacts. Good Thing: IA is becoming recognized in more firms. THERE AIN’T NO RECIPE!
    12. 12. Shhhhhh! Matters not…. the process does
    13. 13. Every development process includes three basic areas of activity. The job of the IA is to find ways to close the gaps between them COMMON FOR ALL PROCESSES Idea Plan Build IA IA
    14. 14. So there’s this guy….
    15. 15. Origin Info Vehicle Destination Disposition INFORMATION TRANSFER <ul><li>Look at these elements. </li></ul><ul><li>Characterize the forces that act </li></ul><ul><li>upon them. </li></ul><ul><li>Decide what you can do to bridge </li></ul><ul><li>the communication gaps. </li></ul>
    16. 16. Domain Expertise Institutional Knowledge System Constraints Location of Resources New Development New Technology Mature or Existing Product Skill Sets Time Cost Quality CHARACTERIZATION FORCES Size of Team
    17. 17. <ul><li>Annotated Wireframe </li></ul><ul><li>Annotated Mock-ups </li></ul><ul><li>Narrative Document </li></ul><ul><li>Interaction-Level Spec </li></ul>FACTORING FORCES IN Idea Plan Build IA IA <ul><li>Conversation </li></ul><ul><li>White board </li></ul><ul><li>Thumbnail Sketch </li></ul><ul><li>Process Flow </li></ul><ul><li>Site Map </li></ul><ul><li>Lo-Fi Wireframe </li></ul><ul><li>Hi-Fi Wireframe </li></ul><ul><li>Interactive Wireframe </li></ul>FORCES? FORCES?
    18. 18. <ul><li>IF: </li></ul><ul><li>The team is small </li></ul><ul><li>They’ve all worked together on the product before </li></ul><ul><li>They’re all located in the same room </li></ul><ul><li>Time is short (but reasonable) </li></ul><ul><li>The features exist elsewhere in same site </li></ul><ul><li>Documentation exists from previous projects </li></ul><ul><li>THEN: </li></ul><ul><li>White-board session to see where high level changes occur </li></ul><ul><li>Tactical Wireframes to model the functionality </li></ul><ul><li>Annotated Screen shots from existing product to show where changes occur </li></ul>FACTORING FORCES IN Idea Plan Build
    19. 19. <ul><li>BUT… IF: </li></ul><ul><li>The team is small </li></ul><ul><li>Some of them worked together on the product before </li></ul><ul><li>Some of them are located in Bangalor and they are new to the team </li></ul><ul><li>Time is short (but reasonable) </li></ul><ul><li>The features are new to the site </li></ul><ul><li>No documentation exists from previous projects </li></ul><ul><li>THEN: </li></ul><ul><li>Process Flows to see where high level changes occur </li></ul><ul><li>Tactical Wireframes to model the functionality </li></ul><ul><li>Detailed functional spec to include screen shots and interaction details </li></ul>FACTORING FORCES IN Idea Plan Build
    20. 27. It’s not the process. It’s not the tools. It’s the practitioner. Choose artifacts based upon your understanding of the forces that will affect communication
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×