Wednesday, December 3, 2008

10 practices to be efficient in a virtual team

Following Sorin's post about working in a virtual team, I decided to write about 10 practices that in my opinion improve a lot the efficiency of a geographically dispersed team, which is using the online medium for business.

Image by SpoiltCat

1. Be strict with email
Don't eliminate email but be disciplined in using it. Also, you don't need separate accounts for personal and business use, but make use of filtering. Keep all the conversations for later search.

2. Use a project collaboration tool
A project collaboration tool must help you keep all your stuff together: tasks, milestones, notes, messages, documents. Sometimes it's easy to let go of this idea, with excuses ranging from: "but what we're doing is not actually a project" or "we use email and we're fine". Email cannot replace properly the role of milestones or tasks, for instance.

3. Write everything down
There isn't a straightforward replacement for the water cooler in a real office. But in a way, this might be an advantage. It happened to me a lot of times to discuss on ideas with my colleagues, only to notice later that we remember less than half of the ramifications our conversation took.

4. Brainstorm and expose
Save any idea that comes to your mind and share it. Let your colleagues "play" with your notes. In turn, find different approaches or fine tune your team mates' proposals. A thing to be careful about here is to avoid going too deep in one direction, since this can be the recipe for getting nothing done.

5. Keep documents in one place
Resist the temptation to send documents as attachments to emails, but upload them in your collaboration application. You don't need to build a hierarchy for the files, just use the search approach.

6. Turn limitations into advantages
In a real office, if someone has a question for a co-worker usually goes to her desk to ask. This is bad, since it creates interruptions and breaks the flow. When working in a virtual team, don't try to mimic the same behavior. If the colleague is not online on IM, don't wait for her but leave a comprehensive message, preferably in the collaboration tool.

If you have a question don't just ask it and wait for an answer, as this may lead to very long conversations. Instead provide all the options you thought about as possible answers, specifying why you like or dislike each of them. This diminishes the time spent on an issue, thus increasing efficiency.

7. Set a working schedule
Everything is set up regarding the way you interact with the colleagues and you're enjoying the flexibility of your own schedule to do the work. But in time, this can get out of control if you don't establish a working schedule for yourself. Spreading the working hours throughout the whole day may affect your personal life and you'll end up "working" all the time, not knowing when it's enough for a day.

Having a schedule also helps the other members of the team, since they would have more accurate expectations on when you're going to do various tasks.

8. Set iteration milestones
Working in iterations is a good practice to have a clear overview of what needs to be done next. It also helps to see if the deliverables were met. Weekly iterations offer a convenient time frame, but depending on your team this may be reduced or extended. However, extending them too much would be like not having them at all.

9. Stick with a given workflow
If you started to use a collaboration tool, keep everything in there. Don't scatter discussion about features of the product in emails, but use messages in the tool. Don't ask for things on email or IM, but set tasks.

10. Get to know your colleagues
If it's possible, meet your team mates personally, go out for a drink or make weekend trips. Getting a glimpse into their personal life and also exposing some of yours helps with the work. If that's not possible, try to connect with them on social networking websites. Find out their hobbies, maybe they match yours, and exchange thoughts about them.

I would not state that this list is exhaustive, but I think it covers 10 important aspects that lead to easier communication and a better workflow in a virtual team. Almost all of the points rely strongly on self discipline, but once it's achieved, it's easier to keep going.

Monday, December 1, 2008

Overcome procrastination with Teamness

Regarding procrastination, I think there are two types of people: those who procrastinate and those who declare they don't.

Putting off things needlessly is a common thing most of us do. How many times did you postpone making an appointment for the dentist, even if you knew you're going to do it eventually? And how many times did you start working on different things, just to delay a burdensome task?

Image by celie

All of us have good business ideas. Most of the time we reject from the start and I think one of the reasons is that we procrastinate on thinking about a roadmap. When thinking about it, the path seems complicated and we tend to see mainly the obstacles.

In this post I'll present a simple way on how using Teamness and mind mapping one can get a better grip on how to pursue a new opportunity.

It all starts with an idea

For the sake of the example let's consider a guy Robert, which was on a holiday in France and bought a funny hat. At least he considered it to be funny, but he was asked a couple of times on the street where he got it from.

One day he asked himself what if he started to bring those hats from France and sell them. When he was about to let go, due to unanswered questions in his mind about the manufacturer, target market, shipping issues and so on, he makes a last effort and decides to give it try.

