Help us Build the Future of MR 💫

Meet the team working on accelerating research workflows using AI, Frances Chen and George Jacob, and see how Early Access feedback turns ideas into capabilities. 📩

In today’s fast-paced market, delivering products that truly resonate with customers requires a strong partnership between Product Management and Product Marketing. Understanding how these two roles work together — especially in gathering and acting on customer feedback, can help you appreciate the thoughtful process behind the products you use every day.

Why Collaboration Matters between PMs & PMMs 🏆

While PMs focus on building the right product for our customers, PMMs focus on telling the right story and making sure customers understand how the product can solve their business problems. Collaboration between these roles ensures what is built is not only useful, addresses customers pain points, but is also clearly communicated to the market.

In this feature, we will highlight how Frances (PMM) and George (PM) work together to create AI capabilities for Market Research that are powered by AI.

How do Frances and George collaborate? 🎖

The core of Frances and George’s collaboration lies in the balance between Problem-Solution fit and Product-Market fit. George ensures the team is focusing on the most important problems and solving them through the product in the right way, while Frances ensures the market understands its value and is ready to adopt it. This partnership ensures that the team isn't just building products correctly, but that they are building the right products for target personas.

Frances often communicates market insights to George through a PR/FAQ document that helps inspire the product vision. George collaborates with a cross-functional team of designers, user researchers, engineers, account executives and other customer-facing stakeholders throughout the product development lifecycle, ensuring the final solution is valuable, usable, reliable, and scalable.

How Customer Feedback Fuels This Partnership 🚥

Early customer feedback is at the heart of the product development process! Before launch, PMs and PMMs often work with customers to validate new functionality and messaging. This might involve beta testing with a select group of users to confirm the feature solves their problem as expected, or running messaging tests to ensure the value proposition resonates with target personas. Feedback from these sessions informs final adjustments to both the product and the go-to-market strategy.

Customer needs are the center of our ecosystem, and your participation is crucial to maintaining a customer-centric approach.

Because of this tight collaboration empowered by feedback:

• Helps solve real customer problems
• Communication is clearer on why a product fits customer needs
• Continuous improvements are made, creating better user experiences over time 

Importance of Feedback 🎯

Frances and George rely on clear, actionable feedback to turn initial ideas into capabilities that truly solve customer problems. Vague feedback can slow down development and make it harder for George to prioritize the right engineering work, or for Frances to craft the right message. To ensure your input has the maximum impact on capabilities, we've distilled the best practices we value from our Early Access users:

1. Be Specific, Not Vague: Pinpoint the exact element or moment you are referring to (e.g.,"the 'Apply Filter' button"). Avoid general statements that don't help the recipient know what to fix (e.g., "The flow needs work," "The feature is confusing").
2. Focus on Observable Behavior or Data: Whenever possible, ground your feedback in what you or others observed or experienced. Use metrics or objective actions (e.g., "I need multiple clicks to get to the designated page").
3. Explain the Impact or Problem, Not Just the Feeling: Detail why the vague thing you noticed is an issue. Connect the observation to a negative outcome or a goal (e.g., the transition "felt abrupt," the red color "is confusing" because "Users might associate it with a failure state,").
4. Offer an Actionable Solution or Alternative (or a path to one): Provide a concrete suggestion or a path forward instead of just pointing out a flaw (e.g., "Consider adding an automated flow to match a designated usecase," "Could we remove whitespace or add a button?.”

In short: Make your feedback S.T.A.R. (Specific, Timely, Actionable, Relevant) by moving from:

• Vague Observation → Specific Detail
• Subjective Opinion → Objective Impact/Data
• Complaint → Constructive Solution/Next Step

X4 🎉 

The Early Access and Product teams will be at X4 this year and we'd love to listen to you! The Early Access team will have a designated booth, and we will share the details with everyone soon.