The founder is the duct tape

Happy Sunday!

Stepping back from the fulfillment work for even a few days taught me something I should have seen earlier.

Things drift. Not in a dramatic way. Just quietly, in the margins.

Decisions lose their edges. Ownership blurs. Nobody notices until you look up and realize the work has wandered off course.

The lag I couldn't feel from inside

We run a weekly ops meeting on Mondays. It's where the team gets on the same page about what shipped, what's stuck, and what's coming next. That's the meeting where I first noticed the drift.

We'd sit down, open the doc, and half the room would be trying to reconstruct what we'd talked about the previous week.

Who owned what. What got moved. Whether the thing that was supposed to ship actually shipped, or if we'd quietly agreed to kick it.

Nobody was slacking. Everyone was working hard.

But the feedback loop between "we decided this" and "we checked if it happened" was a full seven days long. By the time we got back to it, the decision had already evaporated.

The founder was the duct tape

When I was in the work every day, I didn't feel the lag. I was the human glue.

I'd see something slip in a Slack thread on Tuesday, nudge it Wednesday, and by Friday it was back on track without anyone formally tracking it.

That's not a system. That's a founder duct-taping the system together with their own attention.

The moment I stepped back, the duct tape came off, and the gaps were embarrassing.

Talking isn't a forcing function

So I stopped pretending the weekly meeting was the problem. It wasn't a cadence issue. It was a memory issue and an ownership issue.

We'd leave every meeting with a vibe of alignment and no actual record of who was accountable for what, by when. The meeting felt productive because we were talking.

Talking isn't a forcing function.

What we changed

We shifted to Monday, Wednesday, Friday standups. Ten minutes. Explicit owner on every single item.

The rule is simple: if your name isn't on it, it doesn't exist. If your name is on it, you're reporting progress in 48 hours, not seven days.

No wandering agendas. No "let's circle back." The meeting ends when the last owner has said their piece, which is usually before the ten minutes are up.

The quiet surprise

What I did not expect was how much quieter the work got. Fewer surface-area issues bubbling up in random Slack threads. Fewer "wait, I thought you were doing that" moments.

The short loops catch drift before it compounds. By the time something hits the standup, it's already close to resolved.

The meeting is not where work gets done. It's where we make sure work is actually happening.

The real lesson

The founder sets the pace, and pace is not the same as urgency. Pace is the rhythm of check-ins. The tightness of the loop between decision and verification.

You can have a team working at full speed and still drift, because drift isn't a speed problem. It's a feedback problem.

Tighten the loop, and the work carries itself.

I don't think this is a permanent structure. Six months from now I'll probably need to rebuild it again.

The team will be different. The work will be different. The seams that matter today won't be the seams that matter then.

That's fine. The real lesson isn't MWF standups. It's that the moment you step out of the work, the cracks become visible, and the honest thing is to close them before you step back in.

Talk soon,

- Raymond

P.S. What's the longest your team has gone between syncs before things start drifting? Reply — I'm curious where the real breaking point is.