4 ms·
all i can say is two things: 1. someone has to be the boss, the person who makes the final decision for the group. it may not always be their own first choice
by beachstartup 11y ago
all i can say is two things:
1. someone has to be the boss, the person who makes the final decision for the group. it may not always be their own first choice, but after taking input from the group, the decision must be made, and followed. finding this person is hard because they have to override their own opinion sometimes. although for the right group leader, the best decision for the group/goals is their first choice by definition.
2. meet every single day first thing in the morning and go over open issues, blockers, eta, and priorities. note that these are not problem solving sessions, just identification sessions. you can call this agile, a stand-up, a ticket review, whatever. just makes sure it happens. once you get into the groove you can usually keep it to 15 minutes. every effective organization i've been in does this or something very similar (maybe every other day). i've seen some small groups do this 2x a day. once or twice a week is not often enough.
you will find that doing this actually reduces the meeting workload overall, especially when combined with #1.
- SyneRyder 11y ago> meet every single day first thing in the morning and go over open issues, blockers, eta, and priorities... every effective organization i've been in does this I was going to counter this and say not everyone works best with daily meetings... until I saw your username, "Beach Startup"? Because remote work is the counter-example I would have given. Do you work remotely / from a beach & still have these synchronous morning meetings every day? I agree it's important for team members to always be aware of open issues / blockers / eta / priorities, but I'd suggest that's what project management software is for. Team members can work in their own timezones / schedule and still check the issues / priorities themselves daily. Curious to hear if your experience is different.
- deleted 11y ago[deleted]
- beachstartup 11y agoi view the perk of remoteness and a flexible schedule as a trade off to be more rigorous about the few times you actually do have structured communications. you take the opposite view.
- SyneRyder 11y agoFascinating, I genuinely expected asynchronous communication to be almost necessary when working remotely, especially across timezones. Thanks for the great response!