Product Manager's Quick Guide to Commonly Used Cue Words

(journalism) lede

Welcome to the Product Manager Cue Words Quick Reference Manual. This handbook is a collection of tips and tricks that product managers may need to use in their daily work. The content covers from basic skills improvement, case study, management framework application, to tool selection, product release, user feedback processing, data analysis and many other aspects, and provides detailed explanations and practical application examples for each item.

A clear and systematic way of thinking and approaching your product management journey is the cornerstone of success. Whether you are a novice or a seasoned professional, this manual is designed to be a source of inspiration for you to quickly find effective strategies to solve problems. With standardized prompts, it is expected to help you achieve efficient communication, precise decision-making and continuous improvement in your work.

When using this manual, we recommend that you flexibly select the appropriate prompts according to the current work scenario. We also recommend that you use the case studies and operational steps provided in the manual to quickly build a practical action plan. We also recommend that you use this manual as a regular toolkit, and practice and optimize it in your daily work, so as to promote the standardization of product management processes, and ultimately enhance the team's synergy.

We sincerely hope that this manual can become your right-hand man on the road of product management, and help you create greater product value and harvest higher user satisfaction in the complex and changing market environment.

1. Understanding and enhancing product manager skills

Explanation of the cue words

Cue word content :

"Compile a comprehensive list of essential soft skills and leadership attributes required of a product manager. In addition, recommend effective strategies for developing and enhancing these attributes."

(English: "Write a comprehensive list of fundamental soft skills and leadership attributes vital for product managers. Additionally, recommend efficient strategies to nurture and enhance these characteristics. Additionally, recommend efficient strategies to nurture and enhance these characteristics.")

Explanation and application examples

The role of Product Manager requires not only solid technical skills and deep business knowledge, but also excellent soft skills and certain leadership skills, such as efficient communication, teamwork, decisive decision-making and continuous innovation.

Applications at work ::

• application scenario Product managers can use this tip to quickly generate an exhaustive list of soft skills, and then develop targeted training programs that take into account the team's and individual's actual situation.
• Application Examples ::
  • List of soft skills : communication skills, time management skills, conflict resolution skills, emotion management skills, cross-functional coordination skills, user empathy, strategic thinking skills, decision-making skills, negotiation skills, active listening skills, problem solving skills.
  • training strategy ::
    • Actively participate in workshops, seminars, and online courses on a variety of communication and leadership topics.
    • Organize regular cross-sectoral collaboration meetings to simulate actual work scenarios and enhance collaboration capabilities.
    • Create a mentorship system to learn from experienced product managers to accelerate growth.
    • Through the case review, in-depth summarization of experience and analysis of the deep reasons for success and failure.
    • Extensively read relevant books and industry articles and pay close attention to industry developments.
    • Participate in industry conferences and networking events and actively expand your professional network.
    • Conduct role-playing exercises to effectively improve communication and presentation skills.
    • Setting personal development goals and regularly assessing progress to ensure that they are heading in the right direction.

Through the above steps to systematically sort out, not only can help team members clearly recognize the key competencies that product managers should have, but also can be based on the development of training strategies to continuously improve the overall professional quality of individuals and teams.

2. Learning from successful products

Explanation of the cue words

Cue word content :

"Prepare a case study analyzing the product strategy and key decisions of a successful [specify product type, e.g., 'fintech'] product."

(English: "Write a case study analyzing the product strategies and key decisions behind a successful [specify type of product, e.g. 'fintech'] product.") ")

Explanation and application examples

Studying successful products with outstanding market performance and analyzing the product strategies and key decisions behind them can help product managers distill valuable experience and provide useful reference for the future development of their own products.

Applications at work ::

• application scenario : When a product manager develops a product strategy plan or shares success stories within the company, he or she can skillfully use this cue to quickly construct a detailed product case study report.
• Application Examples : Select a product that has achieved remarkable success in the FinTech space, such as a well-known payment platform, and analyze it in depth. The analysis can cover its precise market positioning, segmented user base, continuous iterative feature evolution, flexible pricing strategy, effective marketing tactics, tight risk control measures, excellent user experience optimization, and evolving technology architecture. At the same time, it is also necessary to probe deeply into the key decisions made during the development process, and dig into the deeper reasons and long-term impacts behind these decisions. Finally, summarize the key success factors of the product from a global perspective and analyze the potential implications of these factors for your own product.

Doing so allows you to systematically review good product examples and also to inform your own product strategy.

3. Learning to use the product management framework

Explanation of the cue words

Cue word content :

"What are the most important frameworks I should know as a product manager? Please explain how they apply to my product, which is [describe your product and product vision]."

(English: "What are the most important frameworks I should be knowing as a product manager? Explain their application to my product which [describe your product and your product vision].") product and your product vision].")

Explanation and application examples

Skilled and flexible in the use of various product management frameworks, able to effectively assist product managers in different stages of the product life cycle, systematic analysis and scientific decision-making.

Applications at work ::

• application scenario : When a product manager is in the early stages of product planning or needs to reevaluate and revisit an existing product strategy, he or she can use this cue to quickly generate a learning material on product management frameworks and lay a theoretical foundation for subsequent work.
• Application Examples ::
  • Common Frameworks Lean Canvas, Business Model Canvas, AARRR Model (Pirate Indicator), RICE Scoring Model (Prioritization), HEART Indicator (User Experience Measurement), MoSCoW Model (Requirement Prioritization), Kano Model (User Requirement Analysis), SWOT Analysis (Strengths, Weaknesses, Opportunities, Threats Analysis), Porter's Five Forces Analysis (Industry Competition Analysis), and so on. Analysis (Strengths, Weaknesses, Opportunities, Threats), Porter's Five Forces Analysis (Industry Competition Analysis) and so on.
  • Application Analysis Assuming that the product manager is developing an innovative online education platform, the business model canvas can be used to analyze its value proposition, customer segments, channels, customer relationships, revenue sources, core resources, key activities, key partners, and cost structure; at the same time, the AARRR model can be used to systematically plan the conversion paths from user acquisition, activation, retention to final recommendation and revenue generation; the RICE model will be a powerful tool for prioritizing features; the HEART metrics will provide an effective measure to quantify the user experience; the MoMo will be a useful tool for quantifying user experience; and the HEART metrics will provide an effective measure to quantify user experience, At the same time, the AARRR model can be used to systematically plan the complete conversion path of users from acquisition, activation, retention to final recommendation and revenue generation; the RICE model is a powerful tool for prioritizing features; HEART metrics provide an effective measure for quantifying the user experience; the MoSCoW model helps product managers prioritize requirements; the Kano model can deeply analyze the potential types and priorities of users' needs; and SWOT analysis can clearly reveal the key elements of the user experience. SWOT analysis can clearly reveal the competitive advantages and disadvantages of the product; finally, the Porter's Five Forces model will help product managers understand the competitive landscape of the industry in a comprehensive and in-depth manner.

This helps product managers to be more targeted in choosing and applying the management tools that are most suitable for their products, and to improve the efficiency and quality of their decisions.

4. Application of the product management framework

Explanation of the cue words

Cue word content :

"Please use the AARRR framework to describe the customer journey [describe your product]. Include key metrics and opportunities for improvement at each stage and present the analysis in a structured table. (Can be adapted to other PM frameworks.)"

(English: "Please use the AARRR framework to describe what customer journey would look like for [describe your product]. Include important metrics and opportunities for improvement for each stage. Present your analysis in a structured table format. (You can adapt this Present your analysis in a structured table format. (You can adapt this prompt for other PM frameworks.)")

Explanation and application examples

The AARRR model (user growth model), as a powerful analytical tool, assists product managers in comprehensively sorting out and optimizing the complete customer lifecycle journey.

Applications at work ::

• application scenario This prompt allows product managers to quickly generate a clearly structured and detailed customer journey analysis form when developing user growth plans or deep optimization of existing products.
• Application Example Forms ::

With the help of this form, product managers can visually identify potential problems at each stage of the customer journey and develop refined improvement plans to achieve the dual goals of user growth and product optimization.

5. Exploring development tools

Explanation of the cue words

Cue word content :

"Prepare an exhaustive list of basic development tools and software commonly used in product management, detailing their main functions, benefits, and the specific product management tasks to which they apply."

(English: "Craft an extensive list of essential development tools and software frequently used in product management. Detail their primary features, benefits, and the specific product management tasks they're tailored for.") Detail their primary features, benefits, and the specific product management tasks they're tailored for.")

Optional extensions : The list should include ProductBoard, Miro, Notion, Delighted, Clickup, Linear, Jira, Mixpanel, Amplitude, Prodpad and Dovetail.

Explanation and application examples

Product management covers a wide range of tasks, from collecting user requirements to analyzing product data, to managing daily tasks and handling user feedback. In each process, the rational use of a variety of efficiency tools can significantly improve the efficiency of the product manager's work.

Applications at work ::

