Case study · Personal Project · September 2025 - Present

Chicago Sports Dashboard: From a City-Wide Concept to a Bears-First System

Designed and built a Chicago sports dashboard concept that began as a multi-team selector experience, then intentionally narrowed to a Bears-first dashboard to establish reusable patterns, validate data structures, and reduce scope risk.

0 stable baseline
Dashboard Template
System foundation
0Live, cached, error
Resilient States
Reliability
0Card-based patterns
Reusable Components
Scalability
Role
UX Designer & Frontend Developer
Team
Solo Project
Timeline
September 2025 - Present
Stack
React · Next.js 15 · TypeScript

01 — Problem

The Challenge

The initial goal was to reflect the Chicago sports scene with a unified dashboard experience. The first designs focused on interaction and presentation, but real sports data is inconsistent across leagues and teams. That mismatch made the earliest city-wide dashboard feel incomplete and unstable.

  • A consistent UI template breaks down when each sport exposes different stats and structures
  • Early design prioritized slick selection behavior over long-term data readability
  • Cross-team scope introduced complexity before a stable component and data model existed
  • The season overview cards felt too minimal to explain context or guide users through the page
  • Desktop layouts felt underutilized and mobile layouts felt overly spacious without added meaning

02 — Research

Why I Started the Dashboard Concept

The original goal was to build something that reflects the Chicago sports scene. It started as a drawer-based selector concept, but quickly turned into a bigger question: once a user picks a team, what is the best way to show meaningful season context immediately?

The Early Interaction Idea

The drawer was the initial design hook. It felt slick and lightweight, and I wanted to see how far I could push the UI with CSS-first thinking.

The Idea Expanded

As soon as I considered what should be inside the experience after selecting a team, it became a dashboard problem, not just a selection problem.

What Felt Wrong or Incomplete

I originally wanted a dashboard where all teams looked similar and followed the same template. Once I started mapping real data across teams and leagues, the idea broke down.

Inconsistent Data Across Teams

The information available was different for each team and sport, and I could not keep the experience consistent without either hiding important stats or forcing irrelevant ones.

Scope Was Too Big Too Early

Trying to solve all Chicago teams at once made the project feel unbounded and made it hard to lock in any stable template decisions.

03 — Approach

The dashboard evolved through implementation-driven design. Each iteration revealed data constraints, layout issues, and opportunities to improve narrative flow.

  1. 01

    City-Wide Concept and Team Selection

    Started with a Chicago-first dashboard entry experience focused on team selection. Explored a CSS-forward approach for interaction polish.

  2. 02

    Reality Check: Data Consistency Breaks

    Mapped real sports data across teams and leagues. Discovered structural inconsistencies that prevented a single shared template from working cleanly.

  3. 03

    Scope Pivot: Bears-First Dashboard

    Reduced scope intentionally to create one complete dashboard and use it as the foundation for reusable patterns.

  4. 04

    Season Overview Baseline

    Established the first stable UI pattern with Season Overview cards. Record and win metrics created a clear entry point.

  5. 05

    Story and Flow Improvements

    Focused on density, layout flow, and making stats more contextual. Began adding sections that progress from overview into deeper team understanding.

Before / After

Bears-First Dashboard
Early Concept
Early ConceptBears-First Dashboard
Early ConceptBears-First Dashboard

04 — Outcome

This is a personal build, so results are measured by stability, clarity, and system maturity rather than business KPIs. The main outcome is a foundation that can scale without collapsing under inconsistent data.

0 stable baseline
Dashboard Template
System foundation
0Live, cached, error
Resilient States
Reliability
0Card-based patterns
Reusable Components
Scalability
0Strict TypeScript
Type Safety
Stability

Decision log

Different sports expose different stats and structures. Achieving consistency requires normalization, not visual sameness.