NaoweeHead of Product
Naowee — Sports Sector Platform
Digitizing how Colombia runs its sport: 130+ screens across 8 modules, designed and built with AI.
The product
A coordinator clears an overdue filing. The picker flags who's overloaded; the counters recompute in place, 6 pending to 5.
- / Role
- Head of Product
- / Duration
- Ongoing
- / Team
- Product, design & engineering
- / Year
- Jan 2026 — Now
The impact
One platform now stands in for a stack of disconnected tools, prototyped in code with AI.
Context
Colombia's sports sector ran on paper, spreadsheets and siloed systems. As Head of Product I set the direction and build, in code, the prototypes that define the platform: one design system, AI in the loop.
What I did
- 01
One design system — 38+ shared components and one step-by-step form pattern keep every screen consistent.
- 02
The sector's real hierarchy — committees → federations → leagues → clubs → athletes, modeled with cascading approval.
- 03
Prototypes, not specs — built with Claude Code, Cursor and Gemini; analysts sign off on the running product.
In detail

01Each document checked against the article it answers. 
02The country's sports venues, department by department. 
03A single venue: photos, documents and coordinates. 
04Investment calls, applications and stages in one panel. 
05One of eight technical areas, reviewed article by article.
How it happened
- 01
The sector ran on files
All 30 procedures moved through Word, email and a document manager, GESDOC. Before drawing a screen I mapped 45+ states and 15 roles: the states were the product.
- 02
Athletes and events, modeled by building them
An approved athlete inherits the club's league and federation. Events, results and rankings enter by .xlsx template across 83 sports: valid rows load, failures come back by row number.
- 03
The prototype is what gets signed
Each module starts as a clickable prototype with real roles and states, walked story by story in a guided tour. The design system is the contract; the demo is how we sign it.
Key decisions
One system, or eight dialects
Eight modules, eight deadlines, eight temptations to fork. The rule: no custom component; extend the 38+ shared ones. Anything off on review is a bug, not a preference.
The demo is the requirement, not the document
Specs get read differently by everyone. A running prototype surfaces disagreement while it's cheap and hands engineering a resolved target. It works because I build it myself.
Hierarchy is the product, not a lookup table
A flat athlete table would have shipped months earlier. But approvals cascade from the Ministry down to the club, and medals by league only mean something if the links are real.
- Product Strategy
- Design Systems
- Claude Code
- Cursor
- Gemini
- Generative UI
Head of Product at Naowee: I set direction across the business modules and build the prototypes that define them, alongside business analysts, a designer I lead, and engineering teams.