best practice for product design

ZEN & DAOZEN & DAO

Best Practice for internet product designBest Practice for internet product design

Wang ShengWang ShengEmail: washng@gmail.comBlog: www.shellwang.comBlog: www.shellwang.com

What’s product designWhat’s product design

•Product design is a process to find the DAO to solve the problem.

•who？

•what to do?

•how to do it?

•what’s his/her feeling?

•Product design is a process to find the DAO to solve the problem.

•who？

•what to do?

•how to do it?

•what’s his/her feeling?

What’s ZEN?What’s ZEN?

Constraint for application• in which condition?• what we can achieve?•

Constraint for application• in which condition?• what we can achieve?•

ZENZEN

Phase I: Product AnalysisPhase I: Product Analysis

•Before we start

• Business Analysis

• User Research

•Gather Requirement

• Qualitative&Quantity analysis

• Comparison analysis

• Other factors

• Information Architecture

• Website positioning

• Decision

•Before we start

• Business Analysis

• User Research

•Gather Requirement

• Qualitative&Quantity analysis

• Comparison analysis

• Other factors

• Information Architecture

• Website positioning

• Decision

User ResearchUser Research

•What’s UR?To find out user aim and action:

•who

•what

•how

•why(discussion)

•What’s UR?To find out user aim and action:

•who

•what

•how

•why(discussion)

Product RequirementProduct Requirement

•Gather Requirement

•Market requirement description(Outline)

•Product requirement description(Specification)

•Gather Requirement

•Market requirement description(Outline)

•Product requirement description(Specification)

Phase II. Prototype DesignPhase II. Prototype Design

•Concept model

•Function splitting

•Business flow chart

•page flow

•user flow

•data flow

•Concept model

•Function splitting

•Business flow chart

•page flow

•user flow

•data flow

•Prototype

•Holistic perspective

•Prototype

•Holistic perspective

•Architecture

•Navigation

•Architecture

•Navigation

Phase III. Interaction Design

Phase III. Interaction Design

•Scenario Design

•Story board

•User case

•User story

•Scenario Design

•Story board

•User case

•User story

•Scenario Analysis

•Disassemble to smaller

•Context continuous

•All user actions included

•Most frequently user acted.

•Scenario Analysis

•Disassemble to smaller

•Context continuous

•All user actions included

•Most frequently user acted.

Phase IV. Detailed DesignPhase IV. Detailed Design

•Specifications

•Function specification documents

•Feature list

•Product backlog

•Use case documents

•Design specification

•Logic specification

•Specifications

•Function specification documents

•Feature list

•Product backlog

•Use case documents

•Design specification

•Logic specification

•Usability

•Usability test

•Comparison test

•Contact with users

•Usability

•Usability test

•Comparison test

•Contact with users

Best practiceBest practice

•Gather Requirement

• User research

• MRD/PRD

•Business Flow• page flow

• user flow

•User story• scenario analysis

• logic specification

•Gather Requirement

• User research

• MRD/PRD

•Business Flow• page flow

• user flow

•User story• scenario analysis

• logic specification