A phone kids can use. Boundaries parents can manage.
Yello! pairs a real phone number and network service with a parent portal. Parents approve contacts, and calls and texts are limited to those contacts in both directions.
The product problem spans two users and several systems: a child’s phone, the parent’s controls, and the network service enforcing those controls. Both experiences need to be clear.
Make the idea work
I built Yello!’s initial working prototype using AI-assisted development. It turned the product into an experience we could use and discuss.
As executive sponsor and product lead, I led Yello! through external beta. A cross-functional team delivered the production product.
Hold the beta until the product was ready
I made product quality and the protected phone environment release requirements. Any way for a child to get outside that environment had to be resolved before we put the product in families’ hands.
We held the beta release and pushed go-to-market back. I chose to give up the earlier launch date so we could ship a product we were proud to offer our customers.
A new product available to families
Yello! reached external beta with its own communication experience and parent portal. It is a concrete example of my work across product leadership, hands-on prototyping, and a consumer service that depends on telecom infrastructure.