Turn the idea into a project

One of his friends recommends Teamness to Robert. "But I have no project to run, it's just an idea", was Robert's answer. That's exactly the point. Turn the idea into a project.

Robert creates a project in Teamness and calls it The funny hat. The purpose of the project is to investigate this business idea.

Brainstorming is the first step

He creates a new whiteboard in the project and starts writing all the things that comes into his mind regarding the process: existing products on the market, prices, target demographic, manufacturer, producing prices, shipping costs, storage and all other things that pop into his mind. Using mind mapping is really helpful in this process.

Time for tasks

Robert starts now to formulate questions based on the things he brainstormed about, like "What are the existing products on the market?". This question easily becomes a task: "Make a list with similar products on the market and their retail cost".

One by one, almost all of the other issues start to take the form of a task: "Call the manufacturer and ask for the price; try to get a discount for multiple purchases", "Identify areas for advertising for this kind of product and the target demographic", "Make a plan to microtest the product with PPC advertising" and so on.

Make the roadmap

Now Robert creates milestones. He makes one called "Target market analysis" and assigns the tasks related to his market to it. He sets this milestone to be due one week from now, based on some rough estimations on his free time.

As the project rolls on, information is collected in The funny hat project. Links, lists of prices, contacts, scans after brochures, screenshots made on some websites and so on are now all in one place and the idea turned into something more consistent. It's more clearly now what the good direction might be, based on real investigation rather than fuzzy assumptions.

Having a clear picture on how to continue, it's possible now for Robert to even delegate some of the tasks to a virtual assistant, which can help with some time consuming chores, understandably defined.

Friday, November 28, 2008

Creativity gone wild with mind mapping

Image by Trapac

One of our readers, Eduard, mentioned mind mapping in a comment in this post and I thought it would be interesting to share with you how I apply this technique to come up with ideas for blog posts.

Usually when we think about various creative aspects of our work, the tendency is to come up with an idea and then analyze it on spot. This is not productive, since it requires costly context switches. Mind mapping helps to avoid thinking linearly and it makes us produce as many ideas as possible first, postponing the analyzing phase.

I used the technique described here. The idea is to take the last five posts from your blog and brainstorm around them. For the purpose of this demonstration, I selected three random posts from our blog and set myself the task to come up with five ideas for each. The posts selected were:
A pen and a piece of paper could be ideal for doing this, as they make you step away from the computer and eliminate some distractions. On the other hand, working mostly with computers throughout time, I got to a state in which I type faster than I write, so I used an online application that is pretty fast in response.

The tool is called bubbl.us and it's a neat free web application, written in Flash. It that has some useful capabilities, like exporting the map to an image and collaborating with others, and some not very useful, in my opinion, like sound alerts.
Click on the image for a bigger version

Using mind mapping, I managed to come up with 15 different ideas in about 10 minutes, as you may see in the image. You actually only see the ideas, so you have to trust me for the time interval. Of course, it's not mandatory to write about everything that I came up with, but I got a couple of ideas to play with for new posts.

I find this technique to be as efficient as simple and I consider that it may be applied to a broad range of mental activities, like determining goals and directions for your projects, establishing new features, writing articles or letters, generating ideas for blog posts and also composing a post.

Wednesday, November 26, 2008

Clean up session in Google Reader

A few days ago I decided there was time for a clean up in the feeds I'm following. My aggregator of choice is Google Reader. I use it because it's sleek, fast and comes with some juicy features like graphs about your following habits compared to posting frequency.

Image by Eneas

If you don't know what a feed is, please check these 2 links:
My clean up process included some folders deletion, creation of others, reassigned existing feeds to various folders, unsubscribed from a couple of feeds I haven't been following in a long while.

Feedback on Teamness from Google Reader

In this post I described how we monitor Teamness presence on the web. Google Reader is playing a big role in this, being my RSS and Atom feeds aggregator. I grouped all the feeds obtained for Teamness search options described in the abovementioned post in a folder called About Teamness.

Google Alerts, with which I follow keywords of interest on the web, recently started to offer RSS feeds, besides email. I defined a couple of alerts with terms related to project management and collaboration and I saved their RSS feeds into Google reader. They went into a folder called Teamness terms.

Competition has to be followed from time to time, also. It has its assigned folder called Teamness competitors.

Structure of the feeds

