Daily reports your team will actually write
Every startup tries daily updates at some point. A channel is created, a template is pinned, and for a week it works. Then the updates get shorter, the template gets ignored, and by week three only the most dutiful person is still posting into silence.
The problem is rarely discipline. It is that the update goes nowhere. Nobody signs it, nothing is computed from it, and the author gets nothing back. Here is what we changed with the teams using ShipWoven, and what stuck.
Make it a form, not a message
A message invites prose, and prose invites skipping. A form with four fields takes two minutes on a phone and gives you data you can add up. The form that survives looks like this:
- What did you work on? One or two lines. The pickers below carry the detail.
- Epic and stories. Picked from Jira, not typed. This is what lets hours land on the right project later.
- Hours or a from/to time. Keep whichever your team is honest with.
- Progress, as a percentage of the thing they are on. Nobody is precise about it, and that is fine: the trend is what you read.
- Blockers, optional. The one field a founder reads first.
Add a field for the issues someone spent time on when you run an issue flow. Leave it optional, so it is only filled on the days it matters.
Sign it, up the chain
A report that nobody signs is a diary. A report the team leader signs is a record, and the act of signing is what makes leaders read. The chain is simple: the leader signs the members' reports, the manager signs the leaders', the super admin signs whatever is left. Sending a report back requires a note that says why. That one rule does more for report quality than any template.
Count what is missing, not just what arrived
The most useful number in reporting is the one nobody computes: reports that should exist and do not. To get it, the system has to know each person's working days, their hours, their days off and the public holidays of their country. With that, a missed day is a fact, not an accusation, and a "behind on hours" is measured against a schedule the person agreed to.
Give something back
People keep writing when the report feeds something they can see. In ShipWoven that is three things: the roadmap of what the company works on now, with their tickets first; their own performance page; and, when the company chooses to show it, their points. A signed report is worth points. A missed week costs some. A guide, generated from the actual rules, explains how. That loop is what turns a ritual into a habit.
What to avoid
- Long templates. Every extra field halves the number of people who fill it.
- Reports as performance reviews. They are a log of work, read weekly. Use them for trends, not for a single bad day.
- Letting anyone sign anything. The sign-off has to follow the organisation, or it means nothing.
If you want to see the form and the sign-off chain on your own team, tell us about it. The setup takes an afternoon.