For most of my career, I worked in environments where complexity was expected.
Over nearly two decades in real estate and investment management, I held senior leadership roles at firms including Harrison Street Real Estate Capital, AllianceBernstein, and Abacus Capital Group. The work was demanding and sophisticated. We managed large portfolios, developed products, navigated operational challenges, and helped institutions make decisions with significant consequences.
What I learned across those twenty years, more than any technical skill or market insight, was the value of a good system.
Clear ownership. Shared information. Defined responsibilities. Visibility into what needed to happen and who was accountable for making it happen.
In institutional settings, these things are treated as non-negotiable. You build the infrastructure first. You do not expect complex organizations to run on memory, goodwill, and informal reminders.
What surprised me, as my career progressed and my family grew, was how rarely that same thinking made it home.
The Moment Everything Became Clear
The realization did not come gradually. It came from a specific experience that I have thought about many times since.
When I was laid off from AllianceBernstein, I expected what most senior professionals expect in that situation: some time to gather contacts, download files, and retrieve personal information before losing access to company systems. That window never came. Access disappeared almost immediately.
What I lost was not just professional. Because so much of my life had been managed through work tools, family information had ended up living there too. Appointments that existed only in my work calendar. Details I had entered into systems I no longer had access to. Reminders tied to accounts that were now closed.
In the days that followed, appointments were missed. Information I had assumed was stored somewhere turned out to be stored nowhere I could reach. More than the practical disruption, though, what I felt was a deep sense of disconnection. Years of family management, the scheduling, the coordinating, the remembering, had been scattered across disconnected tools and, ultimately, held together inside my own head. When the professional scaffolding collapsed, a surprising amount of personal life collapsed with it.
What struck me most was not that I had lost access to a work system. It was that my family had no system of its own.
That experience forced me to see something I had been too busy to examine clearly. Family management information did not have a home. It lived in work calendars, personal phones, group texts, sticky notes, and mental lists that only one person was maintaining. There was no shared system. There was just one person serving as the system, holding everything together through effort and memory alone.
I could not stop thinking about what that meant, not just for me, but for every family operating the same way.
The Personal Toll of Carrying Everything
Before I could name what was wrong with the system, I had to reckon with what it had cost me personally.
For years, I had structured my life around the needs of others. At work, I was accountable to clients, partners, and institutions. At home, I was the one tracking the appointments, managing the schedules, remembering what each child needed and when, and filling every gap that no one else had noticed. I was good at it. I kept things running. And I told myself that was enough.
What I did not do, for a very long time, was pay attention to my own wellbeing. I stopped making time for the things that restored me. I moved through each day managing an invisible list that no one else could see and that never seemed to get shorter. And underneath the competence and the forward motion, something quieter was building.
It was not anger, exactly. It was resentment. The slow, corrosive kind that comes not from a single moment but from years of feeling that the weight you are carrying is not seen and is not shared. I did not resent my family. I loved them. But I resented a situation in which I had somehow become the sole keeper of everything, at home and at work, without anyone having decided that was how it should be.
It took me longer than it should have to understand that this was not a personal failing. It was a structural one. The system I was living inside had no mechanism for distributing what I was carrying. And so I carried it alone.
What Mental Load Actually Costs
The term mental load has become more widely understood in recent years, and rightly so.
But I want to be specific about what it actually means in practice, because the phrase can sound abstract until you have lived it.
Mental load is not the doing. It is the thinking behind the doing. It is the layer of cognitive work that ensures the tasks happen at all: the remembering, the anticipating, the planning, the monitoring, and the following up. At Cookie, we often describe this through the Family Recipe: Planning, Procurement, Execution, and Follow-Up. Planning is knowing what needs to happen. Procurement is getting the information, items, or support required. Execution is the visible doing. Follow-Up is making sure the loop is actually closed.
Most families notice the execution. But the real mental load lives in the planning, procurement, and follow-up. It is knowing that the permission slip is due Thursday, that there is nothing planned for dinner on Tuesday, that the dentist appointment needs to be rescheduled, and that someone needs to confirm the carpool for Saturday before Friday afternoon. All at once. In the background. While doing everything else.
Research by Harvard sociologist Allison Daminger, published in the American Sociological Review in 2019, identifies four components of this cognitive labor: anticipating needs, identifying options, making decisions, and monitoring outcomes. Her research found that this work is distributed unequally in most households, with women in different-gender couples carrying more of it overall, and disproportionately more of the most invisible forms, the anticipating and the monitoring, the work that happens before any decision is ever made.
That finding matched exactly what I had been observing, in my own home and in the lives of nearly every parent I knew.
The cost is real. It shows up as fatigue that does not make sense given how much sleep you got. It shows up as difficulty being present, because part of your mind is always elsewhere. It shows up in relationships, too. Without shared systems in place, one person often becomes the household reminder system, constantly asking whether the form was signed, the bag was packed, the appointment was confirmed, or the task was finished. Over time, those reminders can start to sound like nagging to the people receiving them, even when they are really just the visible edge of invisible work. That dynamic wears on partners and children alike. The person carrying the load feels unseen and resentful. The people being reminded feel managed. And the family ends up with more tension, not because anyone lacks care, but because the system is asking one person to hold too much.
For working parents, that burden follows them into the office every morning and home again every evening, never fully turning off.
Why Systems Are the Answer
When I look back at what actually worked in my professional career, it was never the smartest person in the room who made the difference. It was the quality of the systems that surrounded the people.
Good systems do not require any single person to remember everything. They distribute information so that anyone who needs it can access it. They make ownership clear so that nothing falls into the gap between assumed responsibilities. They create visibility so that progress can be tracked without constant check-ins. They reduce the cognitive overhead required to keep things running, which frees people to focus on what actually matters.
These are not radical ideas. They are standard practice in well-run organizations.
The question I could not stop asking was: why do families not have access to the same quality of infrastructure? Not because families are less important than organizations. Quite the opposite. Because in most families, the stakes are higher, the complexity is real, and the person carrying the system is doing so without any of the structural support that professionals take for granted.
Why Existing Tools Were Not Enough
When I started looking for solutions, I found that tools already existed. Calendars. Chore charts. Notes apps. Reminder systems. Task lists. Families were not lacking for options.
But none of them worked together.
That was the problem. Not the absence of tools, but their fragmentation. The calendar lived in one place. The documents lived somewhere else. The tasks were tracked in a third place, or not tracked at all. The children had no real role in any of it. And the only way to hold all of it together was to have one person whose job it was to know where everything was and what needed to happen next.
That person was not using a system. That person was the system.
The tools that existed were designed to handle individual tasks, not the underlying architecture of family management. They could capture an appointment or remind someone about a chore. They could not distribute the cognitive work of running a household. They could not make the invisible visible. They could not move the load from one person's mind into a shared space where everyone could see it, own a piece of it, and contribute to it.
That is the gap Cookie was built to close.
What Cookie Was Built to Do
Cookie was created to help families share the load, not just share the tasks.
There is an important difference between those two things.
Sharing tasks means someone asks, someone responds, and something gets done. The mental load, the remembering, the planning, the monitoring, stays in the same place it always was.
Sharing the load means building a system where information lives in a shared space rather than one person's head. Where responsibilities are visible and owned rather than assumed and forgotten. Where anyone in the household can see what needs to happen, what belongs to them, and where things stand, without having to ask.
That is what Cookie is designed to do. Shared calendars that actually reflect everything the family is managing. Task ownership that is clear rather than implied. A document hub for the information families need but can never find when they need it. A Kids App that introduces children to the concept of contribution in a way that is age-appropriate and genuinely rewarding.
The mission has always been straightforward: help families manage less and live more.
Not by eliminating the complexity of family life, which is not possible and probably not even desirable. But by building infrastructure that makes that complexity manageable without concentrating the entire burden on one person.
What I Know Now That I Did Not Know Then
Building Cookie has taught me things I could not have learned anywhere else.
I came into this with two decades of experience in sophisticated institutions. I understood product development, investor relations, operations, and strategy. What I underestimated was how different it feels to build something that lives inside people's daily lives, rather than inside a portfolio or a fund.
In institutional work, you can measure success with reasonable precision. Returns, timelines, performance against benchmarks. In family life, the measures are softer and more personal. Does this actually make someone feel less alone in what they are carrying? Does a partner notice, for the first time, how much was being managed invisibly? Does a child start to see themselves as a contributor rather than a recipient? Those are the outcomes that matter, and they are much harder to design for than a clean feature set.
The question I return to constantly is not whether we have built something impressive. It is whether we have built something that genuinely moves the load, rather than simply making the existing load look more organized. That distinction drives every choice we make about what Cookie is and what it is not.
Why This Work Matters
I did not set out to build a technology company. I set out to solve a problem I could not stop seeing.
The families I talk to every day are not struggling because they lack effort or love or commitment. They are struggling because the invisible infrastructure of family life was never built to support the complexity modern families are managing. They are running sophisticated operations on informal systems, and the gap is costing them in ways they can feel but often cannot name.
Cookie is an attempt to close that gap. It is built on the belief that families deserve the same quality of systems that support every other complex operation in their lives. That the invisible work of managing a household deserves to be seen. That no single person should have to carry the entire household map alone.
We also believe the stakes are larger than most people realize. When mental load remains concentrated on one person for years, the consequences extend beyond household stress. They can contribute to burnout, relationship strain, and difficult career tradeoffs, particularly for working parents. While no technology can solve these challenges on its own, better family systems can help families share the load more equitably and create the conditions for healthier relationships, greater wellbeing, and more sustainable careers.
That is why I built Cookie.
And it is why I am still building it.
Briana Succop is the Founder and CEO of Cookie Family Management. Learn more at mycookiefam.com.