Founding Product Designer · Frog Street · 2023–present
Frog Street
Founding 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.
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 WordPress content portal carrying real security debt, 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.
Lilypad, the teacher-facing side: the dashboard after login
TACO, the content-and-admin backend, where curriculum is authored, tagged, and published to Lilypad
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.
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.
Onboarding inside the product: Planner enhancements shipped in response to 2025 usability findings, introduced to teachers in place
The Week Report: planner reporting whose skip and revisit states came straight out of teacher testing
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 and codified for AI-assisted prototyping.
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: observation capture "in the moment," the reporting suite (progress by domain, by child, by class), level-progression and pacing views, child portfolios, and the admin settings that configure it all. 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.
Where it started: the Assessments V1 kickoff board, mapping requirements, flows, and first wireframes
Where it shipped: capturing an observation in the moment, with skills and levels three steps away
In usability testing, educators comparing the Assessment Center against the assessment tools they were leaving — including the market-leading platform — consistently described it as the easier of the two.
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 and an honest, standards-literate risk read.
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 in Texas, routing findings straight back into the report designs. Frog Street later onboarded a data scientist and a dedicated UXR team who 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. In 2025, twenty-two sessions across three rounds fed the roadmap. My spring usability round — five educators across five states — found teachers treating the Planner's filters as tools for editing their week rather than just viewing it; that insight shipped as the Week Summary, Week Details, and Daily Prep enhancements introduced in the onboarding above. In the fall, the UXR team's exploratory interviews on how teachers document and level called for in-the-moment leveling support; a month later, thirteen wireframe sessions with preschool, pre-K, infant, and toddler educators found teachers overwhelmingly appreciating the leveling guide, and drove the streamlined three-step observation capture shown earlier.
The loop keeps running. When the UXR team ran a rapid four-session round on the new Favorites feature, it confirmed the core flow worked — every participant already kept a workaround system outside the product just to find resources again — and found that a flat list wouldn't scale, because teachers think in themes and weeks. I reviewed the findings with the team and redesigned the hub around exactly that structure, translating the round into a ticketed epic of fixes, from entry-point states to search scoped inside Favorites.
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. I also built the team's AI-assisted design operations, codifying the design system so quality compounds across designers and sessions rather than living only in my head.
By the numbers
- 585Jira tickets
Jun 2023 – Jul 2026 - 36epics
touched - 22research sessions
three rounds, 2025 - 5parallel workstreams
at peak