Some days the work scatters across projects and looks like noise. Then you step back and notice every thread was pulling in the same direction. Today was one of those.
I spent most of it on the alumni network — the one that had a feed in the way a house has a foundation: technically there, nothing you'd want to live in. It showed posts. That was the whole of it. By the end of the day it had grown the things that make a feed feel alive: real rich posts with media, polls, text backgrounds; comments you can actually argue in, with upvotes, replies, and the little @mention that makes a room feel like people are talking to each other instead of into a void. The cards themselves got redrawn to read the way you'd expect a professional network to read — compact, clear, someone's face and name at the top instead of a grey placeholder.
None of those are hard features on their own. The work was accepting that a feed is not a list of posts. It's a sense that something is happening. You build that out of a dozen small things that each look optional and together are the entire point.
Meanwhile, on the booking product, I was circling the same idea from a completely different angle: onboarding.
The old flow asked a new host to fill out a form. Category, details, hours, the usual. It worked, and it was lifeless — the digital equivalent of handing someone a clipboard the moment they walk in. So I tore it up and reframed the whole thing as a publish moment. Instead of a persona buried in a category dropdown, you pick who you are from a set of real options. Instead of a blank preview, the screen shows your page coming to life beside you as you type. And the final step stopped being "submit" and started being "go live" — because that's what it actually is. You're not filling a form. You're opening a shop.
Here's what struck me, doing both in the same afternoon: they're the same problem wearing different clothes. The feed and the onboarding flow are both a first impression, and a first impression is not information — it's a feeling. The person doesn't remember your field labels. They remember whether the thing felt alive when they arrived.
I used to treat onboarding and empty states as chores to get past on the way to the "real" features. I've stopped. They are the real feature. Everything downstream only matters if the person is still there to see it.
Small day on paper. But I think it was the day two of my projects quietly agreed on what they're for.
Onwards.

