Your SlideShare is downloading. ×
0
evolution of the sitemapimprove the usabilityof your deliverablesChris Pierson & Jacco NieuwlandEuroIA - September 25th, 2...
introductions
Chris PiersonUX consultant10 years UX experience2.5 years at User Intelligence
Jacco NieuwlandUX consultant8 years UX experience4 years at User Intelligence
User IntelligenceIt’s our goal to design interactive products thatprovide great User Experiences, based onknowledge of bot...
what is asitemap
a sitemap is a diagram in which the various pagesor page types throughout the site and the userpaths to and from them are ...
our definitiona design deliverable that seeks tocommunicate the overall structure andnavigation of [a website] –possibly i...
why talk aboutsitemaps?
why talk about sitemaps?
why talk about sitemaps?
why (talk about) sitemaps?• So many of us still do this – and need to do this• Nature of websites and applications is chan...
where have we come from?
Where have we come from?web 1.0 hierarchical top-down static HTML
where are we now?
Where are we now?web 2.0 linked & shared content focused on user & communities XML, RSS
sitemap
primary action map
sitemap + navigation scheme
Alternative visualisations
concept map
user flows
UIAML scheme
screenflow plus scenario
storyboard for interactive movie
interaction matrix / interesting moments grid
wireflow
Where are we going?
Where are we going?web 3.0 the semantic web the machine web linked data clouds
even though the way data is handled willchange, in many cases the design of thewebsites that display that data will not ch...
recap
sitemaps are still used to communicatestructure, navigation and concepts
it takes a lot of these diagrams to createsomething simple
different audiences can have differentinformation needs – documentation needs toaccount for this
so, is there a way to incorporate all theseneeds into one deliverable?
interactive documentation
interactive documentation allows for differentlayers of information and different views ofthe same design
there are existing tools that do this(Axure, Balsamiq, swipr, etc)                       - but none provide thecomplete se...
why not apply our user experience designexperience to our documentation?
requirements for documentation: • easy to create • easy to maintain • creative control (open) • easy to share/publish• con...
sketches /ideas
past experience shows enthusiasm with theaudiences and improved understanding ofthe design
2005 – UK government – communicate thedesign of a complicated web applicationintegratingscreenflows, wireframes, mockups, ...
wrap-up
a sitemap is more than just a hierarchicalcollection of pagesmapping & visualising structure andbehaviour is still importa...
interactive documentation  helps to cater for these audiences in one  deliverable  is an opportunity to apply our UX Desig...
what next?
thank you!                                 user intelligence                                 Amsterdam office             ...
Interested? Want to see more?     Follow our activities     on twitter or subscribe to our newsletter     Visit our websit...
Evolution Of The Sitemap
Evolution Of The Sitemap
Evolution Of The Sitemap
Evolution Of The Sitemap
Evolution Of The Sitemap
Evolution Of The Sitemap
Evolution Of The Sitemap
Evolution Of The Sitemap
Evolution Of The Sitemap
Evolution Of The Sitemap
Evolution Of The Sitemap
Evolution Of The Sitemap
Evolution Of The Sitemap
Evolution Of The Sitemap
Evolution Of The Sitemap
Evolution Of The Sitemap
Evolution Of The Sitemap
Evolution Of The Sitemap
Upcoming SlideShare
Loading in...5
×

Evolution Of The Sitemap

8,734

Published on

This presentation was given during the EuroIA 2009, by Chris Pierson and Jacco Nieuwland. The slides are exactly the same, but the large images of most title slides have been removed to make sure no copyrights are being violated. We want to thank everybody for contributing their materials as examples in this presentation.

