91 Presentation Desc

Slide1: 

Slide2: 

Slide3: 

Slide4: 

Slide5: 

Slide6: 

Slide7: 

Slide8: 

Slide9: 

Slide10: 

Slide11: 

Adam Polansky Lead Information Architect Travelocity.com A PROCESS BY ANY OTHER NAME… Applying Information Architecture With Bridges, Cooking andamp; Hardware

Slide12: 

Maybe because it's entirely an artist's eye, patience and skill that makes an image and not his tools. Ken Rockwell, Your Camera Does Not Matter, 2005

Slide13: 

So there’s this guy….

Slide14: 

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!

Slide15: 

Shhhhhh! Matters not…. the process does

Slide16: 

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

Slide17: 

Origin Info Vehicle Destination Disposition INFORMATION TRANSFER Look at these elements. Characterize the forces that act upon them. Decide what you can do to bridge the communication gaps.

Slide18: 

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 Need For Archived Documents Need For Research

Slide19: 

Annotated Wireframe Annotated Mock-ups Narrative Document Interaction-Level Spec FACTORING FORCES IN

Slide20: 

Idea Plan IF: The team is small They’ve all worked together on the product before They’re all located in the same room Time is short (but reasonable) The features exist elsewhere in the site Documentation exists from previous projects THEN: White-board session to see where high level changes occur Tactical Wireframes to model the functionality Annotated Screen shots from existing product to show where changes occur Build FACTORING FORCES IN Developing a Web Site

Slide21: 

BUT… IF: The team is small Some of them worked together on the product before Some of them are located in Bangalore and they are new to the team Time is short (but reasonable) The features are new to the site No documentation exists from previous projects THEN: Process Flows to see where high level changes occur Tactical Wireframes to model the functionality Detailed functional spec to include screen shots and interaction details Idea Plan Build FACTORING FORCES IN Developing a Web Site

Slide22: 

Slide23: 

Slide24: 

Slide25: 

Slide26: 

Slide27: 

Slide28: 

Slide29: 

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

Slide30: 

Slide31: 

Special Thanks To… Travelocity IA Team –Leah Cave, Candy Bernhardt, Jay Fichialos, Jo Anne Wright, Vinu Singh, Jason Chloupek, Miriam Cabral-Ynocencio, Sonya Smith-Wong, Valerie Milner, Val Jolls Ryan Kowalczyk – Compiling and releasing the Wireframe stencil Michelle Peluso, Jeff Glueck, Troy Whitsett, Dana Thomas andamp; Noel Holmes – The chance to prove this stuff Marc Rettig – External Validation Travelocity Customer Experience Team – General Support All the contributing photographers at Morguefile.com