PCSC2: Defining & Designing Technology for People
Download as PPT, PDF1 like646 views
The document discusses the importance of understanding customer needs in designing technology, emphasizing activity-centered design to analyze customer interactions. It outlines the hierarchical structure of activities, tasks, and operations to comprehend user goals and behaviors, advocating for prototype development and usability evaluations to validate design effectiveness. Ultimately, it highlights the necessity of creating useful, usable, and desirable products that encourage user engagement and satisfaction.
PCSC2: Defining & Designing Technology for People
- 1. Defining and Designing Technology for People Sean Van Tyne Product Camp So Cal 2010
- 2. Defining and Designing Technology for People The Pragmatic Marketer, Volume 8, Issue 2, 2010
- 3. We can only design solutions for people when we have a deep, detailed knowledge of those people’s needs. We build upon our prior knowledge and experience to design and develop better products. Each new generation of solutions improve based on market and customer feedback.
- 4. Understand customer activities with Activity-Centered Design Dr. Donald Norman has suggested a hierarchical structure of activities, tasks, actions, and operation to better understand customers’ interactions with solutions: • Activities are comprised of tasks • Tasks are comprised of actions • Actions are made up of operations
- 5. Understanding the tasks of the activities helps understand the customers’ intentions. Focus on activities our customers perform rather than their requests. Systems that support the activities support the people who perform them. Understand the activity, and the solution is understandable.
- 7. Group your customers and users by similar roles based on their goals and the type of activities they perform. A role is a set of connected behaviors. Usually people with the same role have similar job- related responsibilities, duties, and goals.
- 8. Review market segmentation demographic data and interview stakeholders, customers, and users, in order to gain insight into their goals. A goal is a result one is attempting to achieve. Observe the customers and users using the solution in their environment and develop diagrams of the various customers’ workflows and note where the goals and underlining activities are similar and different.
- 9. Once the various roles and goals are understood, think through the scenarios needed to realize the goals. Scenarios describe a user’s interaction with the solution.
- 10. Determine what activities are needed to complete the goals by roles. An activity is a specific behavior or grouping of tasks. Develop a diagram that illustrates the activities.An activity diagram shows activities and actions to describe workflows.
- 11. Activity diagrams divide the activities into tasks needed to complete the user’s objective. A task is a unit of work. The task itself may be a single step in the process or multiple steps or sub-tasks that make up the task. Tasks analysis looks at tasks as outcomes that have actions.
- 12. Actions usually result in some form of commitment. For example, selecting the “OK” button in a software interface or pressing a button on a device that results in a desired outcome. And an operation is the outcome of the user’s action. The operation is the program initiated and yields the results of the user’s intended goal.
- 13. Develops prototypes to elicit customer feedback to validate the solutions activities, tasks, and actions meet their needs. Define the layout and placement of fundamental design elements in the interface design that visually represent the activities, tasks, and actions. Validate the general workflow navigation, information grouping, information hierarchy, terminology, labels, and general interactions in terms of activities and tasks that need to be complete to meet the customers’ goals.
- 14. Test that your visual design — color scheme, fonts, iconography, branding, and all graphic elements - support the company’s brand and enhance the ease of task completion and efficiency. Define the behavior of how your customers and users interact with your solution. Focus on the tasks that need to be completed and the actions associated with the task and underline operation. Focused on making products more useful, usable, and desirable. Work with customers and users to conduct reviews of prototypes for feedback. Conduct usability evaluations to measure effectiveness, efficiency, and satisfaction. Be sure to measure task completion, time and task, and the emotional response to your solution.