codeforpdx / codeforpdx/tenantfirstaid

UX Research for UX Re-Design

Open
#240 1 comment 0 reactions 1 assignee View on GitHub

@ValeriyaMetla is already working on this.

Since Dec 10, 2025.

UX Research
Dominant language
Python
Stars
13
Forks
21
Avg merge
6d 7h
Merged PRs (30d)
3

Description

OVERVIEW

This issue will track the UX research work supporting the TFA UX re-design. The objective is to gather evidence and best practices to guide improvements across the landing page, user flow/entry experience, information architecture, and the Chat + Letter features. This umbrella issue will consolidate multiple research methods including competitive analysis, heuristic evaluation, feature parity/difference mapping, and synthesis into actionable recommendations. Outputs will be shared with the team and translated into prioritised action items within the linked UX redesign issues.

ACTION ITEMS

  • Confirm research scope and goals
  • Define the research questions we need to answer for the redesign (landing clarity, trust/privacy, flow to Chat vs Letter, letter workflow, export experience).
  • Competitive analysis
    • Identify and categorize competitors (6–12 relevant tools/resources)
    • Identify key features for TFA and competitors
    • Identify the points of parity vs difference b/w TFA and the competitor tools
    • Note how it informs messaging and our UX priorities
  • Conduct Heuristic evaluation for TFA
    • Evaluate our product against Nielsen’s 10 heuristics, Trust & Safety, and Accessibility best practices in UX design
    • Note major usability gaps and top opportunities
  • Conduct SWOT analysis for our product and top competitors to support strategy and positioning.
  • Synthesize findings and create a short summary of key insights and recommended changes. Map each insight to one or more of the 5 redesign issues: layout, navigation, IA, user flow/entry, and key features.
  • Translate findings into MoSCoW priorities.

LINKED ISSUES/DOCUMENTS

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.