← All work

Lead Product Designer · Frog Street · 2023–present

Frog Street

Lead product designer on Lilypad, the teacher-facing early-childhood platform Frog Street bet the company on. I was one of the two people who started its digital product, a team since grown to nearly twenty. My work has covered the product's UX and systems architecture end to end: the ecosystem structure and core flows, the design system, and pieces carried through front-end and QA.

Role
Lead Product Designer
Timeframe
Jan 2023 – present
Scope
Product architecture · UX · Design system · Accessibility · Research ops
Team
Two on the founding digital product team → ~20 today

Quick summary

Role at a glance
Lead Product Designer, from the two-person founding team
Scope
Product architecture, design system, and the Assessment Center — end to end
Cross-functional
Stood up research ops (later run by a dedicated research team), directed a contract designer, and shipped across multiple parallel workstreams
Span
Founding designer → design lead, concept through front-end and QA
See the real product Watch Frog Street's public Lilypad preview Curious what I actually built? Frog Street's own preview — from their 2026 Splash conference — walks through the live Lilypad platform. Public video, hosted by Frog Street, opens in a new tab. Watch the preview →

Context

Frog Street is an early-childhood curriculum company founded in 1989, moving from print into software. When I joined in early 2023, the digital product was just two of us. There was no platform yet, only a legacy content portal, and a company-defining bet: that we could turn decades of classroom curriculum into a product that fits a teacher's real day — planning before class, the lightest possible touch during it, and the heavier work of documentation and reporting after — so the product stays in the background of a room full of toddlers instead of adding noise to it. That portal has since been fully replaced by Lilypad, built on modern infrastructure with current security and accessibility standards designed in from day one.

Lilypad serves several audiences at once: teachers day to day, district administrators, and caregivers, with children as direct users in some experiences. My work has centered on the teacher- and admin-facing side of the platform: the flows, reporting, and architecture they rely on.

A bright early-childhood classroom with child-sized wooden tables and chairs, learning materials on open shelves, and a round rug.
The room the product lives in — an early-childhood classroom, where the work is planning before class and the lightest possible touch during it. (Stock image, for context.)

A note on scope: Frog Street's curriculum and its developmental assessment framework are authored by the company's curriculum and pedagogy team. My work is the product that delivers them: the architecture, flows, interfaces, and design system that put that content in teachers' hands.

What I did

Defined the product architecture

I defined the product ecosystem the whole platform still runs on: a teacher-facing application and a separate content-and-admin backend. That split structured every build decision that followed: where content lives, how it's authored and published, what teachers see, and how districts are provisioned.

A real part of that lift was translation. It meant first understanding the print curriculum — how it's structured, and how teachers actually use it — then adapting it into something that works digital-first rather than a scanned copy of the page, while staying congruent with the print products still in classrooms. Print and digital had to read as one curriculum.

The two-part product ecosystem A content-and-admin backend authors, tags, and publishes content to a separate teacher-facing app. Content & admin backend Teacher-facing app AUTHOR → TAG → PUBLISH
The two-part ecosystem the platform is built on: a teacher-facing app and a separate content-and-admin backend

Designed the core flows and funnels

I designed the platform's core surfaces and the flows that connect them: login, invite, and account creation; SSO and self-service district rostering; the teacher hub and dashboard; program selection; the Resource Center with its search, filter, and bookmarking systems; and onboarding for both teachers and district admins. This is the spine of the product, the path a teacher takes from logging in to running their day.

Built the design system from scratch

I built Frog Street's first design system — tokens, components, patterns — and documented it for the team. Its WCAG-compliant color system was engineered for parity with Frog Street's print materials, bridging the digital product with the company's print heritage. The system has since been expanded twice.

How the design system is layered Foundations and tokens build up through components and patterns into shipped product. Product Patterns Components Tokens Foundations BUILDS UP
How the system is layered — foundations and tokens up through components, patterns, and shipped product. A conceptual view, not the production library.

Owned the Assessment Center, end to end

Frog Street's flagship new capability is a formative-assessment experience for early-childhood educators. I owned its design from kickoff mapping through dev handoff: capturing an observation in the moment, the reporting that turns those observations into a readable picture of progress, and the admin configuration behind it. The developmental framework and standards these reports express belong to the curriculum team; the product that lets a teacher capture an observation one-handed and read a class's progress before a checkpoint closes is mine.

The assessment model An observation becomes evidence, tied to a skill and a level, rolling up into progress. Observation Evidence Skill Level Progress
The assessment model I designed around: an observation becomes evidence, tied to a skill and a level, rolling up into progress. A conceptual view, not the production screens.

In usability testing, educators consistently described observation capture as fast and easy to use in the middle of a busy classroom.

Made accessibility a program

Accessibility was in the work from year one and became a dedicated compliance track, a WCAG/508 epic covering color and contrast, keyboard focus, screen-reader support, alt text, and WAVE remediation. I compiled the platform's accessibility posture into a procurement-ready questionnaire.

Stood up research operations from zero

I established the platform's research practice: the first structured test plan, teacher interviews, a moderated-testing program, analytics instrumentation, and on-site user testing, routing findings straight back into the report designs. The company later grew a dedicated research function that carried the program forward, which is exactly what a founding practice is for.

The practice produced product decisions, not decks, and kept producing after the handoff. Usability testing showed teachers using the Planner to actively shape their week, not just view it; that insight shipped as a set of Planner enhancements. Later wireframe testing with infant, toddler, and preschool educators drove a more streamlined observation-capture flow.

Led design as the team grew

On the digital side, I procured, onboarded, and directed a contract designer. On the print side, I sourced a staffing partner and helped hire a print designer who went on to contribute to Frog Street's new infant product, a hire that had real impact on the print product line.