→ Save Your Spot! Our Free Webinar: Reduce org-wide meeting time and increase your productivity. Sign Up now

How To Run A Product Review Meeting

A Product Review Meeting should be efficiently run by formulating a clear agenda, discussing progress, problems and solutions, evaluating the product against set criteria, gathering and addressing feedback, and laying down clear next steps for every team involved.

A Product Review Meeting is a structured discussion orchestrated by teams involved in the development and marketing of a product, with the aim to assess its performance, usability, and functionality. In this meeting, the team analyzes consumer feedback, revisit the product goals, evaluates its market success, and identifies areas for improvement or necessary modifications. It serves as an essential process in aligning product development with consumer expectations and business objectives, fostering product morphing as market conditions and customer needs evolve.

What is the purpose of a Product Review Meeting?

The purpose of running a product review meeting as a leader is to evaluate the performance and quality of a product, gather feedback from team members, identify areas for improvement, and make informed decisions about the future of the product. It also serves as an opportunity to discuss any challenges, share insights, and align the team towards achieving product goals and objectives.

How To Run A Product Review Meeting: Step-By-Step

1

Step 1: Planning the Meeting

The purpose of the product review meeting is typically to evaluate the product’s features, functionality, and compatibility with its intended use. It’s crucial to develop a meeting agenda, outlining the key discussion topics, which offers structure and contributes to the overall productivity of the session.

Next Step
2

Step 2: Inviting Participants

To conduct a thorough product review, engage critical stakeholders such as team members directly involved in product development, marketing, and sales. Moreover, include individuals capable of providing meaningful feedback such as quality assurance teams, customer service representatives, and external users or consumers.

Next Step
3

Step 3: Preparing for the Meeting

To prepare for an effective meeting, aggregate all vital product data – such as product specifications, customer feedback, competitor comparison, and performance metrics. Distribute these details to all attendees beforehand, permitting adequate time for comprehensive review and preparation for informed discussion during the meeting.

With ZipDo, our application, the hassle of preparing for team meetings is significantly reduced. Meeting leads benefit from a central hub of information from prior meetings, streamlining the retrieval of agendas and notes. This methodical approach ensures complete topic coverage.

Recommendation
Advertisement

Want to run a better meeting? Try ZipDo, our Meeting Note Software.

  • Connect your Google Calendar
  • Automatically create a note for every meeting
  • Organize your meetings and meeting notes in a channel like Slack
Try ZipDo free
Next Step
4

Step 4: Conducting the Meeting

Begin the meeting by methodically going over the agenda. This allows everyone to know the specific points of discussion. Move sequentially through each topic, facilitating a space where everyone has a fair chance to voice their feedback and ideas. Be diligent about noting down action points arising from the discussions. This ensures fine attention to detail and post-meeting follow-ups.

Next Step
5

Step 5: Analyzing Feedback

Once your meeting concludes, meticulously examine feedback on the product. Identify common themes, shared viewpoints, and areas of agreement. This invaluable data will then guide your strategies in refining and enhancing the designed product, leading to better customer satisfaction.

Next Step
6

Step 6: Documentation and Follow-up

It’s essential to meticulously write down key points and objectives that emerge during a meeting. Sharing the minutes with all present enables a collective revision and understanding, encouraging engagement. Post-meeting, reinforce accountability by following up on assigned action items, ensuring they’re undertaken as agreed.

Next Step
7

Step 7: Implement Changes

Upon the evaluation of feedback and subsequent verdict of the meeting, initiate any essential adjustments or enhancements to the product. This might necessitate a revamp in design, refining its component features, or a complete redevelopment of certain aspects to better align it with customer needs.

Questions to ask as the leader of the meeting

1. What were the primary goals and objectives for this product?
Explanation: This question helps the leader understand the purpose and intention behind the product development process.

2. How well did this product meet the stated goals and objectives?
Explanation: This question allows for an evaluation of whether the product successfully fulfilled the initial intentions and criteria.

3. What are the key strengths and weaknesses of the product?
Explanation: Identifying the strengths can help in capitalizing on successful aspects, while recognizing weaknesses is crucial for improvement and addressing customer needs.

4. How does this product compare to our competitors’ offerings?
Explanation: Understanding the competitiveness of the product within the market provides valuable insights and opportunities for differentiation.

