A practical guide to information architecture pdf


    A Practical Guide to Information Architecture. A Practical Guide to Resources: Are there PDF or Word documents, images or other. • downloadable files. A Practical Guide to Information Architecture. Contents. About information architecture. What is information architecture? ia in a project. Who does ia? ia for non. A Practical Guide to Information Architecture | Five Simple Steps For digital products such as PDF and ePub price is subject to UK VAT if you.

    Language:English, Spanish, Portuguese
    Genre:Health & Fitness
    Published (Last):10.06.2016
    Distribution:Free* [*Sign up for free]
    Uploaded by: SHELA

    54097 downloads 160930 Views 14.73MB PDF Size Report

    A Practical Guide To Information Architecture Pdf

    Practical Information Architecture: How to organise and structure online Digital ebook: You'll get an immediate download in ePub, Mobi and PDF formats. A Practical Guide to Information Architecture book. Read 19 reviews from the world's largest community for readers. If you're a website designer, intrane. A Practical Guide to Information Architecture - Kindle edition by Donna Spencer. Download it once and read it on your Kindle device, PC, phones or tablets.

    Jun 04, Mikal rated it really liked it Recommends it for: design professionals; beginning IAs; web project managers While there are and will be IA experts who are available to tackle the really wicked challenges, this book is like putting Industrial Strength Information Architecture in the hands of everyday practitioners. While I feel this book is valuable for any business professional working on a redesign. I think individuals that are already familiar with user-centered design will find the most value. I rated this book four stars but five stars is unatainable for this subject area. Any further in scope or d While there are and will be IA experts who are available to tackle the really wicked challenges, this book is like putting Industrial Strength Information Architecture in the hands of everyday practitioners. Any further in scope or depth and this book would not have been accessible to newcomers to IA or it would have become a textbook vs. The author wisely ends the book without going into too much depth regarding the design. Ultimately the further intricacies of site design are better covered elsewhere. Donna structure's the book through the complete lifecycle of the IA process. I was in the middle of an IA project when I picked up this book. It was incredibly useful and a few of the myths this book dispelled myth: people either search or browse they don't do both in addition to its message that the best topic labels are those that are clear even if somewhat lengthy or boring ; came very much in handy. The short chapters are easy to peruse or keep you focused if you're reading linearly. I completed this book within a week during an IA project. And the clarity it provided me probably saved my working group two weeks of progress with a more satisfactory outcome.

    Nov 27, Jenifer rated it really liked it. This book was an excellent primer into developing an information architecture, though I wish it would have focused more on the actual creation of the IA, understanding categories and how to incorporate all the information you get from the design research. Dec 04, Ian Stewart rated it liked it.

    Unfortunately for me it covered a lot of concepts and strategies I was already familiar with. Jan 15, Talia Skinner rated it really liked it. A good basic introduction to organising information. Aug 26, Dave Emmett rated it really liked it Recommends it for: Junior Information architects. This was a great primer on the practice of information architecture.

    As a young IA, I found a lot of the information refreshed things I already knew, but there was also some new information as well. I think more experienced IAs would find this quite basic, so it might not be the best book for all you seasoned pros. Of the 'new' stuff that I learned from this book, probably the most helpful was the section on IA testing.

    Now, I've done usability testing, and card sorting before, but I hadn't yet r This was a great primer on the practice of information architecture. Now, I've done usability testing, and card sorting before, but I hadn't yet read a detailed methodology for testing a site architecture after it was reasonably established, but before any of the wireframing or design work had started skip to chapter 19 for this.

    I'm going to try to implement at least some level of this testing into my projects from now on. Also, this was the first book I read on the iPad, and I wrote up some thoughts on that experience on my blog.

    Apr 09, dgrebb rated it it was amazing. Another great book from Five Simple Steps. I'd never attempted to think or speak about IA in the scientific way that has become ubiquitous in the industry.

    Hm... Are You a Human?

    This book is a great dive into the theory and vernacular of IA, and has allowed me to more accurately communicate ideas that I've been thinking for over 10 years. Mar 29, Ryan Kennedy rated it it was amazing. If you are involved with building IAs at all, read it. Jan 12, Laura rated it really liked it.

    Interesting read with lots of helpful suggestions and tips for anyone in IA or even UX. Covers everything from the initial user research right through to usability testing of the 'final' product. I would have really appreciated reading this a couple of years ago. A good overview with some pointers for further reading. Dec 20, Sean rated it liked it.

    An ok introduction to IA. A good book to get the lay of the land in practical terms.

    Other books: BARCELONA GUIDE PDF

    A bit repetitive in concepts and to be honest I rushed to finish it out of shear boredom. Feb 09, Ana rated it really liked it Shelves: Good introduction. Dec 10, Anthony is currently reading it. Packed with great detail on the broad subject of Information Architecture. Jul 12, Dana rated it liked it. Jul 13, Carrie rated it really liked it Shelves: This book was a fast read, but I found a lot of helpful advice for designing an IA, including considerations for designing the navigation.

    Miguel rated it it was ok Jun 09, Emma Boulton rated it really liked it Mar 21, Even a small difference in defining something like a geographical boundary makes it hard to compare and combine data.

    Insurance forms are full of classifications, and your answers affect how much you pay. A lot of mobile apps work as a hierarchy, with menus providing access to different parts of the application.

    This IA is just the same as it is for everything else.

    Practical Guide to Enterprise Architecture, A - PDF Free Download

    Everything in this book except navigation design is just as relevant for these examples as it is for websites and intranets. Figure 4 — 6. Stanza allows access to books by authors and groups Figure 4 — 7. However, it can be much harder to get them to articulate what the end result should be. Naturally, the conference has an associated website that has information about the upcoming conference including the program , resources from the previous conference, and online registration.

    Project goals help define what you are doing. A good set of project goals describe what the project is all about, why it is being done and what the end result will be.

    Is one approach better than another? They will also directly affect the IA. This can be tricky sometimes, especially when the business wants to achieve one thing sell more music and the people want to achieve something else download music for free. When you can show how it will achieve the goals of the business, stakeholders will accept it more easily.

    They may have had to figure out what they wanted from the project to get the funding, or they may just be very organised and disciplined. What is the overall goal of this project? This is the key question, and can be one of the hardest to articulate.

    Sometimes the answers are fairly obvious. But it is still worthwhile to check that everyone is on the same page and wants to achieve the same thing. Goals usually fall into three different types — making more money, reducing costs or helping people make better decisions.

    How will we measure the impact of any changes? At the end of a project you may need to show that the site has actually improved particularly for redesigns. This may help you decide whether you are ready to launch, but more often it will be to show that the money spent on a project was worthwhile. I know of lots of projects that spent a lot of money and could show no outcome.

    Figure 5 — 1. Yoink yoink. Ways to collect goals The way you create project goals will depend on your project and your role in it. If your project is part of a larger corporate initiative, start by finding out what the goals of that project may be. Also review any business strategies to see where the project fits in terms of achieving broader organisational goals.

    For some projects, you may be able to get a set of goals from a brief conversation with your client or a senior manager. For something bigger you may need to run a workshop with a range of stakeholders. How you do this will depend on the organisation. Here are three methods I find useful for working out goals. Scenario planning Scenario planning takes a story-telling approach to identify goals.

    By telling stories, people can better visualise and describe an outcome, and you get great information on what the goals really mean.

    Although the stories may initially sound just like tasks, by paying attention and asking questions, you can tease out goals. You can also do scenario planning in reverse — ask stakeholders to describe what a failure looks like again, in story form. Use this as a starting point to figure out how to address the likely points of failure.

    About Information Architecture.pdf - 1 A Practical Guide to...

    With the right organisation this can be very fun and much more productive than tackling the goals head on. Pain points One place to start is to identify current points of pain. Find out what is going wrong, and see if you can get to the bottom of why it is happening. Pain points are a good starting point for a discussion, as they give everyone something concrete to discuss.

    The hardest thing about setting goals is thinking abstractly about the future, so anything concrete is good. As you discuss the pain points, you can start to identify consistent patterns, discuss the underlying issue and turn it into a goal.

    Your goal may not be to reduce phone sales which you could do by making the phone number harder to find as one client of mine did , but to remove the barriers that customers are facing when downloading online and gradually convert phone sales to online sales. Backcasting Backcasting1 is like forecasting in reverse. You start with an end and work backwards to identify what you need to do to get there.

    The end positions are described in scenario form, and may describe a few different outcomes you are trying to reach. I usually create a scenario for an ideal future, an acceptable outcome and something in between. By looking at what would be needed to reach each end point, you can tease out a lot of issues. You can also identify intermediate goals that are more achievable than one big end-goal. Some are easy to customise to do what you want, and some can be harder or more expensive.

    Ask them to explain the basics of how the system stores the content and how pieces of content are displayed on a page. But when you know the basics, keep checking whether the ideas you have for the information architecture can work within the system you are using.

    And if you have no technology constraints to work with, congratulations! Figure 5 — 2. Organisational culture is all about the way an organisation works. The main thing a culture affects is how communications are conducted.

    Will you be able to talk to whoever you want whenever you want, or will all meetings have carefully constructed invitation lists and be scheduled well in advance? Will you be able to present a rough draft of an idea for feedback, or only present detailed final deliverables? Stakeholders When planning a project, consider who is and who should be involved.

    Understand their role in the organisation and where their influence lies. On many projects I discover people being excluded who really should have something to contribute. One of your roles in a project may be to introduce stakeholders to fundamental ideas behind what you are working on. But you need to know and work within them.

    These may already be defined, or you may need to help figure them out. In a five seconds viewing what do you first see and can you work out what the company does? From this research the objectives were defined and documented in the Website Re-creation Brief. This document was used to brief the designer and scope the required project work. With the objectives clearly defined, it was easy to allocate the project work into phases so we could quickly go live with the new website.

    Using the Website Re-creation Brief it was clear what was in and out of scope, which kept our project on track. You start looking up the aisles. No, this aisle is all canned food You decide to give this one a go. And they put those groups into bigger groups, and those groups into even bigger groups. So they put all the chocolate — dark, light, white, bars and pieces — together. Then they put it near other sweet things, which are also arranged into groups of similar items.

    TOP Related

    Copyright © 2019 deilasilimo.cf.