Loading
Imagem principal do projeto Maestria

Product Design & Full-Stack

Maestria

Year

2026

Role

Product Designer & Full-Stack

Duration

MVP + B2B module · continuous iteration

Team

Solo

Tools

Next.js · Prisma · Stripe · GSAP

View Project

The problem

Brazilian designers can't answer 'where am I and what's missing for the next level' — and managers calibrate seniority by gut feeling, with loose spreadsheets.

My role

Product Designer & Full-Stack, solo: market research, PRD, design system, code, infra and monetization, from zero to deploy.

The outcome

Full SaaS live, solo, from PRD to deploy: ~88-skill self-assessment, radar, self × manager gap, per-person development plan and Stripe subscriptions.

Overview

Portuguese-first SaaS for assessing and developing UX/Product Design competencies. You assess yourself against a framework of 14 competencies and ~88 skills on the 6-level Dreyfus scale, and get a radar, a seniority estimate on the Brazilian ladder and a 70-20-10 development plan. The same framework serves managers: self × manager gap, aggregate team radar and per-person development plans.

The Problem

UX professionals in Brazil have no structured, trustworthy and affordable way to answer three questions: where am I? What's missing for the next level? And how does a manager calibrate this fairly across different people? Today this is solved with loose spreadsheets, informal self-assessments and seniority ladders that change from company to company. For the individual, the cost is a generic development plan and seniority negotiations without arguments. For the manager, it's gut-feeling decisions — unfair promotions, copy-paste development plans, turnover. The global tools attacking the problem (Uxcel, TalentGuard, Leapsome) are expensive, English-only and too generic for the Brazilian reality.

Landing: the 'living radar' draws itself and continuously morphs between Junior → Mid → Senior profiles.
Landing: the 'living radar' draws itself and continuously morphs between Junior → Mid → Senior profiles.

Research

Framework grounded in the Dreyfus model of skill acquisition (6 levels with behavioral anchors)Self-assessment bias literature (Dunning-Kruger effect) and product mitigationsCompetitive benchmark: Uxcel, TalentGuard, Leapsome, NN/g spreadsheets and community matricesBrazilian market: salaries by seniority (CAGED, Glassdoor), the Junior->Specialist ladder and BRL price sensitivity

Research surfaced two truths that shaped the product. First: self-assessment carries systematic bias — beginners overestimate, experts underestimate — so an isolated score is worth little; the antidote is a behavioral anchor at every level plus confrontation with the manager's reading. Second: the revenue engine is not the individual, it's the team — the manager who needs to calibrate seniority and run data-driven 1:1s is the one who pays. The individual is top of funnel. No competitor combines a real UX framework, Portuguese, the Brazilian ladder and BRL pricing.

Product Decisions

01
N/A is never zero

Someone who doesn't do motion can't be punished for it. 'Not applicable' is excluded from the average — it never counts as a low score.

02
Seniority is an estimate

The ladder varies across companies. The product always labels the result as an orientative suggestion — a conversation starter, not a verdict.

03
The gap is the feature

The divergence between self-assessment and the manager's reading isn't noise: it's the core calibration artifact and the main value of the team plan.

From assessment flow to radar

The mandatory toggle: radar for synthesis, per-skill heatmap for nuance — research shows the radar alone hides where to act.
The mandatory toggle: radar for synthesis, per-skill heatmap for nuance — research shows the radar alone hides where to act.

Team Mode: the revenue engine

The manager creates a team, invites by link and assesses each person with the same flow as the self-assessment. The system then confronts both readings: the self × manager gap per competency and per skill, sorted by the largest divergences — a negative divergence means the person rated themselves above the manager's reading, and that's exactly where the calibration conversation starts. The module is completed by the aggregate team radar (collective strengths and gaps) and a per-person development plan generated by the same 70-20-10 engine as the individual plan: 70% on-the-job practice, 20% social learning, 10% formal study.

Self × manager gap: two radar series and the largest divergences with numeric deltas — the antidote to Dunning-Kruger bias.
Self × manager gap: two radar series and the largest divergences with numeric deltas — the antidote to Dunning-Kruger bias.

Manager's panel

70-20-10 plan: the biggest gaps become concrete practice, mentoring and study actions.
70-20-10 plan: the biggest gaps become concrete practice, mentoring and study actions.

'Cinematic Gradient' design system

The visual language came from a study of public DESIGN.md files (Framer base): near-black canvas, charcoal surfaces separated by hairlines, compressed display typography (Space Grotesk) and a violet->magenta->orange gradient atmosphere used as a moment, never as a background. Everything is governed by a single token file that generates the CSS — zero hardcoded hex in components, enforced in CI. The 6-color level ramp carries its own semantics (warmth = developing, brand family = proficient+) and never communicates level by color alone: the mono number is always beside it. On the landing, GSAP drives continuous scrollytelling and the SVG 'living radar' morphs between seniority profiles.

The gradient atmosphere as a moment: the landing's gap card, with inner glows and two diverging series.
The gradient atmosphere as a moment: the landing's gap card, with inner glows and two diverging series.
14competencies and ~88 skills in the framework
40automated E2E checks across both phases
0hex values outside design tokens (CI-enforced)

Outcome

An end-to-end functional SaaS: authentication (Google + magic link), 14-day trial, Pro and Team subscriptions with Stripe, a versioned framework in the database, assessment with autosave and immutable snapshots, radar, heatmap, 70-20-10 plan, cross-cycle history and the full B2B module — teams by invite link, manager assessment, gap, aggregate radar and per-person plans. The project also became an exercise in disciplined engineering: business rules locked by E2E tests (N/A excluded from averages, post-completion immutability, team isolation) and a wired design system where editing a token propagates to both product and Storybook.