Part of an ongoing series on ordinary workspace friction, and what happens when you point an agent at it.
Every Friday, someone on your team closes their laptop an hour later than everyone else, because they still have to write the status update.
They dig through Jira tickets to remember what actually got closed this week. They scroll old Slack threads looking for the message where a blocker got resolved, or didn't. They rack their memory for the thing that shipped Tuesday that they'd already half-forgotten. Then they write it up, and it says roughly what everyone in standup already knew. It often ships Monday morning instead of Friday afternoon, because Friday afternoon is when the actual work runs long.
That's the ritual. It happens at most companies, most weeks, and almost nobody questions it.
The update is real work, and it's the first thing cut
Writing a good status update takes real effort: pulling together scattered facts, deciding what matters, phrasing it so a stakeholder who wasn't in the weeds can follow it. That's not nothing. It's just not the thing anyone was hired to do.
So when a deadline gets tight, the status update is the first casualty. It's understandable: shipping the feature matters more than describing the feature. But that trade has a cost nobody tracks. Nobody logs how often the update slips from Friday to Monday. Nobody logs how often it skips a week entirely, or gets rushed into three vague bullet points nobody trusts. Because nobody measures it, nobody treats it as a problem worth fixing. It just quietly keeps happening.
And the update itself rarely earns its hour. Most of what goes into it, the team already saw play out in real time: the PR that merged, the ticket that got blocked on a design review, the deploy that slipped a day. The person writing it isn't producing new information. They're reconstructing information that already exists, scattered across the tools the team used all week, into one paragraph someone can forward to a stakeholder.
The kind of system we'd build
This is the kind of problem we like: not a big transformation, just a specific hour of real work that keeps getting done badly or not at all.
Here's what an agent for this looks like. It watches the tools your team already works in, all week, not just on Friday: what merged, what got marked done, what's been sitting in "in review" for days, what got flagged as blocked and why. It doesn't wait to be asked. By Friday afternoon, before anyone starts digging through tickets, it has a draft update ready: what shipped, what's stuck, what moved, in plain language.
Nobody starts from a blank page. The hour of reconstruction, the part where someone plays detective across Jira and Slack and their own memory, is gone before it starts.
The agent drafts. A person still decides what it means
The agent doesn't replace the person who owns the update, it replaces the part of the job that was never really judgment. It can tell you a ticket moved to "blocked." It can't tell you whether that blocker is a real risk to the deadline or a two-minute fix waiting on a reply. That's still a human call, and it should stay one.
So someone still reads the draft, corrects what the agent got wrong, adds the context only a person on the team would know, and decides what's worth flagging up versus what's routine. The difference is where they start. Instead of an hour spent finding the facts, they spend a few minutes checking them and adding judgment. The update ships when it's supposed to, because the hard part was already done by Friday afternoon.
A question worth sitting with
Next time you write, or read, a status update, look at it closely. How much of it is genuinely new information, something nobody on the team had already seen? And how much of it is just restating what everyone already picked up in standup, in Slack, in the commits themselves?
If the honest answer is "mostly restating," that's not a knock on whoever wrote it. It's a sign the hour they spent was never really about judgment. It was about assembly. And assembly is exactly the kind of work worth handing to something that never gets tired of digging through tickets on a Friday afternoon.