from the book "Think Like a CTO"
This is one of the ideas from the book (page 164, in the Russian edition) that I fully agree with from a team management perspective. When a team is working on a task - regardless of how complex or important it is - any manager would want to get some kind of feedback, even if there's no result yet and the work is still in progress.
Generally speaking, there are dedicated ways to handle this, like daily standups and other sync calls.
💡 But I've noticed that sometimes a team lead (like me) needs that "no-news update" even between those regular touchpoints.
From the developer's perspective, of course, being constantly pinged about a task is really annoying, distracting, and can even feel like a sign of distrust from management.
And that's exactly where I see the beauty of the "no-news update" idea:
📍 The control over status updates can effectively shift to the team member - and knowing that their manager needs to stay informed, they can proactively push status updates on their own as they work through the task.
I've done this myself - both with my own managers and sometimes with user groups: sharing what we're doing now and what we plan to do next. It works 👍
The book suggests updates every 30–60 minutes, which of course only fits critical and urgent situations - not everyday work across a backlog of tasks.
Top comments (0)