About· me, documented

Everyone talked about UX and UI. Nobody talked about systems.

So I decided to be the loud one. I'm Chaw Su Hlaing, and The Productive Schedule is my school and studio for systems design, started in 2024. This page is my file: part documentation, part letter.

01 · The story· why this exists

In Myanmar's design community, the conversation kept repeating itself. UX this, UI that. Design systems never came up. I kept waiting for someone to raise the subject, and nobody did.

“I wanted to be brave and speak louder about systems. In the AI era, systems matter more than ever.”chaw su · asked why this school exists

So I built the answer myself. The first course ran in 2024, made for a real need in a real community, not for a trend. Eight cohorts later, the need keeps proving itself.

say it louder ↗
02 · The letter· from the founder

In my own words

Hi, I'm Chaw Su.

I have spent nearly six years in UX and UI, and the last three and more of them inside design systems. By day I design systems at Codigo. Before that, at ONOW and TestFirst, I built my own and got them shipped.

I did not set out to run a school. I set out to say one thing louder: screens are not the hard part, systems are. The first course was the whole plan. The school and the studio are what happened when that plan met real demand.

I teach the way I wish someone had taught me. Real scenarios, precise feedback, no happy-path answers.

Off the file, I am a mother. The schedule in the name is not branding; it is how cohorts, a day job, and a small human fit into one calendar. Ask me about design, music, food, or motherhood, and I will happily lose track of time.

chaw su
03 · The journey· the schedule itself

How one course became a schedule

2024 · one course

It starts as a single course

The Productive Schedule began as one design systems course I built for the Myanmar design community and the conversation nobody was having. The first cohort ran, finished, and the need was obvious.

8 cohorts · a school

The course becomes a school

One course grew into a program: Foundations for the whole system, Sprint for the agentic part, Core for learning at your own pace. Eight cohorts have come through mine, and their capstones are real systems, not demo files.

now · a studio too

The school grows a studio

Not every problem is a course. Some teams need the system delivered, not taught. So my studio does what my school teaches: UX and product design, agent design, product development, consultancy, and corporate training.

next · the bet

Where it goes from here

My bet stays the same: systems thinking and the designer who also builds are where this field is heading. I am turning The Productive Schedule into an AI-led design systems studio, and taking every cohort along.

04 · Variants· 4 found

One me, four variants

Same component, different props. Hover to switch.

variant=instructor

The Instructor

My default state. I have run every cohort of the program: 8 so far, 100+ designers, 100% positive feedback. I teach design systems with Futura and share the craft at Design Matters events.

props: 8 cohorts · 100+ designers
variant=systems-designer

The Systems Designer

The proof behind my teaching. I shipped Pineapple at Codigo and Tinker at ONOW, built the TestFirst platform's system, and worked on the Porsche Experience Center.

instances: Pineapple · Tinker · TestFirst
variant=mentor

The Mentor

My quiet variant. I support mentorship sessions with UXMM, guiding junior designers one career question at a time.

props: UXMM · one on one
variant=founder

The Founder

The one writing this page. I turned a single 2024 course into a school and a studio, and I still teach every cohort myself.

props: school · studio · since 2024
05 · Usage· guidelines

How to work with me

✓ Do
  • Bring me real product complexity. The messier the flows, the better my answers get.
  • Ask me why until the logic holds.
  • Expect precise feedback on every assignment. My students keep saying so in the reviews.
✕ Don't
  • Expect a happy-path answer. I do not ship those.
  • Ask me for pretty without asking whether it holds.
  • Wait for someone louder to start the conversation. That seat is taken.
06 · Changelog· release history

Versions of me

v0.12019My first UX internship. I learned the craft one screen at a time.
v1.02022I built Tinker at ONOW, the company's first design system, and scaled it.
v1.52024Design systems at TestFirst, then Codigo. Along the way, my TestFirst onboarding redesign cut drop-offs by 80%.
v2.02024The first Productive Schedule cohort ran. The conversation I wanted finally started.
v•2024I became a mother. The schedule in the name stopped being a metaphor.
v2.8now8 cohorts, 100+ designers, a school and a studio. I am turning The Productive Schedule into an AI-led design systems studio.
What we believe

A system that only handles the happy path is not a system. Reasoning you can't defend is not a decision. Pretty that collapses under logic is not design. We teach the invisible part, because that is the part that holds.

Start an inquiry