I’ve also spent most of my career working virtually, so I’ve got increasingly good at communicating. In some ways, my policy has become to over communicate.

If you’ve worked in any sort of communication role, either as a freelancer or within another business structure, you know the old game, “hurry up and wait”. When you’re juggling more than one project, this becomes increasingly problematic.

The key to any successful project is communication, that’s nothing groundbreaking new. Being able to communicate is one side of the coin. The other?

Regularity of communication.

This is often resolved by setting up regular meetings and/or calls. Anyone who’s worked with me in the past knows how much I hate meetings, and that’s only worse when it’s a meeting about another meeting. In every effort possible, I’ve implemented stand-up meeting policies. Part of the success of IndyHall has been our ability to move quickly. Our quick decision making came down to Geoff and I communicating regularly, but never for the sake of communicating.

This is tricky to describe: Geoff and committed to regular communication, in a less formal agreement to one another. The other part of the less formal agreement was to never bring something to the table that couldn’t be quickly discussed and decided upon, most of the time in under 10 minutes. Informally, we’d designed a stand-up meeting that we didn’t even need to come face to face for.

Communication happened often, and in short bursts of valuable, actionable information.

In between actionable item discussions was the other part of the overcommunication that’s often overlooked: status updates.

When working virtually it’s crucial to let your team mates know what’s going on, even in the briefest format. My friends at Wildbit have written some of the best stuff about this, from using twitter for the team to using commit messages correctly. No matter what tool or technique you use, there’s one core concept that I think is the most important:

being on the communication offensive.

Photo by siobhansilke on Flickr

That is, if you’ve got information that’s valuable to the team, don’t wait to bundle it with a larger update or, worse yet, to be asked for it to give it up.

If someone doesn’t need the information now, they may need it later and rather than have to bother for it later, they can simply check past updates.

Also, a “small piece of information” may be critical to someone else’s to-do list and you may not realize it.

I’d make a sports metaphor here but I never claimed to understand sports.

Okay. I’ll try anyway. A core value of teamwork when it comes to sports: even if you’re all star, don’t hog the ball.

Get the ball across the court faster with efficient, regular “overcommunication”.

I can’t believe I wrote a blog post with a sports metaphor. I’m sorry, it’ll never happen again.

Redux, or the A.D.D. version of this post:

1. Scheduled communication is good, but communication for the sake of communicating is a waste of time.
2. Communicate early, communicate often
3. Don’t assume information isn’t important for someone else to know
4. Alex is allergic to sports and still can’t believe there was a sports metaphor in this post.

I’m really, really stoked to announce that I’ve teamed up with Anthillz.com, a Philadelphia startup founded by Blake Jennelle. Blake is also the founder of Philly Startup Leaders, and we have become friends over the last year through the similarities that our organizations’ (PSL and IndyHall) goals share.

Anthillz is building out tools to help freelancers and independents manage their reputations by organizing client and peer feedback and helping generate measurable statistics that can help in freelancer searches, as well.

Where do I fit? Well, besides my obvious interest in the value of freelancers and doing things that make it easier to be an independent, Blake and his team realized there was value on community marketing as well as using member feedback to drive their product design process. I’m being brought in to help advise and lead that process, all along the way helping be a liaison for the community and the management team. I’m there for the community, and there for the team, when they need things and will help facilitate interactions between them.

My favorite part? Read this part of the position description that Blake and I drafted together:

When there’s a tension between his roles of representing the company and advocating on behalf of the community, the advocate should take the side of the community.  Any company has the natural tendency to give extra weight to its own interests, and the Community Advocate is an essential counterweight.

Blake wrote, this not me, but it’s attitudes like this that makes me have hope for company leadership in general. Blake and his entire team are as excited about this new partnership as I am.

I look forward to being able to share our findings as we continue to develop Anthillz as a product and a community, and encourage you to check it out and feed back as well!

I’ve got a couple of other similar projects and partnerships in the work, and am excited to share them with you as they unfold. Stay tuned, everybody!