This document discusses information architecture deliverables for an information architecture project. It provides examples of typical deliverables like interactive objectives, a feature list, high-level IA diagrams, wireframes, clickable prototypes, content models, and more. It also discusses who would be interested in each deliverable and how deliverables are presented and approved throughout the project process.

1. 4/3/2013
Deliverables
SI 658
Information Architecture
Marti Gukeisen

2. Deliverables
4/3/2013
the cake we bake IA in
2 SI658 Information Architecture

3. Deliverables
Deliverables
4/2/2013
3 SI658 Information Architecture

4. Deliverables
the good and the bad of the iceberg
4/2/2013
4 SI658 Information Architecture

5. Deliverables
The Project Process
4/3/2013
Research
Strategy
Design
You are
here
Implementation
Administration
5 SI658 Information Architecture

6. Deliverables
IA strategy aspects
 Determine Goals
Business objectives, user motivation, other stakeholder goals.
 Understand the Environment
Brand context, competitive space, user expectations & habits.
 Plan the Interaction
What states & steps are needed?
 Validate & Assess
Ask, test, iterate.
 Document the Plan
Facilitates shared understanding for everyone involved.
4/2/2013
6 SI658 Information Architecture

7. Deliverables
possible deliverables
Determine
Goals
Understand the
Environment
Plan the
Interaction
Validate /
Assess
4/2/2013
Document the
Plan
Identify Stakeholders Content Inventory Scenarios Heuristic Evaluation Site Diagram
User Segmentation Competitive Review User Flows Online Surveys Wireframes
Needs Analysis Analytics Assessment Task Diagrams User Testing Scripts Story Boards
Consumer Trends Review Research Use Cases
User Testing Analysis
and Reports
Content Map
Personas
Cross-channel
Analysis
Feature Set Interview Scripts
Functional
Requirements
Search Term Analysis User Task Analysis Feature Cards Interview Reports
Functional
Specifications
Identify User &
Business Objectives
Ethnographic
Research
Card Sorting
Prototypes (static,
paper, interactive)
CMS Content Model
7 SI658 Information Architecture

8. Deliverables
some advice
 present deliverables in person (or via video conference)
 practice what you preach: your deliverables should be
clear, concise, un-muddied
 less is more
 establish conventions and stick to them
4/3/2013
8 SI658 Information Architecture

9. Deliverables
Blueprints / Diagrams / High-Level IA
4/3/2013
9 SI658 Information Architecture

10. Deliverables
User Flow
4/3/2013
10 SI658 Information Architecture

11. Deliverables
User Flow
4/3/2013
11 SI658 Information Architecture

12. Deliverables 4/3/2013
12 SI658 Information Architecture

13. Deliverables
fidelity of deliverables
4/3/2013
start middle end
project timeline
13 SI658 Information Architecture

14. Deliverables
this is how we do it
4/3/2013
 [information has been gathered, discussed]
 I make a deliverable to convey a plan
(high level structure | user flow | page layout)
 we meet INTERNALLY (creative director, project
manager, engineer, designer, info architect)
 I present the plan. Explain it.
 Team discusses, suggests revisions. I iterate.
 We present plan to the CLIENT.
 Client discusses, suggests revisions. I iterate.
 Client approves. We move on to the NEXT part.
process repeats.
14 SI658 Information Architecture

15. Deliverables
Typical IA Design Deliverables
 Interactive Objectives
 Feature List
 High Level IA (blueprint)
 Template List
 Wireframes
 Clickable Prototype
 Content Model
 MPII (master page instance inventory)
 Functional Specifications Document
4/3/2013
15 SI658 Information Architecture

16. Deliverables
Who cares?
 Interactive Objectives – IA, strategy, client
 Feature List – IA, ENG, client
 High Level IA (blueprint) – IA, client
 Template List – IA, ENG, PM, design
 Wireframes – IA, client, design, ENG
 Clickable Prototype – IA, design, client, ENG
 Content Model – authors, loaders
 MPII (master page instance inventory) - loaders
4/3/2013
 Functional Specifications Document – design, ENG
16 SI658 Information Architecture

17. Deliverables
Interactive Objectives
 Differentiate – and communicate – the brand advantage
 Help patients, caregivers, and their support teams navigate
the extended care ecosystem.
 Attract prospective patients to our services
 Support key services online successfully (e.g. bill pay, way
finding, locate a physician, class or promotion registration)
 Engage, inform, and support the extended community
 Drive better decision making and improved operations
