Task Analysis

158df2ad2d800432b505bb1b0e6308c8?s=47 Ghis
June 20, 2018

Task Analysis

The process of learning to identify user tasks.

158df2ad2d800432b505bb1b0e6308c8?s=128

Ghis

June 20, 2018
Tweet

Transcript

  1. 2.

    Task analysis is the process of learning about users by

    identifying the route they take using the product and understanding in detail how they perform their tasks to achieve their intended goals PREPARED BY // GHIS
  2. 3.

    How a task is accomplished, including a detailed description of

    both manual and mental activities involved in or required to perform a task – Task allocation – Element durations – Task frequency – Task complexity – Environmental conditions PREPARED BY // GHIS
  3. 4.

    The purpose of Task Analysis ▪ What your user’s goals

    are? ▪ What user’s do to achieve their goals? ▪ What experiences user brings to the task ▪ How users are influenced by their environment ▪ How previous knowledge and experience effect how they think about their task PREPARED BY // GHIS
  4. 5.

    When to use Task Analysis? ▪ Requirements gathers (Scoping) ▪

    Developing content strategy and site structure ▪ Wireframing and prototyping ▪ Performing usability testing PREPARED BY // GHIS
  5. 6.

    Before you start Task Analysis ▪ Trigger ▪ Desired Outcome

    ▪ Base Knowledge ▪ Required Knowledge ▪ Artefacts PREPARED BY // GHIS
  6. 7.

    Task Analysis techniques ▪ Hierarchical Task Analysis: Focused on decomposing

    a high-level task subtasks ▪ Cognitive Task Analysis: Focused on understanding tasks that requires decision- making, problem-solving, memory, attention and judgement PREPARED BY // GHIS
  7. 8.
  8. 9.
  9. 10.

    Fill in water in kettle Add in tea bag Pour

    in hot water Add milk Add sugar Open fridge Pour in cup
  10. 11.

    Cognitive Task Analysis ▪ User Group – Actions performed by

    user – What does user do? ▪ System group – Actions carried out by the system – What does user see? PREPARED BY // GHIS
  11. 12.

    ▪ Question group Unresolved questions associated with the task ▪

    Object | Information group Requirements of the user to carry out an action PREPARED BY // GHIS
  12. 14.
  13. 15.

    Task Optimisation ▪ Eliminate unnecessary steps ▪ Automate repeated steps

    ▪ Optimise the process to help users achieve their goal at much higher speed PREPARED BY // GHIS
  14. 17.

    User Story ▪ As a user, I want to send

    a text message to hospital’s system PREPARED BY // GHIS
  15. 18.

    Task Flow 1. Open the messaging application on mobile phone.

    2. Enter the hospital system’s special number. 3. Move to the text input field. 4. Type the words “next patient”. 5. Check the spelling (because it needs to be precise for the system to accept it). 6. Hit the “send” button. 7. Exit the messaging application. PREPARED BY // GHIS
  16. 19.
  17. 20.
  18. 21.
  19. 22.
  20. 24.
  21. 25.
  22. 26.

    User Story As a user I want to order Japanese

    Ramen with a side boiled egg to my current address in less than 30mins PREPARED BY // GHIS
  23. 27.

    ▪ Trigger: ▪ Desired outcome: ▪ Base knowledge: ▪ Required

    knowledge: ▪ Artefacts: PREPARED BY // GHIS
  24. 28.

    ▪ What prompts users to start their task? ▪ How

    users will know when the task is complete? ▪ What will the users be expected to know when starting the task? ▪ What the users actually need to know in order to complete the task? ▪ What tools or information do the users utilize during the course of the task? PREPARED BY // GHIS
  25. 29.

    ▪ Trigger: Order Japanese ramen ▪ Desired outcome: Receive Ramen

    within 30mins ▪ Base knowledge: Japanese dishes ▪ Required knowledge: GrabFood app on the phone ▪ Artefacts: Smartphone, Internet connection PREPARED BY // GHIS
  26. 30.

    Summary ▪ Task analysis must be backed by solid user

    research and domain knowledge while focusing on what user’s actual needs are ▪ Task analysis is not a one-off process. You can repeat it since Design Thinking is an iterative process that will eventually lead you back to the “define” stage at some point PREPARED BY // GHIS
  27. 31.

    Resources Marine, L. (2014). Task Analysis: The Key UX Design

    Step Everyone Skips https://searchenginewatch.com/sew/how- to/2336547/task-analysis-the-key-ux-design-step- everyone-skips Min, L. (2014) experience mapping vs. Task analysis https://www.akendi.com/blog/experience-mapping-vs- task-analysis/
  28. 32.