1 Notes for User Experience Strategy Discussion Candace Soderston Kuali Rice User Experience Architect 6-30-2011.

  • Published on
    01-Apr-2015

  • View
    212

  • Download
    0

Transcript

  • Slide 1

1 Notes for User Experience Strategy Discussion Candace Soderston Kuali Rice User Experience Architect 6-30-2011 Slide 2 2 User Experience Strategy (Notes for Discussion) UX Philosophy: Deepen our collective understanding of people Bridge users directly into the design & evaluation process (users = IT Professionals, Application Developers, Business Analysts, Faculty/Staff, Students, etc.) Steward Best Practice: Design tenets, patterns, principles, execution Worthy user problems/goals UX engagement rigor (what users?, what patterns?, when in the process?, how engaged?) UX Goals: Maximize user uptake immediate reaction and self-discovery / awareness Minimize user disruption bridge from old to new (revolution is OK, with bridge) Maximize user productivity known pain points and bottlenecks eliminated, desired new tasks enabled, perception of time to goal (significantly reduced) Slide 3 3 Continuous Discovery Continuous Envisioning Continuous Developmen t Product Development Experiential Prototypes / Architectures Business Propositions End-to-end scenario definition End-to-end scenario definition Experiential Prototypes / Architectures Business Propositions End-to-end scenario definition End-to-end scenario definition Deep Dive Observational studies -- Day in the Life of Prioritized tasks / pain points Deep Dive Observational studies -- Day in the Life of Prioritized tasks / pain points Keylearning Keylearning Example: Integrated User Experience in Software Engineering User focus and cross-disciplinary teamwork, in parallel, concurrently multiple time horizons (V1 & future): Continuous Design & Definition V1V2V3 Slide 4 4 UX covers multiple time-horizons Early UX Engagement before next release (2.1): Insights gathered on key user tasks before development moves on to future release: User prioritization across key UI/task improvement opportunities User needs / requirements (per identified task domain) Current pain points analysis Defined user scenarios for key tasks Integrated UX Engagement during release (2.0): Key task opportunities designing the how in current release: UI interaction models, UI Specs, UI widgets Information architecture, navigation, labeling User/Application task flows Storyboard, Wireframes, Prototypes Visual design artifacts Horizon 1 Major Partner: Developers & Technical Architect Horizon 2 Major Partner: Business Analyst & Technical Architect Slide 5 5 Building a Scalable User Experience Process: End Release to field Graphic treatment & Refinements to all Information presentation Interactive prototypes Widgets (buttons, inputs) Refinements Information Architecture Application flows & concepts Wireframes, storyboards Defined user scenarios Functionality required to meet business & user needs User task prioritization: User goals, tasks, habits perceptions & context Start -- Business Needs Original model above: Jesse James Garrett, 2000 Platinum UX starts @ strategy Silver UX starts @ structure Bronze UX starts @ skeleton Basic Health UX starts @ surface Gold UX starts @ scope No UX for some projects (but they can use common design specs & artifacts) Slide 6 6 Ultimate Objective from early research -- Ultimate Objective from early research -- Understand communities/users priorities Slide 7 7 Typical UX Activities: Timeline and Methodologies 1. Understand users, their environment, the tasks they perform, and the importance/satisfaction with how those task are currently performed Slide 8 8 2. Conduct expert user assessment of key tasks on competitor products Typical UX Activities: Timeline and Methodologies Slide 9 9 3. Create high level mockup of new design and evaluate with users Typical UX Activities: Timeline and Methodologies Slide 10 10 4. Refine the design, conduct user assessments of prototypes with iterative evaluations and improvements Typical UX Activities: Timeline and Methodologies Slide 11 11 5. Validate the design with users in the context of defined task scenarios and a real environment Typical UX Activities: Timeline and Methodologies Slide 12 12 6. Compare finished product to competitor product(s) with representative users to verify that usability objectives have been met Typical UX Activities: Timeline and Methodologies Slide 13 13 Affinity with key future directions (ARC, TRC, Foundation) Need-State of the current UI (or lack of) Relationship with key user pain points Team passion & belief in importance of the area, long- term impact, innovation-coolness, visibility across community AND amount of effort & resources available / time in cycle! Prioritization framework for UX coverage: Slide 14 14 Getting Creating Designing Creating Managing Managing Managing Started Applications Workflow Rules Organization Identity Notifications Understanding Current Solutions: Likes and Dislikes? Deployment Research and Design Install, Setup, Configure, Migrate, Upgrade, Update KRAD Research and Design KRMS Research and Design KIM Research and Design Personas Great Kuali UX Great resulting community Uptake! Key User Scenarios UX Scenarios Persona / profiles KEW Research and Design KOM Research and Design UI Specs & Models Wireframes Widgets Prototypes UX across the Landscape for Kuali Rice? KEN Research and Design Slide 15 15 Determine UX coverage model for 2.1 projects: June 2011 Feb 2012 X X Oct 2011 ----------------------------------------------------- First months: Immersion / bootcamp into Kuali: 1.KRMS tactical UX improvements 2.KRAD Accessibility - research standards / tools, evaluations of 2.0 3.Gap analysis: Define UX research needed for 2.1 Form user groups needed for 2.1 (up to 3 groups, 3 demographics profiles) Review/edit/add new material into Rice Users Guide? ------------- Top Rice 2.1 UX candidates: KRAD UX (structure, skeleton, surface arch/design) KEW UX (strategy - research) Getting started (scope) (Import/Export?) ------------------------------------------- Rice 2.0 end & 2.1 Requirements candidates: Prioritize / select key UX task domains for 2.1 and coverage model: Ease of getting started? none? Creating / assembling apps? (KRAD) - Silver Creating workflow? (KEW) Platinum (beginning) Creating/editing rules? (KRMS) none? Managing identity? (KIM) none? Managing organizations? (KOM) none? Managing notifications? (KEN Import/Export) none? Slide 16 16 Rice UX 2.1 work items - in context End Release to field Graphic treatment & Refinements to all Information presentation Interactive prototypes Widgets (buttons, inputs) Refinements Information Architecture Application flows & concepts Wireframes, storyboards Defined user scenarios Functionality required to meet business & user needs User task prioritization: User goals, tasks, habits perceptions & context Start -- Business Needs Original model above: Jesse James Garrett, 2000 Workflow UI research user requirements & current tools UI review KRAD 2.1 work Slide 17 17 Technical Architecture Content Publishing Business Analysis / Planning SW Development User Experience Architecture User-centered, cross-disciplinary Team formation The project manager conveys priorities from ARC & board, coordinates the staffing and plan, schedules and ensures process/intersects, removes obstacles, tracks data to objectives, reviews and makes, approves, and owns decisions (with direction from ARC, TRC, Rice board). The cross-disciplinary team crosses functions and together designs and manages to the objectives / targets, engages with users in feedback/validation exercises, interprets input, turns it into design & architecture decisions -- cross- facets/functions. Items that are controversial and cant be conclusively decided in the cross-disciplinary teams go to program & executive team with recommendations driven by data (customer / user). Typical skills in user-centered design team: Project Management Slide 18 18 Typical skills in user-centered design team, cont: Example Team Structure Business Analyst / Market Strategy & Planning Segment Definitions and Characteristics expertise Identification of Software Solutions and Description of their offerings in feature/function, and task/environment terms University requirements/Technology forecasting expertise..Surrogate input for some end user segments Information Developer Instructional / training design expertise Communication / technical concepts expertise Documentation packaging expertise Translation expertise Online / Hardcopy prototypes Lead Technical Architect SW Architecture expertise SW Programming expertise SW Packaging expertise..SW Prototypes, schematics, & functional models Industry/Technology forecasting expertise Software Developer SW & UI Programming expertise..SW Prototypes, schematics, & functional models Marketing / Communications Advertising and Point-of-Sale materials Current customer & channel contact Knowledge of competitive situations Knowledge of cross-cultural marketing needs Impact of design on marketability expertise Communication Support & Service Impact of design on service costs expertise History of current field problems Current customer contact Help desk planning and Design UI interaction models / sequence / steps / obstacles UI designs: hand drawings / storyboards / wireframes / prototypes Visual and Physical Design expertise Color / size / layout / balance / positioning Aesthetics / metaphor / imaging / visual grammar User Experience Architecture, Research User needs / habits / abilities / wants (including special needs audience / accessibility / color-blindness, etc.) User profiles / persona definitions Opportunity maps (most important/frustrating tasks) Use-case scenarios user task scenario definitions Competitive evaluation - hand-on, user experience Slide 19 19 In addition to focus on key task domains, there are horizontal UX aspects that benefit all tasks / features for UX leadership see next slides Slide 20 20 Some Horizontal UX Aspects (for strategy discussion ) 1.Common, re-usable UI controls & templates framework -- architecture & library 2.Common persona definitions/understanding across feature teams 1.Accessibility focus for standards compliance & leadership 1.Common Install, Setup, Configuration, Migration, Upgrade, Update - Architectural Framework and Requirements 1.Error message Architecture/framework, message database, action- orientation, language 2.Terminology control Strategy, Research, Dictionary / Lexicon / Ontology 3.Unifying portal for discovery & launchpoints populated by Kuali functions that are installed, per individuals authorization/role? Slide 21 21 Aspects of UI Development Process Maturity: Common, re-usable UI controls and frameworks Free design space across feature teams No UI guidance or review, no commonality Common UI templates / models Common UI guidelines / objectives UI design process in place Some projects using Some user involvement Mature Immature Common Artifacts Teamwork Aspects No design process formalized UI task flow & design done while executing No user involvement All key projects using UI design process Users evaluating all key projects (structured methodology, sampling control and non-biasing approach) Slide 22 22 UI Controls Example Design Patterns Patterns represent optimal solutions to common interaction design problems within specific contexts. Examples: Data Views (grids, tables, lists) Form edit views & mechanics Property views Status / notifications Breadcrumb/Path Start/Home page portals framework Paginate (chunking) Dashboard Views Wizard framework Monitor Long-Running Ops/Tasks How to Launch Action/Task Multi-select Drag-drop Next/Back Scroll Explore Browse Search Filter Tag Slide 23 23 Details: Shared UI controls library Envision a UI controls library that all can use: Use of the standard controls expected/required in all Kuali specs. All developers browse the UI controls library first before speccing / executing. Awareness promoted Innovation solicited and shared PMs/Devs across the community who think they can do a better control can submit a prototype to a UI architecture review board for review/evaluation, to get full support: If deemed an improvement, it replaces or adds to the current control and all feature teams inherit the benefit. Otherwise, it goes into a community sandbox area for all to see and play with for future ideation, but does not get service/support in the official Kuali set (free open-source-like model, alpha code). Wiki/blog content. Library includes complex controls/frameworks, (Wizards, etc.), not just OS-level controls. On the web for all to use. Easy to find through our and other websites. Objective: Users can transfer their learning! Software is UI compatible! Developers can share UI primitives and therefore spend more time on other challenges! See: https://wiki.kuali.org/display/STUDENT/User+Interaction+Model https://wiki.kuali.org/display/STUDENT/User+Interaction+Model (from KS team, W.Washington et.al.) Others: http://fluidproject.org/ http://dojotoolkit.org/widgets Google's widget library Yahoo's widget library Slide 24 24 Details: Umbrella, goal-based portal? Single Unifying Kuali Application Portal design, inclusive for all users? Enable role separation / authorization / delegation / collaboration Enable customization by institution (granular roles/permissions) Enable customization by users (their own frequently-used function page). Enable users to handle role changes/evolution, collaboration, delegation through their familiar portal Slide 25 25 Key UX needs? Easy discoverability & navigation Easy discoverability & navigation to features / tasks Adaptive / flexible UI Adaptive / flexible UI - enable role-based, task-based, and team- based workspace UI. Allow all roles to use same UI framework populate w/ appropriate tasks. Work-flow delegation & authorization Work-flow delegation & authorization model to facilitate separation of duties as well as exception scenarios Action-based management Action-based management only show me what I need to be concerned about System and business process metrics System and business process metrics e.g., notifications on key business indicator thresholds Slide 26 26 Terminology control? Strategy, Research, Dictionary / Lexicon / Ontology Point of Contact for formative research and coordination / control of terminology? This work is in the front-end, early UI concept development phase, before improvements are defined and before specs are written. Skills in psycho-linguistics and research methodologies. Liaison with industry-wide standards bodies, universities, other MS divisions lexicons. Research techniques: contextual inquiry, card-sorting, concept/affinity mapping, cloze procedures, multiple choice/matching. Consistent & standard terminology simplifies user experience. (Example above from a job posting for SAS) Slide 27 27 Roles overlap some tasks are done by multiple personas Roles change tasks done by one persona shift to another Tasks vary in frequency, dif...

Recommended

View more >