•

Stage 4 of 6

Make

Make

Real screens and a working prototype, on the real codebase.

real enough to test

1Understand2Frame3Explore4Make5Validate6Dev readythe order I explain it inthe jumps the work actually takes

What it looks like

We design in working code, on the product’s own components and tokens. The design system rules are written down as skills, so screens come out compliant from the start instead of getting checked afterwards.

In the work

  • VETDSS. We encoded the design system rules, so every wizard screen matched the library from the very first build.

  • Admissions bulk move. Our Admissions PM drafted the concept as a standalone HTML page. I refined it on the real codebase in days, with the build, the prototype and Figma kept in sync.

  • ReadySkills. Engineering built a working prototype first. My design brief kept what it proved and fixed three things it got wrong: where errors sit, where Microsoft sign-in lives and how the password rules read, at 390px and 1440px.

  • Re-enrolment. One of my designers took it end to end in eight weeks, across three codebases, and left four reusable assets behind for the next person.

What comes out

Something real enough to test.

Create a free website with Framer, the website builder loved by startups, designers and agencies.