throughout the organization
4/3/2013
17 SI658 Information Architecture

18. Deliverables
Feature Set
4/3/2013
18 SI658 Information Architecture

19. Deliverables
High Level IA
4/3/2013
19 SI658 Information Architecture

20. Deliverables
High Level IA
4/3/2013
20 SI658 Information Architecture

21. Deliverables
Template List
Comp
Set
Wireframe
Group
Template Description
4/3/2013
0 1 T01 – SVH Home homepage for the system site
1 1 T02 – Location Home homepage template for hospital sites, to accommodate all hospital locations
1 1 Find a Physician (T12-T14)
Any necessary revisions to these previously delivered wireframes: Find a Physician
Search (T12), Results (T13), and Physician Detail (T14) pages
2 2 T03 a, b – Channel Landing used for all channel landing pages unless otherwise specified.
2 or 3 3 T17 – Location Map & Directions this is used to show a map and directions to a location
3 4 T07a,b – Service Detail
Detail page for the top level intro to a service area. (Deeper pages will be presented
using the T04 content template)
5 5 T06 a, b – News Article
News article. SVH would like the ability to designate which locations a news article
applies to, and business rules (defaults) around how long news articles should stay
active. sVH wants this to be one of the structured templates.
5 5 T08a,b – Staywell Health Library
Integrated Staywell content into the SVH site. No changes to content presentation.
SVH-created mapping to services will be maintained.
4 6 T11 – SVH ER Wait Times
landing page with all ERs and a map; widget with wait time data for location will also
appear on Locations Landing page
4 7 T21 – Prepare for Your Visit this will be a reskinned template for the existing prepare a procedure content
6 7 T18 a, b– Contact Us
this will be reskinned version of the existing Contact Us form (possibly with very
minor revisions).
6 8 T05 a, b – Item List
Used for all list pages such as lists of classes, articles, patient stories, phone list,
etc.
21 SI658 Information Architecture

22. Deliverables
Wireframes
4/3/2013
mobile
desktop
22 SI658 Information Architecture

23. Deliverables
Clickable Prototype
4/3/2013
23 SI658 Information Architecture

24. Deliverables
Clickable Prototype
4/3/2013
24 SI658 Information Architecture

25. Deliverables
Content Model
C04- News Article Content Type
Content Type T14 – News Article Content Type
Related Page Type T14 News Article Page
Component
Objective
Presents a persistently displayed component on
homepage which highlights a key feature or product.
CMSTitle Unique title for content instance in the CMS (not
displayed on site).
Date (34) Primary heading for the promo.
Title (140) Appears below the heading on the theater panel.
Related Fund Dropdown list (All, Real Estate Income Trust, Inland
Diversified, Inland American, Private Placements,
Institutional Investments)
Body Area Descriptive copy and images
Button Text (20) Label for the call to action button.
Destination URL Dynamic link to the related page in the CMS.
4/3/2013
25 SI658 Information Architecture

26. Deliverables
4/3/2013
MPII (master page instance inventory)
26 SI658 Information Architecture

27. Deliverables
Functional Specifications
4/3/2013
27 SI658 Information Architecture

28. 4/3/2013
Project Time
the part where you collaborate and teach each other
28 SI658 Information Architecture

29. Deliverables
Get in your groups
4/3/2013
29 SI658 Information Architecture

30. Deliverables
group assignment
 last one (it’s a doosey): what you make of it
 revised high level IA
 revised homepage & (3) interior page wires
 cross-channel assessment & recommendations
 brief in ctools
 due April 10 (next week!)
4/3/2013
30 SI658 Information Architecture

31. Deliverables
group project breakdown
 assignment 1 – 100 pts
 assignment 2 – 100 pts
 assignment 3 – 100 pts
 assignment 4 – 100 pts  you are here
 presentation – 500 pts  April 17th
4/3/2013
 participation – 100 pts  you grading each other
31 SI658 Information Architecture

32. Presentation
Time
the part where you teach
4/3/2013
32 SI658 Information Architecture

33. Wrap Up
More stuff for you to do.
4/3/2013
33 SI658 Information Architecture

34. Deliverables
next reading
Due TUES Apr 9nd at 11 pm.
50-300 words responding to
the following:
4/3/2013
Pervasive IA
Ch 9 Designing Cross-channel User Experiences
34 SI658 Information Architecture

35. 4/3/2013
Laters
Questions?
35 SI658 Information Architecture