Published in: Design, Technology
5 Comments
91 Likes
Statistics
Notes
  • Really Great Information :-) Thanks For Sharing....
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Hello! I´m Brazilian!
    I did like so much that I saw.
    This methodology was used in my pos-graduation, inspired at data visualizations.
    One think like this is the Caos Theory, fractais organizations.

    Tks for sharing!
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • So that makes sense then :-)

    Curious to see the next installment ...
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Hi Antje,

    Thanks for sharing your comments! One of the main ideas is that this would NOT become a tool to create your deliverables with. It would rather be some sort of 'combine-all-your-deliverables-in-an-easy-way-and-share' kind of a tool. And as such, should be extensible to include the related design deliverables you mentioned.

    Follow us, we hope to share more thoughts and ideas in the future...
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Hi guys,

    thanks for sharing! Interesting thoughts. Shame I had to miss the actual presentation.

    Not sure if I personally would be using a single tool (as these things always seem to be too restrictive), but might be a good framework for sharing it with the team. (Of course then you'd also want some version control, support for comments & alternatives etc.)

    Within e.g. the user flow, it'd be handy to then also link to the artifacts of e.g. user research stage (persona's, concepts, scenarios etc).

    Great work! - Will be interesting to follow discussions & how it evolves!!
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
8,734
On Slideshare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
461
Comments
5
Likes
91
Embeds 0
No embeds

