Selected work

Real work, built around real operations.

Two working applications show how rules, roles, deadlines, and payments become usable software.

Explore the work Discuss your project

J Will Pick 7 private web application shown during weekly use — Specific workflows. Real interfaces. Practical delivery.

Primary case studies

Two operating models. Different constraints.

The value is in the decisions beneath the interface.

Client portal and operations system

CurioSpark

CurioSpark needed one operating hub for family registration and payments, with separate staff workflows for programs, waitlists, rosters, capacity, and exceptions.

Users: Families, instructors, staff, and administrators
My role: Product structure, UX direction, workflow design, build support, and QA
Built: Responsive family portal plus role-specific staff and administration views
Technology: Responsive, database-backed web application with role-specific access

Key decision: separate family-facing registration from staff and administrative workflows so each role sees the right level of detail.

Design outcomeOne connected operating model for family registration, payments, waitlists, rosters, and administration.

View live site

J Will Pick 7 player and commissioner views from the working application — Player and commissioner views from the working application.

Private web application

J Will Pick 7 Pool

J Will needed one reliable system for weekly rules, approvals, standings, payouts, and kickoff deadlines previously spread across spreadsheets and messages.

Users: Players, commissioner, and administrators
My role: UX direction, application logic, administrative flow, build support, and QA
Built: Registration, weekly picks, kickoff locks, standings, payouts, and commissioner controls
Technology: Responsive private web application with rules and financial administration

Key decision: use the first game kickoff as the weekly lock, keep other players’ picks hidden before kickoff, then reveal them after the deadline.

Design outcomeOne source of truth for weekly picks, locks, standings, payouts, and commissioner decisions.

View live sample

Behind the build

The work behind reliable delivery.

The interface is the visible layer. These samples show the decisions and documentation that make delivery dependable.

01Data & Integration MappingField mapping, transformation rules, import prep, and validation notes.02Reporting & API PlanningAccess assumptions, connection planning, reporting patterns, and handoff notes.03Automation RunbookDry runs, execution, reconciliation, logging, and exception handling.04Validation & ReadinessUAT-style checks, issue tracking, launch review, and go or no-go decisions.05Technical DocumentationSetup steps, operating procedures, workshop notes, and support handoff.06Scope & Launch PacketDeliverables, assumptions, acceptance criteria, change control, and launch checks.

Download all six samples in one packet.

Download sample packet

Discuss your project

Bring the rules, exceptions, and constraints.

A polished brief is not required.

Discuss your project