FINALIZE HI-FIDELITY

DESIGNS & PROTOTYPES

 

FINALIZE YOUR
CASE STUDY

ADD YOUR WOW IMAGE

IN THE BEGINNING & END

OF YOUR CASE STUDY

DO ANY BRAND WORK

IF NEEDED & WANT TO

FEEL FREE TO ADD
THE DESIGN SYSTEMS
INTO THE CASE STUDY

 

( EXTRA CREDIT }

CREATE A FOLDER IN YOUR GOOGLE DRIVE FOLDER &

NAME IT "FINAL CASE STUDY" PUT THE PNG/PDF

 OF YOUR CASESTUDY & A LINK TO YOUR CASE STUDY
WITHIN A GOOGLE DOCUMENT IN THAT FOLDER. DO THIS
BY WEDNESDAY, MAY 20th MIDNIGHT.

 

{ THIS IS A MUST TO PASS THE CLASS }

PUT YOUR FINAL PROTOTYPE LINK
 IN A GOOGLE DOC WITHIN A FOLDER

CALLED "FINAL PROTOTYPE" IN THE YOUR GOOGLE

DRIVE FOLDER BY WEDNESDAY MAY 20th MIDNIGHT.

 

PUT YOUR WORkING PROTOTYPE FILES,
& CASE STUDY FILES IN THOSE FOLDERS AS
WELL FOR SAFE KEEPING. JUST INCASE
YOU EVER NEED THEM.

 

 

FEEL FREE TO DO ANY
ANIMATIONS OR

motion GRAPHICS.

 

 

PRACTICE PRESENTING YOUR CASE STUDY

AND PRESENTING YOUR PROTOTYPE

 

 

IF YOU DO NOT SHOW UP TO THE LAST CLASS -
YOU WILL FAIL. DO NOT BE LATE EITHER.

 

HOMEWORK
THE FINALS

EXCITING!!!

1st

2nd

3rd

4th

5th

6th

7th

8th

10th

11th

{ THIS IS A MUST TO PASS THE CLASS}

{ EXTRA CREDIT }

{ COME TO CLASS PREPARES}

CREATE A LONG SKETCH
FILE AT 1224 pixels WIDE

-

PUT THIS FILE IN YOUR GOOGLE
DRIVE FOLDER - CALL IT CASE

STUDY

-

// CASE STUDY example

// CASE STUDY OUTLINE

Introduce your Target Audience

Don't use the persona yet. Just

user profiles here.

 

• Their Persona Names:

  – Frequent Flyers

  – Occasional Flyers

  – Bart/Muni Commuters

 

• About them

  – Describe a little bit of information about them

  – Just describe a day in the life"

 

Introduce your synthesis:

 

• Show the pictures of user buckets

   that we did in class

 

• Show the pictures of user buckets

   done in realtime board

Show a couple very interesting quotes
that help you build your case on why you

are focusing on a certain problem.

-

Remember:

• Design like a scientist

• Decide like a lawyer

Show some of your survey responses

-

Highlight some key responses

Show pictures of you interviewing.

Lots of pictures!!!!!

Show more than what I have.

Introduce the research

Show how many

people you interviewed

in a visual way

Show some learning goals

Show 2-3 questions under the learning goal

Show pictures of your users

-

You can also show a page from you

user script or topic map.

-

You can have a link to your
user script as well.

SHOW LEARNING GOALS

SHOW A 2-3 QUESTIONS UNDER EACH LEARNING GOAL

SHOW A PAGE FROM YOUR RESEARCH SCRIPT

Do this section last.

Just create a space for
the content..

Create the layout.

Just put your role

and a placeholder logo.

You can add the about

section later. Use

placeholder text.

_

 

You can add a

picture of the kick off

meeting and/or the company

mission statement.

_

 

HIGHLIGHT THE COMPANY

MISSION STATEMENT

Make your goals look good!

Make  this just placeholder

You will come back later

and update it...

INTRODUCE THE PROCESS OR

THE CHAPTERS OF YOUR

CASE STUDY.

 

• COMPETITIVE ANALYSIS

• RESEARCH/DISCOVERY

• RESEARCH INSIGHTS/LEARNINGS

• PROBLEM VALIDATION

• IDEATION/CONCEPTS
• WIRE-FRAMING

• USER TESTING

• FINDINGS/LEARNINGS

• FINAL PROTOTYPE

 

 

INTRODUCE YOUR

COMPETITIVE ANALYSIS

FOR 2 PRODUCTS

AND SHOW THE

S.W.O.T FRAMEWORK

MAKE IT PRETTY.

 

 

 

 

INTRODUCE THE PROCESS

SHOW YOUR COMPETITIVE ANALYSIS & S.W.O.T. FRAMEWORK.

UPDATE THE PRODUCT & BUSINESS GOALS

-

ADD THE WOW IMAGE IN BEGINNING

-

ADD A DIFFERENT WOW IMAGE AT THE END

-

AT THE END SAY "THANK YOU" SOMEWHERE

 

CASE STUDY REMINDERS

Show your Patterns:

 

• Show the pictures of the patterns

   that we did in class

 

• Show the pictures of your patterns

   done in realtime board

Put your key insights
next to your learning goals

What did you learn about

your learning goals?

What were the patterns that

you found?

How many people said this

pattern? ex: 14/19 people said "_"

You can create a section

like this to CALL OUT the
decisions you made based off the learnings above.

Explain why you are going to focus on a certain aspect of the problem you learned.

-

It does not need to be more than one decision. It can be just one decision. This is the place to call out the reasoning behind the problem.

