If the goal is to produce a loosely-coupled organization, should one prioritize starting with a distributed team?
@skamille that's a really interesting question, and I want to hear what answers you get (but don't know if I have a useful answer myself).
-
-
@avibryant am reading a paper that talks about loosely-coupled orgs mirroring OSS communities and does in fact say distributed is part of it -
@skamille@avibryant note that distributed across multiple offices isn't the same - remote workers (offices of one) have diff implications
End of conversation
New conversation -
-
-
@avibryant@skamille in my mind the key thing is having a forcing function (remote/distributed by geo and timezone) on the async parts -
@avibryant@skamille likely there are other ways to prioritize async, which to me is the key to loosely coupled. -
-
@avibryant@lxt maayybe. I'm really not sure that's exactly true.
End of conversation
New conversation -
-
-
@skamille things I've seen distributed teams do: reduce meetings; increase documentation; increase realtime chat; increase code review...Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.