Some of the detail and imagery here is only shared with a password — ask me for it if you'd like to see it.
That's not it — try again.
Problem
Invisible wanted to explore far more product ideas than any team could design and build from scratch each time. Without a shared process, every prototype started at zero — new design decisions, new components, its own approach to validation — and good ideas took months to get in front of users.
Summary
I built the process behind Invisible’s rapid prototyping program: a repeatable way to take a concept to a validated prototype without reinventing the process each time. It leaned on a shared set of design system components instead of one-off design work, and got prototypes in front of real users early rather than after months of polish. That process is what took typical time-to-prototype from months to weeks and supported delivery of 200+ prototypes in under 12 months.
My Role
I defined the process, established the practices teams used to run it, and refined it as more prototypes moved through it.
How it worked
- Reuse over rebuild. Prototypes pulled from a shared set of design system components rather than starting from a blank canvas each time.
- Validate early. User feedback loops happened while a prototype was still cheap to change, not after it was fully built.
- Keep scope tight. Each prototype was scoped to test a specific assumption, not to ship a finished product.
Outcomes
- Cut time-to-prototype from months to weeks
- Supported delivery of 200+ prototypes in under 12 months
- Gave product teams a repeatable path from concept to validated prototype
- Built on reusable design system components instead of one-off design work per prototype
