type
status
date
slug
summary
category
tags
icon
password
This article outlines a comprehensive product management workflow, detailing key activities, tools, and best practices for effective product planning and execution. It covers goal setting, task identification, project prioritization, and performance evaluation, providing practical insights for product managers to streamline their processes and improve overall productivity.
Purpose of These Activities
- Learn to identify the right tasks
- Learn to find tasks aligned with known directions
- Learn to prioritize and complete high-priority tasks efficiently
How to Accomplish These Tasks
Workflow | Tools | Tips |
Define goals and metrics (Monthly metrics meeting) | •Goals and Metrics List: Focus on current situation, estimated values, sorted by metric importance | • Provide calculation formulas and data sources
• Provide current metric values |
List potential tasks based on established goals (Monthly brainstorming session) | •Project Inbox: Focus on current situation (historical ideas have no value), consider metric fulfillment, categorize by metrics (1st), sort by potential benefits (2nd), note sources (3rd)
•
◦ Expert advice
◦ Personal collection
◦ Brainstorming ideas | • Establish a mechanism for inbox management (direct deletion/strikethrough/mark as complete)
• Avoid distinguishing sources; consolidate ideas from different origins |
Manage current and upcoming projects, their priorities, and delivery commitments (Monthly metric planning/Weekly project meetings) | •Ongoing Projects, Project Board, or Requirement Pool: Focus on current situation, consider project priority (combining benefits and urgency), sort by priority, note timestamps (submission time for FIFO, launch time for delivery commitment, evaluation time for benefit commitment). Note:
•
◦ This list should be unique to ensure timely updates
◦ Exclude low-priority projects as they don't represent personal performance; manage through tools like JIRA (e.g., analytics tracking, help tips, bug fixes)
◦ Exclude personal tasks as they're not of interest to team members and management; manage through personal task lists (paper, software, boards)
◦ Include approved but not yet started projects; keep undefined ideas in the inbox
◦ Remove completed tasks and add them to monthly summaries | • Limit the number of fields to avoid daily maintenance nightmares
• Using certain Agile boards may save effort; sticky notes and whiteboards work well too |
Evaluate completed work (At project completion/Monthly summary) | •Metric Value Changes: Consider current and historical situations, focus on completion rate
•Release Notes/Version History: Reflect development team output and feature changes
•Monthly Project Summary: Focus on historical data, reflect personal output, list delivery time and actual benefits for each project, sort by cost-effectiveness | • Only include monthly summaries; monthly planning is already in the requirement pool |
Notes:
- Maintain the above planning content in the project Wiki and share with team members, stakeholders, and managers.
- All lists have priorities, but priority definitions may vary.
- Each tool needs to distinguish between current and historical data needs, categorized as: current only, historical only, or both.
- Author:Zhenye Dong
- URL:https://dongzhenye.com/article/product-planning-workflow-tools-guide
- Copyright:All articles in this blog, except for special statements, adopt BY-NC-SA agreement. Please indicate the source!
![How to display [[roam/js]] results inline in Roam Research?](https://images.unsplash.com/photo-1622993361017-180360aea82c?ixlib=rb-4.0.3&q=50&fm=webp&crop=entropy&cs=srgb&t=172ef3ed-bf26-80d0-a657-cf8f0991d45f&width=800&fmt=webp)