Ask HN: Bootstrapping a remote team in different timezones, looking for tips
3 comments
Allow each to work in their own way.
Discipline everyone to use a WRITTEN not VOICE work flow. Zooms or stand ups or whatever for clarity, not information exchange.
If you have a minimal writing based workflow (tickets, or “document driven deliverables”) everything will develop its own rhythm and work will get done at …some… pace.
It is where you cannot attribute accountability, or fine tune communication failures that you will experience your productivity attrition.
Discipline everyone to use a WRITTEN not VOICE work flow. Zooms or stand ups or whatever for clarity, not information exchange.
If you have a minimal writing based workflow (tickets, or “document driven deliverables”) everything will develop its own rhythm and work will get done at …some… pace.
It is where you cannot attribute accountability, or fine tune communication failures that you will experience your productivity attrition.
Passer plutôt en scrum avec un horaire de standup meeting. Fixer des objectifs plus petit, smart telle est la clé avec un cloud partagé et il faut un garde schiourme
Send me an email (bio) - I will be happy to share my experience on this!
We will of course have async tools in place; slack , google hangouts etc and our development model will support a remote team (CI, Kanban, document everything).
We might have folks in Europe and Seattle, so as some individuals go offline others will start. If we hire in Asia this will add even more of a further reach.