Google Reader allows to put your feeds in different folders. These folders are actually like labels. Or like tags, if you prefer. Therefore, you can assign a feed to multiple folders. This is a bit confusing, even when you try to say it: "I assigned a couple of folders to my feed" or "I put my feed in a few folders" ... doesn't sound natural. I don't understand why Google didn't name them labels, as in Gmail, instead of folders. This post contains some brief thoughts about ontology and organizing data, if you're interested on the topic.

Anyway, getting back to my cleanup process, I made 15 folders in which I put (or assigned, or assigned to) my 117 feed subscriptions. Now, to be honest, I don't actually follow all of them. It seems fairly impossible to me, even though I heard about bloggers claiming that they're following more than 1000 feeds per day. Following doesn't necessarily mean reading. I came up with the organizational scheme described in this post in order to get the most from my feeds.

Getting neat with iGoogle

iGoogle is another gimmick from ubiquitous Google. It's a customizable page, where you can add gadgets such as weather forecast, joke of the day, news and many many more.

iGoogle has a gadget called ... hmm ... Google Reader which can show the feeds you have in the Google Reader itself. The nice thing about this gadget is that you can ask it to display only the feeds in a certain folder.

Therefore, in this revolutionary organization enthusiasm, I made two more folders, which I assigned to two Google Reader gadgets in iGoogle. These folders are called: Essential and Mild.

Essential
contains feeds which are highly important and which I check often, like 2-3 times per day. Mild contains feeds that are still important, but not as important as those in Essential, and gets read once about 1-2 days.

All that is in the folder About Teamness goes also in Essential. Some blogs that I want to follow frequently go there as well.

This setup is pretty neat and allows me to focus on what's important, or essential. I also don't miss other news, of lower importance, which I gather in Mild. When time allows, I can go Google Reader and browse through the other folders, like Photography.

Monday, November 24, 2008

Do you want to be satisfied?

Image by TheAlieness GiselaGiardino

We gave our forum up. We concluded it's a bit complex, a bit old fashioned and it was a different application from Teamness, which also needed maintenance.

So what does one in today's web world, when tools appear everyday for every need, do to offer a solution for its users to ask questions and interact? The answer could be outsourcing and this is what we chose. It means that we're now using another service to provide a way for customer support. This service is GetSatisfaction.

First of all, I think the name of this service is brilliant. You may create enticing phrases, like the one in the title, when you mention that you're using it. But besides that, they come with a bunch of cool features that make the service look like a forum on steroids.

Getsatisfaction offers a win-win situation, regarding customers and providers.

The former can go to a central point and see what other users are saying, interact with other customers, share opinions and so on. Like in a forum, but with a couple of twists.

The latter can get feedback in a structured way. For instance, if one person asks a question, others can simply click a button saying "I have this question too", increasing the number of people who would like an answer on the matter. So a company may answer a question once, instead of replying to a lot of emails. The same goes for ideas, praises and problems.

When you register a company or a service in GetSatisfaction, it gets assigned the URL http://getsatisfaction.com. Therefore I wonder what would happen if About.com decided they want to use the service, since the page http://getsatisfaction.com/about contains the story behind the tool.

We're really excited about the features offered by GetSatisfaction and we're curious how it will work for our customer support in the future. In other words, we're really excited to get satisfaction. (I told you the name is brilliant.)

So please, if you have any question or complain or suggestion or even praise about Teamness, use this link to get satisfied.


Friday, November 21, 2008

Data segregation and the Stockholm syndrome

Dreaming in code, the book I mentioned in this post from last week, follows the creation of a software tool named Chandler. At one point, the author makes a connection between how the development team is trying to make the data structures in Chandler as flexible as possible and intertwingularity, a term coined by Ted Nelson, who also came up with the term hypertext, to express the complexity of interrelations. Ted Nelson said that "people keep pretending they can make things hierarchical, categorizable and sequential when they can't".

Image by Nattu

I find myself many times organizing files into folders on my computer, but as time goes by, the data tend to get dispersed anyway. Then I end up procrastinating to clean up my files and directories on my hard drive again. On the other hand I'm using Delicious everyday to save and retrieve my bookmarks, without worrying about the structure.

We're not supposed to help computers into maintaining the data, but to put them to work. I wouldn't probably spend time creating folders on my hard drive, if retrieving the information by searching would be instantaneous.

I think that trying to maintain hierarchical structures turns us into some sort of data victims or as Patrick Mueller said, it makes us suffer from the Stockholm syndrome.

Image by cambodia4kidsorg


