Close the meeting loop

Thursday, 3pm. Monday's meeting decided to cut two features from the next release and push the timeline out by a week. Everyone in the room agreed. The transcript is clean. The notes are clean.

The PRD still lists the cut features in scope. The roadmap still shows the original date. The customer who was promised a preview has not been told. The engineering lead is writing specs against the old plan because nobody updated the spec. You are about to spend the rest of Thursday afternoon and some of Friday morning doing the work the meeting already did.

This is a normal week.

The transcript was never the problem

Nothing about the record was wrong. Nothing about the work changed. Nothing happened.

Almost every PM, founder, and staff engineer runs into this every week. Almost nobody is working on it.

What it actually is: the decisions got made, and the docs, plans, and threads the decisions were about did not change until a human changed them, days later, from memory.

What Senza does on Monday at 10:15am

Monday, 10:15am. The meeting ends. Senza has been listening to the active work, not just the conversation: the PRD, the roadmap, the sprint plan, the customer thread.

By 10:16am: the PRD has tracked changes removing the two cut features, with the rationale from the meeting attached. The roadmap has a new date proposed. The sprint plan has the new priorities proposed. The email to the customer is drafted in your voice, sitting in your outbox, explaining the revised scope and the new preview date.

You review. You edit. You commit.

Nothing happens without your approval. When you give your approval, things happen immediately, and your afternoon is still yours.

The work will get done eventually. With Senza the work will be done by COB Monday. By the time Monday ends, the decision made on Monday has already updated every doc, plan, and thread it was a decision about. By Tuesday afternoon you're still ahead of your week, not in damage control mode. One meeting doesn't blow the next three days.

Why we're starting here

I've been running this loop for years, as a founder, as a PM, as an engineering lead. The meeting is the most concentrated and most repeated version of a larger pattern: decisions get made, and the docs, plans, and threads the decisions were about sit there until someone opens them and edits them by hand, hours or days later, from memory.

Every operator I know has built private systems to stop this from happening. None of them work, because the systems depend on the same human doing the same manual propagation they were supposed to eliminate.

Senza is the first attempt I've seen at the right primitive. That primitive is durable work state, context that persists across conversations, and action proposed against the docs, plans, and threads themselves, waiting on a human yes.

The meeting is where that primitive shows up first and most obviously. The same primitive applies wherever a decision has to update the docs, plans, and threads it was a decision about.

So this is where we are starting.