It appears that yesterday, SoftLayer had a DDoS attack on one of their DNS servers, though nothing official is confirmed yet.
SoftLayer is our hosting provider and a DDoS attack is a distributed denial of service action to make a resource unavailable, in this case a DNS server. Roughly explained, a DNS server is in charge with translating a domain name to an IP address, making it possible for a user to type a name like www.teamness.com in the browser address bar and get the proper web page back. Pingdom has a blog post called A visual explanation of how DNS lookups work, with a nice picture depicting the process.
All the above means that www.teamness.com wasn't accessible in some areas in the world, at least by the domain name. I tried a few websites that will let you use their DNS servers, to get an idea of where the website wasn't available. Here is the list with these services (I also included IP addresses, since if you have a DNS problem, you might not be able to access them by names):
Website by name: http://www.all-nettools.com/toolbox
Website by IP: http://216.92.207.177/toolbox
Location: United States - Pennsylvania - Pittsburgh
Website by name: http://www.dnsstuff.com/
Website by IP: http://66.36.247.82/
Location: United States - Texas - Dallas
Website by name: http://network-tools.com
Website by IP: http://67.222.132.196/
Location: United States - New Jersey - Ocean City
Website by name: http://ping.eu
Location: Germany - Berlin
Website by name: http://www.demon.net/external
Website by IP: http://194.159.246.194/external
Location: United Kingdom - Scotland - Aberdeen
Website by name: http://www.knossos.net.nz/checkdomain.cgi
Location: New Zealand - Auckland
I used http://whois.domaintools.com to get the locations.
The interesting thing is that www.teamness.com was accessible through all the above, but not from my machine in Sweden. I asked a friend from Cyprus who was up at that time to check it with nslookup and it didn't work from his machine either.
And people were on a re-twitting frenzy about the incident.
More links on the matter:
Showing posts with label Startup stories. Show all posts
Showing posts with label Startup stories. Show all posts
Wednesday, July 29, 2009
Friday, June 5, 2009
The WWW prefix
It comes a time in the start of any web business to pick a domain name. This is a laborious task in itself, since pretty much all the cool domain names that resonate with your business are already taken either by the existing competition or by domain pirates.
It was the case with Teamness and after the domain was chosen and we were about to wipe the sweat off our foreheads, we ran into the unruly question of which URL should we promote: www.teamness.com or teamness.com ?
There are many pros or cons on neither of them. Some believe it's better with the www prefix, others think it's nicer without.
The most important thing is to pick one in the beginning and stick to it. We don't want the links pointing to us on the web to be either with www.teamness.com or teamness.com.
Another important thing is that no matter what the visitors are typing, www.teamness.com or teamness.com, they must reach Teamness nevertheless. We think it's incomprehensibly rude to punish someone who typed teamness.com by sending them to the error page. So a redirect from one form to the other is mandatory.
We chose www.teamness.com over teamness.com and one reason had to do with subdomains: we post ramblings to blog.teamness.com, the private stuff is located at my.teamness.com and probably we'll use more subdomains in the future, so the www form acts as a disambiguator.
There is, however, a technical issue with the www-less domain. The cookies will be set for the whole domain. Each cookie has a domain and a path and the browser sends the cookie to the domain specified in there. If the domain is www.teamness.com, the cookie will not be sent to blog.teamness.com, but if the domain is teamness.com, then the cookie will be sent to all subdomains, like blog.teamness.com, my.teamness.com and so on.
Few people use the www prefix in verbal communication as it became implied when referring to a website. Also, when you type the name in the address bar and hit Ctrl+Enter, every browser will add the www. Prefix and append .com.
It was the case with Teamness and after the domain was chosen and we were about to wipe the sweat off our foreheads, we ran into the unruly question of which URL should we promote: www.teamness.com or teamness.com ?
There are many pros or cons on neither of them. Some believe it's better with the www prefix, others think it's nicer without.
The most important thing is to pick one in the beginning and stick to it. We don't want the links pointing to us on the web to be either with www.teamness.com or teamness.com.
Another important thing is that no matter what the visitors are typing, www.teamness.com or teamness.com, they must reach Teamness nevertheless. We think it's incomprehensibly rude to punish someone who typed teamness.com by sending them to the error page. So a redirect from one form to the other is mandatory.
We chose www.teamness.com over teamness.com and one reason had to do with subdomains: we post ramblings to blog.teamness.com, the private stuff is located at my.teamness.com and probably we'll use more subdomains in the future, so the www form acts as a disambiguator.
There is, however, a technical issue with the www-less domain. The cookies will be set for the whole domain. Each cookie has a domain and a path and the browser sends the cookie to the domain specified in there. If the domain is www.teamness.com, the cookie will not be sent to blog.teamness.com, but if the domain is teamness.com, then the cookie will be sent to all subdomains, like blog.teamness.com, my.teamness.com and so on.
Few people use the www prefix in verbal communication as it became implied when referring to a website. Also, when you type the name in the address bar and hit Ctrl+Enter, every browser will add the www. Prefix and append .com.
Thursday, April 2, 2009
IE6 - to support or not to support
Yesterday I was reading this post from the Pingdom blog. I forgot it was the 1st of April, so I thought they went mad.
I realized it's a joke when I saw the first testimonial on the SaveIE6 website mentioned in the post, testimonial written by a certain Steve B. Bangal, Inventor of spaghetti code.

We didn't discuss yet if we're going to stop supporting Internet Explorer 6 in Teamness. It's very tempting to do it, given all the frustrations we've been through.
So far, we had 18% of the visits on the public website and 6.5% on the private one coming from IE6. The numbers are small, so I believe we can start the countdown for casting out the hacks.
I realized it's a joke when I saw the first testimonial on the SaveIE6 website mentioned in the post, testimonial written by a certain Steve B. Bangal, Inventor of spaghetti code.