As I mentioned above, I keep my bookmarks on Delicious. I have about 1500 and the organization is based on tags. If I would've built a hierarchy for them I would be lost. It's easier to go to a tag and see other tags used in connection with that and so on. The same approach of archiving and searching is so liberating and it makes Gmail so easy to use.

Clay Shirky states the following in this interesting article about categories, links and tags:
One reason Google was adopted so quickly when it came along is that Google understood there is no shelf, and that there is no file system. Google can decide what goes with what after hearing from the user, rather than trying to predict in advance what it is you need to know.
He mentions that categorizing is similar to predicting the future, which turns out to be hard:
Consider the following statements:

A: "This is a book about Dresden."
B: "This is a book about Dresden, and it goes in the category 'East Germany'."

That second sentence seems so obvious, but East Germany actually turned out to be an unstable category. Cities are real. They are real, physical facts. Countries are social fictions. It is much easier for a country to disappear than for a city to disappear, so when you're saying that the small thing is contained by the large thing, you're actually mixing radically different kinds of entities. We pretend that 'country' refers to a physical area the same way 'city' does, but it's not true, as we know from places like the former Yugoslavia.


What about you, do you feel more comfortable building hierarchical categories or tagging information? What tools do you use that offer each of these functions or maybe both?

Wednesday, November 19, 2008

Teamness case study - wedding photography

Andris Zenta is a professional photographer from Latvia who specializes in wedding photography.

In the beginning, please introduce us to your work.

I've been working as professional photographer and illustrator for the last five years and recently I started to focus my interest into wedding photography. It's a very exciting field, but at the same time, exhausting. In any case, it brings me satisfaction both career wise, as well as from a financial perspective.


How did you find out about Teamness?

After shooting a couple of weddings by myself, I decided that I need two assistants to help me, one as a second shooter and one to take care of auxiliary tasks, like preparing the equipment or moving things around to set up scenes, allowing me to focus on taking the photos.

With more than one participant in this kind of project, there was need for a project collaboration tool. Since it was my first assignment with a team I wanted to try a free tool to see how it goes and I ran across Teamness by searching on the web for a free collaboration tool for teams.

I'm very satisfied on how it went and now I'm also seeing the benefits of using project management tool even if you work alone. It helps keeping you organized.


How did you use Teamness for your project?

I used Teamness so far for this wedding project I described, in which I had two assistants helping me.

Wedding photography is one of the most difficult tasks for a photographer. Everything must be very well planned, because you don't get a second chance to shoot the event. Preparation is then the key and Teamness helped us with being prepared.

A lot of details need to be settled prior to the event, like for instance dressing code. It doesn't seem like a photography task, but even if you're not part of the event, you need to blend in. This was written down in a whiteboard in Teamness which I named "General checklist".

The wedding had two parts: a first part in the church with shootings outside afterward in a nearby park and a second part taking place at the party, inside a location. We checked the weather for the day with shooting outdoors and stored the results in Teamness.

Prior to the wedding all three of us did some location scouting. We went to the established places and put down ideas for shots. We then discussed them in Teamness using messages and agreed on shot lists which we saved as whiteboards. I also prepared groups of tasks for my assistants and watched the activity on the dashboard.


What are the roles of every participant and how do you use Teamness for them?

I was doing the main shooting and one of my assistant was taking photos with a wide lens, covering more general aspects. We had a script prepared that list all the actions we needed and for each action I assigned tasks for my second assistant, like making sure to gather every member of the family at a certain time.

I established tasks for my assistants, first for the scouting session in which we simulated a real shooting and then for the wedding itself. The various stages were marked with milestones, for instance I had a set of tasks assigned for different talks with the couple: settings expectations regarding how many shots they want, what things to have covered and also the agreement based on which I charged them.

I made the equipment list for each bag, as different messages in Teamness and assigned tasks for the assistants to take care of each.


Are there any particular features that you value the most?

I liked that we were able to assign tasks to different persons and comment on them, so we agreed easily on every aspect. Building together lists of things to pack and do in whiteboards and seeing what everyone added was neat.


What would you improve in Teamness?

I would like a more flexible way of managing the items tied to a milestone. I would also like to see a richer editing feature for messages, in the same way as for whiteboards for instance. This was very helpful for us to accentuate on various equipment. I will stay with Teamness for my future projects, including a portfolio website that I'm preparing to build at the moment.


Thank you very much for your time.

Thank you.