SwiftTraction Projects and Actions

The SwiftTraction Beta got another new report today along the same lines as yesterday’s addition. This one displays a comparison of the times that each of your users has spent performing a particular action, and compares that time to any estimates you’ve alloted for the Action.

While our test data isn’t extremely comprehensive at the moment, this screenshot can give you a bit of an idea of what you’re working with. Each Project can have any number of Actions, and you can set a projected amount of time for each of the individual Actions. The time estimate for the whole project is just the sum of all of the actions within the project.

The new SwiftTraction Beta Action-Time Report

There been some discussion around here about how to the clarity of these labels in SwiftTraction. To break it down:

  1. A Projectis a set of Actions & Activities
  2. An Action is a general type of action you can take
  3. An Activity is a specific instance of an Action

For those of you interested in SwiftTraction as a time management tool: how do these concepts and labels work for you? What do you like or dislike about them, and how would you like to see them evolve over the course of SwiftTraction’s development? Some of us have been thinking that “Action” & “Activity” should be switched, so that an “Activity” is the category of task and an “Action” is a single instance of performing it.

We’re thinking seriously about how to structure the workflow of SwiftTraction right now, centering mainly on the development of wizards for setting up users and user groups, as well as projects. We’d like to hear about your ideal workflow for setting up and managing your projects. So, if you haven’t already, grab a copy of the beta and let us know what you like and what you don’t in terms of workflow and usability.

A trial is worth a thousand words.
Get started today, no credit card required.