Assignment 3 - CUJ Runthrough + Demo

Your third assignment requires you to utilize another tool, documenting the process and your learnings.

Critical User Journeys (CUJs) are essential to document and test. While product documentation typically outlines the ideal path for using a product, the actual user experience often differs. This variation depends on factors such as the user’s persona, their familiarity with the platform, and any integration work they may be undertaking.

For this assignment, you will define a specific goal you aimed to achieve with [TODO] and thoroughly document the end-to-end process of setting it up. Subsequently, you will summarize both the successes and areas for improvement, offering recommendations on how the experience could be enhanced. Finally, you will present these findings in a written document and a brief three-minute class presentation.

• Requirements
  • CUJ Document
  • Ex. Format
  • In Class Presentation
    • Format
• Submission
• Questions or Concerns?
• Rubric
  • 🔍 CUJ Document Rubric - 80 Points
  • 🎤 CUJ Presentation Rubric - 20 Points
  • Rating Scale

Requirements

CUJ Document

1. Assignment Information:

• Assignment Name

2. Group Details:

• Group Name
• Student Names and Numbers
• Date

3. TL;DR (Summary of Findings - max 65 words):

This section should concisely answer:

• What is it?
• What does it do?
• Why does it matter?

4. User Goal (max 2 sentences):

Clearly state the objective you aim to achieve as the user. This should appear at the beginning of the document.

5. Detailed Summary of Findings (approx. 600 words):

• User Persona: Describe the persona who performed the Customer User Journey (CUJ).
  • Example: What is your expertise level? Have you used that platform before?
• Tools Used: List all tools utilized.
• Highlights and Lowlights Table: Present a table categorizing experiences as Great, Moderate, or Severe. Note: This is not an exact science; choose the option that best reflects your experience.
• Product Recommendations: Suggest improvements for the product.
• Recommendations for Future Users: Provide advice for the next user attempting this task.

6. CUJ Overview Table:

• Refer to the example provided.

7. End-to-End User Journey Documentation:

Create a three-column table (Step, Notes, Screenshot).

• For each step:
  • Time and Context Switches: Record the duration of the step and any context switches.
    • Example: Switching from the SOME_PRODUCT Console to documentation.
  • Concise Notes: Document your actions and their rationale. If you encounter issues or unclear elements, explain your struggles.
  • Screenshot: Include a screenshot of what you, as the user, see.
• Table Header: At the top of the table, indicate the “Total Time” and “Total Switches.”
• Task Summary: Summarize the various tasks involved in the end-to-end journey.

Ex. Format

CUJ Document

A3 CUJ Runthrough + Demo

Team Constellations

Group Members:

• John Doe – 999678463
• Jane Smith – 999123456
• …

Submission Date: 2025/10/02

⚡ TL;DR (Max 65 words)

Briefly summarize what you did, what happened, and why it matters.

🎯 Goal

As a [user persona], I want to [goal/task], so that I can [value or outcome].

🧰 Tools Used

List any tools, platforms, or services you used during the task:

• SOME_PRODUCT Console
• Google Search
• SOME_PRODUCT Documentation
• Postman
• VS Code

🧑‍💻 Persona Description

• Role / Background:
  e.g., 3rd-year software engineering student
• Experience Level:
  e.g., Familiar with APIs, first time using SOME_PRODUCT
• Familiarity with Platform:
  e.g., No prior experience with SOME_PRODUCT Apps

📘 Summary of Findings (Approx. 600 words)

Describe your overall experience. What worked? What didn’t?
Reflect on usability, clarity of steps, platform performance, and task completion.
Include pain points, moments of confusion, and key insights. This section should read like a story of your experience.

💡 Recommendations

For SOME_PRODUCT (Product Improvements):

• Improve error messages during app deployment
• Add clear examples for FAST API and endpoint exposure
• Simplify access to app-related documentation

For Future Users:

• Read the API deployment guide before starting
• Test locally before using SOME_PRODUCT console
• Expect to context switch — have docs and tools open in parallel

Highlights & Lowlights Table

CUJ Overview Table

Total Time: 2.5 hours
Total Context Switches: 8

Full CUJ Table (Step-by-Step Documentation)

In Class Presentation

Format

• Duration: 3 minutes for the presentation, followed by a 2-minute Q\&A session.
• Presenters: One person will present, but the entire group can participate in answering questions.
• Materials: There is no need for a slide deck. Please present the document you created and provide a brief demonstration of your final product.

Submission

You must create a release on your repo. This will give us a snapshot in time and allow us to grade it. See release body criteria and example below. Assignments without a coherent release body that follow the instructions in this assignment will be rejected and marked 1 day late.

One member of your team must submit a link to the release in Quercus for ‘A3 - CUJ’. Only one team member needs to do this.

Assignments are always due at 11:59:59pm Eastern Time.

Questions or Concerns?

• I don’t like part of this assignment
  • File an issue on this repo
• I need to clarify something about this assignment
  • File an issue on this repo
• I need to clarify a question or ask something in private
  • Email the course instructor or email the professor via the email on the homepage / README

Rubric

🔍 CUJ Document Rubric - 80 Points

🎤 CUJ Presentation Rubric - 20 Points

Rating Scale

This scale is used for each line of the rubric above.