Campus ecosystem
UNIT.Labs · B2B whitelabel
Product partner / product designer
Product I cofounded · now 2500+ DAU
Role
Product partner / product designer. I laid out the web and mobile design so one product can wrap any facility — clear, structured, simple, with a real design system. Not only mocks: planning, client meetings, hiring, design QA, retros.
What shipped
- Initiated the company and designed web and mobile apps for any facility under a real design system.
- Product-partner work beyond screens: planning, client meetings, management and engineering, hiring and firing, design QA, retros, merch for the team.
- Designed modules at the intersection of client constraints, what users wanted, and engineering pace.
- Simplified long administrator flows and kept admin vs resident tone distinct across CRM and the resident app.
What I learned
- Stick with nails before the machine gun: covering every path first spends time and still misses the user.
- In a product partner seat, design often comes after product and ops — the design bar still has to hold.
- A structured, simple system is what lets one product wrap many facilities without becoming a different product each time.
Product scoping
Priorities, MVP boundary, client logic. What we learn from the next ship — not a 40-page spec.
Feature ownership
I owned the cut: what we ship now, how it stays one product across facilities, and what waits.
- Owned module scope with clients and engineering — a shippable cut, not a backlog dump.
- Held admin vs resident as two jobs in one ecosystem, so ownership did not split into two products.
- Hiring, design QA, and retros sat in the same loop as the decision, not after it.
Resident app
Resident-facing mobile app in the same campus ecosystem. Different job, different tone than the admin CRM.
- Shaped the resident mobile app (React Native) in the same product as the admin CRM.
- Kept admin vs resident tone of voice distinct so operators and residents are not spoken to the same way.
- News, booking, and facility info in one channel — instead of chats and tables.
Smart City mobile SaaS
Native modules under client and engineering constraints. Narrow valuable slice first, paths later.
- Designed native iOS and Android modules for UNIT.City — the campus where the stick-with-nails bias became explicit.
- Advocated shipping a narrow valuable slice first, then expanding after learning.
- Partner communication and product strategy; App Store and marketing assets with the marketing team.