Management tricks I like the most are the ones which require little to no efforts from your end, but give you a lot in return. Here I want to share a quick trick which can help to get 20% team performance improvement for almost nothing.
The very classic approach used my many orgs is Scrum or some of its variations. This classic process framework includes the following rituals:
Some companies use a slightly different approach, some can add something on top (not remove though), but overall these is it.
In my experience, the step that takes most of the time is estimation. Planning poker is used to check if everyone is understanding the task complexity correctly, and if there's a wide spread (one developer says it is a 5 minute fix and another one is saying it will take at least a few days) you should start conversation and figure out pitfalls. Developers usually use story points, which is an abstract unit used to describe task complexity. The sum of story points is later used to give some time estimation (using some historical data, something like "In our org 1 SP is usually 2 hours of real time"). So you will spend the whole day in a week playing planning poker, discussing story points and trying to figure out how to develop all the core features before the deadline.
This process, however, is not very well optimized and cannot be. Assuming you are working in a weekly sprints, you will have to spend 20% of your time just to get a rough estimate. With other rituals, like retro and company meetings, your team will have about 3 days for the actual implementation. But there's a good alternative.