Experience Strategy

Experience Strategy

• 1.
  Experience Strategy an Overview
• 2.
  Experience Strategy an Overview What is an Experience Strategy? •  An approach to defining and planning for a product’s user experience. •  A recognized process that’s central to user centered design practice. 2
• 3.
  Experience Strategy an Overview What is an Experience Strategy? A clearly defined set of principles based on user needs and desires that guide design and development decisions. 3
• 4.
  Experience Strategy an Overview What does an Experience Strategy do? A good experience strategy: •  Deals well with rapid changes in technology and the marketplace •  Drives team and stakeholder consensus •  Conveys clarity and fosters empathy for the user •  Helps team to focus on the need, not the solution •  Guides all subsequent design decisions •  Answers: “Why?” 4
• 5.
  Experience Strategy an Overview Why would we need one? Do we really need another document? We already have: •  Business and Marketing objectives Identify business needs and how to advance products and brand •  Requirements Identify what features and functions to build •  Market research Identify opportunities in the marketplace None of these activities are wholly driven by user needs or desires. 5
• 6.
  Experience Strategy an Overview What about customer feedback? Sometimes… Yes! Drains are the I want future. a drain! 6
• 7.
  Experience Strategy an Overview What about customer feedback? But more often… Why? I want a window! 7
• 8.
  Experience Strategy an Overview What about customer feedback? But more often… It sounds more like I want to: you need a •  Feel the sunshine chair on the •  Smell fresh air porch. •  Talk to the neighbors •  Watch the cars go by •  Feed the birds 8
• 9.
  Experience Strategy an Overview What about customer feedback? Customer feedback is critical to our work, of course. But it only identifies problems - and not very well. An experience strategy provides a means to solve those problems. 9
• 10.
  Experience Strategy anOverview Why would we need one? Because to customers, the experience is the product. 10
• 11.
  Experience Strategy anOverview Why would we need one? The System How Users See It Interface Interface Business Organization Programming/ Data/ Hosting MAGIC Source: Adaptive Path, 2008 11
• 12.
  Experience Strategy anOverview How about an example? •  Product Vision: The center of a Microsoft entertainment ecosystem •  Market opportunity: a cheaper iPod •  Experience Vision: •  Feature-rich Take your music with you anywhere •  Revenue streams •  Created a new experience, •  Features with no basis in user needs not new features (subscriptions, music reorganization, sharing, •  Revolutionary TV connectors) 12
• 13.
  OK, Iʼm Sold. What’sin an Experience Strategy?
• 14.
  Experience Strategy anOverview The Experience Strategy produces: 1.  Experience Vision the experience promise once the product is developed; the “North Star” 2.  Experience Goals the user’s desired specific results, which become the “experience principles” 3.  Strategies the things we’ll design or do to achieve the user’s experience goals 4.  Audience Groups general categories of our users; their needs, desires and culture 14
• 15.
  Experience Strategy anOverview How does a UX team create the strategy? 1.  Gather requirements and conduct research – with users and project stakeholders (product/project managers, developers, business analysts, etc) 2.  Create a presentation and document that defines the product’s experience vision, and shows steps to meet that vision. 3.  Present to project stakeholders, get feedback and buyoff. 15
• 16.
  Experience Strategy anOverview So when the Experience Strategy is finished… The project has a workable roadmap: instructions on how to proceed with design: •  Information design •  Interaction and visual design •  Conceptual Design •  Technical design 16
• 17.
  Experience Strategy anOverview What’s not in it? Because the strategy is a roadmap, it doesn’t include: •  Site maps, wireframes or visual designs •  Content strategy •  Personas •  Requirements •  Project plans or timelines …but it would call for these things. 17
• 18.
  Experience Strategy anOverview Sample: Advantage Experience Strategy (handout) 18
• 19.
  Experience Strategy anOverview Discussion/ Questions/ Thanks for your time. 19