Designing KidLinks: Connecting with the Parents of Your Kids' Friends
Parents do not need another social network. They need a lightweight view into the
connections they already have through their kids.
Discover
My kid is making lots of friends, but I do not have good ways to keep up.
Define
Need a way to wrangle the contacts for connections made by your kids.
Develop
Simple flows: add a new friend before knowing the parent, link a parent after meeting them, and keep it as a view of contacts, not a social network.
Deliver
PM as creator: use AI coding to turn the product thesis into a working prototype.
discover
The problem appears at birthday-party speed.
The spark was simple: inviting kids to my child's birthday party, while realizing
that I did not have all the parent contact info. Some kids were from playdates,
some from last year's class, and others were new friends I had only heard about at
the dinner table.
I could visualize the web of adults around these kids: parents saved as
"Ivy's friend Sam's Dad," parents connected through old classroom lists, and
families that had not quite exchanged contact information yet.
Contacts
I
Ivy's friend Sam's Dad
messagecallmail
mobile
(555) 013-4288
company
Ivy - school / Sam's Dad
notes
Met at pickup. Maybe parent of Sam from last year's class?
The current workaround bends a contact record into a memory aid.
define
A lightweight relationship layer, not a new network.
The core user is any parent trying to navigate third-hand connections:
parent to kid, kid to friend, friend to parent. The job is not to build a
social graph for its own sake. It is to help a parent answer, "How do I know
this person, and how can I contact them?"
Keep the app simple enough to use during real parent life.
Avoid accounts and heavy contact permissions.
Make unknown information representable instead of blocking entry.
Hand off to the phone's default contact app once the right person is found.
develop
The alternatives were either too ad hoc or too heavy.
Today, parents often solve this with notes in their contacts app, hacked company
fields, names like "Ivy's friend Sam's Dad," or memory. I considered writing KidLinks data
directly into contact notes, but that would require more permissions and would be
less flexible.
School directories used to fill some of this space, but they are less common now.
Facebook can technically connect adults, but it carries too much social baggage
for a quick, practical parent-to-parent connection.
Relationship-first, not contact-first.
Support the dinner-table clue before the full contact record exists.
Remember how we know someone without creating a dossier.
KidLinks
Search kids, friends, parents
Ivy
12 connections
+ child+ friend
Sam
Last year's class
Maya
Playdate
Leo
Parent unknown
Home screen concept: quick entry first, details later.
Ivy's network
school
playdates
sports
Graph concept: zones make messy parent knowledge easier to scan.
Detail concept: context first, then a clear handoff to the phone's contact app.
deliver
PM as creator: shaping the product and building the proof.
I wanted this case study to show more than prioritization and framing. It is also
an example of product management that moves directly into creation: using AI coding
to translate a product thesis into a working web-based mockup prototype.
The prototype lets the PM work stay concrete. The user need becomes data structure,
navigation, empty states, graph views, and deliberate handoffs to the phone's contact
app. That loop is the point: think like a PM, then make enough of the product to test
the thinking.
