Manage non-development project tasks with features and to-dos

Depending on the complexity of a non-development project, you can use Aha! to-dos or features to manage tasks within your project. This article explains both and highlights what works best for the types of tasks you are managing.

When to use to-dos

To-dos are nice, light-weight task management tools. You can enter basic information about the work to be done and assign it to a team member for completion. They are perfect for work that does not require a sophisticated workflow, staging, or layers of data. For examples of common ways to use to-dos and some best practices, see "Use to-dos to manage work across the team."

Due to their simplicity, they don't work quite as well for more complex tasks. And depending on your requirements, features may be a better option. Read more about features below.

When to use features

Features can represent any work required to deliver a complete product experience, such as user stories, marketing tasks, or design work. Features should be used when your project needs:

  • more sophisticated workflow for managing the different stages of work. 
  • Additional project attributes that are handled through custom fields for reporting and filtering purposes, such as team, customer, priority, and more. 
  • Time estimates for work to be done. 
  • Time tracking for actual time spent on the task — common for expense reporting for certain projects, such as consulting.

Note: If you do use features to manage your project tasks, you can customize the terminology to refer to features as tasks, work items, or whatever is relevant for your usage.


Was this article helpful?
0 out of 0 found this helpful