by alichava | Sep 17, 2026 | Organizing & Cleaning, Tools
Recently, I took the recommendations that had accumulated in one of the local WhatsApp groups I started and turned them into spreadsheets.
This will surprise absolutely no one who knows me.
People ask the group for all kinds of recommendations, and the responses are genuinely useful. The problem is that a few days later, those names are buried beneath hundreds of other messages. I wanted to collect the information somewhere people could find it again.
The contractor recommendations were fairly straightforward. I could list the person, the kind of work they did and any comments people had shared.
The doctor recommendations felt different.
I began with the same basic structure: name, specialty, location and contact information. But as I worked through the messages, I realized I needed to include a caveat. A list can tell you which doctors other people recommend. It cannot tell you whether you will have the same experience. The same applies to contractors. I have had two different handymen who have done well with me, but others have experience flakiness and crazy pricing quotes for similar work.
I know that because one of the doctors beloved by many people in my community is someone I would never see again.
The Doctor Everyone Loved
In the summer of 2018, I went to my primary-care doctor because I felt off.
I did not have one neatly defined symptom or a theory about what was wrong. I knew my own body, and something did not feel right.
He dismissed my concerns.
By November, I had developed what I initially thought was a clogged milk duct from breastfeeding. Then the area became larger and did not go away.
I tried to make an appointment with my OB/GYN, but I could not get in for another couple of months. Waiting that long did not feel like a reasonable option.
Fortunately, one of the parents in my son’s class was able to see me the next day. Other people in the community helped me reach an oncologist much more quickly than I would have been able to on my own.
Eventually, I returned to my primary-care doctor for a preoperative appointment. He acknowledged that perhaps he should not have dismissed my earlier concerns. Looking back, he could identify things we might have done differently.
By then, I had been diagnosed with stage 3 breast cancer.
The same doctor is highly recommended by many people in my community. His name comes up regularly when someone asks for a primary-care doctor. Many of the people who speak most enthusiastically about him are men.
They may have had genuinely excellent experiences with him. He may listen carefully to them, respond when they need help and provide exactly the kind of care they want from a primary-care doctor.
Their experiences are real.
So is mine.
I would never go back to him.
A Recommendation Is One Person’s Experience
When the same doctor’s name appears repeatedly in a Facebook group, WhatsApp conversation or neighborhood listserv, it begins to look like a consensus. If ten people recommend one doctor and only two mention another, the first doctor appears to be the safer choice.
But recommendations are not votes, even when we collect them in a spreadsheet.
Ten people may love a particular doctor because they have received excellent routine care for years. That does not tell me how the doctor responds when the symptoms are vague, the first explanation does not fit or the patient keeps insisting that something is wrong.
The experience of a generally healthy man may not tell me very much about how the same doctor will respond to a woman describing changes in her body that she cannot yet explain.
Other differences matter too. Some patients want a doctor who will spend time talking through every possibility. Others value efficiency and easy access. One person may appreciate a direct communication style that another experiences as dismissive.
A recommendation can tell me that someone had a good experience. Without more context, it cannot tell me whether that doctor is a good match for what I need.
What Community Lists Do Not Capture
Positive and negative experiences also tend to appear differently in community conversations.
It is easy to post that you love a doctor. It is much harder to describe a negative experience in a group where the doctor, the doctor’s relatives or dozens of longtime patients may be reading. People may be willing to discuss those experiences privately but not attach their names to them in a public conversation.
That means a recommendation thread may contain plenty of enthusiastic endorsements while leaving out some of the information that would matter most to someone choosing a doctor.
Even when someone does raise a concern, it can disappear beneath a much larger number of positive responses. The positive recommendations do not make the negative experience untrue. The negative experience does not erase the positive ones.
They are different patients describing different interactions.
That is harder to represent in a spreadsheet than a simple tally of names.
Using the List as a Starting Point
I still think community recommendation lists are valuable. I would not have spent the time creating the spreadsheets if I did not.
I am just more cautious about what the lists can tell us.
A name on the list is a place to begin. From there, I want to know why someone recommended the doctor. What kind of care did they receive? How recently did they see the doctor? Did the doctor listen when the answer was not immediately obvious? How did the office respond when something felt urgent?
Not every recommendation needs to include a medical history or a detailed account of someone’s care. People should share only what they are comfortable sharing. But even a little context can be more useful than another vote for the same name.
The list also cannot become a permanent judgment about a provider. Doctors change practices. Office staff changes. Insurance participation changes. One person’s experience, whether positive or negative, cannot predict every future interaction.
What the list can do is preserve a collection of experiences and give someone a more informed place to start.
The Community Was Also What Helped Me
My experience is not an argument against turning to the community for help.
When the formal systems failed me, people in my community were the reason I received care.
I could not get a timely appointment through the usual process. A parent from my son’s class saw me the next day. Other community members helped me get to an oncologist quickly. They knew whom to contact and helped me navigate a system I had never expected to need.
That informal knowledge mattered enormously.
The problem was not that people shared recommendations. The problem was believing that a frequently recommended name told the whole story.
Now, when someone tells me that they love a doctor, I want to know why. I want to understand what the doctor helped them with and what happened when something was not straightforward. I also want there to be room for someone to say, “That was not my experience,” without treating one person’s story as proof that everyone else must be wrong.
I will probably continue turning sprawling WhatsApp conversations into spreadsheets because that is apparently who I am.
I just no longer think the most useful information is the number of times a name appears.
It is the experience behind the recommendation.
by alichava | Sep 8, 2026 | Organizing & Cleaning, Parenting, Simcha
Have I mentioned that my brain is full of a lot at any given time? I’m also a night owl, and there is a stretch somewhere between 10 p.m. and 2 a.m. when the house gets eerily quiet and my brain decides this is the ideal time to become extremely productive. It’s when I write, design and solve problems, and also when one idea has a tendency to turn into 15 others.
One night, I was working through a completely unrelated visualization for an email for work when I started thinking about my son’s bar mitzvah. There were all these different pieces I was trying to keep track of before he gets home, scattered across my brain and various places I’d put them so I wouldn’t forget them.
Somewhere in the middle of working on something else, I started wondering why I was doing it this way.
There had to be a better way to organize all of it.
We’ve Used the Existing Systems
This isn’t our first time doing this. For Child #1, we used Paperless Post. Her bat mitzvah was during COVID, so almost nothing about that experience was particularly normal.
For Child #2, we used RSVPify, and it worked well.
Now we’re at Child #3, so I started looking again at RSVPify, Greenvelope and some of the other systems available. They all do what they’re designed to do. The problem was that I kept wanting things to work a little differently.
I wanted something that worked the way my brain works.
More importantly, I wanted one place where our whole family could see what was happening instead of having the planning live in spreadsheets, emails, invitations, notes and whatever happened to still be stored in my head.
My head is not a reliable family database.
I Wanted a Command Center
I’ve been calling it, at least in my head, the Simcha/Mitzvah Command Center.
What started as an RSVP system quickly became something bigger. I wanted the guest side and the planning side connected. I wanted to know what needed to be done, what had already been done, what we were spending, what meals we were serving and who was responsible for what.
I wanted information we collected from guests to actually connect to the planning we were doing for them.
If someone told us they had a dietary restriction, I didn’t want that information sitting somewhere in an RSVP export while I was making menu decisions somewhere else. If people were coming from out of town, I wanted the information they needed connected to the rest of their experience.
Mostly, I wanted to take the large collection of things I was carrying around in my head and put them somewhere everyone else could see them too.
Families Aren’t Organized Around a “Lead Parent”
One seemingly small thing kept bothering me about a lot of systems: the assumption that there is one lead parent.
A lot of databases, school systems and event platforms are still designed around the idea that one parent gets the information and manages everything from there. Ari wrote about this years ago in his piece about the “lead parent” and the persistence of a 1950s parent culture.
We’ve also used Google tools in our own family specifically because information shouldn’t have to live with only one person.
I didn’t want to reproduce that problem in something I was building.
If I’m inviting a child from my son’s class, I want to be able to communicate with the adults responsible for that child without pretending I’m inviting the entire household. I also don’t want the system to assume that Mom is automatically the point person. Or Dad.
It could be a mother, father, stepmother, stepfather, grandparent or someone else entirely. Sometimes two adults need the information.
That sounds like a tiny database decision, but it really isn’t. Technology encodes assumptions about how people live, often in ways we don’t notice until the technology makes us work around them.
If I was building this myself, I didn’t want mine to make that assumption.
This Is Where My Background Gets Weirdly Useful
I’ve been creating websites for about 31 years, starting not that long after my own bat mitzvah. I also have a master’s and doctorate in visual and communication design.
I tend to think in numbers and data, but also in hierarchy, spacing and structure. When I’m looking at information, I’m thinking about the story it tells and how someone is going to move through it. In my brain, the research-and-math side and the design side have never really been separate.
This project uses all of that.
But the really interesting part is that building something like this is very different now than it would have been even a few years ago.
You don’t need 31 years of experience creating websites to build something useful for yourself anymore.
AI Changed the Barrier to Building
I could have coded this system without AI. It just would have taken me much longer.
Now I can explain what I’m trying to accomplish, work through the logic and have AI help with pieces of the code. I can set something going, head downstairs for dinner and come back to work that has moved forward while I was gone.
That is genuinely remarkable.
It also isn’t magic.
AI can help me build much faster, but I still have to know what I’m trying to build. It isn’t going to spontaneously decide that the “lead parent” model bothers me or think through how I want a family to move through an RSVP. I have to understand the relationships between all of those pieces, recognize when what it gives me doesn’t make sense and keep pushing it toward the system I actually want.
And it certainly doesn’t reliably know when it has done something stupid.
That’s still my job.
For me, AI is taking over some of the work I used to have to do manually. That leaves me more time for the part I actually find interesting: figuring out what the system should do.
The System Keeps Growing
This started as an RSVP system.
Then I wanted planning tasks and a budget. Then vendors, schedules and menus. I wanted a way to track dietary needs and hotel information for people coming from out of town. I wanted to keep communication connected to the people receiving it.
Eventually I looked up and realized that the thing I had imagined as an RSVP page had become something much bigger.
Which, if you know me, is probably not surprising.
I see a problem and my brain immediately starts thinking about all the different ways it could be solved. Sometimes that’s incredibly useful.
Sometimes it is why I’m awake at 1:30 in the morning adding another feature.
The Real Test Comes Next
Right now, this is a very large-scale experiment.
I don’t know that I’ve gotten it right.
Building something that works technically isn’t the same as building something that actually makes life easier. The real test will be whether our family uses it, whether guests find it intuitive and whether it actually reduces the number of places we’re keeping information.
Does it make the months leading up to the bar mitzvah easier?
Does it let other people in the family know what’s happening without asking me?
Does it prevent information from disappearing into one person’s inbox or brain?
And, sometime in November, will I discover that I have built an elaborate planning system while the one piece of information I desperately need is still written on a Post-it note somewhere?
Entirely possible.
I’m Already Thinking About What Comes After
We still have another bat mitzvah in about two and a half years. Ari turns 50 in January, so maybe parts of this will get tested on a completely different kind of celebration before then.
And somewhere in the back of my mind is the family command center I’ve been thinking about for years.
Because the underlying problem isn’t really specific to a bar mitzvah.
Families manage enormous amounts of information: schedules, meals, tasks, school information, travel, medical appointments, forms, carpools, events and the endless question of who is doing what and when.
We’ve gotten very good at solving each individual problem with another app, calendar, spreadsheet, text thread or shared document. What we haven’t necessarily done is design the whole thing around the family using it.
I’m curious about what happens if we start there instead.
For now, though, I have a bar mitzvah to plan.
And apparently I built myself a command center.
by alichava | Jan 20, 2026 | Organizing & Cleaning, Parenting
The start of a new year often brings an urge to reset. New plans, new structures, new intentions meant to carry us forward.
But meaningful resets rarely happen because the calendar changes. They happen when a chapter closes.
Our household reached one of those moments last week when our senior finished school. Over the past year, our daily systems quietly adjusted around that reality. Morning routines shifted. Carpools reconfigured themselves. Extra time appeared where it was most needed.
Those adjustments weren’t written down. They worked because everyone involved understood their role.
Now that the household has changed again, those systems no longer fit. What once created ease now needs to be rethought. The work ahead isn’t dramatic. It’s practical: noticing what has changed, naming what no longer applies, and redesigning routines so the household can function smoothly again.
This kind of reset is familiar in organizations as well. Teams adapt around people, roles, and constraints. Temporary workarounds become permanent. Informal systems carry real weight. When the context shifts, those systems either evolve — or begin to create friction.
January is a natural time to do this work, not because it demands reinvention, but because it offers a pause. A chance to ask:
-
What systems were built for a situation that no longer exists?
-
Where are we relying on arrangements that assumed a different set of people or capacities?
-
What needs to be clarified now that circumstances have changed?
In households, this may mean redistributing responsibilities that were once absorbed quietly. In organizations, it often means revisiting processes that only worked because someone was compensating for them.
The goal of a reset isn’t efficiency for its own sake. It’s alignment. Systems should reflect current reality, not past convenience.
When routines are redesigned with intention, they stop requiring constant adjustment. They allow people — whether family members or colleagues — to step into their roles with clarity.
The best resets don’t announce themselves. They show up in smoother mornings, fewer reminders, and a renewed sense that the structure matches the life it’s meant to support.
That’s the work worth doing when a chapter ends — and another begins.