• application scenario : In the early stages of project team formation for tool selection, or in the team to carry out internal training on the use of tools, product managers can use this prompt to quickly generate a detailed list of tools, the list should contain an overview of the functions of each tool, the core benefits, and targeted use of the recommendations.
• List of sample applications ::
  • ProductBoard : A professional tool focused on product roadmap planning and user requirements management.core functionalityEfficient collection of user feedback, flexible prioritization of requirements, visual product roadmap planning, and refined product release schedule management.Key Benefits: The ability to centralize the management of user requirements and present the product roadmap in an intuitive way.
  • Miro : Powerful remote brainstorming and online collaborative whiteboarding tools.core functionality: Provides an online whiteboard with unlimited canvas, support for real-time online collaboration with multiple people, and a rich built-in template library.Key Benefits: Greatly facilitates teams to collaborate remotely and effectively stimulates team innovation and creativity.
  • Notion : Multi-functional knowledge management and project document collaboration platform.core functionality: Powerful document editing features, flexible database management, and convenient project management.Key Benefits: A collection of features to enable efficient teamwork.
  • Delighted : Professional user feedback collection and Net Promoter Score (NPS) research tools.core functionality: Conveniently launch NPS surveys, effectively collect user feedback, and conduct in-depth data analysis.Key Benefits: Help product managers quickly understand user satisfaction.
  • Clickup : A comprehensive task management and team collaboration tool.core functionality: Flexible task assignment, real-time progress tracking, and efficient time management.Key Benefits: Fully functional and easy to use.
  • Linear : A task tracking tool designed for agile development teams.core functionality: Efficient issue tracking, flexible iteration management, and refined release planning.Key Benefits: The interface is simple and intuitive, tailored for software development teams.
  • Jira : A widely used project management tool in software development.core functionality: Powerful issue tracking, Agile Kanban, Scrum management.Key Benefits: Powerful and highly customizable.
  • Mixpanel / Amplitude : A leading platform for user behavior data analysis and product metrics monitoring.core functionality: In-depth user behavior analysis, refined funnel analysis, user retention analysis.Key Benefits: Help product managers gain insights into user behavior so they can optimize their products.
  • Prodpad : A tool focused on product requirements management and roadmap planning.core functionality: Efficient requirements management, visual roadmap planning, prioritization.Key Benefits: Focuses on the core processes of product requirements management.
  • Dovetail : User research data organization and deep insight mining tools.core functionality: Conveniently record user interviews, efficiently analyze data, and generate insight reports.Key Benefits: Facilitate product managers to systematically organize user research data.
  • Figma / Sketch / Adobe XD: Excellent UI design and prototyping tools.core functionality:: Vector drawing, interactive prototyping, real-time team collaboration. Key Benefits: Support rapid design and iteration, sharing design specifications with development teams and improving collaboration efficiency.
  • Google Analytics / Baidu Tongji:: Popular website traffic analysis tool. core functionality: Website traffic statistics, user behavior analysis, conversion tracking. Key Benefits: Help product managers to fully understand the overall performance of the website and optimize the user acquisition strategy.
  • Hotjar / GrowingIO: Powerful heatmap and screen recording tools for user behavior. core functionality:: Heatmap analysis, screen playback, user feedback collection. Key Benefits: Intuitively understand the trajectory of user behavior on a website and quickly identify potential user experience issues.

Such an exhaustive list of tools can help teams quickly find and select the development and collaboration tools that best suit their needs, thus improving overall work efficiency.

6. Ensuring successful product launches

Explanation of the cue words

Cue word content :

"Develop a comprehensive guide with best practices for planning, executing, and post-release activities to ensure a successful product launch."

(English: "Develop a comprehensive guide with best practices to ensure a successful product launch including: planning, execution, and post-launch activities. activities.")

Explanation and application examples

A product release is a critical milestone in the product lifecycle, and a successful release can effectively minimize potential risks and significantly increase user acceptance and satisfaction with the product.

Applications at work ::

• application scenario : Before the official release of a new product, the product manager can be based on this tip word, systematically put together a detailed product release guide, and organize the relevant departments to release the process of preview, to ensure that nothing is wrong.
• Application Sample Documentation ::
  • Pre-release planning ::
    • In-depth market research: Comprehensive understanding of the real needs of target users, competitors' market dynamics.
    • Thorough competitive analysis: In-depth analysis of competitors' product strengths and weaknesses, market strategy layout.
    • Clarify release objectives: Clearly set the core objectives for this product launch, such as number of user growth, market share share, etc.
    • Thorough user communication program: Develop a detailed pre-launch user communication strategy, e.g., pre-launch campaign planning, email notification sending, etc.
    • Comprehensive risk assessment: Fully identify potential risk factors and develop appropriate response plans in advance.
    • Adequate resource preparation: Ensure that all resources, including human, material and financial resources, are fully available.
    • Detailed release schedule: Develop a detailed product release schedule with clear start and end dates for each task.
  • Implementation phase ::
    • Rigorous internal testing: Conduct comprehensive and detailed internal testing to ensure stable and reliable product quality.
    • User Beta Testing: Invite some users to participate in Beta testing to collect real user feedback and make improvements accordingly.
    • Launch day event coordination: Careful coordination of launch day activities such as press release distribution, social media warm-ups, online/offline launches, etc.
    • Multi-channel synchronization: Ensure that the product is synchronized across scheduled channels (e.g., app stores, official websites).
    • Technical Support Preparation: Ensure technical support team in place Respond to and effectively resolve user feedback in a timely manner.
  • Post-release activities ::
    • Real-time monitoring of system stability: Closely monitor the operational status of the product line to identify and resolve potential problems in a timely manner.
    • Continuous user feedback collection: Continuously collect user feedback through multiple channels to gain a comprehensive understanding of user evaluations and perceptions of new products.
    • In-depth data analysis: In-depth analysis of user behavior data to comprehensively evaluate the actual effect of the product after launch.
    • Development of a follow-up update plan: Based on the results of user feedback and data analysis, develop plans for subsequent version updates of the product.
    • Organizational review and stocktaking meeting: Organize product launch review meetings to systematically capture lessons learned and inform future product launch activities.
    • Continuous Marketing: Ongoing marketing campaigns to expand the product's market reach.

Such a detailed release guide not only ensures that the product release process is standardized and regulated, but also provides a clear and executable course of action for the various teams involved in the release.

7. Optimize product to-do list management

Explanation of the cue words

Cue word content :

"Develop a product to-do list organizing strategy to keep us on track with development. Here are our constraints [specify team size, technology and tools, user and stakeholder feedback collection methods, market conditions, amount of technical debt, regulatory issues, and other relevant information]."

(English: "Generate a backlog grooming strategy to keep our development on track. Here are our constraints [specify team size, technology and tooling, how to gather feedback from users and stakeholders, market situation, amount of tech debt, regulatory issues, and anything else that would be helpful to us]. Here are our constraints [specify team size, technology and tooling, how to gather feedback from users and stakeholders, market situation, amount of tech debt, regulatory issues, and anything else that would be helpful to know for backlog grooming considerations]. know for backlog grooming considerations].").

Explanation and application examples

The effective organization and fine management of product to-do list (Backlog) is directly related to the overall development progress of the product and the quality of the final product. Therefore, product managers must make scientific and reasonable planning based on full consideration of various constraints.

Applications at work ::

• application scenario : During a routine team to-do review meeting, the product manager can use this cue to quickly generate a strategy document with clear prioritization and detailed evaluation criteria for each task.
• Application Example Strategies ::
  • Classification of tasks : Fine-grained categorization based on the source of the task, such as user feedback, market demand, technical debt, regulatory requirements, and innovative experiments.
  • Evaluation criteria ::
    • significance: Assess the potential value of the task to the user and the business.
    • urgency: Determine whether the task needs to be started immediately.
    • development difficulty: Assess the technical complexity of the task and the resources to be invested.
    • exposures: Assess the likelihood of mission failure and its potential impact.
    • Fit with corporate strategy: Assess the extent to which the mission fits with the company's long-term development goals.
  • Flow of the meeting ::
    • Regular review meetings:: Ensure the frequency of reviews, for example, on a weekly basis.
    • Involvement of key stakeholders: Invite development, design, testing, marketing, operations and other relevant stakeholders to participate in the review.
    • Task Discussion and Grading: Each to-do list is fully discussed, collectively scored, and ranked based on predetermined evaluation criteria.
    • Determine the iterative task: Clarify the task items that need to be accomplished in the current iteration cycle.
    • Updated to-do list: Update to-do lists in a timely manner and synchronize them to all team members to ensure information is synchronized.
  • Tool Support Flexible use of project management tools such as Jira, Trello, Asana, etc. to assist in to-do list management.
  • continual improvement : Regularly review the effectiveness of the implementation of the to-do list organizing strategy, and dynamically adjust and optimize it according to the actual situation.
  • Technical debt management:: Product managers need to dedicate time to focus on technical debt to prevent the accumulation of technical debt from adversely affecting development efficiency.

This strategy ensures that the team is able to move forward with product development in an organized manner and keep the project on track in the face of complex and varied constraints.

8. Prioritization

Explanation of the cue words

Cue word content :

"Using [specify a prioritization framework such as the RICE scoring model, ICE scoring model, Value and Complexity Quadrant, Kano model, Weighted Scoring Prioritization, MoSCoW methodology, Opportunity Scoring] and based on [specify a company goal or product vision], helps me prioritize the following:[list all features or viable initiatives that need to be prioritized ]."

