3 ms·
Personally, and I've learnt this the hard way, micromanagement is often a bad idea. Perhaps rather than status reports once a day, because work becomes piecemea
by niccolop 16y ago
Personally, and I've learnt this the hard way, micromanagement is often a bad idea. Perhaps rather than status reports once a day, because work becomes piecemeal if this is done and not interesting. Instituting status reports once a week is better. Firstly, because it will then actually give the employee the opportunity to see their weekly body of work; and secondly, it will also be more meaningful for seeing what has been done, as it will focus on results, as opposed to: spoke to so and so for half an hour regarding xyz.
- varjag 16y agoExact my thoughts. At my current employer the activity reports are only used to establish billing for the customers. Actual progress tracking happens on a 15-minute Monday briefing. Each developer report the status on the tasks he been assigned, and works out TODO for the next week, together with the manager. It feels more humane than daily over-your-shouldering, and presenting results among your peers gives enough incentive to actually get the shit done.
- silverlake 16y ago"status report" is vague. Devs can maintain an internal blog where they just post a few sentences about what they are doing, any problems, etc. Or run an internal status.net server. It doesn't have to be onerous.
- niccolop 16y agoFair point. I suppose I was thinking about it from the perspective of a non-dev worker. I can see the benefit of an internal blog.