Teams Weekly team report
The weekly team report is a ritual that is simple to set up and hard to keep alive. Most die for one of two reasons: they are not read, or they are filtered by the level above before reaching where they would have been useful. The outline therefore matters much less than what is done with it.
Four questions, and a few minutes.
A longer outline produces rarer reports. It is the only trade-off that counts.
| Question | What is expected | Why it is there |
|---|---|---|
| What moved forward | Two or three lines, not exhaustive. | Place the week, and give context for the rest. |
| What got stuck | One blocking point, or the absence of a blocker. | It is the most useful line, and the one people do not dare to write unless invited. |
| What is expected from someone else | An approval, an access, a decision. | Bring dependencies up before they become delays. |
| The tone of the week | One free sentence, with no scale or checkbox. | Let people say what no checkbox captures, in the person's own words. |
SOURCE Outline drawn from orgatypik practice, tested in IT services companies. It can be reused as it stands.
Why weekly reports die.
Four causes, and none is fixed by changing the form.
They get no feedback
Writing every week into the void stops by itself. A report read and commented on every other time is enough to keep the ritual going.
They are filtered on the way up
The manager summarizes, rounds off, removes what exposes them. What reaches management is a version, not the voice.
They are too long
A twelve-field form takes a quarter of an hour. It will be filled in for three weeks, then rushed, then forgotten.
They are used to evaluate
As soon as a report feeds a rating, it becomes an exercise in communication. People write what they are supposed to write.
The draft is private, sending is an act.
Until it is sent, the report stays strictly private: no one but its author can read it, neither the manager nor management. It looks like a technical detail and it is a condition of sincerity, because people do not write the same thing in a document when they do not know who is looking at it while it is being written.
Once sent, it is read at two levels: by the manager, to whom it is addressed first, and by the human resources department. This is not a check on the manager: it is the guarantee that the voice does not depend on a single relay, and that the case where the manager is themselves the subject is not a blind spot.
And it is never rewritten. What is read is what was written, in the person's own words. This is what we call operational commitment management, applied to the human thread rather than the contractual thread.
No one is rated, nothing is scored.
A weekly report produces no index, no ranking, no indicator attached to a person. Nothing analyzes the tone of a text, nothing infers a state of mind from it, nothing claims to anticipate anything.
What the system produces is dated writing, read by humans. Its value does not come from processing: it comes from the fact that it exists, that it is dated, and that it is read by someone other than the person concerned. It is also what makes it possible to reread later: six weeks of reports in a row say something that none of the six said alone, without any calculation having been done on them. The processing of personal data is described in the privacy policy.
In pylotik.
The report is not a separate form: it lives next to the project the week is about.
It is written through the week
Saving is automatic, with no button. You can note on Tuesday what got stuck on Tuesday, rather than remembering it on Friday.
It covers a real scope
The projects the person worked on this week are known. There is no need to restate them.
It is cross-read with the management review
The manager writes what they observe on the same week. See team engagement.
It can be reread over time
Six weeks of reports from the same person are read in a row. That is where a weak signal stops being weak.
The full tour is on the product page.
What we are asked about the weekly report.
What should go into a weekly check-in?
Four things: what moved forward, what got stuck, what is expected from someone else, and the tone of the week. Beyond that, the outline becomes a form and the ritual fades.
How long should it take?
A few minutes. It is a design criterion, not an estimate: a report that costs a quarter of an hour will be rushed after a month, and a rushed report says nothing.
Who reads the report?
The manager, to whom it is addressed first, and the human resources department. Reading at two levels prevents the voice from depending on a single relay.
Is the report used for the annual appraisal?
No, and that is essential. A report that feeds a rating becomes an exercise in communication. No one is rated, nothing is scored: the report is a listening channel, not an appraisal instrument.
What if no one writes?
First check whether anyone reads. Abandonment almost always comes from the absence of feedback, rarely from the effort of writing. A comment from the manager every other week changes everything.
Can you write that you are not doing well?
That is precisely what the fourth question is for, left free and with no scale. The draft stays private until it is sent, and nothing is reworded: what is read is what was written.
Going further.
- Team engagement: the two accounts, and what their gap reveals.
- The workload plan: the overload that lasts, read as a signal.
- Operational commitment management: the definition of the category.
- The privacy policy: what is collected, and what is not.