Aha! is a system for product managers; as such, to-dos are not tasks for developers. To-dos are a powerful way for product managers to manage tasks that need to be completed. Additionally, to-dos are a way product managers can collaborate with other key stakeholders on releases, phases, milestones, features, and requirements.
The intent of to-dos is to assign work to be completed, versus specifying features, or requirements, to be completed. Example to-dos at the feature, or the requirement level, could include:
- "Review this feature description - did I miss any important details?"
- "Add a new requirement to cover the API work."
- "Add an Aha! score for this feature."
In these cases, to-dos in Aha! should be complete before features or requirements are sent to the engineering team to build.
To-dos can also be used to manage cross-functional activities that product managers are involved in such as Go-to-Market messaging, design tasks, or other key tasks that are a part of the new customer experience. Sample cross-functional to-dos might include:
- “Review content for support guides.”
- "Give me feedback on the mockup."
- “Get approval from Jane on release phase changes.”
In these cases, to-dos in Aha! should be complete before releases, phases, or milestones are marked as complete.
To-dos and their associated attributes, such as assignee, status, due date, etc., can all be reported on. Users can get a quick snapshot of all their to-dos by going to the Home menu and selecting My Work. To-do assignees will receive email notifications for any tasks that require their attention.
When to-dos are added, they are manually sortable so they can be organized based on due date or other personal preferences. To sort, hover over a to-do until the cross appears. Click on the cross and drag it into the desired and logical position.