Upload
lmarine
View
113
Download
1
Tags:
Embed Size (px)
DESCRIPTION
Citation preview
Click to edit Master title style
Click to edit Master text stylesSecond level
Third levelFourth level
Fifth level
04/10/2023 1
Fitting User Experience strategy into your processes
Integrating UX into your product development efforts
by Larry Marine
People and Process
PeopleShared visionSkin in the game
ProcessDefine the problem, FIRST
THEN the solutions become self evident
Use visual artifactsShare knowledgeDisplay process evolution
A shared Vision
NASA in the 60’s
Everything relates back to a single goalDefine, agree, concurWhat is the goalWhat metrics define success
Everyone MUST agree!
Define the Problem
Most common 1st point of failureStart with clear concise objectivesPerform good user research!Optimize the affected processes
Avoid automating current frustrations
Involve the entire teamShared knowledge and vision
Task Flows
Prioritization
Defines the end of problem definitionBalance the needs of:
Business & Marketing objectives/valueTechnical feasibilityUser needs/value
Priority MatrixFunction/Task User Experience Business Tech. Feasibility Overall
Researcher 1 1 2
Find previous authors/users 2 1 2 10
Become aware of files, reports, artifacts 1 1 3 10
Determine relevancy of information 1 1 3 10
Collect artifacts in project “folder” 3 2 1 12
Contact relevant experts/authors 2 3 1 12
Search shared drives 1 2 1 8
Search local hard-drives 1 2 3 12
Search multiple intranets (cross firewalls) 1 2 3 12
Search email folders 1 2 1 8
Search the internet 1 2 1 8
Search pay sites and groups 2 3 2 14
Search hard copy libraries 2 3 1 12
Share useful artifacts with others 2 1 2 10
Keep some content private 2 3 1 12
Share some content locally (group/dept) 3 2 1 12
Compile selected data 2 1 1 8
Create working docs 3 1 1 10
Pass reports on to reviewers 3 3 2 16
Attend to Reviewer markups 3 3 1 14
Track revisions/versions 3 1 1 10
Search Across Org Boundaries 1 1 3 10
Multiple Design Phases
High-Level: Big rocksGeneral direction, interaction paradigmsNot detailed, but just enough (50-80%)Process flowScreens: Little rocksProduct flow (80-95%)Controls: SandThe final designs (100%)
Development is NOT Design
What is design?Technical – developmentVisual – graphicalCognitive – UX
UX Design MUST occur before technicalRefinement can occur in developmentBut not design
New Process Flow
Create Shared Deliverables
A single product specContains all aspects of the product evolution
ObjectivesUsersTasks/ProcessesPrioritiesDesign directions
Supports parallel efforts
Free Evaluation
1 ½ hour free evaluationTry it yourself, firstThen, compare your notes to mine