Skip to content

[Feedback Work Item] Align README and UI naming for tracker ("launch tracker" vs "delivery tracker") #328

Description

@github-actions

Problem Statement

The README and product UI use different names for the same feature: docs call it "launch tracker" while the UI calls it "delivery tracker". This naming mismatch causes brief confusion for new users and reduces perceived polish.

User Impact

Who: New users and documentation readers following setup instructions.
How often: Occasional (observed in at least one Discord report).
Severity: Low — causes short-lived confusion ("confused for like 30 seconds").

PM Interpretation

The PM (user chrizbo) ran /create-work-item to convert this triaged feedback into a work item. No additional written rationale was provided by the PM in comments; rely on the triage note which suggested a low-priority, docs/ops fix (P3, Weak Fit to strategy).

Customer Terminology

  • "launch tracker" — as used in README (customer quote preserved, identity redacted)
  • "delivery tracker" — as shown in the UI

Non-Goals

  • This work item does not attempt to change broader product naming conventions or marketing copy beyond the README/UI text for this feature. It does not pick a canonical name without a PM/product decision.

Acceptance Criteria

  • A short, recorded decision exists choosing the canonical term (either "launch tracker" or "delivery tracker").
  • The chosen term is used consistently in the README and in the UI text that currently shows the other term.
  • The original feedback issue (#319) is linked from the implementation PR or commit message and left open as evidence.

Product Constraints

  • Strategy tradeoff to consider: #3 (Transparency by default) — prefer clarity and discoverability even if the change is small.

Source Evidence

  • Feedback: #319 — README says "launch tracker" but UI says "delivery tracker" (Discord message captured in the issue; identity redacted).

Test / Verification Notes

  • Confirm the README and the UI both show the chosen term in the same wording.
  • Confirm a PM comment or PR description documents the chosen canonical term and why it was chosen.
  • Verify the implementation references issue #319 in the PR/commit.

Open Questions

Generated by Feedback Work Item Converter for #319 · codex · gpt50mini · 2.02 AIC · ⌖ 0.648 AIC · ⊞ 17.1K · ◷
Comment /create-work-item to run again

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-readyClean, scoped work item ready for an engineering or agent owner

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions