I've typed the same status update hundreds of times. "Worked on the auth refactor, still going on it, no blockers." Then I'd open the PR I'd literally just pushed and stare at the description I'd already written there, and the commits I'd already named, and think: I just typed all of this. Twice. Why.
We still do async standups, and I think they're useful. But a standup is the wrong place to first learn what your teammates did. By the time you're reading it, the work is hours old and someone retyped it by hand. The "what I did" part already exists. You generated it when you opened the PR and named the commits. Asking a developer to also type it into a separate box is asking them to be a worse version of git log.
So when we built sparQ, an open-source developer-experience suite for teams that live on GitHub, we tried to make one part of this disappear. Not the standup. The status-typing. Its first product, Pulse, is a GitHub-native project management tool, and in it each person's recent activity fills itself in from the work they're already doing, so the standups and updates sit on top of that instead of repeating it.
The mechanism is simple: GitHub webhooks in, status lines out. Everything that turned out to matter was in the details.
