Admin Onboarding - Item Workspace -Right Bar: Best Practice time estimates

There's an easy way to get instant visibility on having too many tasks or tasks that might take too long for a given portion of your project.

Create estimation ranges for each of your item types to track whether—when combined—they will reach the outer level of your estimate for the entire set.

Here's how that works.

In Settings, Create a range for each of your task-level items (1).

In our example below, tasks are our smallest types, so we created suitable ranges of a certain number of hours from xxs tasks all the way to xl tasks.

We also created larger ranges for what we would consider small, medium and large Capabilities, which is the next level up in our item type hierarchy. (1) We could choose to do this with our Module item types as well. We will just show Tasks and Capabilities for this example.

Once we defined our ranges, we created collections named for each type of item and then grouped our ranges into their collections. Then we assigned the collection we wanted to use to our item type. We used related names to help us match our ranges to our collections.

Once in our system, we can apply estimates to each task. Since Tasks are children of Modules in our item hierarchy, we can easily see if the Tasks we have in a given module exceed the sizing we have defined for its (parent) Module.

In our example below, our Module item displays an orange warning icon. This warning lets us know that based on our estimated time, this module could take longer than our definition of a module of this size:

You can click on the warning icon to see the completion stats and the warning details.

This warning icon shows throughout the system, elevating the potential issue.

The takeaway: The better you decompose your work into small estimated tasks that roll up into bigger estimated buckets, the better predictability you have.