In the dynamic realm of product management, mastering the art of organizing and understanding your data is paramount. Productboard's default fields are the foundation upon which your product-related information is structured.
Whether you're a seasoned product manager or just starting your journey, understanding these fields and their best practices can significantly enhance your workflow efficiency.
In this article:
- Customer Importance Score
- Status
- Effort
- Timeframe
- Timeframe visualization
- Health
- Owner
- Hierarchy
- Portals
- Teams
- Dependencies
- See also
Customer Importance Score
The Customer Importance Score quantifies the potential impact of a product idea or feature by evaluating the number of users it will benefit or affect, weighted by how important it is to them. It provides a numerical representation of the idea's relevance and significance to users, helping product managers prioritize initiatives that align with customer needs and preferences.
The higher the Customer Importance Score, the more substantial the positive effect the idea can have on the user base, guiding teams in making data-driven decisions to enhance user satisfaction and product success.
For more information, see Use the Customer Importance Score to surface your top-requested features.
Status
The Status field shows where an item currently sits in your product development lifecycle. Every item that has a status displays a colored icon near its name — you'll see this consistently across boards and in item detail sidebars. Clicking the icon lets you choose a new status for that item right away.
Status is one of the most versatile fields in Productboard. Any board can be filtered by status, so you can quickly create focused views that answer specific questions (for example, a board that shows only items in Discovery, or one limited to everything that's In progress). Status can also be displayed as a column on grid boards, giving you a clear, scannable overview of where multiple items stand at a glance.
Not all item types share the same default statuses, and features and subfeatures share a single status list. You can customize that list to reflect the phases your team actually uses.
For more information, see Customize status values for items.
Effort
The Effort field quantifies the resources, time, and complexity of implementing a specific product idea or feature. It allows teams to assess the feasibility of an idea and make informed decisions based on the effort required for execution. Product managers can prioritize tasks effectively by assigning effort estimates, and balancing high-impact ideas with manageable workloads.
This field aids in resource allocation, ensuring that teams focus on initiatives that align with their capacity and expertise, leading to efficient project planning and successful product development.
For more information, see How does the effort field work?
Timeframe
The Timeframe field lets teams specify the planned duration or deadline for implementing a product idea or feature. It helps set clear project timelines, allowing teams to prioritize tasks and plan their work efficiently. Product managers can align development efforts with business goals and customer expectations by assigning specific timeframes to ideas.
This field provides a structured approach to product management, ensuring that tasks are completed within the desired timeframe and facilitating timely product launches, updates, and enhancements, enhancing overall productivity and customer satisfaction.
For more information, see Use timeframe columns to plan your items against time.
Timeframe visualization
This field adds your timeframe data to a grid board as a mini Gantt chart, making it easy to compare timeframes across many items. This is particularly useful for seeing how your work lines up with concurrent projects, which is critical for quarterly planning and other strategic activities.
You can configure the timeframe visualization column's granularity for a lower- or higher-level view, apply sorting to it just like other columns, and easily edit items' timeframes on the chart without having to add the dedicated Timeframe column.
For more information, see Use timeframe columns to plan your items against time.
Health
The Health field assesses the current state or progress of a product idea or feature. It provides a quick snapshot of its status, indicating whether it's on track, at risk, or needs attention. Teams can use this field to gauge the overall health of their projects, identify potential bottlenecks, and prioritize tasks accordingly.
By regularly updating the Health field, product managers can ensure that projects are continuously monitored, and necessary actions are taken to maintain or improve their status. This helps in proactive issue resolution, efficient resource allocation, and successful project outcomes.
For more information, see Provide health updates for your features
Owner
The Owner field designates a specific team member who is responsible for overseeing and driving the progress of a particular product idea or feature. This field helps establish clear accountability within the team, ensuring that every aspect of the idea's development is managed efficiently. The owner takes charge of communication, decision-making, and coordination, streamlining the workflow and ensuring that tasks are completed in a timely manner.
By assigning owners to ideas, Productboard facilitates effective collaboration, encourages an ownership mentality, and enhances overall team productivity and project management.
Hierarchy
The Hierarchy field allows users to establish a structured relationship between different product ideas, features, or subfeatures. It enables teams to define parent-child connections, outlining how smaller tasks contribute to larger projects. This field is invaluable for organizing complex product structures, breaking them down into manageable components, and understanding their interdependencies.
By using the Hierarchy field, teams can visualize the big picture while managing the details effectively. It aids in clear project planning, facilitates better communication among team members, and enhances overall project efficiency and clarity.
Portals
The Portals field refers to a feature that allows users to create customized portal cards for features or spaces tailored for specific stakeholders, such as customers, internal teams, or partners. These portal cards serve as dedicated platforms where stakeholders can view, provide feedback, and engage with the product-related information relevant to them.
For instance, customers can access product updates, FAQs, and submit feature requests through a customer portal. Internal teams might collaborate on product development details within a separate portal.
Organizations can use the Portals field to enhance stakeholder engagement, gather valuable insights, and maintain transparent communication channels. It ensures that different groups can access the information they need, fostering collaboration, improving customer satisfaction, and streamlining product management processes.
For more information, see Getting started with portals.
Teams
The Teams field allows users to categorize and assign specific product ideas, features, or tasks to different teams within an organization. By utilizing this field, teams can clearly define which department or group is responsible for implementing or overseeing a particular item.
This categorization streamlines communication, ensuring the right team members are involved in relevant discussions and decision-making processes. It fosters collaboration by creating a structured approach to team assignments, enabling efficient delegation of tasks, and facilitating teamwork.
Additionally, it enhances accountability, as team ownership and responsibilities are clearly defined, leading to improved coordination, productivity, and successful project outcomes.
For more information, see Organize members into teams.
Dependencies
The Dependencies field allows users to specify relationships between different product ideas, features, or subfeatures. This field is crucial for indicating dependencies, such as one task relying on the completion of another before it can begin.
By utilizing this feature, teams can visualize the order in which tasks should be tackled, ensuring that prerequisites are met before moving forward. It aids in effective project planning, preventing bottlenecks, and smooth workflow transitions.
Identifying dependencies in Productboard fosters clarity, enabling teams to make informed decisions and prioritize work based on the interconnections between tasks, optimizing productivity and project timelines.
For more information, see Track feature dependencies to mitigate risks.