Skip to content

Weekly Reports

MattDodsonEnglish edited this page Nov 6, 2020 · 2 revisions

Many companies say that they have "Minimal Bureaucracy", but not everyone explains what does it mean in practice. We do.

Reports on Fridays

Our Minimal Bureaucracy™ works like this: once a week, on Friday, you need to write a short report about what you did the past week. These reports are written by all of our employees(yes, even our managers) and are automatically published in Slack over public channels. The reports help us track project progress and keep our colleagues informed.

Reports are written in English in a free form style. The main requirement is that the report is clear about what results have been achieved. For example:

  • "worked on tests for users registration" <- not good, we can't see the result. It is not clear whether this work is finished or not;
  • "covered user registration feature with tests, except Forgot Password form" <- fine, the result is visible.

And what do I write if...

Sometimes the question arises - what to write if there haven't been any concrete results, or if the results aren't significant? This happens, and it's no big deal. Just write what's gone on. You can add some comments, but you don't have to; this is at your discretion. However, we strongly ask that you don't just disregard writing the report. Having no report at all creates uncertainty and discomfort for your colleagues. Write at least one line and don't leave your colleagues in the dark.

If Friday is a non-working day...

If Friday is a public holiday this week or if you are starting your holiday and are taking over this Friday, then write a report on the last working day before Friday.

If Friday doesn't work out...

If something comes up before you write the report, just write it as soon you can the next time you come online.


ProTip™: If you've just joined our team, please take a look at the reports we're writing. It'll help you figure out who's doing what for us.

Clone this wiki locally