The next slide (homework for next week) will be the problem statement(s).

 

 

Introduce YOUR

EMPATHY MAP

Add some copy that says:

I took all my learnings from research and created an empathy map. You may also choose to show YOUR PERSONAS

EMPATHY MAP

AND/OR

PERSONAS

 

 

WRITE YOUR PROBLEM

STATEMENT

SHOW SOME SKETCHES

WRITE YOUR

PROBLEM

STATEMENT

 

Write your Solution statement

Example:

A mobile application that allows clipper card users, to upload their clipper card, check the balance and

easily add money to the clipper card anytime and anywhere, all at the touch of their finger tips.

 

 

-

Show sketches:

You can show the value prompt

sketches we did or ui

sketches that you made.

SHOW CONCEPTS AND

CALL OUT SOME LEARNINGS

Show your concepts:

Call out some of the learnings,

what people liked and what

people didn't like.

 

EXTRA CREDIT

-

IF YOU WANT TO ADD A CUSTOMER JOURNEY MAP THAT MODELS YOUR EXPERIENCE. PLACE IT HEAR AFTER CONCEPTS & BEFORE WIRE FRAMES

MAKE
IT LOOK
GOOD

INTRODUCE YOUR WIRE FRAMES

-

You can add a button to link

to the wirefarme like I have here,

but not necessary, just show the
workflows and screens

You can show you

screens and the questions

 and/or learning goals

you have next to the

screen designs

You can also just show

the designs like the example

on the left to this image.

Introduce the user testing

-

Show lots of pictures
of you testing,

Show user testing

Lots of pictures of you

testing, More than

I have here

Show user testing

Lots of pictures of you

testing, More than

I have here

SYNTHESIS

THE

Introduce your

user testing synthesis

and show your realtime

board (miro) insights

Pick some of the

top learnings and show

them next to the

wireframe screens.

You can show users

quotes as well.

-

You can magnify it

like the example

here to the right

or

Just have text

next to the screen

-

You can show a

before screen

(before you

iterated) and right

next to it show the

after screen (what the

screen looked like after

the fix)

 

 

LEARNINGS

THE

THE

VISUAL

DESIGN

THE

DESIGN

SYSTEM

INTRODUCE
AND

SHOW YOUR

FINAL VISUAL
DESIGN IN

SCREEN

FORMAT.

 

ADD A BUTTON TO VIEW FINAL PROTOTYPE.

EXTRA CREDIT.

INTRODUCE YOUR
DESIGN SYSTEM,

SHOW YOUR FONTS,

COLORS, BUTTONS

AND ICONS

 

SHOW A FINAL

WOW SHOT AND

THANKS THE VIEWER

-

Look on dribbble

for inspiration

 

HERE'S WHAT I'M GRADING YOU ON:

 



• DOES YOUR CASE STUDY HAVE A WOW AREA,

   INTRO SECTION AND INTRODUCTION TO GOALS?

• DOES YOUR CASE STUDY SHOW PERSONAS,
   LEARNING GOALS AND IMPORTANT QUESTIONS

   THAT HELP YOU LEARN MORE ABOUT THE

   PROBLEMS AND THE PERSONAS?

• DOES YOUR CASE STUDY TELL A CLEAR STORY
   ABOUT YOU LEARNING ABOUT THE PEOPLE AND

   THE PROBLEM YOU SET OUT TO LEARN ABOUT?

 

• DOES YOUR CASE STUDY SHOW LOTS OF

   PICTURES OF YOU INTERVIEWING PEOPLE?

• DOES YOUR CASE STUDY SHOW AREAS OF

   SYNTHESIS AND CLUSTERING OF THEMES?

• DOES YOUR CASE STUDY SHOW AREAS
   OF THAT HIGHLIGHT THE THEMES YOU
   ARE LEARNING?

• DOES YOUR CASE STUDY SHOW SKETCHES/

   AND CONCEPTS. DOES IT SPEAK TO LEARNINGS
   ABOUT THE CONCEPTS?

• DOES YOUR CASE STUDY SHOW YOUR
   WIRE-FRAME WORKFLOWS?

• DOES YOUR CASE STUDY SHOW USER TESTING

   GOALS AND QUESTIONS YOU HAVE FOR USER TESTING?

• DOES YOUR CASE STUDY SHOW YOU USER TESTING?

• DOES YOUR CASE STUDY SHOW USER TESTING
   SYNTHESIS AND DOES IT SPEAK TO THE LEARNINGS,

   VALIDATIONS, DECISION AND OR ITERATIONS?

• DOES YOUR CASE STUDY SHOW HI FIDELITY

   SCREEN DESIGNS?

• DOES YOUR CASE STUDY SHOW STYLE GUIDES

   AND PART OF THE DESIGN SYSTEM? EXTRA CREDIT

• DOES YOUR CASE STUDY SHOW A FINAL

   WOW SHOT?

• DOES YOUR CASE STUDY HAVE NICE
   VISUAL DESIGN, LAYOUT AND
   TYPOGRAPHY TREATMENTS?

• DOES EVERY SECTION EXCITE/SURPRISE THE
   VIEWER OR IS EVERY SECTION THE SAME
   LAYOUT AND DESIGN REPEATED?

• DOES YOUR APPLICATION HAVE A COMPLETE

   HAPPY PATH WORK FLOW?

• IS YOUR APPLICATION EASY TO USE AND DO THE

   INTERACTIONS FOLLOW COMMON UI/UX PATTERNS?

• DOES YOUR APPLICATION HAVE NICE VISUAL
   DESIGN AND VISUAL TREATMENTS?