Image by hashmil
First time I read about this call to action by Robert Nyman here. Robert is trying to convince web developers to stop writing special code for Internet Explorer 6. And when you want your web pages to look decent in IE6, you need to write special code. People call it hacks.We didn't discuss yet if we're going to stop supporting Internet Explorer 6 in Teamness. It's very tempting to do it, given all the frustrations we've been through.
So far, we had 18% of the visits on the public website and 6.5% on the private one coming from IE6. The numbers are small, so I believe we can start the countdown for casting out the hacks.
Sunday, March 1, 2009
Yet another Geek Meet
Thursday evening I attended my second Geek Meet in Stockholm, organized in bwin's offices near the Cityterminalen. The previous one took place on December 4th and I mentioned it in this post.
This geek meet featured 2 presentations by Mark Wubben and chili con carne. The chili was good, but I think the presentations were in need for a little bit of a twist. The topics discussed by Mark were typography and sIFR in the first part, and ubiquitous computing, including examples of how RFID may be used in daily life, in the second part.
We worked with sIFR 2 in Teamness and because of this it was easy to understand and follow Mark's code examples dealing with sIFR 3. But I would've liked to see more working examples and differences between good and bad ways of applying it on a web page.
Mark was amused about how other new typography tools aim at becoming sIFR replacements, which is a funny thing to aim for, since sIFR itself is a hacking alternative.
Second presentation managed to keep the beer-sipping geeks more attentive, due to inclusion of videos and real life examples from Mark's work in the area.
This geek meet featured 2 presentations by Mark Wubben and chili con carne. The chili was good, but I think the presentations were in need for a little bit of a twist. The topics discussed by Mark were typography and sIFR in the first part, and ubiquitous computing, including examples of how RFID may be used in daily life, in the second part.
We worked with sIFR 2 in Teamness and because of this it was easy to understand and follow Mark's code examples dealing with sIFR 3. But I would've liked to see more working examples and differences between good and bad ways of applying it on a web page.
Mark was amused about how other new typography tools aim at becoming sIFR replacements, which is a funny thing to aim for, since sIFR itself is a hacking alternative.
Second presentation managed to keep the beer-sipping geeks more attentive, due to inclusion of videos and real life examples from Mark's work in the area.
Wednesday, February 11, 2009
Monitoring a web application
So we got a reliable web hosting service for Teamness and we came up with a security policy to keep the data safe.

All good, but we also needed a monitoring solution, to be informed when something is wrong with the server.
We settled to use Pingdom, a Swedish service built for this purpose. Big guys like Alexa, iStockPhoto, Feedburner and Skype are using Pingdom, but it's also an affordable solution for small startups like us.
This post is not a Pingdom review, but more about the way we're using their services to know that Teamness is up and running.
Our Pingdom account
We set up 3 monitoring options for Teamness, for every web application in Teamness:
There is also the option to pause a checking routine, so the notifications are off while we're doing maintenance work, like uploading a new build.
What do we check for?
We built a special tiny module in Teamness, which performs a couple of sanity checks to be sure the application is running safe. This module is called from a separate page, designed specifically for this purpose, which is further requested in the Pingdom checking routine.
This way we don't only know that the server machine is up and that the web server is running, but also that the inner workings of the application are sane.
Current status pages
You may expose the status of your web application through a public link. We used TinyUrl to generate these custom links for the two websites in Teamness:
They are very useful when our users ask for the uptime. A link to a nice page with the historic of the availability is more valuable than stories and explanations.
The link for the private website, which is the website with your data, is published on the Teamness main page.
Pingdom goodies
They have a set of tools for checking a webpage, by mimicking the way it is loaded in a web browser and also for doing traceroutes or pings.
Tests may be saved for future reference, like this one for The New York Times.
Mr Uptime is a Firefox extension that will let you know when a website you checked and wasn't available is again back in business.
Royal Pingdom is the name they chose for their blog. I like the Swedish humor. And I like the blog, is one of the corporate blogs that issue quality posts and not only blabber about some new offers.

All good, but we also needed a monitoring solution, to be informed when something is wrong with the server.
We settled to use Pingdom, a Swedish service built for this purpose. Big guys like Alexa, iStockPhoto, Feedburner and Skype are using Pingdom, but it's also an affordable solution for small startups like us.
This post is not a Pingdom review, but more about the way we're using their services to know that Teamness is up and running.
Our Pingdom account
We set up 3 monitoring options for Teamness, for every web application in Teamness:
- the public website
- the private website
- the administrative web application that we use internally
There is also the option to pause a checking routine, so the notifications are off while we're doing maintenance work, like uploading a new build.
What do we check for?
We built a special tiny module in Teamness, which performs a couple of sanity checks to be sure the application is running safe. This module is called from a separate page, designed specifically for this purpose, which is further requested in the Pingdom checking routine.
This way we don't only know that the server machine is up and that the web server is running, but also that the inner workings of the application are sane.
Current status pages
You may expose the status of your web application through a public link. We used TinyUrl to generate these custom links for the two websites in Teamness:
They are very useful when our users ask for the uptime. A link to a nice page with the historic of the availability is more valuable than stories and explanations.
The link for the private website, which is the website with your data, is published on the Teamness main page.
Pingdom goodies
They have a set of tools for checking a webpage, by mimicking the way it is loaded in a web browser and also for doing traceroutes or pings.
Tests may be saved for future reference, like this one for The New York Times.
Mr Uptime is a Firefox extension that will let you know when a website you checked and wasn't available is again back in business.
Royal Pingdom is the name they chose for their blog. I like the Swedish humor. And I like the blog, is one of the corporate blogs that issue quality posts and not only blabber about some new offers.
Monday, January 26, 2009
Brainstorming remotely
Today I started a short conversation with Pawel Brodzinski, about how teams respond to working exclusively remote. By the way, his blog, called Software Project Management, is a great resource of posts about working with teams and managing the process of software development, so make sure you subscribe to it.
Pawel was talking about the lessons learned from a startup product called Overto, which was closed some time ago. One of the things he mentioned was the value of working in the same place and the way his team started to feel the negative effects of being separated.

