What Rally HQ should be.
A working prototype of the customer experience Rally HQ would have shipped if it had been designed-first against the personas, market, and operational reality of running a real tournament. Each page shows the proposed surface side-by-side with what's shipped today.
Generated synthetically. No live user interviews. Research synthesized from codebase, sibling-project signals (Volley Rx, Let's Pepper), and competitive landscape. Personas and interview quotes are hypotheses, not evidence.
Landing
Problem-led hero, equal-weight dual CTA, free-mode messaging, sibling-validated typography split.
MarketingPricing
Free-during-launch single card with the four-tier comparison collapsed behind disclosure.
SpectatorTournament page
The primary destination. Per-tournament accent. LIVE pulse. Follow-team CTA. The 80% of traffic page.
OrganizerTournament-day mode
Today's matches, pending registrations, one-tap actions, action-overlay primitive. Setup UI hidden.
OrganizerCreate tournament
Opinionated defaults. Bracket preview live as the organizer fills the form.
CaptainCaptain dashboard
Role-aware. Next match focus. One-tap roster. Account-claim CTA at end.
ScorekeeperScorekeeper interface
One-handed. Big undo. Offline-resilient. Designed for glare.
Post-eventPost-event recap
Auto-generated share card. Champion named. Next-event CTA. The viral surface that doesn't exist today.
SpectatorFollow team
One-tap follow. PWA push for next match + score updates. No signup required.
OrganizerBilling & account
Display-primary. Free-mode states. Flip-back-ready surface.
OrganizerLeagues & series
Series-as-first-class. Cross-event standings. The retention multiplier currently gated.
PartnerPartner / API
Self-serve API key. Webhook for tournament-end. Drops the "partner program" framing.
How to read this
- Each page shows the proposed customer experience.
- The bottom-left "◀ Shipped" drawer shows what's in Rally HQ today (with source-file links).
- The bottom-right "Strategy ▶" drawer explains the design decision, cites the research finding, and names the open question for primary research.
- The toggle at the top of each page switches between "Proposed", "Side-by-side", and "Shipped" — the gap is visual.
Companion documents
Competitive teardown + cross-industry patterns + synthetic persona interviews
Seven rules the prototype obeys
Synthesized UI/UX, IA, navigation, layout strategy
Phased path from shipped → blueprint
Per-page proposed vs shipped delta (companion to UI toggle)