No notes for slide
  • Subtitle – need to determine!
  • LOOK AT PRESO MARTIJN & ADAM – GET INLINE
  • Founded in 2002, recently opened an office in Finland. 16 people.
  • Let’s first set the scene – what are we talking about?http://www.flickr.com/photos/silvaazniv/1595052750/
  • http://www.flickr.com/photos/tonywuhl/3039851375/
  • And why are we talking about sitemaps – they’ve been discussed to death, almost literally. This year’s IA Summit in Memphis had a panel discussion called ‘Evolve or Die’
  • In this panel, deliverables were mentioned a couple of times. (ChristinaWodtke, Joshua Porter, Gene Smith & Russ Unger) It was suggested that we do not need to make these anymore (‘Who does that, anyway?’), and that people that ‘fetishise’ over their deliverables are ‘stuck in the IA box’. We disagree with this statement. We all need to evolve. But evolution means that you gradually adapt to new circumstances, and not throw away everything you’ve done before
  • In this panel, deliverables were mentioned a couple of times. (ChristinaWodtke, Joshua Porter, Gene Smith & Russ Unger) It was suggested that we do not need to make these anymore (‘Who does that, anyway?’), and that people that ‘fetishise’ over their deliverables are ‘stuck in the IA box’. We disagree with this statement. We all need to evolve. But evolution means that you gradually adapt to new circumstances, and not throw away everything you’ve done beforehttp://www.flickr.com/photos/crfarnum/3391221532/
  • In this panel, deliverables were mentioned a couple of times. (ChristinaWodtke, Joshua Porter, Gene Smith & Russ Unger) It was suggested that we do not need to make these anymore (‘Who does that, anyway?’), and that people that ‘fetishise’ over their deliverables are ‘stuck in the IA box’. We disagree with this statement. We all need to evolve. But evolution means that you gradually adapt to new circumstances, and not throw away everything you’ve done beforehttp://www.flickr.com/photos/rustysheriff/3557071616/
  • CHANGE ANIMATION!
  • And why are we talking about sitemaps – they’ve been discussed to death, almost literally. This year’s IA Summit in Memphis had a panel discussion called ‘Evolve or Die’http://www.flickr.com/photos/khalidibn/3636363737/sizes/l/
  • This is where we both started – our first stemaps looked just like this. This will probably be true for many of you.
  • http://www.aufdemmarkt.de/2007/10/22/tomtom-go-720t-navigation-per-sprache/
  • web 3 Open Data Movement - data definitions and linkshttp://en.wikipedia.org/wiki/File:Lod-datasets_2009-07-14_colored.png
  • web 3 Open Data Movement - data definitions and linkshttp://en.wikipedia.org/wiki/File:Lod-datasets_2009-07-14_colored.png
  • Within the real estate available for display
  • Within the real estate available for display
  • Should we change design to ‘experience’?
  • Should we change design to ‘experience’?
  • Should we change design to ‘experience’?
  • Should we change design to ‘experience’?
  • Should we change design to ‘experience’?
  • Transcript of "Evolution Of The Sitemap"

    1. 1. evolution of the sitemapimprove the usabilityof your deliverablesChris Pierson & Jacco NieuwlandEuroIA - September 25th, 2009
    2. 2. introductions
    3. 3. Chris PiersonUX consultant10 years UX experience2.5 years at User Intelligence
    4. 4. Jacco NieuwlandUX consultant8 years UX experience4 years at User Intelligence
    5. 5. User IntelligenceIt’s our goal to design interactive products thatprovide great User Experiences, based onknowledge of boththe users and the business.Services we offer:• Research• Design• Optimizewww.userintelligence.com
    6. 6. what is asitemap
    7. 7. a sitemap is a diagram in which the various pagesor page types throughout the site and the userpaths to and from them are documented. A sitemap is an overview of the pages within a website.A site map is a diagrammaticalrepresentation of the logical structure of aset of webpages the sitemap is an IA relic from the web 1.0 era
    8. 8. our definitiona design deliverable that seeks tocommunicate the overall structure andnavigation of [a website] –possibly including screens, pages,objects, states and flows
    9. 9. why talk aboutsitemaps?
    10. 10. why talk about sitemaps?
    11. 11. why talk about sitemaps?
    12. 12. why (talk about) sitemaps?• So many of us still do this – and need to do this• Nature of websites and applications is changing• Structure needs to be mapped & communicatedSo sitemaps need to evolve to be able toeffectively communicate structure andconcepts
    13. 13. where have we come from?
    14. 14. Where have we come from?web 1.0 hierarchical top-down static HTML
    15. 15. where are we now?
    16. 16. Where are we now?web 2.0 linked & shared content focused on user & communities XML, RSS
    17. 17. sitemap
    18. 18. primary action map
    19. 19. sitemap + navigation scheme
    20. 20. Alternative visualisations
    21. 21. concept map
    22. 22. user flows
    23. 23. UIAML scheme
    24. 24. screenflow plus scenario
    25. 25. storyboard for interactive movie
    26. 26. interaction matrix / interesting moments grid
    27. 27. wireflow
    28. 28. Where are we going?
    29. 29. Where are we going?web 3.0 the semantic web the machine web linked data clouds
    30. 30. even though the way data is handled willchange, in many cases the design of thewebsites that display that data will not changedrastically
    31. 31. recap
    32. 32. sitemaps are still used to communicatestructure, navigation and concepts
    33. 33. it takes a lot of these diagrams to createsomething simple
    34. 34. different audiences can have differentinformation needs – documentation needs toaccount for this
    35. 35. so, is there a way to incorporate all theseneeds into one deliverable?
    36. 36. interactive documentation
    37. 37. interactive documentation allows for differentlayers of information and different views ofthe same design
    38. 38. there are existing tools that do this(Axure, Balsamiq, swipr, etc) - but none provide thecomplete set of features we’re looking for
    39. 39. why not apply our user experience designexperience to our documentation?
    40. 40. requirements for documentation: • easy to create • easy to maintain • creative control (open) • easy to share/publish• contextual communication• easy to navigate / intuitive
    41. 41. sketches /ideas
    42. 42. past experience shows enthusiasm with theaudiences and improved understanding ofthe design
    43. 43. 2005 – UK government – communicate thedesign of a complicated web applicationintegratingscreenflows, wireframes, mockups, validation rules/business rules
    44. 44. wrap-up
    45. 45. a sitemap is more than just a hierarchicalcollection of pagesmapping & visualising structure andbehaviour is still importantvisualisations are naturally evolving withevolving technologydifferent audiences have different needs
    46. 46. interactive documentation helps to cater for these audiences in one deliverable is an opportunity to apply our UX Design experience to our deliverables allows us to present these different layers of information in context
    47. 47. what next?
    48. 48. thank you! user intelligence Amsterdam office www.userintelligence.comChris Piersonpierson@userintelligence.comJacco Nieuwlandnieuwland@userintelligence.com
    49. 49. Interested? Want to see more? Follow our activities on twitter or subscribe to our newsletter Visit our website Blog posts, articles, cases and much more See more of our presentations slideshare.net/UserIntelligence
    1. A particular slide catching your eye?

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

    ×