Since I believe in the remote proficiency of virtual teams, I had a different opinion. I think that after the preliminary discussions around the fresh idea of the product, collaborating in writing instead of ad-hoc meetings may bring great effectiveness into the product.
Written communication versus spoken brainstorming
I mentioned the following arguments for communicating over writing mediums, like email, as opposed to verbal meetings:
Let ideas flow, then examine the results
It's pretty common that once an idea is out, it's exposed to being examined. This leads to context switching and instead of focusing on building a list of things to discuss about, you'll find yourself analyzing ideas.
For instance, when you discuss holiday destinations with your spouse, it's probably the case that you find a place, discuss about it, then find another, comment on it and so on.
The drawbacks of this approach are presented more explicitly in the book The Myth of Multitasking. The book includes a demonstration that switching back and forth between two different tasks, makes them take more time than doing them sequentially.

Use mind-mapping, build a list of things that you think are suited, and then pass it on. If the others are doing the same, undisturbed, your team ends up with a more productive flow of ideas and better yet, you have everything written down.
Experiment and stick to what works for you
I'm not trying to say that this model is supposed to work for everyone. We are a team of two people, me and Sorin. It's been like this not only for the time we've been working on Teamness, but since 2005 when we started our company. We used to work from home on different projects for some clients and we always collaborated remotely. This is basically the reason for building Teamness in the first place.
In the beginning we were talking on Skype about clients, implementation details, decisions and so on. We used to have long conversations and sometimes we didn't remember everything that was discussed. We still have conversations, but when we talk about new features or design decisions, we use Teamness. We write the proposal in a message and then comment on it. This keeps it focused. We also use email from time to time, but what I want to stress upon here is that we're trying to keep the verbal communication related to our projects to a minimum, since it didn't prove efficient for us.
Please also note that I'm not trying to express that social interaction is bad, like having lunch with your colleagues or coffee breaks discussions. But when your product has 1000 features, writing things down becomes the key ingredient for a solid collaboration.
Pawel was talking about the lessons learned from a startup product called Overto, which was closed some time ago. One of the things he mentioned was the value of working in the same place and the way his team started to feel the negative effects of being separated.

Image by timabbott
Since I believe in the remote proficiency of virtual teams, I had a different opinion. I think that after the preliminary discussions around the fresh idea of the product, collaborating in writing instead of ad-hoc meetings may bring great effectiveness into the product.
Written communication versus spoken brainstorming
I mentioned the following arguments for communicating over writing mediums, like email, as opposed to verbal meetings:
- On email it's more natural to keep the discussion focused on an aspect. Talking makes this a bit chaotic.
- It's easier to follow a point of view, when you have it written on the screen, maybe with additional links to external resources.
- When you need to write, you focus more on the points you'd like to add to the discussion. Talking is faster, so it might lead to loosing the focus.
- Everything that's discussed gets logged, so you avoid the post-meeting confusion over some pieces of conversation or forgotten parts.
- You're undisturbed in your own mind-mapping flow process and you don't disturb the others.
Let ideas flow, then examine the results
It's pretty common that once an idea is out, it's exposed to being examined. This leads to context switching and instead of focusing on building a list of things to discuss about, you'll find yourself analyzing ideas.
For instance, when you discuss holiday destinations with your spouse, it's probably the case that you find a place, discuss about it, then find another, comment on it and so on.
The drawbacks of this approach are presented more explicitly in the book The Myth of Multitasking. The book includes a demonstration that switching back and forth between two different tasks, makes them take more time than doing them sequentially.

Image by h.koppdelaney
The above example is a bit extreme, since it involves the spouse. Don't do it at home unsupervised. But in my opinion, the same thing applies to teams and brainstorming. It's nothing wrong with getting together for a drink/lunch and discuss about a new product or feature, but I find writing more efficient.Use mind-mapping, build a list of things that you think are suited, and then pass it on. If the others are doing the same, undisturbed, your team ends up with a more productive flow of ideas and better yet, you have everything written down.
Experiment and stick to what works for you
I'm not trying to say that this model is supposed to work for everyone. We are a team of two people, me and Sorin. It's been like this not only for the time we've been working on Teamness, but since 2005 when we started our company. We used to work from home on different projects for some clients and we always collaborated remotely. This is basically the reason for building Teamness in the first place.
In the beginning we were talking on Skype about clients, implementation details, decisions and so on. We used to have long conversations and sometimes we didn't remember everything that was discussed. We still have conversations, but when we talk about new features or design decisions, we use Teamness. We write the proposal in a message and then comment on it. This keeps it focused. We also use email from time to time, but what I want to stress upon here is that we're trying to keep the verbal communication related to our projects to a minimum, since it didn't prove efficient for us.
Please also note that I'm not trying to express that social interaction is bad, like having lunch with your colleagues or coffee breaks discussions. But when your product has 1000 features, writing things down becomes the key ingredient for a solid collaboration.
Friday, January 16, 2009
Managing project collaboration
I'm sometimes asked if Teamness is able to solve various specific project management issues, like financial resources dependencies or risk management.
Not really. Teamness is a project collaboration tool. It was born with the intent to help people gather their projects data in a centralized place, from where they would be able to share it with their colleagues.
Easy online project collaboration for teams is our tagline. Saying that I'm currently managing to collaborate on my projects using Teamness doesn't necessarily mean that Teamness is acting like a project management tool, in a way a CEO would see it.

We're not building Teamness exclusively for people in suits, but also for the aspiring freelancer or members of a family who work together on home projects. You don't need a MBA to use it, but merely a Google or Yahoo account.
We want Teamness to be flexible enough to accommodate any collaborative task you're taking. After all, real work is done by real people, which in my opinion get motivated by awarding goals, not well connected Gantt charts.
Teamness has been working fine for our purpose so far. By using it, we see different aspects that need to be improved and we're adding them in the task list and we're open to suggestions and feedback.
However, Teamness was not designed with the intent to help a project manager manage her or his team, but to help a team manage their projects together.
Not really. Teamness is a project collaboration tool. It was born with the intent to help people gather their projects data in a centralized place, from where they would be able to share it with their colleagues.
Easy online project collaboration for teams is our tagline. Saying that I'm currently managing to collaborate on my projects using Teamness doesn't necessarily mean that Teamness is acting like a project management tool, in a way a CEO would see it.

