The document discusses simple methods for involving real users in product design and development through contextual design. It recommends conducting field studies to understand what users actually do and care about. Contextual design involves contextual inquiry, interpretation sessions, work models, affinity diagramming, visioning, storyboards, interaction patterns, paper prototyping, and agile development. The goal is to design products that support and extend user intentions by embodying users' work practices discovered through contextual inquiry in the field.
UX and Business Analysts - Stop the MadnessAndrew Hinton
The document discusses problems with how software is typically designed and calls for a more user-centered approach. It argues that most software focuses too much on features rather than the user experience. In contrast, the app iA Writer is highlighted as an example of software designed to be enjoyable to use for its target users. The document calls for involving users more directly in the design process through techniques like personas and scenarios to help ensure software meets user needs and motivations.
This document summarizes a workshop on creating customer-centered product visions using contextual design. The workshop will have participants analyze customer data to understand user needs and issues, then brainstorm ideas for addressing those needs. Participants will develop multiple visions for how new technologies could improve the customer experience. They will evaluate the visions and consolidate them into a coherent solution. The goal is to redesign products and services around customer needs revealed by contextual inquiry research methods.
The document summarizes a presentation given at a Business Analyst Conference on requirement traceability matrices. It defines what a traceability matrix is, describes the components of requirements that need to be traced, and provides an example matrix. It explains why traceability is important for requirements management, change impact analysis, and ensuring quality. While traceability was once seen as a paperwork exercise, it now enables better project control and process improvement when used with requirements management tools.
Solution Validation & Assessments - A practical ApproachJulen Mohanty
The document discusses solution assessment and validation techniques for business analysts. It outlines the importance of solution assessment and validation in the CMMI framework and lists key tasks business analysts perform in this area, such as developing alternative solutions, evaluating technology options, facilitating solution selection, and supporting implementation. The document also describes specific activities business analysts do in solution assessment, including ranking solution options, identifying additional capabilities, and evaluating technology options to ensure the selected solution fulfills requirements.
Mind the 'business' while you 'analyze' - Mangesh NadkarniBAConfPune
The document summarizes the key aspects of business analysis and the ideal way it should be conducted. It outlines the typical business analysis journey from defining measures of success, to requirements gathering, solution development and implementation. However, it notes that some key elements are often missing - understanding market trends, competitor products, and latest technologies. The ideal approach involves understanding the business arena, focusing on cost optimization, end-user experience, and ensuring the solution meets evolving needs. This leads to satisfied clients and fulfilled business analysis.
This document summarizes a presentation on adopting an agile approach to requirements for complex systems and distributed teams. It discusses using a product backlog, user stories, use cases and scenarios to understand desired outcomes. It also covers exploring solutions through visualization, prototyping, and reviews. The presentation emphasizes using the right level of detail for requirements and a blend of techniques including backlogs, models, prototypes and specifications.
Orca Creation is a product design company established in 2005 with a team of over 10 designers experienced in product design, engineering, and program management. They specialize in turning intangible ideas into physical products through services like product design and development, engineering analysis, and program management. The company utilizes design tools like Unigraphics, ProEngineer, and Solidworks and has experience in industries like consumer electronics, industrial equipment, and medical devices.
UX and Business Analysts - Stop the MadnessAndrew Hinton
The document discusses problems with how software is typically designed and calls for a more user-centered approach. It argues that most software focuses too much on features rather than the user experience. In contrast, the app iA Writer is highlighted as an example of software designed to be enjoyable to use for its target users. The document calls for involving users more directly in the design process through techniques like personas and scenarios to help ensure software meets user needs and motivations.
This document summarizes a workshop on creating customer-centered product visions using contextual design. The workshop will have participants analyze customer data to understand user needs and issues, then brainstorm ideas for addressing those needs. Participants will develop multiple visions for how new technologies could improve the customer experience. They will evaluate the visions and consolidate them into a coherent solution. The goal is to redesign products and services around customer needs revealed by contextual inquiry research methods.
The document summarizes a presentation given at a Business Analyst Conference on requirement traceability matrices. It defines what a traceability matrix is, describes the components of requirements that need to be traced, and provides an example matrix. It explains why traceability is important for requirements management, change impact analysis, and ensuring quality. While traceability was once seen as a paperwork exercise, it now enables better project control and process improvement when used with requirements management tools.
Solution Validation & Assessments - A practical ApproachJulen Mohanty
The document discusses solution assessment and validation techniques for business analysts. It outlines the importance of solution assessment and validation in the CMMI framework and lists key tasks business analysts perform in this area, such as developing alternative solutions, evaluating technology options, facilitating solution selection, and supporting implementation. The document also describes specific activities business analysts do in solution assessment, including ranking solution options, identifying additional capabilities, and evaluating technology options to ensure the selected solution fulfills requirements.
Mind the 'business' while you 'analyze' - Mangesh NadkarniBAConfPune
The document summarizes the key aspects of business analysis and the ideal way it should be conducted. It outlines the typical business analysis journey from defining measures of success, to requirements gathering, solution development and implementation. However, it notes that some key elements are often missing - understanding market trends, competitor products, and latest technologies. The ideal approach involves understanding the business arena, focusing on cost optimization, end-user experience, and ensuring the solution meets evolving needs. This leads to satisfied clients and fulfilled business analysis.
This document summarizes a presentation on adopting an agile approach to requirements for complex systems and distributed teams. It discusses using a product backlog, user stories, use cases and scenarios to understand desired outcomes. It also covers exploring solutions through visualization, prototyping, and reviews. The presentation emphasizes using the right level of detail for requirements and a blend of techniques including backlogs, models, prototypes and specifications.
Orca Creation is a product design company established in 2005 with a team of over 10 designers experienced in product design, engineering, and program management. They specialize in turning intangible ideas into physical products through services like product design and development, engineering analysis, and program management. The company utilizes design tools like Unigraphics, ProEngineer, and Solidworks and has experience in industries like consumer electronics, industrial equipment, and medical devices.
ANIS2012 workshop2 Howard Chan_JoonSang Baekngoinnovation
This document discusses design for social innovation. It outlines three aspects of design: 1) Design as a professional discipline which can help visualize and promote social innovations as well as design social innovation products. 2) Design as a tool for thinking which can apply design processes to planning and implementing social innovation projects. 3) Design as a concept of operation which can design sustainable systems and define roles among stakeholders. The document also presents the Double Diamond design process and provides examples of using design to study marginalized knowledge and build cross-sector systems.
The document discusses design thinking and innovation at HP. It begins by describing how industrial designers traditionally take a strategic, big picture approach to innovation. It then discusses the importance of design thinking, which involves understanding customer needs, conceptualizing solutions, and making concepts tangible through prototyping. A key part of this process is listening to and observing customers through activities like executive briefings and advisory councils to discover opportunities. The document provides the example of how HP developed its Quick Release bracket by solving a trading floor customer's problem of replacing displays quickly. It discusses how this solution led to broader innovation opportunities. It concludes with thoughts on continuously innovating and embracing change.
Nailing It Down: Detailed Design to Preserve the UX Visionjsokohl
Here are the key details for this page:
- Header displays reservation details like dates, room type, number of guests
- Breakdown of nightly rate, taxes, and total amount due per night
- Total for entire stay displayed prominently
- Links to terms, cancel policy displayed
- Large "Confirm Reservation" CTA button
- Footer with site links
Developer: Please implement the following:
- Pull reservation details like dates, room type, guests from booking API
- Calculate nightly rates, taxes, totals programmatically
- Display totals for full stay by multiplying nightly totals
- "Confirm Reservation" button triggers confirmation workflow
- Ensure all styling/layout matches existing
This document provides an overview of Joe Sokohl's presentation on detailed design for preserving the user experience vision. The presentation covers what detailed design is, where it breaks down, and potential solutions. It applies to agencies, independent UX practitioners, and distributed or cross-border teams. The presentation compares typical documentation approaches to detailed design processes like VIEWW and FiveDs and discusses activities at each stage to refine requirements and designs for development.
The Statistical Package provides applications that utilize a systematic True Corner-based design methodology to account for process variation effects. It can analyze designs to identify failures and determine a set of True Corners. It also analyzes mismatch effects and allows running Monte Carlo simulations or verifying high-sigma designs. This provides accurate analysis of process variations to help designers identify and address problems.
Power Up - Your Influence on Non-Design DeliverablesPeter Boersma
Presentation at IxDA Hamburg networking event on Monday, September 26, 2011.
The presentation aims to make UX people aware that they can and should influence non-design deliverables.
The document provides an overview of the UX designer's portfolio, including research methods like field studies, surveys, competitive analysis and design documentation. It also lists analysis methods like affinity diagrams, user profiles, task analysis and design solutions like user scenarios, design patterns and prototypes. The portfolio highlights experience conducting user research through contextual inquiry and interviews, as well as design work like creating personas, storyboards, wireframes and prototypes across various industries. Evaluation methods employed include heuristic evaluations, usability testing and focus groups.
UX-Lx -a tour of non-design deliverablesPeter Boersma
This document provides a tour of common non-design deliverables and how they influence user experience (UX). It discusses pitches, estimates, positioning, competitive analysis, scoping, optimizing, team roles, design processes, and roadmaps. For each deliverable, an example and how-to is presented, along with the potential UX input and the impact on defining vision, budget, expectations, focus, and successful delivery. The overall message is that while non-design work may seem separate, it profoundly shapes the UX outcome.
This document discusses strategies for implementing user experience design policies to influence product development. It describes the evolution of Primax Electronics' UX team from initial usability testing to integrating interaction design and user-centered design processes earlier. To strengthen the UX team's strategic influence, the document proposes establishing UX governance, re-engineering the organization structure, and setting regular communication channels. It suggests leveraging existing product development processes and using a balanced scorecard to define and measure UX's value and return on investment. The changes aim to empower the UX team to directly impact products and evaluate performance using defined metrics.
26-05-10 making the most of your internshipJPStrategy
The document provides career advice for summer interns, including securing a challenging assignment to demonstrate skills, building networks within the company, and using the internship to learn about the company's business, culture, and potential job opportunities. Interns are also advised to have a supervisor for their assignment, identify a mentor, produce their best work, provide and receive feedback, and keep their university's career services informed of their progress.
Innovation product design planning process style 3 powerpoint presentation te...SlideTeam.net
This diagram outlines an innovation process that considers various internal and external factors. It maps how an organization's culture, leadership, values, and capabilities influence its business model, processes, and product or service offering. It also examines how the customer experience, expectations, insights, and context relate to the brand, market approach, and technologies used. Key stakeholders are represented as influencing different elements of the process.
Natalie Hanson, PhD. April 2011 presentation to the Philadelphia chapter of ACM-CHI (Association for Computing Machinery, special interest group on Computer Human Interaction).
The document is a guide to the Business Analysis Body of Knowledge (BABOK), which defines the profession of business analysis. It describes the knowledge areas, tasks, skills, and techniques that business analysts use to work with stakeholders and recommend solutions that help organizations achieve their goals. The guide provides an introduction to key business analysis concepts and structures the remainder of the document around knowledge areas, tasks, competencies, and techniques.
The document provides an overview of Southbeach Modeller 3.0, visual modeling software for creativity, design, analysis, and problem solving. It can be used for communication, facilitation, root cause analysis, and improving processes. Southbeach Modeller implements a unique "situational improvement" approach and is the first tool to use Southbeach Notation. It has a user-extensible rules engine and allows creating and reusing models across multiple files.
The document outlines the Business Analysis Body of Knowledge (BABOK), which provides best practices for business analysis. It details 36 techniques used in business analysis across 6 knowledge areas: business analysis planning & monitoring, elicitation & facilitation, requirements management & communication, enterprise analysis, requirements analysis, and solution assessment & validation. It also lists 6 underlying competencies needed for business analysis.
Look Around You - Influences on UX (UX Sofia)Peter Boersma
My presentation "Look Around You - Influences on UX", delivered at UX Sofia 2011, where I show the influence that non-UX team members have on the user experience, but also how UX team members can influence their deliverables.
This document outlines the tasks, inputs, and outputs involved in business analysis according to the BABOK guide. It details 6 key business analysis areas: requirements management & communication, solution assessment & validation, planning & monitoring, elicitation, analysis & design, and strategy analysis. Each area contains multiple subordinate tasks that define the essential activities, dependencies, and work products to effectively perform business analysis according to standard practices.
Begroten als het model = de applicatie = de documentatie - Gerard Ohm - NESMA...Nesma
This document discusses model-driven development using the Be Informed platform. It makes three key points:
1. With Be Informed, there is no clear distinction between design and development - the design is directly implemented. This impacts traditional function point analysis for estimating.
2. Productivity depends highly on customer maturity and ability to make decisions. Experience of the implementation team also impacts productivity.
3. A "Be Structured" approach is recommended, starting with architecture and business function models to provide structure before detailing and growing applications live. This provides better predictive value for estimating than traditional function points.
Geoportales y realidad aumentada para integrar contenidos (Borja Rodriguez Niso)Foro JuanLuisVives
Este documento describe las evoluciones pasadas y futuras de la web, con un enfoque en la integración de contenidos geoespaciales y la realidad aumentada. Discutió la evolución de la web 1.0 a la web 3.0 y más allá, con características como contenido generado por el usuario, web semántica y la integración de diferentes formatos de contenido. También exploró aplicaciones como geoportales, turismo con geolocalización y ejemplos de innovación como mapas interactivos y realidad aumentada.
The View Resort in Egypt welcomes visitors to enjoy its beautiful sandy beaches along the Red Sea, which offers excellent diving in crystal clear waters teeming with coral and tropical fish. Egypt has a variety of resorts along the coast with amenities and activities such as water sports, and its warm climate makes it a popular year-round destination for beach vacations. Sharm El Sheikh on the Sinai Peninsula is a renowned diving spot with a bustling nightlife and amenities for relaxing in a tropical paradise or exploring the desert interior through activities like safaris.
El documento presenta las respuestas de Kiara Pereira a 42 preguntas sobre diversos temas científicos como física, química y biología. Las respuestas brindan justificaciones breves sobre conceptos como las propiedades de los estados de la materia, reacciones químicas, estructura atómica, fuerzas y movimiento, sistemas biológicos y procesos ecológicos.
ANIS2012 workshop2 Howard Chan_JoonSang Baekngoinnovation
This document discusses design for social innovation. It outlines three aspects of design: 1) Design as a professional discipline which can help visualize and promote social innovations as well as design social innovation products. 2) Design as a tool for thinking which can apply design processes to planning and implementing social innovation projects. 3) Design as a concept of operation which can design sustainable systems and define roles among stakeholders. The document also presents the Double Diamond design process and provides examples of using design to study marginalized knowledge and build cross-sector systems.
The document discusses design thinking and innovation at HP. It begins by describing how industrial designers traditionally take a strategic, big picture approach to innovation. It then discusses the importance of design thinking, which involves understanding customer needs, conceptualizing solutions, and making concepts tangible through prototyping. A key part of this process is listening to and observing customers through activities like executive briefings and advisory councils to discover opportunities. The document provides the example of how HP developed its Quick Release bracket by solving a trading floor customer's problem of replacing displays quickly. It discusses how this solution led to broader innovation opportunities. It concludes with thoughts on continuously innovating and embracing change.
Nailing It Down: Detailed Design to Preserve the UX Visionjsokohl
Here are the key details for this page:
- Header displays reservation details like dates, room type, number of guests
- Breakdown of nightly rate, taxes, and total amount due per night
- Total for entire stay displayed prominently
- Links to terms, cancel policy displayed
- Large "Confirm Reservation" CTA button
- Footer with site links
Developer: Please implement the following:
- Pull reservation details like dates, room type, guests from booking API
- Calculate nightly rates, taxes, totals programmatically
- Display totals for full stay by multiplying nightly totals
- "Confirm Reservation" button triggers confirmation workflow
- Ensure all styling/layout matches existing
This document provides an overview of Joe Sokohl's presentation on detailed design for preserving the user experience vision. The presentation covers what detailed design is, where it breaks down, and potential solutions. It applies to agencies, independent UX practitioners, and distributed or cross-border teams. The presentation compares typical documentation approaches to detailed design processes like VIEWW and FiveDs and discusses activities at each stage to refine requirements and designs for development.
The Statistical Package provides applications that utilize a systematic True Corner-based design methodology to account for process variation effects. It can analyze designs to identify failures and determine a set of True Corners. It also analyzes mismatch effects and allows running Monte Carlo simulations or verifying high-sigma designs. This provides accurate analysis of process variations to help designers identify and address problems.
Power Up - Your Influence on Non-Design DeliverablesPeter Boersma
Presentation at IxDA Hamburg networking event on Monday, September 26, 2011.
The presentation aims to make UX people aware that they can and should influence non-design deliverables.
The document provides an overview of the UX designer's portfolio, including research methods like field studies, surveys, competitive analysis and design documentation. It also lists analysis methods like affinity diagrams, user profiles, task analysis and design solutions like user scenarios, design patterns and prototypes. The portfolio highlights experience conducting user research through contextual inquiry and interviews, as well as design work like creating personas, storyboards, wireframes and prototypes across various industries. Evaluation methods employed include heuristic evaluations, usability testing and focus groups.
UX-Lx -a tour of non-design deliverablesPeter Boersma
This document provides a tour of common non-design deliverables and how they influence user experience (UX). It discusses pitches, estimates, positioning, competitive analysis, scoping, optimizing, team roles, design processes, and roadmaps. For each deliverable, an example and how-to is presented, along with the potential UX input and the impact on defining vision, budget, expectations, focus, and successful delivery. The overall message is that while non-design work may seem separate, it profoundly shapes the UX outcome.
This document discusses strategies for implementing user experience design policies to influence product development. It describes the evolution of Primax Electronics' UX team from initial usability testing to integrating interaction design and user-centered design processes earlier. To strengthen the UX team's strategic influence, the document proposes establishing UX governance, re-engineering the organization structure, and setting regular communication channels. It suggests leveraging existing product development processes and using a balanced scorecard to define and measure UX's value and return on investment. The changes aim to empower the UX team to directly impact products and evaluate performance using defined metrics.
26-05-10 making the most of your internshipJPStrategy
The document provides career advice for summer interns, including securing a challenging assignment to demonstrate skills, building networks within the company, and using the internship to learn about the company's business, culture, and potential job opportunities. Interns are also advised to have a supervisor for their assignment, identify a mentor, produce their best work, provide and receive feedback, and keep their university's career services informed of their progress.
Innovation product design planning process style 3 powerpoint presentation te...SlideTeam.net
This diagram outlines an innovation process that considers various internal and external factors. It maps how an organization's culture, leadership, values, and capabilities influence its business model, processes, and product or service offering. It also examines how the customer experience, expectations, insights, and context relate to the brand, market approach, and technologies used. Key stakeholders are represented as influencing different elements of the process.
Natalie Hanson, PhD. April 2011 presentation to the Philadelphia chapter of ACM-CHI (Association for Computing Machinery, special interest group on Computer Human Interaction).
The document is a guide to the Business Analysis Body of Knowledge (BABOK), which defines the profession of business analysis. It describes the knowledge areas, tasks, skills, and techniques that business analysts use to work with stakeholders and recommend solutions that help organizations achieve their goals. The guide provides an introduction to key business analysis concepts and structures the remainder of the document around knowledge areas, tasks, competencies, and techniques.
The document provides an overview of Southbeach Modeller 3.0, visual modeling software for creativity, design, analysis, and problem solving. It can be used for communication, facilitation, root cause analysis, and improving processes. Southbeach Modeller implements a unique "situational improvement" approach and is the first tool to use Southbeach Notation. It has a user-extensible rules engine and allows creating and reusing models across multiple files.
The document outlines the Business Analysis Body of Knowledge (BABOK), which provides best practices for business analysis. It details 36 techniques used in business analysis across 6 knowledge areas: business analysis planning & monitoring, elicitation & facilitation, requirements management & communication, enterprise analysis, requirements analysis, and solution assessment & validation. It also lists 6 underlying competencies needed for business analysis.
Look Around You - Influences on UX (UX Sofia)Peter Boersma
My presentation "Look Around You - Influences on UX", delivered at UX Sofia 2011, where I show the influence that non-UX team members have on the user experience, but also how UX team members can influence their deliverables.
This document outlines the tasks, inputs, and outputs involved in business analysis according to the BABOK guide. It details 6 key business analysis areas: requirements management & communication, solution assessment & validation, planning & monitoring, elicitation, analysis & design, and strategy analysis. Each area contains multiple subordinate tasks that define the essential activities, dependencies, and work products to effectively perform business analysis according to standard practices.
Begroten als het model = de applicatie = de documentatie - Gerard Ohm - NESMA...Nesma
This document discusses model-driven development using the Be Informed platform. It makes three key points:
1. With Be Informed, there is no clear distinction between design and development - the design is directly implemented. This impacts traditional function point analysis for estimating.
2. Productivity depends highly on customer maturity and ability to make decisions. Experience of the implementation team also impacts productivity.
3. A "Be Structured" approach is recommended, starting with architecture and business function models to provide structure before detailing and growing applications live. This provides better predictive value for estimating than traditional function points.
Geoportales y realidad aumentada para integrar contenidos (Borja Rodriguez Niso)Foro JuanLuisVives
Este documento describe las evoluciones pasadas y futuras de la web, con un enfoque en la integración de contenidos geoespaciales y la realidad aumentada. Discutió la evolución de la web 1.0 a la web 3.0 y más allá, con características como contenido generado por el usuario, web semántica y la integración de diferentes formatos de contenido. También exploró aplicaciones como geoportales, turismo con geolocalización y ejemplos de innovación como mapas interactivos y realidad aumentada.
The View Resort in Egypt welcomes visitors to enjoy its beautiful sandy beaches along the Red Sea, which offers excellent diving in crystal clear waters teeming with coral and tropical fish. Egypt has a variety of resorts along the coast with amenities and activities such as water sports, and its warm climate makes it a popular year-round destination for beach vacations. Sharm El Sheikh on the Sinai Peninsula is a renowned diving spot with a bustling nightlife and amenities for relaxing in a tropical paradise or exploring the desert interior through activities like safaris.
El documento presenta las respuestas de Kiara Pereira a 42 preguntas sobre diversos temas científicos como física, química y biología. Las respuestas brindan justificaciones breves sobre conceptos como las propiedades de los estados de la materia, reacciones químicas, estructura atómica, fuerzas y movimiento, sistemas biológicos y procesos ecológicos.
Este documento trata sobre las transformaciones digitales en la sociedad de la información. Aborda temas como la evolución de Internet a la web 2.0 como un nuevo espacio de interacción social; el poder y contra-poder en la red; las identidades y subjetividades en un contexto digital; y la relación entre los jóvenes y las redes sociales. También analiza conceptos como la sociedad de la información, el espacio de flujos, las nuevas narrativas emergentes y los cambios en las representaciones simbólicas en la era digital.
Imathia Construccion is a Spanish construction company that has been operating since 2004. It provides civil construction services to Spanish and international clients. Imathia is part of the larger Imathia Global Group, which offers additional services like engineering, transport consulting, and financial consulting. All of Imathia's staff have extensive experience in corporate management, strategy, and technical challenges in both the public and private sectors. They perform all work according to their certified quality, environmental, and health and safety management systems.
Ponente: Eduardo Martinez. Marketing4food.
Una de las claves de éxito de nuestras empresas se encuentra en el marketing.
En este taller, destinado al público del sector agroalimentario, analizaremos el perfil de nuevos tipos de cliente a la hora de producir, desarrollar un producto de altísima calidad, pero sobre todo, hacérselo saber al cliente a través de herramientas y estrategias de marketing específicas para el sector agroalimentario.
En esta linea descubriremos nuevas ideas sobre: Tendencias en Marketing Online agroalimentario; Nuevos modelos de negocio; Oportunidades en e-commerce; El Plan de Marketing Digital; Herramientas de monitorización de marca y análisis de la competencia; Redes sociales profesionales: oportunidades en Linkedin; Casos de éxito. Captación de potenciales clientes en el B2B: Food Marketplaces, etc.
Este documento presenta una guía para elaborar un plan de negocios efectivo. Explica que un plan de negocios debe contener un resumen ejecutivo, una descripción de la empresa y su situación actual o pasada, detalles sobre el producto o servicio, un estudio de mercado, un plan de marketing, y requisitos financieros. El objetivo es brindar una visión clara y organizada del negocio para lograr el éxito.
La Secretaría de Comunicaciones y Transportes pospuso la publicación de las bases del nuevo proceso licitatorio para la construcción del Tren de Alta Velocidad México-Querétaro. La SCT argumentó que estudiará recomendaciones para dar mayor claridad, certeza y transparencia en el proceso. Organizaciones como Human Rights Watch y Amnistía Internacional rechazaron la "verdad histórica" presentada por la PGR sobre el caso Ayotzinapa, al igual que los padres de los normalistas. El director de la Normal Rural de Ayotzinapa afirmó que los
El documento describe los elementos clave de la mezcla de promoción, incluyendo la publicidad, promoción de ventas, relaciones públicas y otras herramientas. Explica que la promoción es fundamental para diferenciar el producto, posicionar la marca y segmentar el mercado de manera efectiva. También cubre factores estratégicos clave para diseñar la mezcla de promoción como el público objetivo, objetivos de la promoción, naturaleza del producto y etapa de su ciclo de vida.
Aquapol presentation book English, renovation and elimination of moisture in ...GREENTECH SRL
A full description of the renown Aquapol system to dry humid walls in old and less old buildings and houses without the use of chemicals, totally natural ecologic system. Handles all water coming form the ground.
More than 50,000 installations in Europe. Totally non invasive with double warranty on the Aquapol device itself (20 years) and on the final result of dried walls. With sathisfied or refound formula.
Full diagnostic of the building, salt analysysi, checklist of collateral actions to do for humidity non coming form the ground, and 36 months of techcnical services include.
Please contact us at www.muriumidi.info or www.green-tech.it or www-aquapol.it (for Italy) or visit www.aquapol.com rest of the world
"Creación de Mapas Android" con Marcadores usando la API de Google MapsBugster18
El documento describe los pasos para crear una aplicación de mapas en Android usando la API de Google Maps. Se crea un proyecto en Eclipse y se agrega el fragmento de mapa en el archivo de diseño XML. Luego se vincula el proyecto con la biblioteca Google Play Services y se agrega código Java para mostrar el mapa con marcadores en dos ubicaciones de Cartago, Valle del Cauca.
This document provides information on pipeline and geothermal valves and services offered by Alfa Oiltech, including:
- Product information on their expanding plug valve (AlfaSeal), trunnion ball valves (AlfaBall T), and other valve types.
- Specifications like pressure classes, materials of construction, end connections, sizes, weights and dimensions for each valve type.
- Details on available trim options, spare parts, and compliance with applicable standards.
- The company aims to leverage over 100 years of experience in geothermal valves to provide reliable products, applications expertise and after-sales support to customers.
El documento describe el proceso de litografía, un método de impresión creado en 1796 que utiliza una piedra caliza sobre la cual se dibuja la imagen con una sustancia grasa. Al humedecer la piedra, la tinta solo se adhiere a las zonas dibujadas debido a la incompatibilidad entre el agua y la grasa. Para cada color se requiere una piedra diferente. Los carteles litográficos solían imprimirse con 15 o más tintas.
Guía práctica clínica sobre el manejo de la enfermedad meningocócica invasivaPediatria_DANO
Este documento trata sobre el tratamiento de la enfermedad meningocócica invasiva (EMI) en atención primaria. Describe los síntomas y signos clínicos de la EMI, así como el manejo prehospitalario y de soporte para mejorar la supervivencia. Resalta la importancia del diagnóstico y tratamiento tempranos para reducir la morbilidad y mortalidad de esta enfermedad.
Este documento presenta el manual del programa G-Stat 2.0, un programa completo de análisis estadísticos desarrollado por el departamento de Biometría de GSK. Incluye descripción general, requisitos técnicos, instalación, mejoras con respecto a versiones anteriores, y explicación de las funciones y menús del programa.
Las enfermedades no caen del cielo, entran por la boca, vía nuestros alimentos, con ellos también nos podemos curar.
Quieres bajar de peso y hagas lo que hagas no lo consigues?
Nadie se curó solo hablando de salud, tenemos que hacer algo es nuestra responsabilidad y el resultado depende de nosotros.
Te invito a regenerar tu cuerpo a nivel celular, regalate 90 dias con ayuda de la Trofología (Alimentación Alcalina): Te asesoro para que tengas una correcta selección, preparación y combinación de insumos = SALUD TOTAL
Desde cualquier parte del mundo, cuenta conmigo, informes: solamentepatricia@gmail.com
Using rapid prototying_for_design_iterationdrewz lin
This document discusses using rapid prototyping and iterative design to incorporate user feedback into the product development process. It advocates for:
1) Conducting user research like contextual inquiries and creating work models to understand user needs before design.
2) Developing low-fidelity paper prototypes to validate the product structure and features with users.
3) Iteratively testing prototypes with users, interpreting the feedback, and quickly modifying the prototypes.
4) Integrating this user-centered design process into an Agile development methodology with short sprints to incorporate user input at each stage of design.
More Elements of UX: real-world design deliverablesPeter Boersma
Presentation delivered to UX Russia 2010 (October 7, Moscow). Introduces an overview of elements that influence the user experience, with examples of design deliverables and design processes.
Introducing Business Analysis, IT Business Analyst & UMLEdgar Khachatryan
This document provides an introduction to business analysis, the role of a business analyst, and UML modeling. It defines business analysis and describes the main sub-disciplines. It outlines the role of a business analyst in understanding business needs, facilitating communication between stakeholders, and ensuring IT solutions meet business requirements. The document also introduces the Unified Modeling Language and common UML diagram types used in modeling software systems. Finally, it discusses business analysis certifications and references for further reading.
UX focuses on designing products with the user experience in mind. It aims to create products that are satisfying, easy to use and encourage users to return. UX involves understanding users through research, designing interfaces and interactions, then testing and refining the design. The goal is to increase usability, engagement and business metrics like sales and reduce support costs. Research shows that investing in UX can yield returns of 2-100 times the initial investment through improving these factors. The UX process involves strategies like defining personas, wireframing interfaces, testing designs and analyzing results to iteratively improve the user experience.
The Business Analysts Role in Agile Software Developmentallan kelly
The document discusses the role of business analysts in agile software development. It argues that the product owner role is often filled by a business analyst. While business analysts take a backseat in early agile adoption, their role becomes more important as teams become more effective in delivering business needs. Specifically, business analysts are key to reducing unnecessary work through improved analysis and requirements. The document recommends a ratio of one business analyst for every 3-7 developers, depending on how stable the product is and how rapidly requirements change.
The BA role in Agile software developmentallan kelly
The document discusses the role of business analysts in agile software development. It argues that in traditional approaches, requirements are gathered at the start of a project by business analysts who then leave the project. However, in agile approaches, requirements gathering is an ongoing process and business analysts need to stay involved throughout to have a dialogue rather than just produce documents. The business analyst role evolves from an "order taker" to an internal consultant, facilitating discussions between business and development teams.
This document provides an overview of common user experience deliverables including pitching, estimating, positioning, researching users, designing concepts and prototypes, testing, and optimizing. It discusses how to summarize research findings with personas, sketch concepts rapidly, design specifications that match projects, and test early and often. The goal is to help teams create great experiences through a user-centered process tailored to their needs.
Challis Hodge is the VP of User Experience at Bridge Worldwide. The document provides an overview of experience planning and why it is important to involve UX practitioners. It defines experience design as considering patterns of life, goals, activity, context, repeated use, learning, sharing, emotion and more while applying the design process. UX practitioners seek to account for and minimize bias, bring a customer perspective, and facilitate a balance between business goals, user needs and technology. The document emphasizes that bias needs to be controlled and accounted for, and provides examples of how different groups like marketing, IT and creatives may have biases that distort their vision compared to focusing on the customer. It presents a process framework for UX and
Stakeholder Persuasion - How to quantify your gut feelingUser Intelligence
This document discusses how to quantify user experience research findings to persuade stakeholders. It provides two case studies: 1) Validating a new website navigation structure using tree testing which found the new structure was 40% better. 2) Measuring expected success of a new concept for Philips' website by testing tasks, satisfaction and goals on prototypes which provided convincing results to support investment. The key takeaways are to use quantitative analyses in design to facilitate objective communication with stakeholders and identify issues before development.
The document introduces the eDesign HCI team and their user-centered design process. The team is comprised of 6 members with diverse educational and professional backgrounds. They follow a contextual design methodology which involves studying users in their environments to understand needs, creating shared models and visions, then developing prototypes. The deliverables include consolidated models, personas, storyboards, prototypes and a functional design. The team welcomes questions.
This document discusses revolutionizing the user experience through Oracle's products. It outlines that Oracle aims to provide a modern user experience through seamless integration of functionality and user interfaces in its WebCenter Suite. This suite provides capabilities for portals, websites, composite applications, social collaboration, and content management to enable productive and efficient work. It supports both business users and IT developers through tools for rapid development and management of customizable solutions.
SketchFlow allows users to quickly prototype and iterate on user interface designs without extensive time or resource investments. It provides an informal way to explore ideas and evolve rough concepts into living prototypes. This rapid and cost-effective approach focuses on being creative and building the best solution.
Effective prototyping with SketchFlow allows experimenting with application flow, screen layouts, and state transitions. The interactive player engages clients by displaying working prototypes and collecting feedback directly in Expression Blend.
Agile practices like iterative development and user-centered design help teams collaborate effectively and respond quickly to change.
The document discusses common challenges that design teams face when working on projects. It outlines five key challenges: 1) unclear or differing project objectives between stakeholders, 2) uncertain budget ownership and funding streams, 3) design methods and processes being forced onto stakeholders, 4) team members lacking a shared language, and 5) conflicts between user and business needs. For each challenge, it provides lessons learned, such as the importance of understanding stakeholder motivations, expressing value in the stakeholders' terms, balancing user and business needs, and having a shared project language. The document advocates taking a collaborative approach to design that considers all perspectives.
This document provides an overview and schedule for an introductory management course. It outlines the course concepts, theories, and drivers that will be covered over 13 weeks. These include topics such as organizational culture, social responsibility, decision making, leadership, and control. The document also provides exam preparation tips and emphasizes applying knowledge through assignments. It details the process for Assignment 1, including researching concepts and theories, collecting field evidence from an interview, and organizing the written response. Finally, it offers time management guidance for completing Assignment 1 over a 3-week period through planning, research, interviewing, thinking, writing, and editing.
BizSpark SF Lightning Talk: "Design Patterns for Designers" by Stephan OrmeMark A
The document discusses design patterns for product design. It explains that design patterns originate from Christopher Alexander's work and capture solutions to common design problems. The document then outlines the key components of the product design process, including understanding needs, agreeing with stakeholders, and providing direction. It describes discovery and design processes that involve user research, diagramming solutions, and developing models, views, and controls. The goal is to understand needs, get stakeholder agreement, and provide clear direction for developers.
The Essentials of Great Search Design (ECIR 2010)Vegard Sandvold
This document outlines an essential search design process called "Sprint 0" that involves cross-disciplinary collaboration. It emphasizes learning from stakeholders, users, and technical experts to understand business goals, user needs, and technological capabilities. Concepts are developed through inspiration, ideation, and iterative prototyping and testing of interaction and technical designs. The goal is to unite business goals, user needs, and technological possibilities to discover solutions and innovate through an inclusive design process.
The document discusses collaboration between design and engineering teams at Yahoo. It provides an overview of design and engineering processes, then describes Yahoo's collaborative process. The process involves strategic planning, inspiration, ideation, project planning, design, build, and evaluate phases. It also presents two use cases: a photo lightbox and sentiment slider. For the photo lightbox, feedback was gathered and iterations made the experience more optimized for different devices. For the sentiment slider, fast iterations simplified the design to increase engagement and distribution.
The document outlines the SIPs (Strategic Innovation Processes) process which includes four main phases: 1) Define & Discovery, 2) Design & Architecture, 3) Development & Execution, and 4) Roll Out. It also lists the roles involved in a project including founders, partners, team members, and users/stakeholders.
The document discusses the concept of lean user experience (UX) design. It is inspired by lean and agile development theories and focuses on bringing the true nature of design work to light faster with less emphasis on deliverables and more focus on the actual user experience. The key aspects of lean UX discussed include cross-functional teams, continuous discovery and design experiments, establishing assumptions and hypotheses to test, rapid prototyping, and obtaining frequent user feedback to iterate quickly. The goal is to reduce waste and cycle time through techniques like defining minimum viable products and conducting usability testing to continuously learn and improve the design.
Similar to Simple methods for_reliable_user_involvement (20)
Web security-–-everything-we-know-is-wrong-eoin-kearydrewz lin
1) Web application security is often approached incorrectly, focusing too much on annual penetration tests and compliance, rather than ongoing monitoring and prevention through the development process.
2) Many vulnerabilities are introduced through third party libraries and dependencies, which are not properly tested or managed. Continuous testing across the full software supply chain is needed.
3) Not all vulnerabilities are equal - context is important. A risk-based approach should prioritize the most critical issues based on factors like impact, likelihood, and the development environment. Compliance alone does not ensure real security.
This document summarizes a presentation about the mobile security Linux distribution Santoku Linux. It discusses how Santoku Linux was created by modifying Lubuntu to include mobile forensic and security tools from the company viaForensics. Some key tools discussed include AFLogical OSE for Android logical acquisitions, iPhone Backup Analyzer, and utilities for analyzing mobile malware samples. Real-world examples of analyzing the Any.DO task manager app and Korean banking malware are also provided.
This document discusses sandboxing untrusted JavaScript from third parties to improve security. It proposes a two-tier sandbox architecture that uses JavaScript libraries and wrappers, without requiring browser modifications. Untrusted code is executed in an isolated environment defined by policy code, and can only access approved APIs. This approach aims to mediate access between code and the browser securely and efficiently while maintaining compatibility with existing third-party scripts.
This document discusses how HTML5 features can be used for authentication purposes and addresses some security challenges. It describes APIs like local storage, canvas, geolocation, and notifications that could be leveraged for authentication factors like passwords, patterns, and one-time passwords. However, it also notes risks like storing sensitive data on devices, spoofing locations, and notifications not being reliable. The document advocates using HTML5 responsibly and understanding privacy and user behavior when designing authentication solutions.
Owasp advanced mobile-application-code-review-techniques-v0.2drewz lin
The document discusses code review techniques for advanced mobile applications. It begins with an overview of why mobile security is important given the rise in mobile usage. It then discusses different mobile application types and architectures that can be code reviewed, including native, hybrid, and HTML5 applications. The document outlines the goals of mobile application code reviews, such as understanding the application and finding security vulnerabilities. It provides the methodology for conducting code reviews, which includes gaining access to source code, understanding the technology, threat modeling, analyzing the code, and creating automation scripts. Finally, it discusses specific vulnerabilities that may be found in Windows Phone, hybrid, Android, and iOS applications.
The document discusses research conducted by Gregg Ganley and Gavin Black at MITRE in FY13-14 on iOS mobile application security. It describes their work on a tool called iMAS (iOS Mobile Application Security) which aims to provide additional security controls and containment for native iOS applications. iMAS addresses vulnerabilities related to runtime access, device access, application access, data at rest, and threats from app stores/malware. It utilizes techniques like encrypted code modules, forced inlining, secure MDM and more to raise security levels above standard iOS but below a fully customized/rooted mobile device environment. The document outlines the motivation, capabilities and future research directions for the iMAS project.
Defeating xss-and-xsrf-with-my faces-frameworks-steve-wolfdrewz lin
This document discusses how to defeat cross-site scripting (XSS) and cross-site request forgery (XSRF) when using JavaServer Faces (JSF) frameworks. It covers validating user input, encoding output, and protecting view states to prevent XSS, as well as configuring JSF implementations to protect against XSRF by encrypting view states and adding tokens to URLs. The presentation emphasizes testing validation, encoding, and protection in specific JSF implementations since behaviors can differ.
This document summarizes a presentation on defending against CSRF (cross-site request forgery) attacks. It discusses four main design patterns for CSRF defenses: the synchronizer token pattern, double submit cookies, challenge-response systems, and checking the referrer header. It then provides details on implementing these patterns, specifically looking at libraries and features in .NET, .NET MVC, Anticsrf, CSRFGuard, and HDIV that can help implement CSRF tokens and validation. The document covers the tradeoffs of different approaches and considerations for using them effectively on the code and server level.
Chuck willis-owaspbwa-beyond-1.0-app secusa-2013-11-21drewz lin
This document provides an overview of the OWASP Broken Web Applications (OWASP BWA) project. It discusses the background and motivation for the project, describes the current status including what applications are included in the virtual machine, outlines future plans, and solicits feedback to help guide and expand the project. The goal of OWASP BWA is to provide a free, open-source virtual machine containing a variety of intentionally vulnerable web applications to aid in testing tools and techniques for finding and addressing security issues.
This document provides a summary of a presentation by Robert Hansen on the future of browser security. Hansen argues that while browser developers want to improve security and privacy, their companies' business models focused on advertising revenue prohibit them from doing so. He outlines various techniques used by advertisers and browser companies to track users against their preferences. Hansen advocates for technical controls that allow users to opt out of tracking through a "can not track" approach, rather than relying on ineffective "do not track" policies. He concludes by discussing WhiteHat Security's focus on privacy and their plans to add more security and privacy features to their Aviator browser.
Appsec usa2013 js_libinsecurity_stefanodipaoladrewz lin
This document summarizes Stefano di Paola's talk on security issues with JavaScript libraries. It discusses how jQuery's $() method can be considered a "sink" that executes HTML passed to it, including examples of XSS via jQuery selectors and AJAX calls. It also covers problems with JSON parsing regular expressions, AngularJS expression injection, and credentials exposed in URLs. Solutions proposed include validating all input, auditing third-party libraries, and moving away from approaches like eval() that execute untrusted code.
Appsec2013 presentation-dickson final-with_all_final_editsdrewz lin
(1) A study surveyed 600 software developers and found that most did not have a basic understanding of software security concepts, with 73% failing an initial survey and the average score being 59% before training. (2) However, after training, developers' understanding of key concepts increased, with some areas like cross-site scripting seeing a 20 percentage point gain. (3) The study concluded that targeted security training can improve developers' knowledge in the short-term, though retention of this knowledge may require refresher training over time.
This document summarizes Bruno Gonçalves de Oliveira's talk on hacking web file servers for iOS. It introduces Bruno and his background in offensive security and discusses how iOS devices store a lot of information and mobile applications are often poorly designed and vulnerable. It provides examples of vulnerable file storage apps, outlines features and vulnerabilities like lack of encryption, authentication, XSS issues, and path traversal flaws. The document demonstrates exploits like unauthorized access to file systems on jailbroken devices and how to find vulnerable systems through mDNS queries. It concludes that mobile apps are the future but designers still do not prioritize security and there are too many apps for users to vet carefully.
Appsec 2013-krehel-ondrej-forensic-investigations-of-web-exploitationsdrewz lin
This document discusses forensic investigations of web exploitations. It presents a scenario where a web server in a DMZ zone was exploited but logs are unavailable, so network traffic must be analyzed. Wireshark will be used to analyze a PCAP file of recorded traffic to determine what happened and find any traces of commands or malware. The document also provides information on the costs of different types of cyber attacks, how to decode HTTP requests, and discusses tools that can be used for network forensics investigations like Wireshark, tcpdump, and Xplico.
Appsec2013 assurance tagging-robert martindrewz lin
The document discusses engineering software systems to be more secure against attacks. It notes that reducing a system's attack surface alone is not enough, as software and networks are too complex and it is impossible to know all vulnerabilities. It then discusses characteristics of advanced persistent threats, including that the initial attack may go unnoticed and adversaries cannot be fully kept out. Finally, it argues that taking a threat-driven perspective beyond just operational defense can help balance mitigation with detection and response.
The document summarizes a presentation on vulnerabilities found in SCADA systems between 2009-2013. It analyzed vulnerabilities by component, with the majority (66%) found in communication components like Modbus and DNP3 protocols. Examples of vulnerabilities are described for several devices. Real-world issues with SCADA systems are discussed like lack of authentication and patching. Recommendations are provided like auditing SCADA networks, implementing secure protocols and password policies, and keeping systems updated.
This 3-page document discusses the real-world challenges of implementing an agile software development lifecycle (SDLC) approach from the perspectives of Chris Eng and Ryan O'Boyle. It was presented at the OWASP AppSec USA conference on November 20, 2013 and focuses on practical lessons learned and best practices for incorporating security throughout an agile SDLC.
This document outlines a presentation given by Simón Roses Femerling on software security verification tools. It discusses BinSecSweeper, an open source tool created by VulnEx to scan binaries and check that security best practices were followed in development. The presentation covers using BinSecSweeper to verify in-house software, assess a company's software security posture, and compare the security of popular browsers. Examples of plugin checks and reports generated by BinSecSweeper are also provided.
1. Simple Methods for Reliable User
Involvement
Hugh Beyer
hugh.beyer@incontextdesign.com
Karen Holtzblatt, CEO 978.823.0100 www.incontextdesign.com
Hugh Beyer, CTO info@incontextdesign.com www.innovationincool.com
2. UX and Agile: The promise
Agile says development in steps – and iterate
UX says work with users to create value – and iterate
Phase 0 The “ideal” product
ideal
sets direction
(requirements)
User Iteration
refines the interface
and function
What users really
need
3. Base principle for real user feedback
Real user feedback – Doesn’t come from:
Product owners
Stakeholders
User surrogates
Purchasers
People who used to be users
Demos
Focus groups
And…
You can’t put the user on the team
Users can’t give you a design
U
Users can’t t ll you what th want
’t tell h t they t
4. Solving the problem of design
The system’s work
model has:
ode as
Language
System Structure
Features
Concepts
The user’s
work model has:
Language
Work Structure
Work Flow
Intention
Result
Design the optimal match:
Products and systems
embody work practice
Design must support and
extend user intent
5. Contextual Design
olutions
1 Contextual Inquiry
Talk to your customers in the field
ments & So
2 Interpretation Session
Interpret the data as a team to capture key issues and activities
Work Models &
Requirem
3 Affinity Diagramming Consolidate data across customers for a full market view
4 Visioning
Generate new products & the next product concepts steeped in data
Define & Validate Concepts
5 Storyboards
Work out the details of particular tasks and roles
Interaction Patterns &
6 User Environment Design Define system structure, function, content and user interaction
7 Paper Prototype Interviews
Mock up the interface to validate direction and UI with customers
p
e
8 Visual Design & Agile Stories
Design and test the final look; base stories on validated function
6. Contextual Design
1 Contextual Inquiry
2 Interpretation Session
3 Work Models & Affinity
4 Visioning
Field t di
Fi ld studies yield
i ld
5 Storyboards
real understanding
of what customers
actually do and
6 Interaction Patterns & UED
what they really
y y
care about
7 Paper Prototype Interviews
8 Visual Design & Agile Stories
7. Contextual Design
U21 Flow Model
1 Contextual Inquiry Discuss open litigation
Board of Directors
Administrative Assistant
General Counsel Discuss open
litigation
SOP
Ask for legal advice Email
2 Interpretation Session Business
Unit
Managers
U21
SOP
Outside
Provide legal advice Senior Corporate Counsel Counsel
Hand deliver SOP Open email to see
Discuss legal options
U3-1 request
and log in info
TRIGGER:
3 Work Models & Affinity She wants to understand HR
what her boss is doing.
doing
Department
Receive email
from partner
Open email to see
request
U5 and log in info
U3-2 Sequence:
Open CCH Online
Does she advise her boss Keyword
on how to answer or Search
4 Visioning U3-3 manage his schedule? Pg. 1 of 3
Type log in info
Log in doesn’t work
Can we design a better way
for her to keep informed? Re-type user name
and password in
5 Storyboards
Intent: Restrict
Domain to get
from email
Decide to search in
Cross-functional team relevant results
Fed
interprets the data to Intent: Account for
research time
Select search form
capture issues and Remembered to
6
Intent: Say what I
start
Interaction Patterns & UED want in computer
terms client
tracker
model activities Type complex
keyword
k d
search using
Creates a shared Boolean
7 Paper Prototype Interviews perspective of the
data and implications
8 Visual Design & Agile Stories
8. Contextual Design
1 Contextual Inquiry
2 Interpretation Session
3 Work Models & Affinity
4 Visioning
Consolidates data across all
5 Storyboards customers reveals the big
picture of the market: key
issues, tasks, values,
6 Interaction Patterns & UED collaboration, work process,
and technology impact
7 Paper Prototype Interviews Find the opportunities to
guide innovation.
8 Visual Design & Agile Stories
9. Contextual Design
1 Contextual Inquiry
2 Interpretation Session
3 Work Models & Affinity
4 Visioning
5 Storyboards
Must have
6 Interaction Patterns & UED
models for Agile
7 Paper Prototype Interviews
8 Visual Design & Agile Stories
10. Contextual Design
1 Contextual Inquiry
2 Interpretation Session
3 Work Models
4 Visioning
5 Storyboards Facilitated group
ideation session –
with evaluation
6 Interaction Patterns & UED
First immerse in the
data then generate
concepts for new and
7 Paper Prototype Interviews
existing products
8 Visual Design & Agile Stories
11. Contextual Design
1 Contextual Inquiry
2 Interpretation Session
3 Work Models & Affinity
4 Visioning
Develop the details of the
5 Storyboards
new to-be activities
Clarify function, user
6 Interaction Patterns & UED
experience, automation
rules, data, and technology
based on the vision
7 Paper Prototype Interviews
8 Visual Design & Agile Stories
12. Contextual Design
1 Contextual Inquiry
2 Interpretation Session
3 Work Models & Affinity
4 Visioning
Represent the system
5 Storyboards
structure, requirements,
and user interface layout
6 Interaction Patterns & UED
Ensure consistency,
coherence, and a smooth
user experience product
7 Paper Prototype Interviews
wide.
8 Visual Design & Agile Stories
13. Contextual Design
1 Contextual Inquiry
2 Interpretation Session
3 Work Models & Affinity
4 Visioning
5 Storyboards Validate product concepts,
process changes, and user
experience while testing user
6 Interaction Patterns & UED reception
Or bring out concept boards
7 Paper Prototype Interviews to validate direction before
detailed design
8 Visual Design & Agile Stories
14. UX and Agile: The promise
Agile says development in steps – and iterate
UX says work with users to create value – and iterate
The “ideal” product
ideal
Phase 0: What do
we write on the
story cards?
Contextual Inquiry
Consolidation
Visioning End of sprint:
Paper prototyping What does the
During sprint: Get
user think?
the details right
Field interviews
Paper prototyping
16. The Contextual interview
The interviewing process of
Contextual Design
One-on-one 2-hour field interview
Gathering detailed information about
work practice
p
In the workplace while people work
Through observation and discussion
of on-going work
on going
Based on a model of apprenticeship
to the customer
17. Contextual Inquiry principles
Key concepts to guide understanding the customer
Context: Collect data in the context of people’s work
p p
• Go to your user's workplace
• Talk to your users while they work
Partnership: Work with customers as partners in inquiry
• Help users articulate their work practice
• Let them lead
Interpretation: Uncover the meaning and implications of customer action and
language
• Create a shared understanding
• Draw out the implications
p
Focus: Listen and probe from a clear intention
• Know your purpose
• Challenge your assumptions
18. What is context?
Get as close to the work as possible
Go to the customer
Interview while they are working
Be grounded in real objects and events
Pay attention to non-verbal communication
Ongoing work versus summary experience
People tend to give summaries
Ongoing work is never summarized
Stay concrete don’t abstract
concrete, don t
Ongoing work
Retrospective account — from the last two weeks
Look at artifacts
19. Dos and don’ts: Context principle
Don’t Do
Let the user talk in the air or talk in Make talk concrete:
abstractions • Follow actual work and specific cases from
recent past
• Get or draw artifacts; annotate with intent
and usage
Allow the user to summarize a story Reconstruct a situation:
• Back up the user when he skips a step
•H
Hypothesize steps to prompt the user
h i h
Discuss feature requests out of the Probe to understand what actual work
context of usage situation prompted the request
Follow the real work example
Ask “What would you have done next?” Avoid predictions of future scenarios
when the user did not actually do it in Only
O l care about what is h
b t h t i happening now
i
this case
Do a retrospective account of past work
20. What is partnership?
Partnership as relationship
The user is the expert
• They know everything about their
work but can’t tell you Withdrawal
So follow their lead
Help the users articulate and see
their work practice
Return
Avoid ineffective interview styles
The Traditional Interviewer
The Expert/Novice
The Guest/Host
21. Dos and don’ts: Partnership principle
Don’t Do
Take the expert role: When asked for tool tips, ask how he/she
• Do not teach or tell user how to do their would have done without you
jobs
Give tips at the end
• Do not give tips on tool use
Invite
I it users to educate you
t d t
Create a distant relationship: Reconstruct a situation:
• Sit back, have a reserved attitude • Lean forward, be fascinated
• Be apologetic or timid • Be confiding and genuine
• Be overbearing
Create a formal relationship Be nosy, overcome formality
Sit on the “visitor” side of the desk while Pull up a chair next to the user and
the user is talking his/her computer screen. Make sure you
can see what’s happening
what s
22. What is interpretation?
Interpretation is the data
A shared understanding of what is g g on
g going Customer
Offer interpretations
• Don’t ask open-ended Fact
q
questions
Listen for the “No” tune the interpretation
• Huh?
Hypothesis
• Umm... could be
• “They” would like it
• “Yes” comes with elaboration
Implication
• Watch for non-verbal clues
• Check your design ideas as they occur
Design
Idea
23. Dos and don’ts: Interpretation principle
Don’t Do
Just watch what happens and record it Look for patterns, intents, issues, and the
role people play in the work, and then
share them with the user
Just ask “yes” or “no” questions Offer hypothesis that invite elaboration
Just ask “why?” or open-ended Use metaphors to explain what the work
questions is like and ask the user if you get it right
24. What is focus?
Know your purpose
We all have an entering focus
• A set of preconceived assumptions and beliefs
Drive interviews with your project focus
• A clear understanding of what work you are trying to
understand
Expand your focus
• Challenge your assumptions, probe the unexpected
Probe to expand focus
Surprises and contradictions
“Nods” — What you assume
is true
What you do not know
The problem behind solutions
Share
Interpretations for validation
Design ideas for co-design
25. Dos and don’ts: Focus principle
Don’t Do
Hide your focus Show your focus:
• The user can help find relevant cases and issues
Focus on the software, configuration or Focus on work; identify cases in the focus to
hardware pursue
Pursue issues or events outside your focus Expand focus based on what you see the user do
Gloss over irrelevant events introduced by the user
Remember: It is not rude to not engage the users in
things that are not in focus. You don’t want to teach
g
the user that you are interested in irrelevant
information.
Dismiss issues because you don’t understand
y Probe things y don’t understand or are
g you
them surprised by
Talk from an implicit list of questions you want Follow the work, discuss how the work is
answered structured, not topics in your head
Nod without asking in order to verify everything Share your interpretations of their words and work
you think you understand even if it is obvious
26. Key concepts in Contextual Inquiry
Be an apprentice
Context
Go to your user's workplace
Talk to your users while they work
Partnership
Help users articulate their work practice
Let them lead
Interpretation
Create a shared understanding
Draw out the implications
Focus
Know your purpose
Challenge your assumptions
27. Structure of the interview
Traditional interview steps Observe and co-interpret
(5-10 minutes) (1 ½ hours)
Introduce yourself Take notes
Reveal your focus Follow your focus
Be nosy
y
Promise confidentiality
Interruptions are data too
Start recording
Get an overview of their work Wrap-up
(10-15 i t )
(10 15 minutes)
Look for a starting point
Create a large interpretation of
Deal with opinions about tools your learning about
their role
Switch to contextual interview
Ask “pet” questions
Reset the rules Give tips on system use
Th k th user
Thank the
28. What to record
Record as much detail as possible
User’s words
User’s actions, step by step
Coordination with others
Indications of the culture and feelings of the user
Your shared interpretation of the meaning and intent of actions
Collect artifacts and annotate with usage
Draw the user’s physical environment and annotate with usage
29. Exercise: Conference Attendance Planning
What does it take to plan conference attendance?
Discover:
How the user planned attendance prior to arrival
• retrospective account
t ti t
How the user planned today
Plan tomorrow (if not yet done)
• Ongoing work
Look at:
A tif t
Artifacts
Annotations
App usage
pp g
30. Contextual Design fulfils Phase 0
Release
Phase 0 Development Deployment
Planning
g
Field Research
• Contextual Inquiry Visioning Concept Validation
• Work models • Low-fidelity prototyping
Determines who the customer is and what to build
Necessary precursor to Agile Development
Result: Tested and validated product structure and features
31. Example schedule of CD Agile Phase 0
Week 1 – Gather data from 8-10 users User-centered Agile
print
Compressed into a short
Sp
Phase 0
Week 2 – Consolidate data
• For constrained project
focus only!
Week 3 – Vision and storyboard
Phase 0 sprints
Sprint
using Scrum as a
process framework
Week 4 – UED and UI
Week 5 – Release planning & validation
(2-4 users)
rint
Spr
Week 6 – Validation & redesign
nt
Sprin
Development Sprint 1
32. Contextual Design enables Agile development
Release Development
Phase 0 Deployment
p y
Planning sprint | sprint | sprint | sprint | sprint
Detailed In-the-moment Quick user
design guidance feedback
Sprint planning – Detailed planning session to define tasks for the sprint
Sprint development – The coding and UX work of the sprint
Sprint review – End of sprint reflection