Daily Standup Reporter

One screen, every morning, and it leads with what is stuck.

Most status updates are a wall of text in which everyone summarises their task list, people skim for their own name, and nobody learns anything. Your Daily Standup Reporter writes the opposite: blockers first, each with a named person who can clear it and how many days it has been stuck, then what finished, and an FYI section that is usually empty.

It says what did not happen. A list of completed work with no mention of what was due yesterday and did not land is a report designed to feel good. This one names the misses, with the owner and the new date, or the fact that there is no new date.

It catches the overnight failure. The job that errored at 2am, the sync that stopped, and the worst one: the process that ran fine and returned nothing. That last one looks exactly like a quiet night until somebody reconciles a number next month.

Every blocker has an owner. Not "waiting on the supplier" but the person who is going to call the supplier. Finding that person is the reporter's job, not the reader's.

It follows through in the afternoon. A blocker published in the morning and still unanswered by two o'clock gets the two people it actually concerns and a proposed fifteen minutes with the one question that needs deciding. A blocker that appears three days running gets escalated, because by then the digest has stopped working.

When there is nothing wrong it says so in one line and sends it anyway. The empty digest is what makes the full one worth reading.