What went well

This week was a reminder that the work is real, the demand is real, and the execution bar is also very real.

Not a victory lap. Just the kind of progress that tells me that at least the work I’m putting in is not only showing itself in the quality of deliverables, but in the viability of Zibby as a concept and myself as its steward

Old peers, mentors, colleagues. I went in looking for feedback on Zibby and came out with something better: people started telling me how it could actually change their lives. And then, almost inevitably, they started sharing their own family lore. That’s still my favorite signal. If the idea lands, people don’t talk about features. They tell stories.

This is a hard nut to crack. It’s emotional. It’s personal. It’s not “growth hackable” in the dumb way. But it’s encouraging seeing other builders find meaning in the challenge. Also, the economics are there if you get the habit loop right.

This one mattered. Zibby is a product about identity, memory, relationships, legacy. That means we will need emotional hooks. We will need habits. We will need to be intentional about what we’re asking people to do and how often we’re asking.

So I asked the question directly: can you build this into a habit in a healthy way, or does it drift into something destructive?

The answer was: yes, it can be healthy. Also yes, there are red lines.

The red line is rumination.

That’s the line I’m not crossing. If a product like this pushes people into spirals, that’s a failure, even if the metrics look great. Part of building in public for Zibby is that trust and safety, privacy, and community welfare are going to be visible, not buried in a policy page. More to come as we do the work.

Also, one of the most surprising (and honestly motivating) findings from her research: in studies of hundreds of adolescents, basically everyone wanted to hear more family stories from their grandparents. Not “some.” Not “half.” Almost all of them.

Operationally unsexy. Strategically necessary. We got in to Azure’s Startup program but with that, it made sense to create a new resource group, Entra tenant, etc. Yeah there’s work arounds to keep things as they are, but it was a good time to see what it takes to take to do a clean deploy. If nothing else to validate our bicep and deploy process as will be needed when we scale out of a dev instance.

There were lessons learned. Mostly order of operations of services and what I should just script instead of fighting the system.

Missed a gym day. No yoga. I can rationalize it, but I’m not going to. When sleep goes, everything else gets more expensive.

This is not a “nice to have.” Onboarding is the front door. It’s also the first real test of whether Zibby feels easy, safe, and worth repeating. If I want testers, and if I want growth, this has to be tight.

I wanted more product screenshots, but I didn’t have high-enough quality seeded content ready in the new tenant. That’s on me. Investors (and testers) don’t buy abstraction. They buy clarity.

I didn’t hear back from Active Senior groups in Austin, and a lot of cold outreach for interviews got ignored or trashed. I need to stop treating silence as a surprise and start treating it as the default. If I want “yes,” I need volume, better targeting, warmer intros, and a tighter value exchange.

Zibby can only “win” if it makes people’s lives better in real ways, not if it just makes them come back.