03
Cohort 03 · Opens May 1520 seats · Rolling acceptance

You can build a design system.
Nobody uses it.

The Design Systems Operator is a 6-week cohort for product designers who want to ship a system their engineers actually adopt — and the staff title to prove it.

6 WEEKS€790 EARLY-BIRD20 SEATS
MF
Taught by Maren Fischer · 12 years in product design · ex-staff designer at a top European fintech · Shipped 4 systems across 6 teams.
Here's what nobody tells you

Most design systems fail. Not because the tokens are wrong — because nobody uses them.

I've watched 6 design systems die in 12 years. Not one died from bad typography choices. They all died the same way:

  • 01 /Nobody on the team actually uses what you shipped.
  • 02 /Engineers rebuild your components their way, in their sprint.
  • 03 /Leadership defunds the system in the next quarterly planning cycle.
  • 04 /You get credit for nothing, even though you did 300 hours of work.

The fix isn't better Figma files. It's operating skill — the political, organizational, and measurement work that separates senior designers from staff designers. That's what I teach here.

By the end of 6 weeks

You'll have one working system your engineers adopt — and the case to earn the staff title.

Week 3
A working component library in your actual production codebase. Not a demo Figma file.
Week 4
A contribution model that makes engineers want to use it — not route around it.
Week 5
3 adoption metrics on a public dashboard your CTO checks weekly.
Week 6
A political win-doc you can show in your next performance review.
Ongoing
The title-shift strategy from "senior designer" to "design systems lead."
For life
A cohort of 20 design-systems operators across Europe and the US as peers.
6-week curriculum

Not Figma theory. Operating playbook.

Every week ends with a deliverable inside your actual company — not a homework exercise.

WEEK 01
Audit — Map your current chaos.
Interview 5 engineers. Catalogue inconsistencies. Find the real pain — not the pain you assume exists. You'll finish the week with a 1-page audit your team can't argue with.
WEEK 02
Scope — The 12 components that unblock 80% of work.
The trap every system falls into: build all 60 components. We scope to the 12 that matter. Everything else is year two — or never.
WEEK 03
Build — Tokens, primitives, composition.
In code, not just Figma. Paired with an engineer from your team (non-negotiable). You'll ship component #1 into production this week.
WEEK 04
Adoption — The political work.
Contribution rituals. PR review patterns. Office hours. How to get your tech lead to defend the system in standup — without you being in the room.
WEEK 05
Measure — 3 metrics your CTO will defend in a budget cut.
Component reuse rate. Time-to-ship for new features. Design-engineering cycle time. You'll build the dashboard live in cohort.
WEEK 06
Ship + position — Internal launch and win-doc.
Internal launch deck. Win-doc for your next performance review. Your title-shift strategy mapped step-by-step.
Be honest with yourself

This cohort isn't for everyone.

✓This is for you if
  • You've been a product designer for 3+ years.
  • You've tried to start a design system and felt it die on the vine.
  • You want the systems lead title and you're done waiting.
  • You have at least one engineer you can pair with.
  • You can commit 6–8 hours a week for 6 weeks.
×This is not for you if
  • You're a junior designer looking for a portfolio piece.
  • You're a design manager wanting to delegate this.
  • You think "design system" means a Figma library.
  • You can't find a single engineer to pair with.
  • You want theory, not a shipped deliverable.
From past cohorts

Three alumni became staff / systems leads within 90 days.

"I'd tried and failed to start a design system twice. Maren's week-4 adoption framework is the reason it stuck this time. Promoted to staff 60 days after the cohort."
EB
Elena B.Now Design Systems Lead · Fintech scale-up (DE)
"The political work content alone is worth the price. Nobody teaches this. I've since tripled my team's adoption rate and finally got the headcount I've been asking for."
TK
Theo K.Staff Product Designer · HealthTech (UK)
"Warm, direct, zero fluff. I left every call with a concrete action for Monday. The win-doc I built in week 6 got me a 28% raise."
AP
Alma P.Design Systems Lead · Logistics SaaS (ES)
"Finally a course that treats the adoption problem as the actual problem. The engineer-pairing rule changed how my whole team works together."
RM
Rui M.Senior → Staff Designer · B2B SaaS (PT)
Cohort 03

Join 20 designers shipping real systems.

May 15 → Jun 26 · 2 live calls/wk · Async Slack
€890€790
EARLY-BIRD UNTIL MAY 5
Rolling acceptance · Refund until end of week 1
FAQ

Questions from past applicants.

Do I need to already have a design system? +
No. Many cohort members are starting from zero. Others are inheriting a system that's been languishing. Both work — the curriculum adapts.
What if I can't find an engineer to pair with? +
Then this cohort isn't for you — yet. The engineer-pairing is non-negotiable because every failure mode I've seen traces back to designers working alone. Come back when you can find one. I'll hold your seat.
Is this live or self-paced? +
Live. Two 90-minute calls per week (recorded for flexibility), plus async Slack and two 1:1 office hours with me in weeks 2 and 5.
Can my company expense this? +
Yes. I'll send you a one-page justification template (used by past cohort members to get budget approved) after you apply.
Refund policy? +
Full refund through end of week 1 if it's not what you expected. No questions asked.
Will you run this again? +
Maybe in autumn. Maybe not. I run this cohort only when I have the capacity to be fully present. If now works for you, take the seat.