Ed-Tech · Multi-User Platform · User Research · Product Design

TripSlip

Designing a multi-sided platform that connects teachers, parents, school admins, and venues — turning field trip chaos into a 10-minute workflow.

— In progress, Version 1 launching September 2026

TripSlip heroTripSlip multi-view hero
Contract Product Designer
TripSlip (Startup)
Ongoing since June 2025
Figma, FigJam, Notion
4 user types, 20+ planned interviews

THE CHALLENGE

Four users, one platform, zero precedent.

Field trip coordination is broken. Teachers burn 10+ hours weekly chasing permission slips. TripSlip is the first platform to connect all four parties into one workflow.

FOUR PERSPECTIVES, ONE PLATFORM

Every user sees what matters to them

Each user type has a distinct mental model, priority set, and workflow.

Teachers

Create trips, collect payments, send permission slips, track attendance

30+ screens designed

Parents

Sign slips, pay fees, view trip details

12+ screens designed

School Admins

Approve trips, manage rosters, compliance

Scoping in progress

Venues

Manage bookings, set availability

October launch

THE SOLUTION

A 10-minute trip, start to finish from chaos to clicks

The teacher flow is the most complex — 30+ screens covering trip creation, permission slips, payment collection, QR check-in, and student roster management.

Trip CreationTrip Creation

Trip Creation

Template-first flow with elevated payment and permission sections

Permission SlipsPermission Slips

Permission Slips

Digital slips sent to parents with real-time tracking

KEY DECISIONS

What I chose and why

01

Payment & permission slips elevated, not buried

User interviews revealed teachers' top priority was collecting payment and permission slips. I moved them to dedicated sections with context cards.

02

Template-first trip creation

Teachers expressed interest in reusable trip types. I designed a template entry point so repeat trips take minutes, not hours.

03

IA before screens, always

With four user types and 60+ total screens, I built the full information architecture in FigJam first, catching feature overlap early.

WHERE IT STANDS

30+

Teacher screens

4

User types

2/20

Research interviews

7

Functional sections

Sep 1

Launch target

This project is actively in progress.

VISIT TRYTRIPSLIP.COM ↗

WHAT I'M LEARNING

Designing for a market that doesn't exist yet means every interview reshapes the product. The biggest shift so far: teachers don't want more features — they want fewer decisions. Working under mentorship at Newlab has sharpened how I scope ambiguity and communicate trade-offs.