<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Working in different time zones?  - BrainReactions.net Online Brainstorming</title>
    <link>http://www.brainreactions.net/brainstorms/1414</link>
    <description>BrainReactions.net Online Brainstorming</description>
    <pubDate>Tue, 24 Apr 2007 19:43:18</pubDate>
    <generator>BrainReactions.net Online Brainstorming</generator>
    <webMaster>webmaster@brainreactions.net</webMaster>
    <ttl>20</ttl>
    <item>
      <title>4. You are either a global org or you aren't: If you sell service to other time zones, you are committed to support them - deal with it! If you are working "construction" across timezones, the Veriphone model seems to work well; Make sure you have at least 3, ideally 4, centers equidistant around the globe where the end of one "day" overlaps the beginning of the next region's "day." Daily handoff mtg</title>
      <link>http://www.brainreactions.net/brainstorms/1414</link>
      <guid>15590</guid>
      <pubDate>Tue, 24 Apr 2007 19:43:18</pubDate>
    </item>
    <item>
      <title>3. Use Skype to keep everyone conferenced at least once a day.</title>
      <link>http://www.brainreactions.net/brainstorms/1414</link>
      <guid>15491</guid>
      <pubDate>Fri, 20 Apr 2007 03:37:50</pubDate>
    </item>
    <item>
      <title>2. Separate tasks into two categories: one requiring night-shift real-time work and the other requiring just on-time delivery, but not real-time interaction with the client. Create a smaller team to handle the night hours for the real-time interaction stuff.</title>
      <link>http://www.brainreactions.net/brainstorms/1414</link>
      <guid>15490</guid>
      <pubDate>Fri, 20 Apr 2007 03:28:59</pubDate>
    </item>
    <item>
      <title>1. Have everyone collaborate online in non-real time so that the time shift is a non-issue.</title>
      <link>http://www.brainreactions.net/brainstorms/1414</link>
      <guid>15489</guid>
      <pubDate>Fri, 20 Apr 2007 03:27:55</pubDate>
    </item>
  </channel>
</rss>