(English: "Using [specify a prioritization framework, e.g. RICE scoring model, ICE scoring model, Value vs. Complexity Quadrant, Kano Model, Weighted Scoring Prioritization, the MoSCoW method, Opportunity Scoring] and given [specify your company goals or product vision], help me prioritize the following.

.")

Explanation and application examples

A scientific and rational prioritization model can help product managers more objectively assess how well each feature or improvement initiative fits with the company's strategic goals, so that they can make more informed decisions.

Applications at work ::

• application scenario : When a product has accumulated too many functional requirements and it is difficult to make a choice, the product manager can organize a team meeting to discuss the issue of feature prioritization. At this time, with the help of the prompt, you can quickly generate a report containing detailed sorting results.
• Application Examples (using the RICE model as an example):
  • R (Reach - coverage) : Estimate the number of users that each feature will reach in a given period of time. This can be expressed quantitatively using specific numbers or percentages. For example, how many users will use the feature in a quarter?
  • I (Impact) : Assess the extent to which each feature potentially impacts the user experience or business growth. This can be measured using a rating scale (e.g., 1-3, with 3 representing the highest impact) or more specific metrics. For example, how much will this feature contribute to improved user satisfaction or increased revenue?
  • C (Confidence) : Assess the team's level of confidence in the successful implementation of the function. This can be expressed as a percentage, e.g. 50%, 80% or 100%.
  • E (Effort - workload) : Estimate the resources, including labor and time costs, that will need to be invested in the development of the feature. This can be expressed in units such as man-days, man-weeks, or man-months. For example, how many person-months will it take to complete the development?
  • sorting process The RICE Score is calculated for each function, and then the functions are prioritized in descending order of their RICE Score. The final prioritization should be fine-tuned with the company's long-term strategic goals, and the RICE Score calculation formula is:

  RICE Score = (Reach * Impact * Confidence) / Effort

  • Other modeling examples:
    • ICE Scoring Model. Focuses on Impact, Confidence, Ease. The ICE Score is calculated using the formula:ICE Score = Impact * Confidence * Ease
    • Value and Complexity Quadrant. The function or initiative to be evaluated is analyzed by placing it in a two-dimensional matrix. The horizontal axis of the matrix represents complexity and the vertical axis represents value. Product managers should prioritize those features or initiatives that are in the high-value, low-complexity quadrant.
    • Kano model. User needs are subdivided into different types such as basic needs, expectation needs, excitement needs, undifferentiated needs and reverse needs. Product managers should prioritize the basic and desired needs of users to enhance user satisfaction.
    • MoSCoW methodology. Prioritize functional requirements by dividing them into Must have, Should have, Could have and Won't have.

Prioritization methods, such as the RICE model, help teams focus on work that has a higher input-to-output ratio and more strategic value, improving resource efficiency.

9. Preparation of release notes

Explanation of the cue words

Cue word content :

"What are the basic elements that should be included in a release note [describing your product]? Please provide best practices and examples to effectively communicate new changes and improvements to users."

(English: "What are the essential elements of a well-written release note for [describe your product]? Please provide both best practices and examples for crafting notes that effectively communicate new changes and improvements to users.")

Explanation and application examples

Clear and concise product release notes effectively communicate to users the content of new version updates, details of feature improvements, and potential caveats, enabling users to quickly grasp the latest changes to the product.

Applications at work ::

• application scenario : When each product version update is released, the product manager can refer to this reminder to write a standardized release note document to ensure the accuracy and completeness of information delivery.
• Example elements ::
  • version information : Clearly labeled with version number and detailed release date for easy identification by users.
  • New Features : Introduce in detail the new features added in this update and elaborate on their core benefits, preferably complemented by intuitive screenshots or demo videos to help users quickly understand them.
  • Description of improvements : Clearly state specific improvement measures in performance optimization, user experience enhancement, interface adjustment, etc.
  • Problem fixing : List the bugs fixed in this release and their impact areas, and thank users for their positive feedback to enhance user interaction.
  • Known issues: If there are problems that have not yet been fixed but are known to exist, they should be clearly communicated to users here to increase transparency.
  • Follow-up Tips : Inform users how to get more help or channels to provide feedback, as well as initial plans for future version updates to enhance user stickiness.
  • Compatibility Notes:: If necessary, compatibility requirements for operating system versions, browser versions, etc., should be clearly stated to avoid compatibility problems when users use them.
  • choice of words:: When writing release notes, try to use simple, clear, easy-to-understand, everyday language and avoid excessive use of jargon to ensure the effectiveness of the information conveyed.
• Sample text ::
  

  "[Product Name] Version 2.1.0 Release Notes - March 2025

  Dear User.

  We are very excited to announce that [product name] version 2.1.0 is now live! This update brings you many exciting new features and experience optimizations:

  new feature

  • Online Collaboration Functions: Now you can easily invite your team members to collaborate on documents in real time and work together to get things done efficiently.
  • dark color mode: The long-awaited dark color mode rocks! Effectively protect your eyesight and make you more comfortable when using at night.

  Description of improvements

  • performance optimization: We have deeply optimized the performance of the system, the page loading speed is greatly improved 50% and the operation experience is more smooth and silky.
  • Interface adjustments: Based on user feedback, we have fine-tuned the layout of the navigation bar, and the search function is now more convenient and efficient.

  Problem fixing

  • The technical team has efficiently fixed the login anomaly issue reported by some users. We would like to thank @username1, @username2 and other users for their positive feedback!

  Known issues

  • The adaptation of the dark color mode for mobile is still in full swing, and is expected to be with you in the next version, so stay tuned.

  Follow-up Tips

  If you encounter any questions or problems in the process of use, please feel free to visit our help center or directly contact the customer service team, we will be happy to serve you. Thank you again for your support of [Product Name], we will continue to work hard to provide you with better products and services!
  "

By adopting this standardized release note format, it not only helps users to quickly and accurately grasp the core content of the version update, but also helps to enhance users' trust and brand loyalty to the product.

10. Publish product update announcements

Explanation of the cue words

Cue word content :

"Please draft a product update announcement for our users. This release includes [describe the release]."

(English: "Please draft a product update announcement for our users. The release includes [describe release].")

Explanation and application examples

Product update announcements are usually used for public product version releases, so the tone should be friendly and professional, not only to clearly convey the highlights of the update, but also to make users aware of the future direction of product improvement, so as to build good user relations.

Applications at work ::

• application scenario When a new version of a product is about to be released, the product manager can quickly generate a draft of the product update announcement with the help of this reminder, which will then be reviewed by the marketing, customer service and other related departments to ensure the accuracy of the announcement and the consistency of the caliber of the announcement to the outside world.
• Sample Application Bulletin ::
  

  "Dear [product name] users.

  Greetings! We are excited to announce that the latest version of [Product Name] is now available! In this update, we have listened to the valuable feedback from our users, carefully polished and re-launched the long-awaited [New Feature 1] and [New Feature 2], and deeply optimized [Optimization 1] and [Optimization 2], aiming to bring you a smoother and more efficient using experience!

  • [New feature 1]: [Brief description of the feature], [What core value and tangible benefits the new feature will bring to users].
  • [New Feature 2]: [Brief description of the feature], [How the new feature will enhance user experience or address user pain points].
  • [Optimization point 1]: [Specific optimizations], [What positive impacts will result from the optimization].
  • [Optimization point 2]: [Specific optimization content], [How the optimization will improve user efficiency or satisfaction].

  We sincerely thank you for your continuous support and trust! We always uphold the attitude of excellence, and continuously improve [Product Name], and strive to provide you with more excellent products and services. We invite you to try out the latest version of [product name] now and feel free to give us your feedback!

  [Product Name] Team Toami"

  • Publishing Channels: Product managers can choose appropriate channels to announce updates, such as through email, in-app push messages, social media platforms, and official blog posts, to ensure that the information reaches the widest possible audience.

Such well-written announcements can not only clearly convey product update information, but also effectively enhance the user's sense of participation and sense of belonging, and establish a good communication bridge with the users.

11. Improving user interface usability

Explanation of the cue words

Cue word content :

"Identify 10 areas of usability improvement in our user interface. The product is [describe the product]. [upload a screenshot of the site or app, do not use the Kraftful plugin]"

(English: "Identify 10 areas of usability improvement in our user interface. The product is [describe product]. [Upload screenshot of the website or app, do not use the Kraftful plugin]")

Explanation and application examples

By systematically analyzing usability issues in the user interface (UI), product teams can target design optimizations to significantly improve the product's user experience.

Applications at work ::

• application scenario : After a product design review meeting, or after a user experience test, the product manager can utilize this cue to quickly generate a detailed user interface improvement list. This list can be accompanied by screenshots of the actual interface, and the areas that need to be improved are clearly labeled, making it easy for designers and developers to understand and implement.
• Example areas of improvement ::
  • Navigation hierarchy is too deep: The hierarchical structure of the navigation bar is overly complex, making it difficult for users to find targeted content.
  • Low differentiation between buttons and links: The buttons and links on the page are not visually distinguishable and users are prone to misuse them.
  • Excessive information density: The information on the page is too densely arranged and lacks the necessary white space, which makes the page as a whole look disorganized and makes it difficult for the user to quickly capture the key information.
  • Unfriendly form design: The design of the form is not humanized enough, such as the length of the input box is too short, the lack of clear input prompts, and the lack of clear checking rules, which leads to poor user experience when filling out the form.
  • Loading animation is missing or doesn't make sense: The page loading process lacks the necessary loading animation, or the loading animation design is not reasonable enough, resulting in the user is easy to feel anxious and uneasy while waiting.
  • Responsive design to be optimized: The responsive design of the product needs to be improved, and the display effect on different sizes of device screens is not satisfactory, which affects the user's experience on different devices.
  • Lack of color contrast: Unreasonable page color contrast settings may make it difficult for some users, especially visually impaired users, to clearly identify the content of the page.
  • inconsistent font size: Attributes such as font size and font weight of the page are not standardized, which affects the overall aesthetics and readability of the page.
  • Pop-up alerts are not obvious or too frequent: The design of pop-up tips is not eye-catching enough, which is easy for users to ignore; or the pop-up tips are too frequent, which interferes with the normal operation of users.
  • Help documentation portal is hard to find: The help documentation portal is not clearly located, making it difficult for users to quickly find the help documentation and obtain effective support when they encounter problems.
  • Lack of clear operational guidance: For new users, the product interface lacks clear operation guidance, which makes it difficult for users to get started and do not know how to operate.
  • Inadequate search function: The search function built into the product is not powerful enough to help users find what they need accurately and quickly.
  • Unfriendly error message: When a user makes an error in an operation, the error message given by the system is not friendly enough, and it is difficult for the user to understand the cause of the error and know how to correct it.
  • Lack of shortcuts: The lack of convenient shortcuts for users to complete certain common operations leads to inefficient operations.
  • Suggestions for improvement: For each of these usability issues, the product manager needs to further suggest specific and feasible improvements, for example:
    • Optimize navigation bar structure: Optimize the structure of the navigation bar, reduce the navigation hierarchy, use breadcrumb navigation and other ways to help users more clearly understand the current location and page hierarchy.
    • Distinguish between buttons and links: In terms of visual design, use different colors, icons, underlining, etc. to effectively differentiate between buttons and links and reduce the possibility of user misuse.
    • Optimize page layout:: Redesign the page layout, reasonably control the density of information on the page, increase the white space on the page, and highlight the key information on the page.
    • Optimize form design:: Optimize form design, such as increasing the length of input boxes, setting clear input prompts, and clarifying checking rules, to improve the efficiency and experience of users in filling out forms.
    • Use appropriate loading animations: Use appropriate loading animations during the page loading process to effectively alleviate users' anxiety while waiting.

Such an exhaustive list of improvements not only serves as an important basis for designers to optimize the user interface, but also helps the product manager to track the actual progress of the improvements in the subsequent work to ensure the optimization effect.

12. Enhancing product accessibility

Explanation of the cue words

Cue word content :

"Propose a set of features to enhance the accessibility of our products. The product is [describe product]. [Upload screenshots of your website or app, do not use Kraftful plugin]"

(English: "Propose a feature set to improve the accessibility of our product. The product is [describe product]. [Upload screenshot of the website or app, do not use the Kraftful plugin]")

Explanation and application examples

Enhancing product accessibility means that products are better able to meet the needs of a wider range of user groups, including those with special needs and disabilities. This is not only a reflection of corporate social responsibility, but also an important aspect of enhancing the competitiveness of products in the marketplace.

Applications at work ::

• application scenario : In a product review meeting, a product manager can use this prompt to quickly generate a proposal for improving product accessibility. This proposal can be combined with actual interface screenshots to clearly point out the current accessibility issues in the interface and make targeted suggestions for improvement.
• Sample Recommendations ::
  • Enhanced keyboard navigation support: Ensure that users have smooth access to the full range of product functions using only the keyboard, without having to rely on assistive devices such as a mouse.
  • Add alt text to images: Add descriptive alternative text to all image elements on a page to make it easier for users with screen readers to understand the image content.
  • Provides high contrast mode: Provide users with switchable high-contrast display modes to meet the reading needs of visually impaired users.
  • Optimize screen reader compatibility:: Ensure that the product is designed and developed with full consideration of screen reader compatibility to ensure that the product can work well with mainstream screen reader software to achieve barrier-free access to information.
  • Optimize form labels and error alerts:: Help visually impaired users fill out forms without barriers by semanticizing the labels on the forms and ensuring that error messages are correctly recognized and read aloud by screen readers.
  • Provide adjustable font size function: Provide users with the ability to freely adjust the font size, so that users can adjust the font size to the most comfortable according to their own visual needs.
  • Adding subtitles and audio descriptions to videos:: Add accurate subtitles and detailed audio descriptions to video content in products to facilitate barrier-free access to video information for hearing-impaired users.
  • Avoid flashing or rapidly changing content:: Excessively frequent flashing or rapidly changing content elements should be avoided in product design to prevent the induction of health problems such as photosensitive epilepsy.
  • Provide clear page structure and headings:: When designing the page structure, ensure that the page structure is clear and logical, and use semantic heading tags to make it easy for users and screen readers to quickly understand the content and hierarchy of the page.
  • Using the ARIA Attribute: Enhance the semanticization of the page by using ARIA (Accessible Rich Internet Applications) attributes in the HTML code to further improve the understanding and accessibility of the page content for screen reader users.
  • Perform WCAG compatibility testing: Upon completion of product development, products should be thoroughly tested for accessibility in strict accordance with the WCAG (Web Content Accessibility Guidelines) international standard to ensure that they comply with accessibility design specifications.

This detailed proposal can effectively help the development team to systematically improve the product's accessibility features, enhance the product's user experience as a whole, and benefit a wider range of user groups.

13. Data analysis

Explanation of the cue words

Cue word content :

"You can use the following SQL table: events, containing columns: user_id, timestamp, name. your task is to return the SQL query. How many users have triggered the 'Signup Success' event in the past week?"

(English: "You have the following SQL table available to you: events. It has the columns: - user_id - timestamp - name. Your job is to respond with SQL queries. How many users triggered the 'Signup Success' event in the past week?")

Explanation and application examples

Data analysis plays a crucial role in the process of continuous product optimization and iteration. Reasonable data query and analysis can help product managers quickly and accurately understand user behavior, thus providing strong data support for product decision-making.

Applications at work ::

• application scenario When product managers need to evaluate the effectiveness of the user registration process, they can use this prompt to quickly generate standard SQL query statements to efficiently obtain the required data.
• Sample SQL Query ::

SELECT COUNT(DISTINCT user_id) AS signup_users
FROM events
WHERE name = 'Signup Success'
AND timestamp >= DATE_SUB(CURDATE(), INTERVAL 7 DAY);

The above SQL query statement aims to count the number of de-duplicated users who successfully triggered the "Signup Success" event in the past 7 days, which provides reliable data support for the subsequent in-depth analysis of user registration conversion rate.

More complex example.

• Calculate the number of daily active users (DAU) for the past month.

SELECT DATE(timestamp) AS event_date, COUNT(DISTINCT user_id) AS dau
FROM events
WHERE timestamp >= DATE_SUB(CURDATE(), INTERVAL 30 DAY)
GROUP BY event_date
ORDER BY event_date;

• Calculate the average time it takes for a user to complete their first purchase from registration to.

-- 假设有一个名为 "purchases" 的表，包含 user_id 和 purchase_timestamp 列
SELECT AVG(TIMESTAMPDIFF(SECOND, signup.timestamp, purchase.purchase_timestamp)) AS avg_time_to_purchase
FROM (
SELECT user_id, MIN(timestamp) AS timestamp
FROM events
WHERE name = 'Signup Success'
GROUP BY user_id
) AS signup
INNER JOIN purchases AS purchase ON signup.user_id = purchase.user_id;

14. Responding to social media user feedback

Explanation of the cue words

Cue word content :

"We received the following user feedback on social media:[paste message]. Please draft a response to the user feedback. [Include rough notes on what you would like to communicate to the user, e.g. you plan to develop the feature they requested, already have a way to fulfill their needs, etc.]"

(English: "Here's some user feedback we got on social media: [paste message]. Draft a response to user feedback. [Include rough notes on anything you want to communicate to users, e.g. you plan to build what they are asking for, there Include rough notes on anything you want to communicate to users, e.g. you plan to build what they are asking for, there 's already a way to do what they want to do, etc.]").

Explanation and application examples

Responding to user feedback on social media platforms in a timely and professional manner is critical to maintaining and enhancing brand image, and effectively communicates how seriously an organization takes the needs of its users.

Applications at work ::

• application scenario Product managers can use this prompt to quickly generate a preliminary draft response to user comments or feedback received on social media platforms, which can then be refined and reviewed by the marketing and customer service departments before being released to the public.
• Example response ::
  • Scenario 1: A new feature request is made by a user
    

    "Hello! Thank you very much for your interest and support for [PRODUCT NAME] and your valuable suggestions! The [Function Name] feature you proposed is a great idea, and we have taken note of your feedback and will carefully evaluate its feasibility in the subsequent product planning. The [product name] product team has been committed to continuous improvement of product features, constantly optimize the user experience, and strive to bring you more excellent products and services, please look forward to the future version of the update!"

  • Scenario 2: User feedback on problems encountered during product use
    

    "Hello, very sorry for the inconvenience! We've already noticed your [Problem Description] issue, and our technical team is actively investigating the problem and trying to solve it as soon as possible. In order to pinpoint the problem and solve it efficiently, could you please provide us with more detailed information, such as the model of the device you are using, the version of the operating system, and screenshots of the problem? You can contact us at [Contact] and we will be happy to help you. Thank you for your understanding and support!"

  • Scenario 3: Users praise and recognize the product
    

    "Greetings! Thank you very much for your recognition and love for [Product Name]! Your encouragement is a strong motivation for us to keep moving forward. We will continue to work hard to optimize product features, improve user experience, and strive to bring you more surprises! If you have any suggestions or comments in the process of using, please feel free to give us feedback."

  • Scenario 4: Users inquire about the use of existing features
    

    "Hello, thank you for your inquiry! The [Feature Name] feature you mentioned is actually supported by [Product Name]! You can operate it by the following steps: [Detailed step-by-step instructions]. If you encounter any problems during operation, or have other questions, please feel free to contact us, we will be happy to answer your questions!"

  • Common Response Points:
    • expression of gratitude:: Start by sincerely thanking users for their feedback or questions and bring them closer.
    • Recognition of the problem:: If the user feedback is about a product problem, acknowledge it honestly and apologize for it, demonstrating a responsible attitude.
    • Providing solutions:: If there is a clear solution to the problem, the user should be informed in a timely manner and detailed operating instructions or alternatives should be provided.
    • Commitment to follow up:: If the issue is more complex and requires further investigation or processing, there should be a commitment to actively follow up and provide timely feedback to users on the progress of processing.
    • Maintain a positive attitude: Maintain a positive, friendly attitude at all times in responding to users, conveying positive energy and building good user relations.

As you can see from the above examples, a high-quality user response not only effectively expresses the importance of user feedback, but also allows users to feel that the company is actively listening to their voices and trying to solve their problems, thus increasing user satisfaction and loyalty.

15. Drafting of bug reports based on user feedback

Explanation of the cue words

Cue word content :

"Here's some user feedback: [paste message]. Draft a bug report based on user feedback."

(English: "Here's some user feedback: [paste message]. Draft a bug report based on user feedback.")

Explanation and application examples

Organizing fragmented problem information from user feedback into structured bug reports can help development teams quickly locate problems and efficiently perform problem fixing and version iteration.

Applications at work ::

• application scenario When the product manager receives feedback from the user, pointing out that the product has functional anomalies or defects, he or she can quickly generate a preliminary bug report document with the help of this prompt, laying the foundation for the follow-up and resolution of the problem.
• Sample Error Reporting Structure ::
  • Title of report: The title should be concise and summarize the core of the reported problem in a single sentence. For example: "User Feedback: 'System Error' message when submitting an order".
  • Description of the problem : Describe in detail the specific problems encountered by the user, including the phenomenon of the problem, the frequency of the problem, and the scope of the problem.
  • Steps to Reproduce : Detail the action steps that will reproduce the issue, which should be as detailed as possible to ensure that the developer can accurately reproduce the issue based on the reported steps.
  • Expected results : Describe the expected results that the system should present under normal circumstances after completing the above operational steps.
  • actual result : Detailed description of the current problem when the system actually presents the abnormal results, including error messages, screenshots of the exception page, and so on.
  • Environmental information: Provide as much detailed information as possible about the environment at the time of the problem, for example:
    • operating system: e.g. Windows 10, iOS 15, Android 12, etc.
    • browser (software): e.g. Chrome 98, Safari 15, Firefox 97, etc.
    • Equipment Model: e.g. iPhone 13, Samsung Galaxy S21, PC, etc.
    • application version: e.g. version v2.1.0.
    • network environment: e.g. Wi-Fi, 4G, 5G networks, etc.
  • Scope of impact : Preliminary assessment of the range of user groups or functional modules that may be affected by the issue.
  • prioritization: (Optional) Initial assessment of the priority of the problem based on the scope and severity of its impact, e.g., high, medium, low.
  • note : In the Notes section, you can include a screenshot of the original user feedback, a link to the relevant logs, or other additional information that will help the developer locate and resolve the issue.
  • author: Record the name or ID of the person who submitted the bug report to facilitate problem follow-up and accountability.
  • Date of submission:: Record the submission date of bug reports to facilitate problem tracking and statistical analysis.
• typical example::

  User feedback: "I was buying something in the app yesterday, and after adding the cart and tapping 'go to checkout', a box popped up saying 'system error, please retry later', and I tried several times and it didn't work, so I didn't end up buying it. I'm using an Android phone."

  false::

  • Title of report: User feedback: "System error" message at checkout
  • Description of the problem Some Android users have reported that when they try to checkout after adding a product to the shopping cart within the App, a "System Error, Please Retry Later" prompt appears on the page, preventing them from completing the normal purchase process.
  • Steps to Reproduce ::
    • Open the App.
    • Browse through the products and select your favorite items.
    • Click the "Add to Cart" button.
    • Click on the shopping cart icon in the upper right corner of the page to go to the shopping cart page.
    • On the shopping cart page, click the "Go to checkout" button.
    • Observe whether the "System error, please try again later" prompt appears.
  • Expected results : The system should jump to the checkout page properly and display the order information and available payment options correctly.
  • actual result : After clicking the "Go to Settlement" button, the system pops up a "System Error, Please Retry Later" prompt box, and the user is unable to proceed with the subsequent settlement process.
  • Environmental information::
    • operating system: Android (user did not provide specific version information, need further ** уточнить ( уточнить - уточнить)**)
    • browser (software): N/A (problem occurred within the App)
    • Equipment Model: Android cell phone (user did not provide specific model number, need further ** уточнить ( уточнить - уточнить)**)
    • application version: (need to confirm the specific App version number to the user)
    • network environment: (need to confirm with the user the network environment of the user at that time, e.g. Wi-Fi or 4G)
  • Scope of impact : Initially, the issue is likely to primarily affect users who use Android devices and make purchases through the App.
  • prioritization: Preliminary assessment of the problem priority: high, the problem directly affects the user normal shopping settlement, need to be fixed as soon as possible.
  • note : Attempts have been made to contact the user for further ** уточнить ( уточнить - уточнить)** more detailed information about the device model, application version, network environment, etc., and to ask the user to provide a screenshot of the page at the time of the problem in order to pinpoint the issue more precisely.
  • author: [your name/ID]
  • Date of submission:: May 16, 2024

After such structured and organized bug reports, it can help the technical team to quickly locate the problem, so as to more efficiently carry out the problem fixing, and make targeted improvements in the subsequent version iteration to improve the product quality.

16. Product strategy

16.1 Guide to Creating a Product Roadmap

Explanation of the cue words

Cue word content:

"Create a comprehensive, step-by-step guide for [specify product] that explains the process of producing a roadmap to a successful product. This guide should effectively incorporate best practices, utilize the best tools, and suggest effective communication strategies."

(English: "Create a comprehensive, step-by-step guide that explains the process of crafting a successful product roadmap for [specify product]. This guide should effectively incorporate best practices, utilize optimum tools, and suggest effective communication strategies.")

Explanation and application examples

The product roadmap is a core component of product strategic planning, which visualizes a clear presentation of the product's future direction, feature priorities, and a detailed timeline.

Applications at work:

• application scenario: When a product manager conducts annual or quarterly product planning, he or she can quickly generate a product roadmap creation guide with the help of this cue word, providing methodological guidance for subsequent roadmap development work.
• Sample Guide:
  • Clarify product vision and goals:
    • Define the product vision: In the initial phase of developing a product roadmap, product managers need to first clarify the long-term vision and core mission of the product to set the tone for the roadmap.
  • Setting measurable short-term goals (e.g. OKRs):: Setting quantifiable and achievable short-term goals guided by a long-term vision, for example, using the OKRs (Objectives and Key Results) goal management methodology to ensure that each stage of the roadmap has clear and measurable objectives.
  • Collect user feedback and market research information:
    • User feedback collection: Extensively collect real voices from users through various channels such as user interviews, user questionnaires, user feedback data analysis, etc., to gain an in-depth understanding of user needs.
    • market research: Conduct comprehensive market research, analyze competitors' product strategies and market dynamics in depth, and grasp market development trends.
  • Refining Product Themes and Epics:
    • Summarize product themes: Summarize and distill user requirements and market insights collected into highly generalized product themes. Themes should be closely centered on the product vision and goals.
    • Breakdown to Epic (Epics): Refine and break down macro product themes into more specific, actionable product epics. Each Epics should represent a relatively independent functional module or user value.
  • prioritize:
    • Applying the prioritization framework: Select a suitable prioritization framework, e.g., RICE scoring model, MoSCoW model, etc., to prioritize product epics (Epics).
    • synthesize and consider:: When prioritizing, it is necessary to take into account a variety of factors, such as user value, business value, risk of technological realization, required workload, etc., to ensure that the prioritization is scientific and reasonable.
  • Estimated time and resources:
    • Teamwork Estimates: Work closely with the development team to estimate the development time and resource investment required for each Epic product to ensure accuracy.
    • Assessing Team Capacity:: During the prognosis process, the actual capacity and development speed of the team are fully considered to ensure that the planning of the roadmap matches the actual capacity of the team.
  • Creating Product Roadmaps:
    • Select Roadmap Tool: Select professional product roadmap tools, such as ProductBoard, Roadmunk, Aha! etc., to improve roadmap production efficiency and visualization.
    • Road map elements: Ensure the completeness of roadmap information by clearly presenting core elements such as product themes, product epics, timelines, and key milestones in the roadmap.
    • Selecting the right view: Select the appropriate roadmap view according to the actual needs, such as Gantt chart, Kanban view, etc., to display the roadmap information more intuitively.
  • Effective Communication and Collaboration:
    • Stakeholder communication:: Share the product roadmap with all key stakeholders (e.g., company management, development team, marketing team, etc.) in a timely manner to ensure synchronization of information.
    • Periodic review and update:: Establish a mechanism to regularly review and update the product roadmap, make dynamic adjustments based on market changes and user feedback, and keep the roadmap ** актуальность (актуальность - актуальность)**.
    • Maintain transparent communication:: Maintain open and transparent communication during the development and implementation of the road map to ensure that all team members and stakeholders are fully updated on the progress of the road map.
  • best practice:
    • Maintaining road map flexibility:: Recognize the dynamic nature of the market environment and user needs, and maintain flexibility and resilience in the product roadmap in order to adapt quickly to changes.
    • Focus on user value and business goals:: Always make user value and business goals the core drivers of product roadmaps, ensuring that roadmap development and execution are closely centered on users and the business.
    • Periodic review and adjustment:: Establish a mechanism to review and adjust the product roadmap on a regular basis, optimize it based on actual implementation and market feedback, and ensure the effectiveness of the roadmap.
  • Effective Communication Strategies:
    • tiered communication:: Develop differentiated communication strategies for different audience segments and provide different versions of the road map. For example, top management is more focused on strategic direction and macro progress, while development teams are more focused on specific tasks and timelines.
    • Periodic review meetings:: Organize regular product roadmap review meetings, inviting all key stakeholders to jointly review the roadmap progress and listen to the opinions and suggestions of all parties.
    • Visualization tool aids: Make full use of visualization tools, such as charts and graphs, to present the product roadmap in a more intuitive and easy-to-understand way, and improve communication efficiency.

16.2 Product Discovery and Competitive Analysis

Explanation of the cue words

Cue word content:

"Perform an [specify framework: SWOT, PESTLE, Porter's Five Forces] analysis of [specify competitor name or describe their product experience if it is a lesser known brand]."

(English: "Perform [specify framework: SWOT, PESTLE, Porter's 5 force] analysis on [specify competitor's name or describe their product experience if it's a less well-known brand].")

Explanation and application examples

In-depth competitive analysis is an important prerequisite for developing an effective product strategy. Through competitive analysis, product managers are able to fully understand the competitive landscape of the market, gain insight into the strengths and weaknesses of major competitors, and on this basis, clarify the market positioning of their products and differentiated competitive strategies.

Applications at work:

• application scenario: Before a company plans to enter a new market segment or prepare for the launch of a brand new product line, product managers can use this prompt to select the appropriate analytical framework to conduct an in-depth analysis of competitors and provide strong support for product strategy decisions.
• Example (SWOT Analysis):
  • competition:: [name of competitor]
  • Strengths:
    • Strong brand awareness and market influence.
    • Wide user base with a large user base.
    • Mature technology platform with strong technical strength.
  • Weaknesses:
    • The user interface design is rather outdated and the user experience needs to be improved.
    • Customer service response is slow and user feedback is not handled efficiently.
    • Insufficient innovation in product features and lack of highlight features.
  • Opportunities:
    • Emerging markets are expanding and there is huge market potential.
    • The rapid development and application of new technologies brings opportunities for product innovation.
    • User demand presents diversification and personalization trends, providing space for product differentiation and competition.
  • Threats:
    • New competitors continue to enter the market and the market is becoming increasingly competitive.
    • Rapidly changing user preferences place higher demands on products.
    • Increasingly stringent regulatory policies have challenged corporate compliance.
• Example (PESTLE Analysis):
  • competition:: [name of competitor]
  • Political:: Analyze the impact of political factors such as government regulatory policies, industry trade policies, and tax policies on competitors and the market.
  • Economic:: Analyze the macroeconomic environment, e.g., economic factors such as economic growth rates, interest rate levels, inflation rates, exchange rate fluctuations, etc., on the market and competitors.
  • Social:: Analyze the impact of social factors, such as demographic trends, sociocultural values, and shifts in users' lifestyles, on user demand and market preferences.
  • Technological: Analyze the impact of technological factors such as new technology development trends, automation technology applications, and industry R&D investment efforts on product innovation and the competitive landscape of the market.
  • Environmental: Analyze the impact of environmental factors such as increasingly stringent environmental regulations and the rise of the concept of sustainable development on business operations and product design.
  • Legal: Analyze the impact of legal factors, such as intellectual property protection policies, consumer rights protection laws and regulations, and changes in industry regulatory policies, on the business behavior of enterprises and the order of market competition.
• Example (Porter's Five Forces Analysis).
  • Degree of competition from existing competitors in the industry. Analyze the number of competitors, degree of product differentiation, market growth rate, and exit barriers within the industry to assess the degree of competition.
  • Ability of potential competitors to enter. Analyze factors such as high or low barriers to entry, economies of scale, user brand loyalty, and channel control in the industry to assess the ability and likelihood of potential competitors to enter the market.
  • Substitutability of alternatives. Analyze the existence of alternatives in the market with similar performance and lower prices, as well as the cost to the user of switching to the use of alternatives, and assess the potential threat of alternatives to the existing product.
  • Bargaining power of suppliers. Analyze the number of suppliers, industry concentration, degree of product differentiation, cost of switching suppliers and other factors to assess the bargaining power of suppliers in the industry chain.
  • Bargaining power of buyers. Analyze the number of purchasers (users), concentration, single purchase volume, price sensitivity, and other factors to assess the bargaining power of purchasers in a transaction.

16.3 Identify relevant KPIs

Explanation of the cue words

Cue word content:

"To measure the market performance of our products, 20 unique KPIs are proposed. product is [describe product]."

(English: "Propose 20 unique KPIs to measure our product's market performance. The product is [describe product].")

Explanation and application examples

KPI (Key Performance Indicator) is an important system of quantitative indicators to measure the success of a product and its performance in the market.

Applications at work:

• application scenario: After a product has been officially released and launched, product managers can use this prompt to quickly identify a set of key performance indicators (KPIs) that need to be tracked and monitored in order to continually assess the product's performance in the marketplace and identify potential problems and opportunities for improvement in a timely manner.
• Example (assuming the product is an e-commerce app):
  • Customer Acquisition Cost (CAC)
  • Customer Lifetime Value (CLTV)
  • Monthly Active Users (MAU)
  • Daily Active Users (DAU)
  • DAU/MAU Ratio (User Stickiness Indicator)
  • User retention rate (by day, week, month, etc.)
  • Churn Rate
  • Conversion rates (e.g. signup conversions, purchase conversions, etc.)
  • Average Order Value (AOV)
  • Repeat Purchase Rate (RPR)
  • Cart Abandonment Rate
  • Net Promoter Score (NPS)
  • Customer Satisfaction (CSAT)
  • App Store Rating
  • Return Rate
  • Average Revenue Per User (ARPU)
  • User engagement metrics (e.g., average user hours, frequency of use of core features, etc.)
  • Return on Investment (ROI) of marketing campaigns
  • Customer Service Response Time
  • Social Media Mentions

16.4 KPI Program

Explanation of the cue words

Cue word content:

"Develop a comprehensive guide for evaluating and monitoring product success through KPIs. The guide should prioritize the following: [specific metrics, targets, effective reporting methods, and any analytical tools used]."

(English: "Develop a comprehensive guide on assessing and monitoring product success through KPIs. The guide should prioritize the following dimensions: [specific metrics, targeted objectives, effective reporting methodologies, and any analytics tools used.]")

Explanation and application examples

A well-developed and effective KPI (Key Performance Indicator) program should include the following core elements: clearly selected KPIs, reasonably set target values, scientific reporting methods, and appropriate analytical tools.

Applications at work:

• application scenario: When an enterprise needs to build or systematically optimize the KPI monitoring system of an existing product, the product manager can use this prompt to quickly generate a KPI planning guide to provide methodological guidance for the construction and optimization of the KPI system.
• Sample Guide:
  • Selecting Key Performance Indicators (KPIs):
    • Alignment with product goals: In the early stages of KPI selection, it is important to ensure that the selected KPIs are highly aligned with the overall product goals and strategic direction to avoid deviation.
  • Ensuring the SMART principle:: Selected KPIs need to conform to the SMART principles of Specific, Measurable, Achievable, Relevant and Time-bound.
  • KPI Classification: Categorize KPIs according to different dimensions, such as user acquisition KPIs, user engagement KPIs, revenue KPIs, etc., to form a systematic indicator monitoring framework.
  • target setting:
    • Setting specific target values: Set clear, quantifiable targets for each KPI, e.g., increase user retention to XX%.
    • Challenging objectives:: Set target values that are challenging enough to drive the team to make progress, but also ensure that the targets are achievable, so that they are not too high and lead to a loss of confidence in the team.
    • Reference industry benchmarks: In the process of setting target values, reference can be made to industry averages and historical data to ensure the reasonableness of target setting.
  • Establishment of a reporting mechanism:
    • Determining the frequency of reporting:: Determine a reasonable reporting frequency, such as daily, weekly, monthly, etc., based on business needs and the characteristics of KPI indicators.
    • Creating a KPI Dashboard: Create KPI dashboards using data visualization tools to present key KPI data in graphical and other intuitive forms for real-time monitoring and analysis.
    • Regular reporting on KPI progress: Establish a regular KPI progress reporting mechanism, e.g., weekly and monthly reports to stakeholders on KPI fulfillment and the overall health of product operations.
  • Selection of analysis tools:
    • Principles of tool selection: Choose the most appropriate analytics tool based on a combination of factors such as product type, data volume size, and team budget.
    • Commonly used analytical tools: Commonly used data analysis tools in the industry include Google Analytics, Mixpanel, Amplitude, Tableau, etc., and product managers can choose the right combination of tools according to their needs.
  • Data collection and integration:
    • Data accuracy:: Ensure that the KPI data collection process is accurate, so that data bias does not affect the accuracy of the results of subsequent analyses.
    • data integrity: Ensure the completeness of KPI data to avoid one-sided analysis results due to missing data.
    • data integration:: Integrate data from different data sources into a unified data analysis platform to break down data silos and achieve data fusion.
  • Data analysis and interpretation:
    • Regular data analysis:: Establish a mechanism for regular data analysis, such as weekly and monthly in-depth analysis of KPI data, in order to identify data trends and potential problems in a timely manner.
    • Digging deeper into the data: In the process of data analysis, it is not only necessary to pay attention to the surface changes of data, but also to dig deeper into the deeper reasons behind the changes of data, such as changes in user behavior, changes in the market environment and so on.
    • Data-driven decision-making: Transform data analysis results into executable product optimization strategies and operational improvement measures, truly realizing data-driven decision-making.
  • Action and optimization:
    • Development of optimization measures: Based on the results of data analysis, develop targeted measures for product function optimization and operation strategy adjustment.
    • Continuous monitoring of KPIs: Continuously monitor changes in KPIs after the implementation of optimization measures to assess the effectiveness of optimization.
    • KPI Dynamic Adjustment: Dynamically adjust KPI indicators and target values according to changes in the market environment, user feedback, and product iteration to ensure the ** актуальность (актуальность - актуальность)** and effectiveness of the KPI system.

16.5 Product Release Indicators

Explanation of the cue words

Cue word content:

"To measure the success of our most recent release, a set of metrics is suggested. This release includes [describe version]."

(English: "Suggest a set of metrics to measure the success of our recent release. The release includes [describe release].")

Explanation and application examples

Measuring the success of a product launch requires choosing the right metrics for the content of the launch.

Applications at work:

• application scenario:: Evaluate the effectiveness of new product releases after they are released.
• typical example:
  • Posted content: Added the "Online Collaboration" feature and optimized the user registration process.
  • Suggested indicators:
    • Utilization of new features:: Measure how many users have utilized the "online collaboration" feature.
    • User retention rate for new features:: Measure the subsequent retention of users who utilize the "online collaboration" feature.
    • Rate of completion of collaborative tasks:: Measure the number and proportion of tasks accomplished through the "online collaboration" function.
    • Registration Conversion Rate:: Measure whether the conversion rate of new user registrations improves after optimizing the registration process.
    • User feedback: Collect user feedback on new features and registration processes (e.g., NPS, app store ratings).
    • Key operational indicators: Evaluate the impact of new features and registration process optimizations on key business metrics (e.g., DAUs, MAUs, revenue).
    • Length of user participation: Measure whether there is a change in the total time a user spends within the app.
    • Crash rate/error rate:: Monitor new releases for technical problems.

16.6 Increased user participation

Explanation of the cue words

Cue word content:

"Propose a set of A/B tests to improve user engagement. The product is [describe product]."

(English: "Propose a set of A/B tests to improve user engagement. The product is [describe product].")

Explanation and application examples

A/B testing is an effective way to improve user engagement by comparing different solutions to find the optimal solution.

Applications at work:

• application scenario:: When user engagement needs to be optimized for a particular part of the product.
• Example (assuming the product is a social app):
  • Test different push notification texts:.
    • Group A: Use personalized copy (e.g. "@username, someone sent you a message!"). .
  • Group B: Use generic copy (e.g. "You have new messages!"). ).
  • Metrics: push notification click-through rate, user activity.
  • Testing Different Content Recommendation Algorithms.
    • Group A: Use of user interest-based recommendation algorithms.
    • Group B: Use recommendation algorithms based on popular content.
    • Metrics: content click-through rate, user dwell time, interaction rate (likes, comments, shares).
  • Test different interface layouts.
    • Group A: Use a card layout.
    • Group B: Use a list layout.
    • Metrics: depth of user navigation, frequency of feature use.
  • Testing different newbie orientation processes.
    • Group A: Use of video guides.
    • Group B: Use of graphic guides.
    • Metrics: newbie orientation completion rate, key feature usage.
  • Test different ways of social interaction.
    • Group A: Add an "@" function to allow users to mention others in their comments.
    • Group B: Status quo.
    • Metrics: number of comments, frequency of user interaction.
  • Testing Different Virtual Gift Designs.
    • Group A: Use a nicer virtual gift design.
    • Group B: Use the current virtual gift design.
    • Metrics: number of virtual gifts given, user activity.

16.7 Pricing Strategy

Explanation of the cue words

Cue word content:

"Propose 3 alternative pricing strategies for our new product. product is [describe product]."

(English: "Propose 3 alternative pricing strategies for our new product. The product is [describe product].")

Explanation and application examples

Pricing strategy directly affects the market competitiveness and profitability of the product.

Applications at work:

• application scenario: Develop a pricing strategy prior to the launch of a new product.
• Example (assuming the product is a SaaS software):
  • Value-based pricing.
    • Pricing is based on the value the product provides to the customer.
  • Prices vary for packages with different features and usage.
  • For example: Basic Edition (for individual users), Professional Edition (for small teams), Enterprise Edition (for large organizations).
  • Competition-based pricing.
    • Refer to competitors' pricing.
    • It can be slightly higher, equal or lower than the competition.
    • For example, if a competitor's similar product is priced at $100 per month, we can price it at $90 per month (penetration pricing) or $110 (premium pricing).
  • Cost-plus pricing.
    • A margin is added to the cost of the product.
    • For example, if the product costs $50 per month to develop and operate, and we want a 50% margin, then the pricing could be $75 per month.
  • Freemium Pricing:
    • Offer a free basic version to attract users.
    • Premium features or greater usage require a fee.
  • Penetration Pricing.
    • Initially enter the market with a low price to acquire users quickly.
    • Gradually increase prices as market share increases.
  • Skimming Pricing.
    • Initially enter the market at a high price, targeting early adopters who are willing to pay a high price.
    • Gradually reduce prices as competition increases.

17. Preparation of documentation

17.1 Product Requirements Document (PRD) Template

Explanation of the cue words

Cue word content:

"I am creating a detailed product requirements document for [describe your product at a high level]. Please give me a template and explain the purpose of each section."

 

 

(English: "I am looking to create a detailed Product Requirement Document for [describe your product at a high level]. Please give me a template and explain the purpose of each section.")

Explanation and application examples

PRD is an important basis for product development, which describes in detail the requirements, functions, and specifications of the product.

Applications at work:

• application scenario:: Before starting a new project or new feature development.
• Example templates:
  • Document Revision History:
    • Record the version number, date of modification, modifier and content of the document.
  • Overview:
    • Background: Briefly describe the product's background, market opportunity, and user needs.
    • Goals: Describe what the product is trying to achieve, either qualitatively or quantitatively.
    • Target Audience: Describe the product's target user group, including their characteristics, needs, and pain points.
  • Requirements:
    • User Stories: Describe the requirement from the user's perspective, usually in the format "As a , I want in order to ".
    • Functional Requirements: Describe in detail the functions of the product, including inputs, processing, and outputs.
    • Non-functional Requirements: Describe the performance, security, reliability, maintainability, and scalability requirements of the product.
  • Design:
    • Prototypes (Mockups/Wireframes):: Provide interface prototypes or wireframes for products.
    • UI Specifications: Describes the layout, colors, fonts, interactions, and other details of the interface.
  • Release Criteria:
    • Define the conditions under which the product meets the release criteria, such as completing the development of all features, passing tests, and meeting performance metrics.
  • Open Issues:
    • List outstanding issues or matters requiring further discussion.
  • Assumptions:
    • List the assumptions made in the document so that they can be verified in the follow-up process.
  • Appendix:
    • Include any supporting documentation such as market research reports, user interview transcripts, competitive product analysis, etc.

17.2 Preparation of PRDs

Explanation of the cue words

Cue word content:

"Please write a detailed Product Requirements Document for [describe your product or feature]. Include all important details and the following sections [list any sections your product team would like to see in the PRD]."

 

 

(English: "Please write a detailed Product Requirement Document for [describe your product or feature]. Include all the important details and the following sections

.")

Explanation and application examples

Populate the sections of the PRD template according to the specific product or function.

Applications at work:

• application scenario: Describe specific product requirements in detail.
• Example (assuming an "Online Collaborative Documentation" feature is to be developed):

  Product Requirements Document (PRD)

  1. Document revision history

  version number	Modification Date	modifier	Content of the modification
  1.0	2024-05-16	[Your name]	first draft (of writing)

  2. Overview

  • contexts: Currently, when team members collaborate to write documents, they need to exchange files frequently via email or instant messaging tools, which is inefficient and prone to version confusion.
  • goal:
    • Improve the efficiency of team members collaborating on documents.
    • Reduce document version confusion.
    • Enhance the collaborative experience of team members.
  • target user:: Team members who need to collaborate on documentation.

  3. Demand

  • User Stories:
    • As a team member, I would like to be able to invite others to co-edit documents in order to make collaboration more efficient.
    • As a team member, I want to be able to see what others are editing in real time to keep up with progress.
    • As a team member, I would like to be able to comment and respond to the documentation for discussion purposes.
    • As a team member, I would like to be able to view the historical version of a document in order to go back through the revision history.
  • functional requirement:
    • Multiplayer real-time editing:
      • Supports multiple users editing the same document at the same time.
    • Display other users' edits in real time.
    • Cursors and selections for different users are distinguished by different colors.
    • Comments and replies:
      • Users can comment on any part of the document.
      • Other users can reply to comments.
      • Comments and replies support @mentions to other users.
    • revision history (of a web page):
      • Automatically save historical versions of documents.
      • Users can view, compare and restore historical versions.
    • Rights Management:
      • The document creator can set permissions (Edit, Comment, View) for other users.
    • notifications:
      • When a document is edited, commented on or replied to, the relevant user is notified.
  • non-functional requirement:
    • performances: Documents load in less than 3 seconds, with no noticeable delays when multiple people are editing at the same time.
    • safety: Encrypted storage of document content to prevent unauthorized access.
    • dependability:: System availability of 99.99%.
    • scalability:: Support the addition of more collaboration features in the future.

  4. Design

  • original form:: (Provide prototype drawings or links)
  • UI Specifications: (describes the layout, colors, fonts, interactions, and other details of the interface)

  5. Publication standards

  • Complete all functional requirements.
  • Pass all test cases.
  • Meet the performance, security, and reliability metrics defined in the non-functional requirements.

  6. Unresolved issues

  • Do I need to support offline editing?
  • How does it integrate with existing systems?

  7. Assumptions

  • Users are already familiar with basic document editing operations.

  8. Appendix

  • (Optional)

18. User experience

18.1 Collaboration with designers

Explanation of the cue words

Cue word content:

"Please provide best practices for working with the design team on [describe your product]. [You may also specify any relevant information about your product team, design team, tools used by either, and any related processes (e.g., Lean or Agile methods, SAFe, Waterfall).]"

 

 

(English: "Please provide best practices for collaborating with a design team on [describe your product]. [You can also specify anything relevant about your product team, the design team, the tools either team uses, and any relevant processes (e.g. lean or agile methodology, SAFe, waterfall.]"). agile methodology, SAFe, waterfall.]").

Explanation and application examples

Good collaboration between product managers and designers is key to creating a great user experience.

Applications at work:

• application scenario:: When working with design teams on new projects or optimizing existing products.
• best practice:
• Early engagement: Involve designers early in the project to discuss product goals, user needs, and potential solutions.
• clear communication:
  • Provide a clear Product Requirements Document (PRD).
  • Explain user stories and scenarios in detail.
  • Use visualization tools (e.g., flowcharts, user journey maps) to aid communication.
• develop a common language:
  • Understand basic design principles and terminology.
  • Work with designers to develop design specifications.
• Respect for the profession:
  • Trust the designer's expertise.
  • Don't overly interfere with design details.
  • Provide constructive feedback rather than subjective opinions.
• Iterative feedback:
  • Conduct regular design reviews with designers.
  • Provide timely feedback to help designers iterate quickly.
  • Verify the design solution using A/B testing.
• Collaboration tools:
  • Use collaborative design tools such as Figma, Sketch, and Adobe XD.
  • Track design tasks using project management tools such as Jira, Trello, etc.
• Cross-functional teams:
  • Form cross-functional teams of product managers, designers, developers, etc.
  • Adopt agile development methodologies and promote teamwork.
• Building empathy:
  • Try to think about things from a designer's point of view.
  • Understand the workflow and challenges of designers.

18.2 Login Page Design

Explanation of the cue words

Cue word content:

"Create a list of must-have visual elements and design principles for an effective [describe your product] landing page. The page should advance [specify customer experience goals] and [list key brand guidelines] based on these."

(English: "Create a list of must-have visual elements and design principles for an effective landing page for [describe your product]. The page should advance [specify customer experience goals] and be based on these

.")

Explanation and application examples

The login page is the first impression of the product for users, and a good design can effectively increase the conversion rate.

Applications at work:

• application scenario:: When designing or optimizing product login pages.
• Essential Visual Elements:
  • logo: Clearly display the product logo.
  • value proposition: A clear and concise statement of the product's core values and benefits.
  • Call to Action (CTA) Button: Eye-catching, easy-to-click sign-up or login buttons.
  • form (document):: Simple, easy-to-fill registration or login forms.
  • Social Login Options: Provides the option to log in using a social account (optional).
  • Element of trust: Display user reviews, security certifications, partner logos, etc. (optional).
  • Background image or video: Use high-quality images or videos to engage users (optional).
  • Product Showcase: A brief demonstration of the product's core features in the form of pictures or videos (optional).
• Design Principles:
  • pithy: The page layout is clean and the information hierarchy is clear.
  • consistency:: Consistency with brand image.
  • usability:: Forms are easy to fill out and flow smoothly.
  • responsive:: Displays well on different devices.
  • visual appeal: Use high-quality images, icons and color schemes.
  • Loading speed:: Optimize page loading speed and reduce user waiting time.
  • A/B testing:: A/B testing of different design solutions to find the optimal solution.
  • emphasize the key points: Place the most important information (e.g., value proposition, CTA button) in the most prominent place.
  • leave a message: Use white space appropriately to avoid overcrowding the page.

19. User feedback

19.1 User research strategy

Explanation of the cue words

Cue word content:

"Please develop an effective strategy for user research and gathering valuable feedback for [describe your product]. Consider the following methods and tools: [specify the methods and tools you are considering]."

(English: "Please create a strategy for conducting effective user research and gathering valuable feedback for [describe your product]. Considering these methods and tools: [specify methods and tools you're considering].")

Explanation and application examples

User research is an important tool for understanding user needs and improving products.

Applications at work:

• application scenario:: When developing product plans, optimizing existing products or exploring new opportunities.
• be tactful:
  • Defining research objectives:
    • Define user information (e.g., user needs, pain points, behaviors) to be understood.
  • Determining the use of research findings (e.g., guiding product design, optimizing user experience).
  • Selection of research methodology:
    • quantitative research:
      • Surveys: Large-scale collection of user data.
    • Data Analysis: Analyzing existing user behavior data.
    • A/B Testing: Comparing the effects of different scenarios.
    • qualitative research:
      • User Interviews: Gain insight into the thoughts and feelings of your users.
      • Usability Testing: Observing how users use a product.
      • Focus Groups: Organize group discussions to gather user feedback.
      • Diary Studies: Records user usage over time.
      • Card Sorting: Understanding how users organize information.
      • Eye Tracking: Understanding the user's visual focus on the interface.
  • Selection of research tools:
    • Survey tools: SurveyMonkey, Typeform, Google Forms.
    • User interview tools: Zoom, Google Meet, Microsoft Teams.
    • Usability testing tools: UserTesting, Lookback, Hotjar.
    • Data analysis tools: Google Analytics, Mixpanel, Amplitude.
  • Recruitment of participants:
    • Appropriate participants were selected based on the objectives of the study.
    • Recruitment can be done through user databases, social media, and recruiting platforms.
    • Provide appropriate incentives to encourage user participation.
  • Implementation research:
    • Strict adherence to the research program.
    • Remain objective and neutral and avoid leading users.
    • Keep good records, such as audio, video, notes, etc.
  • analysis:
    • Organize and analyze the data collected.
    • Distill key findings and insights.
    • Write a research paper.
  • Application results:
    • Apply findings to product design and optimization.
    • Continuously track user feedback and evaluate improvements.
  • take note of:: Different combinations of research methods are used for different phases (e.g., product conceptualization, prototyping, post-launch).

19.2 User interviews

Explanation of the cue words

Cue word content:

"Explain the process of designing and conducting user interviews for [describe your product], providing guidance on preparing interview questions, selecting participants, and managing the interview process."

(English: "Explain the process of designing and conducting a user interview for [describe your product], providing guidance on preparing interview questions, selecting participants, and managing the interview process. questions, selecting participants, and managing the interview process.")

Explanation and application examples

User interviews are an effective way to gain insight into user needs and pain points.

Applications at work:

• application scenario: When exploring user needs, validating product concepts, and evaluating user experience.
• course of events:
  • Determine the objectives of the interview:
    • Define the user information to be understood (e.g., user perceptions of the existing product, expectations of new features, pain points when using the product).
  • Translate interview objectives into specific questions (e.g., "In what situations do you typically use our product?" , "What do you feel are the shortcomings of the current product?" , "What problems do you expect the new features to solve?") .
  • Preparation of interview questions:
    • Design open-ended questions that encourage users to express their thoughts and feelings, and avoid closed questions (yes or no answers only).
    • Avoid leading questions (e.g. "Did you find this feature difficult to use?"). .
    • Questions should cover user background, usage scenarios, pain points, needs, and expectations.
    • Prepare back-up questions for different scenarios (e.g., the user is not articulate, goes off on a tangent, etc.).
    • Control the number of questions and avoid lengthy interviews (30-60 minutes is recommended).
    • Sequencing of questions: from simple to complex, general to specific, background information before delving into specific issues.
    • Use the STAR method to guide the user through specific cases (Situation, Task, Action, Result).
    • Examples of questions:
      • "Can you briefly introduce yourself? (to understand the user's background)"
      • "Under what circumstances do you typically use our products/services?"
      • "Have you encountered any problems or difficulties in using the program? Can you give me an example?"
      • "What is your overall satisfaction with our products/services?"
      • "In what areas would you like to see our products/services improved?"
      • "If there is a new feature [describe feature], do you think it would be helpful to you?"
      • "Is there anything else you'd like to tell us?"
  • Select Participants:
    • Select eligible users (e.g., target users, typical users, churned users) based on the interview objectives.
    • Consider the diversity of users, such as age, gender, occupation, experience of use, etc., to get more comprehensive feedback.
    • Participants were recruited and informed of the purpose, process, duration, confidentiality agreements, and incentives for the interviews.
    • Number of participants: 5-8 participants is usually sufficient to identify most problems, but this should be adjusted accordingly.
  • conduct interviews:
    • Choose a quiet, comfortable environment to avoid distractions.
    • Establish a congenial atmosphere that relaxes users and encourages them to speak freely.
    • Follow the interview outline, but be flexible and follow up with questions based on the user's answers.
    • Listen carefully, avoid interrupting the user, remain neutral, and don't judge the user's point of view.
    • Keep records, such as audio and video recordings (with the user's consent) and notes.
    • Control of interview time and thanking users for their participation.
    • Interviewing techniques:
      • Active Listening: Focus, eye contact, nodding in response.
      • Ask questions at the right time: ask for details, clarify doubts.
      • Guiding the user: When the user goes off-topic, politely guide them back.
      • Neutral: not evaluating, not refuting, not arguing.
      • Control the pace: Keep track of time and avoid time-outs.
  • Analyzing the results of the interviews:
    • Organize interview transcripts (e.g., audio to text, notes organization).
    • Find out what users have in common and what differentiates them.
    • Distill key findings and insights (e.g., core user needs, pain points, expectations).
    • Share the results of the interviews with the product team and discuss how to improve the product.
    • This can be analyzed using tools such as the Affinity Diagram.

19.3 Questionnaire

Explanation of the cue words

Cue word content:

"Draft a survey to gather customer feedback on our latest release. This release includes [describe release]."

(English: "Draft a survey to collect customer feedback on our latest release. The release includes [describe release].")

Explanation and application examples

Surveys collect user feedback on product releases on a large scale.

Applications at work:

• application scenario: Collect user feedback after product release.
• typical example:

  Questionnaire title: [Product Name] [Version Number] User Feedback Survey

  Introduction.

  Dear [product name] users:

  Thank you for using [PRODUCT NAME]! We have recently released version [version number] with [new features/optimizations] (brief description). In order to better understand your experience and to continuously improve our product, we invite you to fill out this short survey. Your feedback is very important to us!

  This survey will take approximately [time] minutes and all information will be kept strictly confidential.

  Question.

  • Are you already using the [version number] version?
  • be
  • No (skip to question X)
  • How satisfied are you with the [version number] version overall? (Likert scale, e.g. 1-5, with 1 being very dissatisfied and 5 being very satisfied)
  • Are you using [New Feature/Optimization]?
    • be
    • No (skip to question X)
  • How satisfied are you with [new features/optimizations]? (Likert scale)
  • Does [New Feature/Optimization] meet your needs?
    • Very satisfying.
    • more satisfied
    • general
    • Not very satisfying.
    • Very unsatisfying.
  • What do you think are the advantages of [new feature/optimization]? (open-ended question)
  • What do you think [new feature/optimization] needs to be improved? (open-ended question)
  • Have you encountered any problems or difficulties in using the [version number] version? (open-ended question)
  • What are your suggestions or expectations for the future of [PRODUCT NAME]? (open-ended question)
  • (Optional) Would you like to leave your contact information so that we can further understand your feedback? (Name, e-mail, phone number, etc.)

  Ending.

  Thank you again for your participation! Your feedback will help us to continuously improve [Product Name] and provide you with better service!

  Key points of questionnaire design:

  • clear-cut objective:: Identify the information to be collected.
  • Concise questions:: Questions are short, clear and easy to understand.
  • Avoid leading:: Avoid using tendentious questions.
  • logical:: The questions are in a logical order and fit the user's habits of mind.
  • Control length:: The questionnaire should not be too long to avoid user fatigue.
  • Provision of options:: Use multiple-choice questions wherever possible to facilitate user completion and data analysis.
  • Open-ended questions:: Appropriate use of open-ended questions to gather more detailed feedback.
  • questionnaire:: Conduct a small test to ensure that there are no problems with the questionnaire before officially releasing it.
  • data analysis:: Analyze collected data to distill key findings and insights.

20. Stakeholder collaboration

Explanation of the cue words

Cue word content.

"Develops a strategic blueprint for product managers to facilitate productive collaboration with cross-functional teams. Highlight specific communication techniques and tools that product managers can use and recommend best practices to optimize collaboration. [Describe your product, company, stakeholders, or any other relevant context.]"

 

 

(English: "Develop a strategic blueprint for a product manager to facilitate efficient collaboration with cross-functional teams. Highlight specific communication techniques and tools that the product manager can use and recommend best practices for optimized collaboration. specific communication techniques and tools that the product manager can use and recommend best practices for optimized collaboration. [Describe your product, company, stakeholder, or any other relevant context. Highlight specific communication techniques and tools that the product manager can use and recommend best practices for optimized collaboration. [Describe your product, company, stakeholder, or any other relevant context.]")

Explanation and application examples

Product Managers need to collaborate with a variety of stakeholders, including development, design, marketing, sales, customer service, executives, and others. Effective collaboration ensures that products are developed and released smoothly and that business goals are met.

Applications at work:

• application scenario:: In day-to-day product management.
• strategic blueprint:
  • Identify key stakeholders.
    • List all stakeholders associated with the product.
  • Understand their roles, responsibilities, expectations and concerns.
  • Create a Stakeholder Map.
  • Establishment of a communication plan.
    • Determine the frequency, manner and content of communication with different stakeholders.
    • Regular communication: e.g., weekly meetings with the development team and monthly reports to executives.
    • On-demand communication: for example, communicating with the relevant people in a timely manner when issues arise or decisions need to be made.
    • Mode of communication: Choose the appropriate mode of communication according to the situation, such as face-to-face meeting, video conference, e-mail, instant messenger, etc.
    • Communication content: customized messages based on different audiences.
  • communication skill:
    • active listening:: Listen carefully to the views and suggestions of stakeholders and understand their perspectives.
    • articulate:: Use simple, clear language and avoid jargon.
    • think sth through in another place (idiom); to put oneself in sb else's shoes:: Thinking from the perspective of stakeholders and understanding their needs and concerns.
    • timely feedback:: Respond to stakeholder emails, messages and questions in a timely manner.
    • build trust:: Building trust through honest, transparent and reliable behavior.
    • Managing expectations:: Clarify product goals, scope and timelines to avoid unrealistic expectations.
    • conflict resolution:: Timely and effective resolution of conflicts between stakeholders.
    • stay positive: Maintain a positive and optimistic attitude and create a good atmosphere for cooperation.
  • Collaboration tools:
    • Project management tools: Jira, Trello, Asana, Monday.com and more.
    • Communication tools: Slack, Microsoft Teams, Nails, Flybook, etc.
    • Document Collaboration Tools: Google Docs, Confluence, Notion, and more.
    • Prototyping Tools: Figma, Sketch, Adobe XD and more.
    • Meeting tools: Zoom, Google Meet, Microsoft Teams, and more.
  • best practice:
    • Establishment of common goals:: Ensure that all stakeholders understand and agree with the product objectives.
    • Clarification of roles and responsibilities:: Ensure that each team member is clear about their roles and responsibilities.
    • Maintaining transparency of information:: Share product information, including progress, issues and risks, with all stakeholders.
    • Regular review and improvement:: Regularly review the collaboration process and make improvements.
    • Building cross-functional teams: Form a team of members from different departments who are collectively responsible for the success of the product.
    • Celebrating Success:: Timely celebration of team achievements to enhance team cohesion.
  • Communication Strategies for Different Stakeholders:
    • executives:: Focus on strategic direction, key metrics, risk and return on investment.
    • development team:: Focus on technical feasibility, workload, schedule and risk.
    • Design Team:: Focus on user experience, interface design and interaction.
    • Marketing Team:: Focus on marketing, user acquisition and branding.
    • Sales Team: Focus on product features, pricing and sales strategies.
    • Customer Service Team:: Focus on user feedback, problems and solutions.

summarize

This manual aims to provide product managers with a set of systematic and professional guidelines for the use of cues to help you achieve standardized and process-oriented management in all aspects of your work, from skills enhancement, product case analysis, framework application, tool selection to data analysis and user communication. Through the application examples in real work scenarios, you can better understand and flexibly use these cues to promote the continuous optimization of the product and the efficient collaboration of the team. We encourage you to use this manual as a daily reference tool to practice, summarize and optimize, and become an indispensable partner on the road of your product management.