UX-Lx -a tour of non-design deliverables

Download UX-Lx -a  tour of non-design deliverables

Post on 18-Oct-2014

6.634 views

Category:

Design

1 download

Embed Size (px)

DESCRIPTION

My UX Lisbon 2011 presentation "More Elements of User Experience - a tour of non-design deliverables" in which I showed the impact that non-design deliverables and processes (scope, pitch, positioning, skill sets, etc.) have on the user experience, and how designers can (and should) influence them.

TRANSCRIPT

<p>20110512_UX-LX_tour_of_non-design_deliverables_slideshare.key</p> <p>peter boersma@pboersma</p> <p>m reelements of</p> <p>user experiencea tour of non-design </p> <p>deliverables</p> <p>2001</p> <p>2011</p> <p>?</p> <p>Design</p> <p>ResearchStrategy</p> <p>Process</p> <p>Evaluation</p> <p>Manage</p> <p>Business</p> <p>Design</p> <p>Strategy</p> <p>Research</p> <p>Process</p> <p>Manage</p> <p>Business</p> <p>Strategy</p> <p>Evaluation</p> <p>Design</p> <p>ResearchElemen</p> <p>ts of </p> <p>User E</p> <p>xperien</p> <p>ce</p> <p>Process</p> <p>Manage</p> <p>Business</p> <p>Strategy</p> <p>Evaluation</p> <p>Design</p> <p>ResearchtypicalUser-Centered Design</p> <p>Business</p> <p>Design</p> <p>ResearchEvaluation</p> <p>StrategyManage</p> <p>Process</p> <p>theseinfluence the</p> <p>User Experience too!</p> <p>Business</p> <p>Design</p> <p>ResearchEvaluation</p> <p>StrategyManage</p> <p>Process</p> <p>MoreElements of</p> <p>User ExperienceMore</p> <p>Elements ofUser Experience</p> <p>Business</p> <p>Design</p> <p>ResearchEvaluation</p> <p>StrategyManage</p> <p>Pitch</p> <p>Scenarios</p> <p>Position</p> <p>Service Design</p> <p>Roadmap</p> <p>Prototype</p> <p>RequirementsReviewTest</p> <p>Scope</p> <p>Optimize</p> <p>Estimate</p> <p>Beta</p> <p>ConceptDetailed Design</p> <p>Sketch</p> <p>Personas</p> <p>Competition</p> <p>Process</p> <p>Roles</p> <p>Steps</p> <p>Interviews</p> <p>for each non-design deliverable in this tour, I will show:</p> <p>* an example* a How-To</p> <p>* input by the UX team* impact on UX</p> <p>BusinessPitchScenarios</p> <p>Estimate</p> <p>X</p> <p>How-To for Pitchinghelp your client</p> <p>to en-vision the futureby visualizing it</p> <p>UX input for a Pitch* visions of the future</p> <p>* partial solutions* scope items for </p> <p>solutions* (answers to RFP &amp; questions)</p> <p>impact of the Pitch on UX* define UX Vision* inspire &amp; get inspired* determine budget* set expectations* analyze competition</p> <p>IIIII</p> <p>BusinessPitchScenarios</p> <p>Estimate</p> <p>how many sunflowers do you see?</p> <p>manyand</p> <p>a lotare good first guesses!</p> <p>output</p> <p>assumptionscalculationsexplanations</p> <p>risks</p> <p>when possible</p> <p>input for estimates</p> <p>scope itemsrequirements</p> <p>approachteam skills</p> <p>experience with subjectexperience with client</p> <p>experience of client</p> <p>when available</p> <p>example output</p> <p>assumingwe design 10 wireframes(5 complex + 5 medium)</p> <p>plus 15 components</p> <p>output</p> <p>assumptions</p> <p>calculations</p> <p>(explanations)risks</p> <p>we estimatewe need 300 hours</p> <p>butwe dont know the </p> <p>documentation needsof the developer</p> <p>(5x16 + 5x8) + (15x12)</p> <p>How-To for Estimating1. you determine what </p> <p>gets estimated2. explore every </p> <p>assumption you make(3. keep estimates honest; use any </p> <p>margins to wow the client)</p> <p>UX input for an Estimate</p> <p>* assumptions* whats easy/hard?</p> <p>* estimates for deliverables</p> <p>* risks </p> <p>impact of an Estimate on UX* define UX Vision I* inspire &amp; get inspired I* determine budget I* set expectations I* analyze competition I* focus attention I* define way of working I</p> <p>* determine budget I* set expectations I</p> <p>Strategy</p> <p>Position</p> <p>Competition</p> <p>sales service</p> <p>communitiescore brandclient</p> <p>clientclient</p> <p>client</p> <p>Competitor</p> <p>CompetitorCompetitor</p> <p>CompetitorCompetitor</p> <p>Big Competitor</p> <p>Big Competitor</p> <p>sales service</p> <p>core brand</p> <p>communities</p> <p>client</p> <p>client Competitor</p> <p>Competitor</p> <p>How-To for Positioning1. create a map</p> <p>2. find the spot that matches your vision3. see who is there</p> <p>4. identify differences</p> <p>UX input for Positioning</p> <p>* attributes that are important to users* competitors, in </p> <p>terms of UX* scope-items that </p> <p>differentiate</p> <p>impact of Positioning on UX* define UX Vision I* inspire &amp; get inspired I* determine budget II* set expectations II* analyze competition I* focus attention I* define way of working I* analyze competition I</p> <p>* define UX Vision I</p> <p>* focus attention I</p> <p>Strategy</p> <p>Position</p> <p>Competition</p> <p>How-To for Competitive Analysis</p> <p>know your enemy(Sun Tzu, The Art of War)</p> <p>UX input forCompetitive Analysis</p> <p>* competitors, in terms of UX</p> <p>* SWOT analyses</p> <p>impact of Competitive Analysis on UX* define UX Vision II* inspire &amp; get inspired I* determine budget II* set expectations II* analyze competition II* focus attention II* define way of working I* analyze competition I</p> <p>* inspire &amp; get inspired I</p> <p>* know what (not) to do I</p> <p>Research</p> <p>Personas</p> <p>Interviews</p> <p>DesignConceptDetailed Design</p> <p>Sketch</p> <p>Evaluation</p> <p>Prototype</p> <p>Test</p> <p>Manage</p> <p>Scope</p> <p>Optimize</p> <p>Beta</p> <p>easy hard</p> <p>contribution</p> <p>essential</p> <p>quickwin</p> <p>repair quality</p> <p>winner!</p> <p>pickjust a few of these for your </p> <p>project!</p> <p>How-To for Scoping</p> <p>1. rank all candidate scope items</p> <p>2. determine their dependencies</p> <p>3. select the winners</p> <p>UX input for Scoping* whats easy/hard?* whats essential?* what should go </p> <p>together?</p> <p>impact of Scoping on UX* define UX Vision II* inspire &amp; get inspired II* determine budget II* set expectations II* analyze competition III* focus attention II* define way of working I* know what (not) to do I* focus attention I* know what (not) to do I</p> <p>* set expectations I* determine budget I</p> <p>Manage</p> <p>Scope</p> <p>Optimize</p> <p>Beta</p> <p>28% better</p> <p>A</p> <p>B</p> <p>ABCC</p> <p>How-To for Optimizing</p> <p>1. experimentto learn what works</p> <p>with YOUR users</p> <p>2. GOTO 1</p> <p>UX input for Optimization</p> <p>* UX version of Key Performance Indicators* alternative designs* analysis of usage</p> <p>impact of Optimizing on UX* define UX Vision II* inspire &amp; get inspired II* determine budget III* set expectations III* analyze competition III* focus attention III* define way of working I* know what (not) to do II* know what (not) to do I</p> <p>Manage</p> <p>Scope</p> <p>Optimize</p> <p>Beta</p> <p>Process</p> <p>BusinessPitchScenarios</p> <p>Estimate</p> <p>Design</p> <p>ResearchEvaluation</p> <p>Strategy</p> <p>Position</p> <p>Prototype</p> <p>Test</p> <p>ConceptDetailed Design</p> <p>Sketch</p> <p>Personas</p> <p>Competition</p> <p>Interviews</p> <p>Process</p> <p>Service Design</p> <p>Roadmap</p> <p>RequirementsReview</p> <p>Roles</p> <p>Steps</p> <p>T-model</p> <p>wide experience</p> <p>deep</p> <p>know</p> <p>ledg</p> <p>e</p> <p>T-model</p> <p>user experience</p> <p>info</p> <p>rmat</p> <p>ion </p> <p>arch</p> <p>itec</p> <p>ture</p> <p>T-model</p> <p>user experience</p> <p>inte</p> <p>ract</p> <p>ion </p> <p>desi</p> <p>gn</p> <p>T-model</p> <p>user experience</p> <p>inte</p> <p>ract</p> <p>ion </p> <p>desi</p> <p>gn</p> <p>info</p> <p>rmat</p> <p>ion </p> <p>arch</p> <p>itec</p> <p>ture</p> <p>T-model</p> <p>user experiencevi</p> <p>sual</p> <p> des</p> <p>ign</p> <p>user</p> <p> rese</p> <p>arch</p> <p>inte</p> <p>ract</p> <p>ion </p> <p>desi</p> <p>gn</p> <p>info</p> <p>rmat</p> <p>ion </p> <p>arch</p> <p>itec</p> <p>ture</p> <p>usab</p> <p>ility</p> <p> test</p> <p>ing</p> <p>prot</p> <p>otyp</p> <p>ing</p> <p>How-To for Team Roles</p> <p>1. build a team,made of overlapping</p> <p>T-shapes2. keep the team </p> <p>balanced over time</p> <p>UX input for Team Roles* team skills</p> <p>* required skills* gap analysis* career plan</p> <p>impact of Team Roles on UX* define UX Vision II* inspire &amp; get inspired II* determine budget III* set expectations III* analyze competition III* focus attention III* define way of working I* know what (not) to do III* focus attention I* define way of working I* know what (not) to do I* deliver successfully I</p> <p>Process</p> <p>Service Design</p> <p>Roadmap</p> <p>RequirementsReview</p> <p>Roles</p> <p>Steps</p> <p>Area</p> <p>Area</p> <p>Area Area</p> <p>Area</p> <p>Area</p> <p>Area</p> <p>Area Area</p> <p>Area</p> <p>progress</p> <p>progress progress</p> <p>progress progress</p> <p>Area</p> <p>Area</p> <p>Area Area</p> <p>Area</p> <p>progress</p> <p>progress progress</p> <p>progress progress</p> <p>progress</p> <p>progress progress</p> <p>progress progress</p> <p>Area</p> <p>Area</p> <p>Area Area</p> <p>Area</p> <p>progress</p> <p>progress progress</p> <p>progress progress</p> <p>progress</p> <p>progress progress</p> <p>progress progress</p> <p>moment momentmoment moment</p> <p>How-To for Roadmaps</p> <p>1. define the futureof the system</p> <p>2. identify incremental,meaningful steps</p> <p>UX input for Roadmaps* areas for progress</p> <p>* scope items per area* estimates</p> <p>* what should go together?</p> <p>impact of Roadmaps on UX* define UX Vision II* inspire &amp; get inspired II* determine budget III* set expectations III* analyze competition III* focus attention IIII* define way of working II* know what (not) to do IIII* deliver successfully I</p> <p>* set expectations I* determine budget I* define UX Vision I</p> <p>* deliver successfully I</p> <p>Process</p> <p>Service Design</p> <p>Roadmap</p> <p>RequirementsReview</p> <p>Roles</p> <p>Steps</p> <p>A B?</p> <p>A B21 3 4</p> <p>C D2a</p> <p>1 3 5</p> <p>2b</p> <p>4b</p> <p>4a</p> <p>4c</p> <p>6</p> <p>SITEMA</p> <p>P</p> <p>wireframesrequire-</p> <p>mentsusability test</p> <p>Screen</p> <p>FLOWproto-type</p> <p>designprinciples</p> <p>Persona</p> <p>1 2 3 4</p> <p>Persona</p> <p>SITEMA</p> <p>P</p> <p>wireframesrequir</p> <p>e-</p> <p>ments</p> <p>usability testScreen</p> <p>FLOW</p> <p>proto-type</p> <p>designprinciples</p> <p>userresearch</p> <p>conceptdesign</p> <p>detaileddesign</p> <p>prototype &amp; evaluate</p> <p>C Dconceptdesign</p> <p>detaileddesign</p> <p>userresearch</p> <p>prototype &amp; evaluate</p> <p>prototype &amp; evaluate</p> <p>A B21 3 4?</p> <p>userreseach</p> <p>concept design</p> <p>detaileddesign</p> <p>prototype &amp; evaluate</p> <p>Persona</p> <p>SITEMA</p> <p>P</p> <p>wireframesrequire-</p> <p>ments</p> <p>usability testScreen</p> <p>FLOW</p> <p>proto-type</p> <p>designprinciples</p> <p>How-To forDesign Processes</p> <p>1. brainstorm steps2. create diagram</p> <p>3. document process(do NOT copy</p> <p>someone elses diagram)</p> <p>UX input for Design Processes</p> <p>* team deliverables* preferred way of </p> <p>working* team responsibilities</p> <p>Impact of Design Processes on UX* define UX Vision III* inspire &amp; get inspired II* determine budget IIII* set expectations IIII* analyze competition III* focus attention IIII* define way of working II* know what (not) to do IIII* deliver successfully II</p> <p>* focus attention</p> <p>I</p> <p>II</p> <p>I</p> <p>I</p> <p>* define UX Vision</p> <p>* set expectations</p> <p>* define way of working* deliver successfully* know what (not) to do I</p> <p>Business</p> <p>Design</p> <p>ResearchEvaluation</p> <p>StrategyManage</p> <p>Pitch</p> <p>Scenarios</p> <p>Position</p> <p>Service Design</p> <p>Roadmap</p> <p>Prototype</p> <p>RequirementsReviewTest</p> <p>Scope</p> <p>Optimize</p> <p>Estimate</p> <p>Beta</p> <p>ConceptDetailed Design</p> <p>Sketch</p> <p>Personas</p> <p>Competition</p> <p>Process</p> <p>Roles</p> <p>Steps</p> <p>Interviews</p> <p>Total impact of non-design UX* define UX Vision * inspire &amp; get inspired* determine budget* set expectations* analyze competition* focus attention* define way of working* know what (not) to do* deliver successfully</p> <p>Total impact of non-design UX* define UX Vision IIII* inspire &amp; get inspired II* determine budget IIII* set expectations IIIII* analyze competition III* focus attention IIIII* define way of working III* know what (not) to do IIIII* deliver successfully III</p> <p>Process</p> <p>Manage</p> <p>Business</p> <p>Strategy</p> <p>Evaluation</p> <p>Design</p> <p>Research</p> <p>theseinfluence the</p> <p>User Experience too!</p> <p>Process</p> <p>Manage</p> <p>Business</p> <p>Strategy</p> <p>Evaluation</p> <p>Design</p> <p>ResearchElemen</p> <p>ts of </p> <p>User E</p> <p>xperien</p> <p>ce</p> <p>MoreElements of</p> <p>User Experience</p> <p>peter boersma@pboersma</p> <p>m reelements of</p> <p>user experiencea tour of non-design </p> <p>deliverables</p>

Recommended

View more >