Task/Scenario Evaluation #1 :Introduction to UI Design (User Interface Design Specialization) Answers 2026
✅ Question 1
Does the response contain a sensible retail customer task?
-
✅ Yes
-
❌ No
Explanation:
The task aligns with something a retail customer would reasonably want to do.
✅ Question 2
Clarity of the task description
-
❌ Completely
-
✅ Mostly. The task has some areas that are less clear, but most shoppers could figure it out.
-
❌ Not very well
-
❌ No description provided
Explanation:
The task is understandable, though it could be tightened slightly.
✅ Question 3
Specific and concrete task?
-
❌ Yes, well done!
-
✅ Mostly. A few minor issues, but generally concrete.
-
❌ Parts too vague
-
❌ No description / too abstract
Explanation:
The task is concrete enough to evaluate, with only minor vagueness.
✅ Question 4
Clear statement of who is doing the task?
-
✅ Yes, who is clear.
-
❌ Who isn’t clear, but inferable
-
❌ Who isn’t specified at all
Explanation:
The scenario provides enough user context to judge task suitability.
✅ Question 5
Is this a complete job (not just a sub-step)?
-
✅ Yes, the task makes sense as a reasonably complete thing someone might want to do.
-
❌ More of a sub-task
-
❌ No meaningful task
Explanation:
The task stands on its own as a full user goal.
✅ Question 6
Is this task central and important to shopping-site design?
-
✅ Yes, this is a core, important task.
-
❌ Mostly
-
❌ Not really
-
❌ No meaningful task
Explanation:
Poor design of this task would significantly harm the user experience.
✅ Question 7
Any interface-dependent “how” instructions?
-
✅ No, there’s nothing interface-dependent. It is a pure task.
-
❌ Minor “how” elements
-
❌ Too specific about “how”
-
❌ No meaningful task
Explanation:
The task focuses on what the user wants to accomplish, not how.
✅ Question 8
Do scenario steps match the task?
-
✅ Yes.
-
❌ Not quite
-
❌ Steps don’t match
-
❌ No meaningful scenario
Explanation:
The scenario actions are aligned with the stated task.
✅ Question 9
Are steps understandable to a typical user?
-
✅ Yes.
-
❌ Not quite
-
❌ No
-
❌ No meaningful scenario
Explanation:
Steps are written in user-friendly, understandable terms.
✅ Question 10
Does the scenario include “what” vs just “how”?
-
❌ Just “how” steps
-
❌ Some “what” mixed in
-
✅ As much “what” as “how,” or maybe more.
-
❌ No meaningful scenario
Explanation:
Good scenarios emphasize intent (“what”), not just mechanics.
✅ Question 11
Is the action sequence reasonably correct?
-
✅ Yes.
-
❌ Mostly
-
❌ I don’t think so
-
❌ No meaningful scenario
Explanation:
The sequence follows a logical, realistic flow.
🧾 Summary Table
| Q# | Best Evaluation Choice | Key Skill Practiced |
|---|---|---|
| 1 | Yes | Task relevance |
| 2 | Mostly clear | Task clarity |
| 3 | Mostly concrete | Specificity |
| 4 | Who is clear | User context |
| 5 | Complete task | Task completeness |
| 6 | Core task | Design importance |
| 7 | No “how” bias | Task vs implementation |
| 8 | Steps match task | Scenario alignment |
| 9 | Understandable | User language |
| 10 | Balanced “what/how” | Good scenario writing |
| 11 | Correct sequence | Logical flow |