Daniel,

First of all thanks for using TeamLook and taking the time to ask this insightful question.

We do not link Team Tasks to Outlook Tasks after creating an Outlook Task from a Team Task.  We thought about this for a long time and came up with the following reasons:

1. For a Team Task there is a simple state/transition model that somewhat maps to Outlook Tasks.  However, for most Work Items, the states they can be in does not map to the partially completed/completed state definition of an Outlook Task.  Because the Team Task is defined in the Process Template and we wanted to be Process Template agnostic (ie. support all/customized process templates), we did not map any work item type semantics to an artifact in Outlook.  However, there are very interesting scenarios once we cross that line which can be enabled.  If customers send us feedback (which you have), we'll definitely consider it for v2.
2. Since Tasks (like other work items) affect Team Reporting and visibility, we thought it would be nice for users to use the Outlook Task list as a personal store.  In fact, without using the collaborative features of Sharepoint, Outlook Tasks are personal for the most part unlike Team Tasks.  For example, it's nice to have Outlook Tasks that migrate to my Smartphone, but they are not actionable on my phone since I'm likely not at my workstation.  In a sense, it's a reminder.  When I complete a Team Task, I want to notify my Team that it's done.  Perhaps an interesting way to solve this problem is to have TeamLook automatically check what Team Tasks that were used to create Outlook Tasks have been completed and mark the Outlook Tasks appropriately.  I'm hesitant in going the other direction...  Thoughts?

Cheers,
Juan