Image by David
We're not building Teamness exclusively for people in suits, but also for the aspiring freelancer or members of a family who work together on home projects. You don't need a MBA to use it, but merely a Google or Yahoo account.
We want Teamness to be flexible enough to accommodate any collaborative task you're taking. After all, real work is done by real people, which in my opinion get motivated by awarding goals, not well connected Gantt charts.
Teamness has been working fine for our purpose so far. By using it, we see different aspects that need to be improved and we're adding them in the task list and we're open to suggestions and feedback.
However, Teamness was not designed with the intent to help a project manager manage her or his team, but to help a team manage their projects together.
Tuesday, January 13, 2009
URL got shorty
On the web we're in a constant chase for higher traffic, bigger revenues, more posts and greater designs, but one thing we'd like to be short: the URL.
Some URLs are not only long, but unpleasant, like links to products on ebay:
To solve this problem, services that shrink URLs appeared. They're useful when you want to give a friend a link like the one above over IM or email. Short URLs are also handy in services like Twitter, where messages are limited to 140 characters. A short URL leaves more space for the actual text.

So far we tried three services that provide short aliases to redirect long URLs:
TinyURL
This is probably the most known service of its kind. It's been around for a long time, since 2002, and there are some funny stories related to its early algorithm for generating the short URLs' identifiers.
One neat option of TinyURL is that you may create aliases like: tinyurl.com/teamness-uptime-public or tinyurl.com/inboxdiet.
Here is an article about TinyURL and his creator, Kevin Gilbertson.
Tweetburner
When we started using Twitter, Tweetburner came in to help us generate short links and keep track of user clicks. They offer some basic analytics and daily graphs of the clicks you get on the links. We generated 35 Twurls (this is how they name the short URLs), which have been clicked 669 times until now.
Cligs
Tweetburner did a good job, until it started being quite slow for us. Then we switched to Cligs. Behind the funny name, they're offering:
When doing reasearch for this post, I came across gog.is. It's an URL shortner for Google search. If you put the keywords in the query, like http://gog.is/easy,team,collaboration it will redirect you to the Google search for "easy team collaboration".
Some URLs are not only long, but unpleasant, like links to products on ebay:
http://cgi.ebay.com/Apple-Iphone-3G-8GB-unlocked-Brand-new-No-Contract_W0QQitemZ140290947446QQcmdZViewItemQQptZCell_Phones?hash=item140290947446&_trksid=p3286.c0.m14&_trkparms=72%3A570|66%3A2|65%3A12|39%3A1|240%3A1307|301%3A1|293%3A1|294%3A50
To solve this problem, services that shrink URLs appeared. They're useful when you want to give a friend a link like the one above over IM or email. Short URLs are also handy in services like Twitter, where messages are limited to 140 characters. A short URL leaves more space for the actual text.

Image by B&M Photography
So far we tried three services that provide short aliases to redirect long URLs:
TinyURL
This is probably the most known service of its kind. It's been around for a long time, since 2002, and there are some funny stories related to its early algorithm for generating the short URLs' identifiers.
One neat option of TinyURL is that you may create aliases like: tinyurl.com/teamness-uptime-public or tinyurl.com/inboxdiet.
Here is an article about TinyURL and his creator, Kevin Gilbertson.
Tweetburner
When we started using Twitter, Tweetburner came in to help us generate short links and keep track of user clicks. They offer some basic analytics and daily graphs of the clicks you get on the links. We generated 35 Twurls (this is how they name the short URLs), which have been clicked 669 times until now.
Cligs
Tweetburner did a good job, until it started being quite slow for us. Then we switched to Cligs. Behind the funny name, they're offering:
- real time analytics
- rules you may define to direct people to different web pages, based on their geo-location
- a world map with the hits for a clig
- an API on which several tools were based
When doing reasearch for this post, I came across gog.is. It's an URL shortner for Google search. If you put the keywords in the query, like http://gog.is/easy,team,collaboration it will redirect you to the Google search for "easy team collaboration".
Wednesday, December 10, 2008
Focus on the outcome for success
One feature frequently requested on Teamness support was to display all the items assigned to a milestone. We also felt the need for an overview of all the tasks and messages that belong to a milestone, therefore the page View milestone was born.
Why was it needed?
First of all, let's think about what a milestone is. It is an objective that must be met during the development cycle. An objective is met by doing work, which is translated into tasks.
In Teamness it was possible to assign tasks and messages to a milestone, but there was no way to aggregate all these together.
How to use this feature?
One of the most powerful concepts of David Allen’s GTD system is outcome-based thinking, as Merlin Mann points out.
Setting the outcome like Merlin describes in terms of "I need to $FOO because I want to $BAR" gives you something you can use. It clearly shows the goal. But in order to avoid procrastination to settle, a listing of the steps to get you to this goal is required.
How about an example?
Christmas is coming soon. Santa Claus didn't reply to my letters, so I have to take care of the presents for my family this year. But doing Santa's job is a piece of cake with the use of the new View milestone page.
First, I'm setting the milestone, Merlin Mann style: I need to buy presents for my family members because I want them to feel the Christmas spirit.
Now that I have my goal set in clear terms, I need to build the list of steps. I create the following tasks and assign them to this milestone:
While working towards completing the tasks, often you need to store various bits of information to help you in this journey toward the goal. Teamness allows assigning also messages to a milestone.
I used this feature to store various related information, like the followings:

