Team Builder / Section 04 of 06
Process
Design Philosophies
- Design for real-world complexity
- Team formation is inherently messy. We prioritized flexibility, partial progress, and reversibility over rigid, idealized workflows.
- Reduce cognitive load at critical moments
- High-stakes actions — invites, role assignment, finalization — were designed to be clear, focused, and time-efficient through progressive disclosure.
- Favor adaptable systems over one-off flows
- Rather than optimize for a single club model, we designed shared primitives that could support multiple organizational structures and evolve over time.
- Make system state explicit
- Draft vs. saved states, permissions, and visibility were treated as first-class concerns to reduce uncertainty and support confident action.
- Build trust at business/user intersections
- Monetization-adjacent moments were designed to feel predictable and fair, reinforcing user confidence while supporting completion and revenue outcomes.
- Design with delivery in mind
- Close collaboration with engineering ensured solutions were feasible, maintainable, and scalable — without compromising core UX intent.
Defining the key mental models. Through discovery and ongoing feedback, it became clear that admins approach roster building with different mental models — often within the same session:
- "I'm just rearranging players on teams."
- "I'm assigning players but will invite them later."
- "I'm finalizing rosters and sending offers now."
The system, however, must distinguish between moves (same-program changes), invites (cross-program actions), and draft assignments vs. committed actions. A major design goal was to make the system's interpretation of admin intent visible and predictable — without forcing admins to think in system terms.
Defining the MVP. I collaborated with my product manager and engineering manager to phase the rollout:
Recreational League Roster Formation
- Launch directly from the program dashboard
- Drag-and-drop players between multiple teams
- View roster capacities and duplicate warnings inline
- Filter by custom form responses
Club-Level Team Management
- Create new teams from scratch
- Import players from past seasons
- Invite players to join new teams
- Autofill rosters using AI suggestions and bulk messaging
Key Design Decisions & Tradeoffs
Auto-detect "Move" vs. "Invite"
WhyAdmins should not have to decide the technical difference between moving a registration and inviting a player.
TradeoffRequired extremely clear status indicators and review steps so admins understood the consequences of each assignment.
Draft-first, irreversible-last
WhyRoster formation is iterative, and premature execution would cause confusion and player churn.
TradeoffCreated complexity in how draft states interact with the legacy Invite-to-Join tool, which does not support drafts.
Review actions in a slide-out, not inline
WhyInline warnings would overwhelm the primary task and interrupt flow.
TradeoffHad to carefully communicate that some actions (like revoking an invite) still have immediate consequences even from the review surface.
RUN DEMO: Review moves, invitations and sent invites before finalizing
No inline undo in the review surface
WhyUndoing actions at the review stage risks obscuring the true system state, especially when registrations or invitations are involved.
TradeoffSlightly higher friction, but significantly reduced risk of silent errors. Admins must correct mistakes directly in Team Builder.
Invitation Lifecycle & Guardrails. To reduce ambiguity, players in Team Builder clearly surface one of several states:
- Invite Needed
- Assigned to a team but not yet invited
- Pending
- Invitation sent, awaiting response
- Registered
- Invitation accepted and registration completed
RUN DEMO: See every invitation state on one board
- Automatic invalidation of invitations when players are reassigned
- Visual warnings when actions will revoke invites or cancel registrations
- Clear separation between draft assignments and sent invitations
This approach prioritizes transparency over cleverness — ensuring admins understand what the system will do before it happens.
Collaboration & Implementation. We maintained a cadence of biweekly feedback sessions tailored to different audiences: design, engineering, customer success, and leadership. A key internal debate emerged around the default state of Team Builder: should users start with an empty interface or a populated set of teams?
I facilitated a journey mapping exercise that revealed admins typically created teams before entering Team Builder. This led to the final decision: display the ten most recently created teams by default, giving Rec admin users immediate context without overwhelming them. Club programs only ever created 3–5 teams, so they'd only see what they needed.
Engineering collaboration was close and constant. We conducted "boxing" sessions to create detailed mappings of design elements to backend APIs, annotating every prototype for handoff. Auto-save wasn't feasible for MVP, so I introduced a destructive modal to prevent accidental data loss when navigating away — and proposed auto-save as a fast-follow enhancement.