5. What customer feedback have we received so far?
Explanation: Customer feedback is a critical element in assessing product performance and identifying areas for improvement.

6. What have we learned from user testing or beta trials?
Explanation: User testing and beta trials provide valuable information on how the product functions in real-life scenarios, uncovering potential issues or highlighting areas of success.

7. How has customer demand for the product been since its launch?
Explanation: Evaluating customer demand can help gauge the product’s reception, popularity, and future potential in the market.

8. Are there any technical or logistical challenges encountered during the development or production process?
Explanation: Identifying any challenges faced can help address any existing bottlenecks and find ways to streamline processes for future endeavors.

9. How has the product’s performance been in terms of sales and revenue?
Explanation: Assessing sales and revenue helps measure the product’s commercial success and financial viability.

10. What are the next steps and actions needed based on the product review?
Explanation: Determining the next course of action ensures that any required improvements, adjustments, or enhancements are identified and included in the product roadmap.

As a leader, preparing a product review meeting agenda involves a clear structure. Start with an overview to set the context, followed by specific items to be discussed. Include time frames for each item to ensure a focused discussion. End with actionable next steps and assign responsible team members for follow-up tasks.

How To Prepare For A Product Review Meeting
Meeting Preparation Icon

In a product-review meeting, it is crucial to discuss the product features, advantages, and benefits, as well as any shortcomings or issues encountered. The meeting should also cover customer feedback, market trends, competitor analysis, and recommendations for improvement or future enhancements.

See Our Product Review Meeting Template
Meeting Template Icon

Software tools to facilitate a Product Review Meeting

Software helps leaders run product review meetings by providing a centralized platform to organize and track product feedback. It enables leaders to easily collate and analyze feedback from team members, identify key issues, and track progress in addressing them. With features like real-time collaboration and analytics, software streamlines the review process, allowing leaders to make informed decisions and drive product improvement.

Our Recommendations:

Conclusion

To run a successful product review meeting, it is essential to foster open communication, properly plan and schedule, keep the conversation focused and data-driven, and allocate precise yet flexible time for each point on the agenda. It is also equally important to ensure the meeting is efficient, concise, and yields actionable results. Remember, the end goal is not just to identify shortcomings but also to recognize strengths, learn from successes and failures, and visibly advance the development of the product. By following these guidelines, your product review meetings are set to become a driving force in your company’s growth and success.

Jannik Lindner

I'm Jannik and I write on MeetingFever about the experiences from my career as a founder and team lead.

If you have any questions, please contact me via LinkedIn.

Popular Questions

What is the main purpose of a Product Review Meeting?

The primary purpose of a Product Review Meeting is to evaluate the performance, reliability, and effectiveness of a particular product. It’s an opportunity for teams to discuss the product’s strengths and weaknesses, feedback from customers, and strategies for improvement or potential enhancements.

Who should attend a Product Review Meeting?

Typically, a Product Review Meeting should include product managers, design teams, marketing teams, and higher-level executives. These meetings may also involve customer representatives, sales teams, and any other stakeholders who could provide valuable insights about the product’s performance.

What outcomes can be expected from a Product Review Meeting?

The outcomes can include a range of action items such as product improvements, alterations in marketing strategy, customer service enhancements, or changes in the production process. Additionally, conclusions or decisions may be reached about the product’s future, such as whether to launch a new version, discontinue the product, etc.

How can we ensure a Product Review Meeting is successful?

For a successful meeting, it’s crucial to come prepared with all necessary data and feedback on the product, encourage open and honest communication, keep the meeting focused and on track, and ensure that everyone leaves the meeting with a clear understanding of the decisions made and their subsequent responsibilities.

How often should Product Review Meetings be held?

The frequency of Product Review Meetings can largely depend on the nature of the product and market conditions. In a rapidly changing market, these meetings may need to be held more frequently, such as once a quarter. For products in stable markets, bi-annual or annual review meetings might be sufficient.

Get free access to our meeting webinar

By submitting the form you are subscribing to our newsletter. Our newsletter contains information about new blog articles, other offers, tips and promotions from MeetingFever. You can unsubscribe at any time. Information on data protection, revocation, performance measurement and logging can be found in our privacy policy.