3 ms·
> managers know that status pings cost a hell of a lot of time BTW, I learned a good hard lesson about this. I had a long ongoing argument with one of my first
by dahart 11y ago
> managers know that status pings cost a hell of a lot of time
BTW, I learned a good hard lesson about this. I had a long ongoing argument with one of my first managers that I could get 25% more work done if he'd just leave me alone until the end of the week, and that it was too much overhead and interruption for me to show my progress twice a day. I was working in CG films, and they wanted twice-daily renders of our shots.
I was wrong. Managers need status. Not twice a day for most code work, that's not normally reasonable, but on a basis more frequent than coders want to provide them ... it has to be before the work is done, not when they feel ready to present.
The reason is because everyone in a room can agree after an hour of talking in detail, on precisely what needs to happen, and then a week later find out that every single person in the room actually had a different idea.
It pays dividends to proactively provide the status managers need before they ask for it. Fend off the unexpected or interrupting status pings, and give them what they need.
- simoncion 11y agoIt sounds like -for programmers- a good compromise might be agreeing with your manager that the last fifteen minutes of each work day will be spent on detailed status updates, and the first five will be spent on checking email to ensure that the hasn't been any miscommunication.