We hope you'll find this feature useful and that it will considerably improve your workflow.
Why was it needed?
First of all, let's think about what a milestone is. It is an objective that must be met during the development cycle. An objective is met by doing work, which is translated into tasks.
In Teamness it was possible to assign tasks and messages to a milestone, but there was no way to aggregate all these together.
How to use this feature?
One of the most powerful concepts of David Allen’s GTD system is outcome-based thinking, as Merlin Mann points out.
Setting the outcome like Merlin describes in terms of "I need to $FOO because I want to $BAR" gives you something you can use. It clearly shows the goal. But in order to avoid procrastination to settle, a listing of the steps to get you to this goal is required.
How about an example?
Christmas is coming soon. Santa Claus didn't reply to my letters, so I have to take care of the presents for my family this year. But doing Santa's job is a piece of cake with the use of the new View milestone page.
First, I'm setting the milestone, Merlin Mann style: I need to buy presents for my family members because I want them to feel the Christmas spirit.
Now that I have my goal set in clear terms, I need to build the list of steps. I create the following tasks and assign them to this milestone:
- Make the budget for the presents
- Find a nice blue shirt size 42 for dad, since I heard him saying he needs one
- Decide if I buy my mother some piece of jewelry or an electronic photo frame
- Look for websites where I can order that thing my girlfriend was dreaming about for months
While working towards completing the tasks, often you need to store various bits of information to help you in this journey toward the goal. Teamness allows assigning also messages to a milestone.
I used this feature to store various related information, like the followings:
- I built a list of websites with Christmas gifts ideas.
- I took some paragraphs from some blog posts about what others are considering buying for their family members.
- Talking to my friends I asked what they are buying for their parents and then put all the notes down in a message named "Presents my friends are considering".

We hope you'll find this feature useful and that it will considerably improve your workflow.
Friday, December 5, 2008
Tooth brushing techniques for geeks
The tooth brush industry seems to be the most dynamic there is. Every time I need to get a new one there is a whole new generation on the shelves. The classic "normal" ones are long gone.
Now you can find weird flexible ones, dragon style tooth brushes that clean both sides of the mouth at the same time and tooth brushes with plastic extensions that massage your shoulders while you use them.
But isn't the conscientious usage the key here?
Yesterday I attended the GeekMeet in Stockholm. Mingling with people in between presentations by the wise redheaded Chris Heilmann, I noticed that even the geeks consider a bit overwhelming the amount of web tools that pop up every day.
Is this good or bad? I think it's like the tooth brushes. Get a fancy one or get a more classical one, but use it religiously.
One of the presentations was called Playing With The Web in which Chris advocates for reusing already built APIs and tools in web development. There are a couple of nice existing platforms to build upon out there. Using them gets even easier to make new products. And that's a good thing because it generates more options for us, the users.
But I think we're becoming sloppy in what we're doing. We're buying too many clothes and not using them, we're changing our mobile phones every other month for a newer model, even before using the one we have to the full potential and we're also just trying out new web tools without getting the best of those we already use.
Or maybe it's just me. I have to get this.
Now you can find weird flexible ones, dragon style tooth brushes that clean both sides of the mouth at the same time and tooth brushes with plastic extensions that massage your shoulders while you use them.
But isn't the conscientious usage the key here?
Yesterday I attended the GeekMeet in Stockholm. Mingling with people in between presentations by the wise redheaded Chris Heilmann, I noticed that even the geeks consider a bit overwhelming the amount of web tools that pop up every day.
Is this good or bad? I think it's like the tooth brushes. Get a fancy one or get a more classical one, but use it religiously.
One of the presentations was called Playing With The Web in which Chris advocates for reusing already built APIs and tools in web development. There are a couple of nice existing platforms to build upon out there. Using them gets even easier to make new products. And that's a good thing because it generates more options for us, the users.
But I think we're becoming sloppy in what we're doing. We're buying too many clothes and not using them, we're changing our mobile phones every other month for a newer model, even before using the one we have to the full potential and we're also just trying out new web tools without getting the best of those we already use.
Or maybe it's just me. I have to get this.
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.
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.
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
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.
Tuesday, November 18, 2008
Login through Google and Yahoo
In order to have an account in Teamness one needs an email address. The reasons for this are simple. Firstly, the email address is part of the login credentials. Secondly, Teamness sends notifications by email, so asking the users for a valid email address is a guarantee that they will have a good and consistent experience.
Delegating the login
By analyzing our logs we noticed that the most of the accounts were created with Gmail addresses. Yahoo came second.
In this case, why not take advantage of the authentication delegation mechanism from these services? Yahoo puts it best here: You build great web applications. We have millions of users who store their data on Yahoo!. Browser-Based Authentication (BBAuth) makes it possible for your applications to use that data (with their permission).
Why delegated authentication?
It's easier for everyone to remember her or his Gmail or Yahoo account, which she/he has been using for a while, instead of a new one specially created.
The decision to make it easier for new users to try Teamness was eased by the fact that both Google and Yahoo offer the support of delegating the authentication.
What about the existing users?
New users don't have to remember new passwords now. But what about the exiting ones, that already created accounts?
They can associate their Yahoo and/or Gmail accounts to the account they're already using. I can now use my old Teamness account, along with my Gmail and my Yahoo account, so I can use all these three to login into the same account in Teamness.
Is this safe?
Yes. The authentication process is delegated to Google or Yahoo, which ask you if it's ok for Teamness to access your details, consisting in your name and your email address.
If you're still skeptical, just think about this: why would Google and Yahoo give away users' sensitive data, like passwords? They won't and they don't do it.
You may find more information about these services in the following places:
Delegating the login
By analyzing our logs we noticed that the most of the accounts were created with Gmail addresses. Yahoo came second.
In this case, why not take advantage of the authentication delegation mechanism from these services? Yahoo puts it best here: You build great web applications. We have millions of users who store their data on Yahoo!. Browser-Based Authentication (BBAuth) makes it possible for your applications to use that data (with their permission).
Why delegated authentication?
It's easier for everyone to remember her or his Gmail or Yahoo account, which she/he has been using for a while, instead of a new one specially created.
The decision to make it easier for new users to try Teamness was eased by the fact that both Google and Yahoo offer the support of delegating the authentication.
What about the existing users?
New users don't have to remember new passwords now. But what about the exiting ones, that already created accounts?
They can associate their Yahoo and/or Gmail accounts to the account they're already using. I can now use my old Teamness account, along with my Gmail and my Yahoo account, so I can use all these three to login into the same account in Teamness.
Is this safe?
Yes. The authentication process is delegated to Google or Yahoo, which ask you if it's ok for Teamness to access your details, consisting in your name and your email address.
If you're still skeptical, just think about this: why would Google and Yahoo give away users' sensitive data, like passwords? They won't and they don't do it.
You may find more information about these services in the following places:
Wednesday, November 12, 2008
Twitter pals
We are big fans of Twitter and with its growing popularity we believe it's a very good tool to make contacts. We recently started using Twitter to promote Teamness through it and we try to stay focused on this purpose, without being obtrusive. At the same time we watch what other people are doing and writing about.
To make our Twitter life easier, we're using a couple of related tools and in this post I'm going to list them with a short description:
Twitter Search
We mentioned Twitter Search already in this post, writing about the way we use it to stay up to date with Teamness being mentioned in the tweets.

