information architecture class12 04 03

DeliverablesSI 658 Information Architecture

Marti Gukeisen

4/3/2013

Deliverables

4/3/2013

SI658 Information Architecture2

the cake we bake IA in

Deliverables

Deliverables

4/2/2013


Deliverables

the good and the bad of the iceberg

4/2/2013


Deliverables

The Project Process

4/3/2013


Research

Strategy

Design

Implementation

Administration

You are

here

Deliverables

IA strategy aspects Determine Goals

Business objectives, user motivation, other stakeholder goals.

Understand the EnvironmentBrand context, competitive space, user expectations & habits.

Plan the InteractionWhat states & steps are needed?

Validate & AssessAsk, test, iterate.

Document the PlanFacilitates shared understanding for everyone involved.

4/2/2013


Deliverables

possible deliverables

Determine

Goals

Understand the

Environment

Plan the

Interaction

Validate /

Assess

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 CasesUser Testing Analysis

and ReportsContent Map

PersonasCross-channel

AnalysisFeature Set Interview Scripts

Functional Requirements

Search Term Analysis User Task Analysis Feature Cards Interview ReportsFunctional

Specifications

Identify User & Business Objectives

Ethnographic Research

Card Sorting Prototypes (static,paper, interactive)

CMS Content Model

4/2/2013


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


Deliverables

Blueprints / Diagrams / High-Level IA

4/3/2013


Deliverables

User Flow

4/3/2013


Deliverables 4/3/2013


Deliverables

fidelity of deliverables

4/3/2013


start endmiddle

project timeline

Deliverables

this is how we do it

[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.

4/3/2013


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


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

Functional Specifications Document – design, ENG

4/3/2013


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


Deliverables

Feature Set

4/3/2013


Deliverables

High Level IA

4/3/2013


Deliverables

Template ListComp

Set

Wireframe

GroupTemplate Description

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 DetailDetail 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 ArticleNews 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 LibraryIntegrated 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 Timeslanding 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 Usthis will be reskinned version of the existing Contact Us form (possibly with very

minor revisions).

6 8 T05 a, b – Item ListUsed for all list pages such as lists of classes, articles, patient stories, phone list,

etc.

4/3/2013


Deliverables

Wireframes

4/3/2013


mobile

desktop

Deliverables

Clickable Prototype

4/3/2013


Deliverables

Content Model

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


C04- News Article Content Type

Deliverables

MPII (master page instance inventory)

4/3/2013


Deliverables

Functional Specifications

4/3/2013


Project Timethe part where you collaborate and teach each other

4/3/2013


Deliverables

Get in your groups

4/3/2013


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


https://docs.google.com/a/umich.edu/presentation/d/1muAD2mxE0-WYb3LrHtPpuO7unJhfCNIN6Xrk518Cefw/edit?usp=sharing

Deliverables

group project breakdown

assignment 1 – 100 pts



assignment 4 – 100 pts you are here

presentation – 500 pts April 17th

participation – 100 pts you grading each other

4/3/2013


Presentation

Timethe part where you teach

4/3/2013

32 SI658 Information Architecture

Wrap UpMore stuff for you to do.

4/3/2013

33 SI658 Information Architecture

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

LatersQuestions?

4/3/2013


information architecture class12 04 03

Internet