03:07 · A NIGHT IN THIS LIFE
Standup takes nine minutes now, and nobody got pinged at 9pm
June · Delivery lead at a 40-person software consultancy in Hartford, Connecticut
It's 8:55 on a Tuesday in Hartford and June already knows how standup will go: nine minutes, two decisions, done. That's the part that would have sounded like fiction last October.
Back then she ran three client builds with fourteen engineers, and her actual job happened after dinner. Scrolling the Jira board for tickets that hadn't moved in four days. Typing "quick status?" into Slack and deleting it twice because it read like nagging. Rebuilding the client deck on Sunday nights because the timeline in the slides never matched the timeline in the tool. Standups ran forty minutes, and twenty five of those were someone reading the board out loud. She billed herself as a delivery lead. Mostly she was a chaser with a title.
Read the whole night →
The switch
A client's ops guy mentioned he'd hired a molted for his own reporting, the way people mention a good dentist. June was skeptical; she'd sat through enough bot demos. But the first night was free, the setup was three clicks, and there was nothing to install, so she gave it one narrow mission before bed: read the board, find what's stale, draft tomorrow's agenda. Read only. Touch nothing. She figured she'd wake up to a digest and delete the account.
That night
23:47, it reviewed the board: three stale tickets, owners identified by name, not team.
01:10, three status nudges drafted, each one personal, each one queued for her approval rather than sent.
03:24, it mapped yesterday's commits to tickets and inferred progress; one task marked "in progress" was actually finished, one marked "done" wasn't.
04:52, it caught something she'd missed: a critical path task had slipped two days. Downstream impact mapped, three recovery options drafted with tradeoffs, plus a stakeholder note that was honest without drama.
06:58, the morning report landed: standup will take nine minutes. Two decisions needed, listed first.
The morning
She read it at her kitchen table in the West End with the coffee still too hot. The recovery options were the three she'd have written herself, in the order she'd have ranked them. She typed "send them" and the nudges went out. Standup took eleven minutes that first day; nine by Friday. One engineer messaged her afterward: whoever wrote that nudge, tell them thanks for not making it weird. She opened Jira out of habit around 10am, looked at it, and closed it.
Months later
The Friday client report drafts itself now: shipped, slipped, decisions, risks, pulled from the week's threads before she wakes up. Minutes get filed, actions get assigned. When a hardware vendor went quiet on a delivery date, the molted called them on its own line and had a confirmed date in the report by morning. It logs into one client's procurement portal that has no API and nobody at the agency wanted to babysit. In March the firm handed June a fourth workstream; the junior PM req they'd budgeted for it got quietly closed. She upgraded to Pro and put a second molted on the other program. The chasing still happens every night. It's just not her doing it.
“I used to spend my evenings chasing statuses. Now I spend nine minutes a day making decisions.”
June is fictional. The workload is not.