Tweetburner
When you include an URL into an update, Twitter converts it to a short one using TinyUrl. Tweetburner does the same thing, only that it tracks the links your URL receives. This way you would know how many people clicked on the URLs in your messages.

FriendOrFollow
With FriendOrFollow you may easily see who you're following that's not following you back and who's following you that you're not following back. You may also see your mutual follow contacts. It's a fast way to follow back at interesting people who are following you already.

Tweetscan
Tweet Scan searches Twitter and other micro blogging services and delivers reports on email or RSS.

Twittercounter
This tool shows you how popular you are on Twitter. You'll get a nice graph with the daily status of your followers, so you'll see how many more are following you day after day. Or, sadly, how many stopped following you.

Yoono
Yoono is a browser add-on that aggregates social networking information and keeps it in one place. It comes in very handy especially if you're active on a few social networks and you want to handle all of them from one place.
No matter what are the tools used, make sure you use Twitter for business the right way. As written in the post, it's more valuable to actually interact with people than hastily promoting your products.
Here is another list of Twitter related services and in this post you'll find a presentation of five ways to connect to people on Twitter.
To make our Twitter life easier, we're using a couple of related tools and in this post I'm going to list them with a short description:
Twitter Search
We mentioned Twitter Search already in this post, writing about the way we use it to stay up to date with Teamness being mentioned in the tweets.
Tweetburner
When you include an URL into an update, Twitter converts it to a short one using TinyUrl. Tweetburner does the same thing, only that it tracks the links your URL receives. This way you would know how many people clicked on the URLs in your messages.
FriendOrFollow
With FriendOrFollow you may easily see who you're following that's not following you back and who's following you that you're not following back. You may also see your mutual follow contacts. It's a fast way to follow back at interesting people who are following you already.
Tweetscan
Tweet Scan searches Twitter and other micro blogging services and delivers reports on email or RSS.
Twittercounter
This tool shows you how popular you are on Twitter. You'll get a nice graph with the daily status of your followers, so you'll see how many more are following you day after day. Or, sadly, how many stopped following you.
Yoono
Yoono is a browser add-on that aggregates social networking information and keeps it in one place. It comes in very handy especially if you're active on a few social networks and you want to handle all of them from one place.
No matter what are the tools used, make sure you use Twitter for business the right way. As written in the post, it's more valuable to actually interact with people than hastily promoting your products.
Here is another list of Twitter related services and in this post you'll find a presentation of five ways to connect to people on Twitter.
Wednesday, November 5, 2008
5 questions to ask yourself when evaluating project management tools
Students participate in online groups to chat and share information. Small companies use emails for communication and network drives for storing documents. Non-profit organization may rely on a free online solution. Software departments could keep the schedule in an Excel file. Some individuals use notebooks and pens to put down appointments in a paper agenda or type reminder items in an online or desktop solution on the computer.
The name and the complexity of the tools used vary with the type of organization and the activity performed. Every organization, from big companies to individuals, uses a mechanism for project management, even if they don't call it like this.
The name and the complexity of the tools used vary with the type of organization and the activity performed. Every organization, from big companies to individuals, uses a mechanism for project management, even if they don't call it like this.
Image by El FotopakismoIn this post I will try to identify a few preliminary questions that may be asked to asses the needs for an online type of project management solution. It is not meant to be a complete and exhausted list of questions, but more of a guide for choosing a solution that will best suit the needs.
1. What is the structure and behavior of your organization?
Project-driven organizations have different internal processes than functional-driven ones.
Examples of project-driven organizations are: a construction company who builds wooden houses, a group of students working on a class assignment or even a wedding photographer doing assignments.
A functional-driven organization is usually a service or information company, like a small family hotel or a department in a bank working with processing checks. Such an organization may need to define either small multiple projects, which can be archived when becoming inactive or define fewer ongoing ones for each type of activity.
2. What is the complexity of your projects?
The number of people involved and the estimated activity must be taken into account. A project generating a lot of data, with a high posting frequency needs a fast solution on the web and options to filter and group the data for easier retrieval. Searching is a must, since it's easier to archive and look for, instead of spending time classifying the data.
3. What is the life expectancy of a project?
Some projects don't have a deadline, like an on-going activity for a functional-driven organization. They may require task grouping under milestones, though. A project with a long life span faces the challenge of getting old data out of the way, but being able to retrieve it at any times.

