We have a startup in Germany, which should work with their employees remotely. It's a startup, doing online paid services for foreigners willing to come to Germany. We have employees for each country, native speakers, and it's very hard to find all of them in one city to be able to work in an office space. Therefore we can only work remotely. But we can't communicate, solve problems properly and effective online. We hired some of them from their country, thousands kms distance from Germany. When we hire, we must explain the workflow which is very hard explaining it online. We used:<p>Trello
Skype
Mobile tel
Complex explanations are drawn in Photoshop(!!!) sent via emails<p>None of them were useful and everytime when I hire someone I try to fly there and explain the work etc. Can you please list your favorite tools communicating your remote employees. This thread can also be used as a reference for others having remote employees or freelancers.
I work at Cheezburger and our group is spread around the country with one person even working in Poland. Here are the tools we use:<p>Campfire (casual group conversations.. basically our "watercooler")
Skype (Main IM program for important questions, voice chat, video chat)
Ventrilo (Great for casual chat throughout the day.)
Google Chat (Some people use this in addition to Skype... dunno why!)
Webex (Whole company dev meetings/screen sharing)
Google Sites (Company blogs/information sharing)
Google Groups (For email lists)
Gmail
Fogbugz Wiki (dev work processes)
PivotalTracker (organizing team work)<p>For me personally having never been a remote worker before, it works so well that I don't feel like a remote worker. As you can see that's an awful lot of technology though. We're constantly trying new things to consolidate but the tools that do everything seem to just do it poorly.
To plug my own product: try <a href="http://iDoneThis.com" rel="nofollow">http://iDoneThis.com</a><p>We make it easy to know what everyone is getting done. Tracking and accountability are two of the biggest problems we've seen with remote teams.<p>Often work with remote employees requires asynchronous communication because of time differences, making it difficult to sync up via Skype or Hipchat (two great tools).<p>With iDoneThis, we email everyone and ask what they did. They just reply and it goes into a central place. The next morning, everyone gets a digest with what they did.<p>It's been a big help for us sync up with our remote developers who are freelancing for us. We use it along with Skype, Campfire, Trello, and Google Groups.
At woboq here we are both using IRC with an IRC channel for the two of us.
As IRC client we use Quassel which is an IRC client that keeps you connected on IRC and you can attach/detach from it. This means you never lose any message and can read the backlog.<p>We also use a private Wiki together if some information needs to be more persistant than a chat log.<p>This worked well for the periods when we are not in one office (the periods had a maximum length of 3 weeks so far).
It also helps to have this when working at the same place: You can keep distractions low by just writing what you want instead of always using real verbal communication.
There is a gap between IM/chat and email and documents, specifically in regard to remote team collaboration. That was one of the strengths of Google Wave, except that Wave had a learning and familiarity threshold people weren't willing to climb over. There's a huge opportunity there for a startup that I haven't seen anybody really tackling yet.<p>You can't get away from the value of face to face meetings though. If it is possible, getting face to face occasionally is a huge benefit in strengthening relationships in a team. In the end, teams are about relationships. Remote teams work great, and I prefer them to co-located teams, but figuring out a way to meet in person on occasion is worth the effort.
We use <a href="http://www.tandberg.com/" rel="nofollow">http://www.tandberg.com/</a> and I find it incredibly good. I recommend you to go see a real demo, because you can't grasp the real feel by just looking at some pictures. It's quite expensive, but in my opinion it's worth every dollar.
I have used Mikogo quite successfully in the past. Something that I found useful was that you can swap who the "Presenter" is at any time. This allowed different members to share their desktops when trying to explain something.<p><a href="http://www.mikogo.com/" rel="nofollow">http://www.mikogo.com/</a>
I systemize and automate businesses end-to-end for a living.<p>Don't despair, this is a bit of an art and it's slowly becoming a science.<p>I have largely virtualized my consulting practice that I have run for 10+ years using remote developers both locally and out of town.<p>This is a problem I have obsessed over solving the past 12 years. It was hard enough to get it working in-house with employees, to learn the key qualities needed to make it work from anywhere.<p>There are a few key things you must solve:<p>0) KNOW YOUR PROCESS.<p>Are you able to take all the steps of your process and lay it out on a flowchart, no matter how complex?<p>Can you take any request currently in your business and place it on this flow chart?<p>Once you can do this, you are ready to systemize. Until then, this is where you are needing to clarify and build out things.<p>1) A CENTRAL SYSTEM THAT HANDLES YOUR WORKFLOW.<p>There is no magic ONE tool that will solve anything. Most suggestions will be helpful with one or a few parts of the process. Instead you will need to <i>connect</i> multiple tools to get what you need.<p>The key is having a central communication system.
It doesn't sound like you have this yet. This is a non-neogotiable.<p>The communication system must be based around requests/cases. All communication, regarding work people need to do, needs to be in this system. The cases need to be run through a fulfillment process that captures and reflects your competitive advantage.<p>2) DOCUMENTATION IS YOUR FRIEND.<p>Documentation can suck, royally. Meaningful documentation is even harder. But it's the only thing that allows people to answer their own questions. Being able to capture your intellectual capital and spread it is critical to having your business grow.<p>If you're having trouble teaching, remote workers are having a hard time remembering. The key is to create a culture of self-serve updating documents. A wiki is often critical for this, however I am also a _big_ fan of videos integrated.<p>3) BUILD YOUR TIME / BILLING TRACKING INTO THE BREAD.<p>Billing, and time tracking, also sucks. Whatever unpleasantness we don't want to deal with now has to be dealt with doubly later.<p>It's best to bake time tracking/billing into the bread and your process. With the right configuration based around your process this is pretty possible.<p>If you have to track billing/time for this, it must be a simple, usable, system that is hopefully integrated right into your system. I am a quickbooks guy for most of my stuff, however I've started using Freshbooks for the Accounts Receivable / time collection side of my business and it's working a lot better.<p>If you have a process but works and just lacks in being clearly explained / taught, I can help you with that. Reach me by email or ask any questions here. I guarantee results if you're willing to do what's needed.
We use Flowdock and Github for most of team communication. Skype and Teamviewer for collaborative "real-time" work. I wrote about the workflow here: <a href="http://news.ycombinator.com/item?id=3274080" rel="nofollow">http://news.ycombinator.com/item?id=3274080</a>
I work remotely with a web designer (I'm a programmer), and we mostly use a combination of Skype, GitHub and Gmail (for asynchronous communication)<p>We haven't found collaboration software for documentation and such good enough for our needs yet, but we are trying Trello.
Have you tried Google hangouts? We've been pretty happy with its screen-share (Hangouts with extras).<p>Also we use redmine as a wiki+issue tracker with git integration. An almost github like setup :)
Perhaps something like OpenQwaq might be useful.<p>VoIP, web cam, chat, meeting rooms, open office, and more.<p><a href="http://code.google.com/p/openqwaq/" rel="nofollow">http://code.google.com/p/openqwaq/</a>