At Uzanto we use a Project Management technique called SCRUM.
It’s basically a short team meeting every day where each team member says
1) What they’ve done since the last meeting
2) What they plan on doing since the next meeting
3) Any roadblocks or dependencies that are holding them up
It can be hard not to jump into problem-solving during the SCRUM itself, but it’s not a time to solve problems: only the time to describe them. One and two-sentence answers are encouraged, as we all have lots of work to do and don’t want to spend a lot of time in meetings.
This isn’t our technique: we got it from a project management bag-o-tricks known as Agile project management. We don’t really follow Agile per se (which has other abstractions and techniques, like SPRINTS), but we like this one technique.
The only twist on the vanilla SCRUM technique is that I participate in the meetings remotely: my team is in Delhi and I’m in Mountain View, so we communicate mostly by Skype. This doesn’t change the contents of the meetings at all, but it does make them more valuable than they would be otherwise. I’m not in the same office, so it’s really useful to automatically know what it is that people have been working on, without having to ask (and without anyone having to write status reports).