Image by lumaxart
4. Are the projects internal?
If everything is public for everyone in the project, a solution with complicated privacy policies is not needed. But if you need your clients to have a peek once in a while, you probably don't want to expose everything from under the hood.
5. Are you already using any software for disciplines related to your activity?
If there is already an established procedure for certain disciplines involved in the project, like requirements management or issue tracking, the transition to the new solution must be as smooth as possible. The learning curve for your team should be as easy to climb as possible. Trying to keep the same type of workflow can save a lot of time.
This list doesn't cover many aspects related to choosing a solution, for instance there is nothing about security. I wanted to keep the list focused on the workflow of the team.
Simple tools like online todo lists, text or Excel files may be more efficient than a complex solution, so it's important to identify the requirements prior to deciding for a given solution.
Sunday, November 2, 2008
Blogging for a startup
A lot of blogging resources recommend having a blog for your business. A blog can be useful for various reasons, the most important one being that you may promote your product.
I believe that for promoting the product, the content of the blog must be interesting enough for people which are not familiar with the product to come and read the posts. Then, they find out about the product and use it, fulfilling the mission of the blog and not the other way around, having the product sending readers to the blog.
I believe that for promoting the product, the content of the blog must be interesting enough for people which are not familiar with the product to come and read the posts. Then, they find out about the product and use it, fulfilling the mission of the blog and not the other way around, having the product sending readers to the blog.
Image by El FotopakismoSome of the general reasons mentioned for having a blog as a business include:
- Announcing new features. This is good, but then your readers would be the users of your product. Who else is going to read a list of upcoming new stuff you worked a lot upon, other than the already existing users? In Teamness, we made a special page called News, where we're adding information about new features. There is also a RSS feed provided for this News page. This way, we spare the users who are only interested in the product to spend time going through our blog posts.
- Frequently asked questions about the product. Why spread them around posts in a blog, when you can display all of them with a searchable feature in your website? In Teamness we gathered them all under the Help page. We also implemented a mechanism to offer contextual help, by sending the user directly to the questions in Help referring to the page she/he started from.
- What are you working on. This is also related to announcing new features. It might be interesting only for existing users.
- A mix of the above. Not such a good idea, in my opinion. As problogger describes it, writing about multiple topics on a blog makes users "became disillusioned with the blog". People wanting to know if a new feature is available will become annoyed by other types of posts.
Many of the advices found on the web regarding blogging for business omit the fact that as a startup, you would want to maintain a blog in order to get users for your product. Therefore, we think that the blog has to become attractive, independently of the product.
We are continuously trying to find subjects to write about in order to keep this blog interesting. We found two interesting directions:
Writing about Teamness as a startup and the way we try to grow Teamness as a product. We often find blogs on the web for various products which write about their development process and it's an interesting and useful resource.
Writing about product collaboration and management methodologies and how can these be applied to small businesses. Teamness users are people working and collaborating on various projects. Having this topic on the blog could bring new insights for some and could introduce Teamness to them.
What's your opinion about blogs for businesses? Also, what subjects would be of interest to you on this blog?
Friday, October 31, 2008
Feedback for a startup
Every web service needs some kind of feedback mechanism. When working on a startup, feedback is probably even more valuable than when the product is mature. Here are some thoughts regarding the feedback for Teamness and how we're trying to make it easy for our users to make themselves heard.
Image by Orange_BeardWhy is feedback important for a startup?
It keeps you on the right track. You'll focus on the things that users actually demand, beside the ones that you think are desired. This doesn't mean that the features you're thinking about are useless, but it may imply they're less important than you think. Then it comes to prioritizing in an efficient way.
It increases the motivation. When people start using your application, this will constitute a good incentive for you to keep up the work. Getting feedback from them is a way of knowing that they're actually using it.
Situations you didn't consider show up. The diversity of the users generates context you probably didn't think about before.
How do we get feedback for Teamness?
Right from the beginning, we asked ourselves how we can make it easy for the users to send us feedback. As I pointed out in a previous post about support, it's hard to obtain feedback in the beginning stage of a product, because most users just walk away if something doesn't work.
We cannot change this behavior. After all we are all users and act in the same way, but we can make sure there are a lot of options for people to contact us. Here is a list of current choices Teamness users have for that:
1. Direct feedback from any page in Teamness
The user must get in the situation of searching for how to contact us. The method to do it should be right there and this is why we added a link called "Send feedback" in the header of every page. The link sends the user to a page with a simple contact form. Since we added this feature, we received more messages this way than through email.
2. Email
This is how we used to get most of the feedback, before implementing the option above. The emails usually consist in bug reports or feature requests, but we also receive business proposals.
3. Blog
A blog is a good place to improvise in all directions regarding the project. Using a blog you may conduct polls, invite users to participate in discussions and so on. We started blogging here after we launched, but I think that if we would've started before, like these guys did, it would've helped collecting more feedback and in an earlier stage of the product.
4. Forum
We have set up a message forum as an environment for users to provide feedback. However, we observed that most of them prefer the private way of a direct message, like email or the contact form. In any case, a forum is good in the long run, because it's a way of allowing users to engage in conversations about your product amongst themselves.
Don't get carried away
Users want the products they’re using to fit their needs as a glove. However, this is very difficult to achieve, due to the diversity of the necessities out there. We're trying to balance the options we have and to refrain from plunging into implementing a feature that will make life easier for a user, unless it's obvious it will make life easier for many users.
One of the most common advices for small web startups from experienced entrepreneurs is to launch early. A strong reason for that is feedback accumulation for the reasons described in the beginning of this post. Of course, you cannot launch a product that does pretty much nothing and expect users to come and tell you what to do, but providing a single solution for a single problem may be a good start.
Saturday, October 25, 2008
Monitor your web presence

