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 13, 2026 | High Holidays, Jewish Holidays
On the night of September 10, 2001, I was working at the Columbia Spectator. As happened on many nights, I was the last person out of the office after sending the finalized edition to the printer.
Nothing about that night suggested how different the world would be by the following morning.
My first class on September 11 was Talmud. At that point, there was still more confusion than reliable information. We were hearing all kinds of different stories, and most of us went to class because we did not yet understand the scale of what was happening.
I was supposed to read Gemara for the first time, and I had badly misunderstood the passage. I was very new to Gemara study. Under ordinary circumstances, getting it that wrong probably would have occupied most of my attention.
Instead, I was worried about my grandparents.
They were supposed to have landed in New York that morning, and I had not heard from them. We had been trying to finalize our plans for that evening. Now I did not know where they were.
By the time Talmud class ended, ash was falling from the sky. It continued for several days. Phone service was badly disrupted, making it even harder to locate people. My grandparents’ flight had been diverted, first toward Washington and then to Richmond, where my uncle eventually drove for hours to retrieve them.
We did not yet know how many people had died or what would happen next. We certainly did not understand how the attacks would change New York, the country, air travel, national security or the decades that followed. We knew only what we could see and the small pieces of information we could gather.
That evening, I was supposed to attend the first meeting of a graduate-level literature course at the Jewish Theological Seminary called Jews in Catastrophe. The course included undergraduate, graduate and rabbinical students.
The subject of that first class was: What is a catastrophe?
It probably sounded like a reasonable academic question when the syllabus was written. The class would not meet for another two weeks.
September 11 was one of the most significant catastrophes I have experienced. It was not the first, and it would not be the last.
When the Wind Chimes Woke Me
The Northridge earthquake happened shortly after my parents divorced and after I had moved into a new place.
I had finally gotten everything arranged. My belongings had places. My room looked like my room. When so much else in my life had recently changed, having that space settled mattered.
Then my wind chimes started clanging together and woke me up.
By the time the shaking stopped, the room I had worked so hard to put together looked as though a tornado had gone through it. The sense of order I had finally created was gone in a matter of seconds.
That morning, my father did not stop to think through what was happening. He rushed to get to us. A section of freeway collapsed behind him.
When I think about the Northridge earthquake, I know the scale of the damage across Los Angeles. But what I remember most clearly is my bedroom. I remember the sound of the wind chimes and the room I had finally put together becoming unrecognizable.
I remember my father trying to reach us and how lucky he was not to have been a couple of minutes later, when the freeway collapsed completely.
That is often how I remember catastrophes. The scale of the larger event matters, but the memories that remain are very specific.
What Changed After September 11
Rosh Hashanah began only six days after September 11.
I was in my first year working with kindergarteners and first graders in a new community for the High Holidays. Suddenly, the adults were trying to make decisions about locked doors, access and security while also deciding what, if anything, to say to young children.
Synagogues did not know how to react. None of us really did.
We did not know which precautions were appropriate, how long they would be necessary or how to make families feel safe when the adults did not feel particularly safe themselves.
We were all on heightened alert in a way that, unfortunately, has become normal in synagogue life today.
Twenty-five years later, our children assume security is part of entering a Jewish institution. They have grown up with locked doors, security plans and constant attention to who is entering the building. What felt new and reactive after September 11 gradually became part of how our synagogues function.
That was one of the changes we could not yet see while we were standing in classrooms trying to understand what had happened. September 11 changed airports, government policy and national security. It also changed the places where we prayed, taught children and gathered as a community.
When our Jews in Catastrophe class finally met two weeks later, the question on the syllabus was no longer theoretical.
We now knew what catastrophe felt like.
I have continued to think about that question ever since.
When the Power Lines Came Down
In the summer of 2012, a derecho came through the Baltimore area shortly before we were preparing to move away.
The power lines came off our house.
We lost power for a week. Shabbat during that outage was one of the most uncomfortable Shabboses I can remember. It was hot, dark and miserable. There was no technological workaround and no way to reorganize the schedule enough to make the problem disappear.
We were already preparing to move, and now the basic infrastructure of the house was not functioning. Whatever we had planned for that week had to be adjusted around the circumstances we actually had.
The derecho was not September 11. They were entirely different events in every meaningful way. But once again, something I had assumed would continue working simply stopped.
All we could do was figure out what still worked and move from there.
Cooking Down the Freezers
Hurricane Sandy arrived only a few months later, after we had moved into a new community.
We were still new enough that many of our relationships were new too. Then the power went out, food began thawing and everyone had to figure out what to do with what was in their freezers.
So we cooked.
There is something strangely clarifying about a freezer full of food that will not remain frozen. You stop thinking about what you had intended to make. The immediate questions are what needs to be used first, what can be cooked and who can eat it.
One family we had recently befriended somehow kept electricity throughout the aftermath of the storm. Their home became a place where people could cook, gather and use food before it spoiled.
I have always thought God was blessing them for the extraordinary amount of kindness they showed, and continue to show, to everyone in the community. They did not become generous because they happened to have electricity. They had electricity, and their instinct was to use what they had to help everyone else.
We made lifelong friends that week.
I would not describe the destruction caused by Hurricane Sandy as a gift. But our experience of that week showed me how quickly new relationships could become a real community. We had not known one another very long. Suddenly, we were cooking through our freezers together and helping one another manage without power.
Learning How to Respond
I do not think one catastrophe prepares us neatly for another. An earthquake did not prepare me for a terrorist attack. September 11 did not tell me what to do when power lines came off our house. A week without electricity did not make another major storm easy.
But the experiences did accumulate.
Over time, I became better at recognizing when the original plan no longer mattered. I learned to start by figuring out what had actually happened, what was still functioning and what needed immediate attention. Sometimes we were in a position to help. Sometimes we needed to let other people help us.
I also learned to notice who showed up.
My father rushed toward us as the freeway collapsed behind him. My uncle drove to Richmond to retrieve my grandparents. New friends used the electricity they still had to help people cook through freezers full of food.
Knowing how to respond did not make any of these experiences less frightening or disruptive. It simply gave me somewhere to begin.
Twenty-Five Years Later
Last year, I visited the September 11 Memorial Museum for the first time. It had taken me that long to feel able to go. One of the ways I was able to think about 9/11 in the aftermath was reading all of the amazing stories of people who had missed arriving on time that morning to work and were saved. Or the people who had moved on to other things just beforehand and were no longer working in the towers.
There was something surreal about entering a museum devoted to an event I remembered so vividly. September 11 is now history taught to people who were not alive when it happened. For me, it was still the ash, the failed phones, my grandparents’ diverted plane, the Spectator the night before and the days afterward, and a Gemara passage I had badly misunderstood.
This year, the 25th anniversary fell on a Friday and led directly into Rosh Hashanah.
Rosh Hashanah asks us to look backward and forward at the same time. We reflect on the year that ended while entering a new one with no real idea what it will contain.
The liturgy does not pretend that the structures around us will always hold. Unetaneh Tokef names ways life can be upended, including fire, water and earthquake. It is difficult to hear those words without bringing our own memories to them.
We still make plans because life requires us to make plans. We arrange our homes, schedules and relationships into some kind of order. Most days, we assume the systems around us will continue to function.
Sometimes they do not.
Twenty-five years later, I still do not have one answer to the question my literature course posed. Catastrophe can be measured in lives lost, homes destroyed, infrastructure disabled and history redirected. But when I think about the catastrophes I have experienced, I remember them through smaller details.
I remember wind chimes clanging in the dark and a room that had finally been put in order. I remember a phone call that would not go through and not knowing where my grandparents’ plane had landed. I remember power lines pulled from our house and a freezer beginning to thaw.
Eventually, after the first shock and confusion, the question changes from “What is happening?” to “What do we do now?”
I am not sure any of us is ever fully prepared for the next catastrophe. Experience has taught me how to begin responding, but I would rather have a year that asks less of that particular skill.
As we enter this new year, I hope for good health, safety, and many more ordinary days than extraordinary ones. I hope we find meaning in the lives we are building, not in the catastrophes themselves. And when life does not go according to plan, I hope we have the ability to adjust, the willingness to help and people around us who will show up.
Shana tovah. May it be a good, sweet year, and healthy year. May you find the meaning you are looking for in this new year..
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 | Sep 2, 2026 | Travel
I recently wrote about why I overplan every family vacation.
Washington State was the trip that made me want to write that post.
I had built a very detailed itinerary before we left. Then we changed it repeatedly.
Some of those changes happened before the trip. We reversed the direction we planned to travel around Olympic National Park. We changed hotels. We dropped activities that looked good on paper but made less sense geographically.
Other changes happened while we were there because of weather, parking, energy, timing or simply discovering that we could fit in more than I expected.
The result was a trip that included Seattle, Mount Rainier, Olympic National Park, Shabbat in the city, waterfalls, rainforests, beaches, Boeing and quite a lot of driving.
This is the itinerary we actually did.
The basic route
We flew into Seattle and rented a minivan.
Our trip went roughly:
Seattle-Tacoma Airport → DuPont → Mount Rainier → Tacoma → Seattle → Lake Quinault and the Olympic coast → Forks → Hoh Rain Forest → Lake Crescent → Hurricane Ridge → Kingston-Edmonds ferry → Lynnwood/Everett → Seattle → airport
We stayed:
- One night in DuPont before Mount Rainier
- Three nights in Seattle, including Shabbat
- One night in Forks
- One night in Lynnwood before our final day
This worked very well geographically.
The one thing I would emphasize if you are planning something similar is that Olympic National Park is enormous. There is no road through the middle of the park. You are driving around it.
Looking at the route on an actual map before booking hotels matters.
I learned this even more emphatically when one of my early AI-generated trip maps cheerfully showed us driving across water.
Day 1: We Landed Late, So the Goal Was Just to Get South
Our flight landed in Seattle at night, and the first night was intentionally boring.
We picked up the rental car and drove down to DuPont, where we stayed at the Home2 Suites. The whole point was to wake up already south of Seattle and closer to Mount Rainier instead of starting our first real vacation day in traffic.
One small thing that helped: I had packed everyone’s pajamas and Rainier clothes together so we did not have to unpack six people’s luggage around midnight.
Nothing memorable happened that night. That was fine. The next morning was the point.
What worked: positioning ourselves for an early Mount Rainier start instead of trying to make Seattle the base for everything.
Day 2: Mount Rainier Kept Giving Us More Time Than I Expected
This was the day where all the overplanning really paid off.
We entered Mount Rainier through the Nisqually Entrance and started working our way toward Paradise. I knew the basic order of the stops, but I did not know how long each one would actually take once we were there.
We stopped at Longmire Museum, hiked to Carter Falls, saw Christine Falls, stopped at Ricksecker Point, and then went to Narada Falls.
By 11:00, we had already done all of that.
That was not what I expected.
We passed the visitor center at Paradise, but parking was completely full, so instead of circling forever, we stopped elsewhere and ate lunch.
This is where having too much research helped. I already knew what else was around. We could decide whether to go back toward Paradise, add another hike, stop at Reflection Lakes, or simply keep moving.
We ended up doing more around the mountain and then headed toward Tacoma.
The thing I kept thinking that day was: starting early changes the whole experience. By the time parking was becoming a real problem, we had already seen a lot.
That evening we went to the Museum of Glass in Tacoma for Third Thursday. We watched live glassblowing and walked the Chihuly Bridge of Glass.
Mount Rainier followed by a glass museum sounds like a strange combination.
It actually worked really well.
What surprised me: how much we had already done before lunch.
What I would repeat: the early start and the Nisqually-to-Paradise route.
Day 3: Seattle, but With a Friday Deadline
Friday had a very different rhythm because we needed to be back at the hotel with enough time to get ready for Shabbat.
We started with the Space Needle, then stopped to shop for Shabbat food and get lunch.
After that we took the monorail downtown and went to Pike Place Market.
We wandered around Pike Place for a while, then took the monorail back toward Seattle Center. Later we went to Chihuly Garden and Glass and then IMAX before heading back to the hotel for Shabbat dinner.
This was one of those days where I was constantly doing the mental math of, “Do we have time for one more thing?”
We had talked about a number of other possibilities earlier in the planning process, but once we were actually there, I cared much more about doing the things we really wanted without making the end of the afternoon miserable.
The location of the hotel made a huge difference. We could walk to Seattle Center, use the monorail instead of moving the car, and get back without spending half the day dealing with parking.
The highlight for me was Chihuly. It had been one of the things I really wanted to do before the trip, and it lived up to that.
What mattered most: being close enough to Seattle Center that we did not have to keep moving the minivan.
Day 4: Shabbat Was Part of the Trip, Not a Break From It
Saturday was slower, which we needed.
We went to shul, then spent time at the Artists at Play playground, came back for Shabbat lunch, and played games in the hotel.
Later we walked again, including Denny Park, the Spheres, and Olympic Sculpture Park, before heading back to the hotel and then to shul again.
It was a full day, but not in the same way the national park days were full.
There was no pressure to “fit everything in.”
Some of the day was sightseeing. Some of it was just sitting around playing games.
That balance felt right.
One of the things I had worried about while planning was whether staying in Seattle for Shabbat would feel like we were losing a day of the trip.
It did not.
Because we had chosen a hotel where we could walk to so much, Shabbat became its own kind of Seattle day.
What worked: choosing the hotel around Shabbat needs first and sightseeing second.
Day 5: We Were at Ruby Beach by 2:00, Which Was Not the Plan
Sunday was our Olympic coast day.
The plan had been centered around Kalaloch, the Tree of Life and Ruby Beach.
Instead, by 2:00 we had already done Lake Quinault, stopped at the ranger center, seen the Tree of Life, explored Beach 4, and made it to Ruby Beach.
This was one of those moments where I realized we had somehow moved much faster than the itinerary.
I kept asking, “What else should we do?”
But there was also a point where adding something just because we could fit it in stopped making sense.
Ruby Beach was worth staying at.
The coast was one of my favorite parts of the trip because every stop felt different. Lake Quinault was lush and quiet. Beach 4 had a completely different feel. Ruby Beach had the dramatic sea stacks.
And then there was the Tree of Life.
Very cool.
I should have worn flip-flops.
That was not in any of the planning guides.
We also discovered something I somehow had not come across in all of my pre-trip research. We collect Junior Ranger badges at national parks, but Olympic also has patches the kids could earn. There was a coastal activity booklet for one of them, so in addition to adding Junior Ranger badges to the collection, we came home with patches.
Apparently there is still more for me to overresearch.
We eventually drove to Forks and checked into Olympic Suites Inn. The room was not fancy, but it was spacious, and having a kitchen was useful before another early national park morning.
What surprised me: how much we managed to fit in before mid-afternoon.
What I would do again: Lake Quinault, even though it had not been the main focus of the original plan.
Day 6: Hoh Early, Then One of the Best Pivots of the Trip
Monday was the day I was most worried about overloading.
The plan was Hoh Rain Forest, Lake Crescent, Marymere Falls, and then Hurricane Ridge only if it still made sense.
We left Forks early because I had read too many reports about the line to get into Hoh later in the morning.
That was absolutely the right decision.
We did both the Hall of Mosses and the Spruce Nature Trail while things were still relatively quiet. Then we drove to Lake Crescent and hiked to Marymere Falls.
At that point, Hurricane Ridge was still a question mark.
I did not want it to become one of those things where everyone is exhausted, we are two hours behind schedule, and I am still insisting we go because it is written down on the itinerary.
So we checked the conditions.
The weather was gorgeous. Clear skies. Great visibility.
We went.
Hurricane Ridge turned into one of the best parts of the entire trip.
The views were incredible. And because I had always treated it as something we would do if it made sense, rather than something we were obligated to accomplish, going up felt like a really good decision instead of one more thing we were dragging ourselves through.
Afterward we drove toward Kingston and took the Kingston-Edmonds ferry.
I had spent far too much time researching ferry schedules before the trip. Naturally.
But after several days of driving, getting out of the car and standing outside on the ferry was actually a really nice way to end the Olympic portion of the trip.
What mattered most: getting to Hoh early.
Best pivot: keeping Hurricane Ridge optional until we knew the weather and timing were actually worth it.
Day 7: Boeing Was the Anchor, and the Rest of the Day Just Happened
Our last day did not start nearly as early as I had planned.
At that point, I was okay with that.
We had one fixed thing: the Boeing Future of Flight tour.
We did the tour and spent time afterward looking at the planes and exhibits. Then we headed toward Seattle and stopped at the Fremont Troll.
And then came one of those extremely specific things that ends up on a family vacation.
We had heard there was a Boeing plane sitting between buildings near Denny and Stewart Streets.
That sounded weird enough that we wanted to see it.
So before heading to the airport, we went.
It is exactly what it sounds like.
A plane.
Between buildings.
Completely strange and very cool.
There was no grand trip-planning logic behind that stop. We had time. It was close enough. Somebody had told us about it. We were curious.
That was enough.
It was also a fairly appropriate way to end a trip I had spent weeks planning in enormous detail.
Boeing was worth building the day around.
What made the ending fun: having enough flexibility left to follow something random.
Packing lunches made the national park days easier
One of the least exciting pieces of our trip planning was also one of the most useful: we packed lunch. A lot.
With six people, I did not want our national park days organized around the question of where we could find food at noon.
We carried sandwich supplies, snacks, water and other easy food with us. That meant we could eat when it made sense instead of leaving a trail, giving up a parking spot or driving somewhere simply because everyone was hungry.
At Mount Rainier, when Paradise parking did not work out the way we expected, we could just stop and eat.
On the Olympic Peninsula, we could stay at a beach or keep moving toward the next stop without building the day around finding lunch.
There were certainly prettier picnic locations than others. Sometimes we were basically just eating where it was convenient.
That was fine.
Having food with us gave the itinerary another layer of flexibility, and it also made keeping kosher while we were moving through places with limited food options much simpler.
If I Were Planning This Trip Again
I would not copy our itinerary minute for minute.
That would sort of defeat the point.
I would keep the overall structure, but I would still go into each day knowing that something was likely to change.
If Mount Rainier is a priority, give it a full day and start early.
If you are visiting Hoh in the summer, get there early.
If you are driving around Olympic National Park, spend some time looking at the actual geography before you choose hotels. The park is enormous, and there is no convenient road cutting through the middle of it.
If something like Hurricane Ridge depends heavily on weather, keep it optional until you know what the conditions actually look like.
Pack lunch.
And research more possibilities than you expect to use.
You may never need most of them.
That is fine.
Sometimes the extra research gives you a backup when the parking lot is full. Sometimes it lets you add Lake Quinault because the day is moving faster than expected. Sometimes it helps you recognize that the thing you planned to do is no longer worth doing.
And sometimes it means you have enough room left in the trip to go look at a random airplane sitting between buildings on your way to the airport.
For us, that is part of what makes all the overplanning worth it.
What I would tell someone planning this trip
I would not copy our itinerary minute for minute.
That would defeat the point of the way I plan trips.
Instead, I would start with the pieces that matter most to your family.
If Mount Rainier is your highest priority, give it a full day and start early.
If you are visiting Hoh in summer, get there early.
If you are driving around Olympic National Park, look carefully at the geography before choosing hotels.
If something like Hurricane Ridge depends heavily on weather, keep it optional until you know what conditions actually look like.
And if you are traveling with a family, research more possibilities than you expect to use.
You may not need most of them.
That is fine.
Sometimes the extra research gives you a backup when the parking lot is full.
Sometimes it lets you add a beach because you are two hours ahead of schedule.
Sometimes it tells you when to stop adding things and just enjoy where you are.
And occasionally it leads you to a random airplane sitting between buildings on your way to the airport.
For us, that is part of what makes the trip work.
