I thought I’d be launching my first product for Mother of Invention by now.
I’m not.
A few months ago, I discovered that one of its core components was engineered incorrectly. I made the difficult decision to redesign it from the ground up.
That delayed my launch, but it also clarified my values. I refuse to ship prematurely.
While I finish the redesign, I’m going to use this newsletter to share what I’m learning. I'll be writing here weekly, from inside the company-building process because I believe the best way to understand transformation is to document it as it happens.
I’m a serial entrepreneur who became a mother twice. I set out to solve a practical problem—diaper changing—and ended up inside a much larger one: how to give women tools to navigate the disruptive identity shift that comes with becoming a mother.
There’s a medical term for this transition: matrescence. It describes the psychological and neurological reorganization of motherhood. Think something akin to adolescence.
It’s accurate.
It’s also cold, and too clinical for my taste.
Mine began in earnest after the birth of my second daughter in 2021. I’m still in it.
This work exists because that shift dismantled parts of me I once depended on and rebuilt others I didn’t know I’d need. It wasn’t linear, and it didn’t always feel like growth.
But it taught me this: the problems are the curriculum.
When you stay inside a problem long enough, patterns emerge. Tools get designed… sometimes physical ones, sometimes conceptual ones.
That’s what Mother of Invention is becoming: objects and ideas that support women navigating one of the most disruptive transitions of their lives.
And this email is changing with it.
I’ll be writing about how identity shifts during motherhood and how design, science, and daily care either support that process or actively work against it. This includes care rituals, attachment theory and attunement, and what it means to mother in an age of unprecedented technological growth.
If you're a mom-to-be or new mom, I can’t offer a definitive roadmap. I can, however, show you what it looks like to stay in a problem long enough for real frameworks to emerge. To build while shifting, and to build because of it.
Thank you for being here,