Image by fazen
A celebrity is used to being talked about. A known business is mentioned in too many places to bother keeping track of them. But with a small startup like Teamness we cannot afford not being aware of the places on the web where we’re mentioned.Why is it important to know where you're mentioned?
We want to know what's being said about Teamness for the following reasons:
- Start new relationships. Relationships, even web ones, are good for the business. People are more likely to use your product if they know you. And they’re more likely to recommend your product.
- Participate in conversations about your product. People comment on reviews of your product and sometimes they ask questions about it. Other people make various assumptions, which may be wrong and if left unclear or unanswered, they might create a false perspective over the product. It's a good thing if conversations about your product on other websites are not left undone.
- Get notice about critical opinions. Some critiques may be wrong and it could be good to correct the perception. You may also come upon nasty comments about your product, perhaps in the forums of the competitors. This is unpleasant, but it's something we don't want to ignore.
- Find out mentions of your blog posts. If you have a blog in which you promote the product, it's good to know if some of the posts are mentioned. This way you may also track successful posts of your own.
How do we know where Teamness is mentioned?
My favorite method to watch for Teamness on the web is by using RSS feeds. I created a folder called "About Teamness" in Google Reader, which is the RSS aggregator I'm using. Here I added a couple of feeds to let me know where Teamness pops up, by using various features from a few web services, as following:
Technorati watchlist
Technorati allows you to watch various items by using keywords or URLs. In the watchlist page I inserted the “Teamness” keyword and I obtained a RSS feed which I then added in the “About Teamness” in Google Reader. If you don't like RSS (and I noticed there are still a lot of people who don't), you have the possibility to access your Technorati watching list in the page itself, without using the RSS feed.
Type the search term in either Google News or Google Blog Search and along with the search results, you'll get a RSS or Atom feed. I typed “Teamness”, of course, and I then used the two RSS feeds offered by Google.
Using search.twitter.com you may input search terms for tweets and you can get a RSS feed. They even offer advanced search capabilities, so you may get only tweets with "positive attitude :)", for instance.
Delicious
Delicious offers a feature called Subscriptions, through which you may subscribe to certain tags used by all the users. I created a subscription for the tag "Teamness" and I also got a RSS feed for it, which went into the "About Teamness" folder. Here is a nice post explaining how to use Delicious subscriptions.
Other ways of monitoring your presence
Using Google Alerts is another way of staying up to date with your presence on the web. Google Alerts are "email updates of the latest relevant Google results (web, news, etc.) based on your choice of query or topic". You may track keywords through various media like news, blogs, web, groups and video.
Other services like TechRepublic or Magnolia offer similar capabilities which may be used in the same way to keep track of your startup.
Tuesday, October 7, 2008
The five seconds test
The other day, one of our Twitter contacts pointed out the 5-Second Test for measuring your site's content pages. It took about 5 seconds to set up a 5-seconds test with a screenshot of the Teamness web page here.
What's the test about?
As the test page itself states, it consists in showing an image of the front page of the Teamness website for 5 seconds. Then the visitor is asked to fill in 5 of the things she/he remembers. It's a quick technique for evaluation the impact of your web pages. And it's also fun.
The results of the test
1: easy
2: online
3: project
4: collaboration
5: teams
1: teamness
2: easy collaboration
1: online
2: application
3: easy
4: team
5: orange colour
1: screenshot to right
2: how to get started
3: teamness logo with small dots
4: layout breakdown - 2 upper half
1: a project management application
2: collaboration
1: toolbar
2: top menu
3: two columns design
4: some pictures and text
1: teamness logo upper left made of tiles
2: screenshot of a web interface upper right
3: sign up button, big - suggestive
4: the word 'easy' in a title
5: pleasant color scheme, good use of nonintrusive fonts
1: teamness
1: easy online colaboration for teams
1: easy project collaboration tools
2: teamness
3: screenshots
4: blue, red
What do the results say?
The test doesn't tell much, but if in 5 seconds you manage to transmit your site's message to the viewer, then it's more probable you'll have the user for longer on your website. The longer it takes a visitor to understand what your site is about, the higher the chance of leaving the page.
Some of the conclusions are:
What's the test about?
As the test page itself states, it consists in showing an image of the front page of the Teamness website for 5 seconds. Then the visitor is asked to fill in 5 of the things she/he remembers. It's a quick technique for evaluation the impact of your web pages. And it's also fun.
The results of the test
1: easy
2: online
3: project
4: collaboration
5: teams
1: teamness
2: easy collaboration
1: online
2: application
3: easy
4: team
5: orange colour
1: screenshot to right
2: how to get started
3: teamness logo with small dots
4: layout breakdown - 2 upper half
1: a project management application
2: collaboration
1: toolbar
2: top menu
3: two columns design
4: some pictures and text
1: teamness logo upper left made of tiles
2: screenshot of a web interface upper right
3: sign up button, big - suggestive
4: the word 'easy' in a title
5: pleasant color scheme, good use of nonintrusive fonts
1: teamness
1: easy online colaboration for teams
1: easy project collaboration tools
2: teamness
3: screenshots
4: blue, red
What do the results say?
The test doesn't tell much, but if in 5 seconds you manage to transmit your site's message to the viewer, then it's more probable you'll have the user for longer on your website. The longer it takes a visitor to understand what your site is about, the higher the chance of leaving the page.
Some of the conclusions are:
- The word Easy stands out.
- Collaboration is also observed, but it's not always put together with Easy, as desired.
- The term Project is not noticeable, meaning that the idea of Easy online project collaboration needs more than 5 seconds to get into the mind of the user.
- The name of the service, Teamness, is easy to remember and to make note of it.
- The colors are noticeable in connection with the service.
Thursday, October 2, 2008
Are you confident in SaaS tools?
Image by lumaxartRecently I was discussing with a friend about Software as a Service (SaaS) tools. Teamness is such a tool, hosted as a service and provided to customers across the Internet.
My friend expressed the concern of storing his data in an online tool. Me, on the other hand, I feel dependent on online tools, using them for email, todo lists management, collaboration, notebooks, documents storage etc.
I tried to list a few of the advantages of this type of service for him:
- No upfront investments in infrastructure, server investment, training, support personnel, and installation.
- The provider of the service takes care of the scaling. If there are more users in the system, you don't need to buy more hardware.
- You only pay for how much you're using. Different plans in the SaaS are tailored for different needs.
- You only pay for how long you're using. If you decide to quit, you're not tied to any contract.
- Security might be better with SaaS. These services usually offer SSL encryption, backups, database management etc. Also, they invest in vulnerability testing from security companies. Teamness uses the McAfee Secure service.
- No worries about updates. The version you're using is the last one available.
- High availability of the data. The tool is the provider's business, so they strive making it as available as possible.
Subscribe to:
Posts (Atom)




