This template was developed to help Product, Design, and Technology teams organize themselves in one place and gain visibility into features and their requirements.
With a role very similar to that of User Stories, this template can replace them. The idea is to promote collaborative work among Designers, Engineers, and Product Managers.
The focus is on what the user needs to do to complete a task, organizing this task into a table that controls information about these actions and provides guidance on where to find this information across various Design files and relevant Handoff documentation.
It does not replace your PRD (Product Requirements Document).
When creating a new feature, it has requirements that may come from the business area, the system, the company’s legal department, and user experience requirements.
There are various requirements that are part of a feature, and it’s easy to lose track of them. This template aims to organize and facilitate the visualization of each requirement, providing details so that the team can understand what they are creating and which important details should not be overlooked.
To fill out this template, consider a feature to create, such as the Login of an application. Start with the question:
What does the user need to complete this task?
Fill in as the requirements become clear. For a login, the user needs to: