Report the daily delta, not the total that only goes up

Even the factory’s own marketing is engineered against hype. That is what surprised me about this automation, and it is the one a marketing team should read most closely.

The factory built in public at software-factory.dev has an automation called the Tweet Drafter. It posts the factory’s updates to the public timeline three times a day. Its full definition is the Tweet Drafter automation file on GitHub (opens in a new tab).

Three posts a day, each with its own job

The trigger is three separate cron lines: 0 9 * * *, 0 15 * * * and 0 21 * * *. Morning, afternoon, evening.

Each slot has a job:

• Morning posts the planned work, the items the agents will pick up that day.
• Afternoon posts what shipped: the pull requests merged and bugs fixed since morning.
• Evening posts the day’s numbers and a short reflection on what was hard or surprising.

To do that it reads the day’s metrics file, the pull requests merged today, the open backlog and the work in progress. It also reads its own earlier posts from the day, so it does not repeat itself.

The rules at the bottom of the file

The detail worth copying sits in the rules at the bottom of the file. The automation is told to use the day’s delta numbers, not the cumulative totals. It is told to vary its opening rather than repeat a format. It is told to avoid superlatives.

Why the delta is the honest number

The delta-not-totals rule is the sharp one. Cumulative totals only ever go up, so they always read like progress, even on a day nothing happened. The delta is the honest number. It can be small. It can be zero. A factory left to its defaults will quote the flattering total every time, because the total always looks like a win.

Restraint has to be written in

Here is the lesson, and it fits anyone in marketing. A system that describes itself slides into vanity metrics and breathless language unless restraint is written in. Honest self-description does not happen by default. It is designed, one plain rule at a time, the same as any other guardrail on the line.

When your team reports its own progress, is it quoting the number that always goes up, or the one that tells the truth about today?

Further reading

• Agent observability →
• Agentic Software Factory: Advanced Team Training →