How to incorporate private customer needs into a public product roadmap
Blog post from GitLab
Effectively communicating customer needs to product teams is crucial for a product's success, as demonstrated by GitLab's practices, which emphasize transparency and collaboration. GitLab employs public issue trackers to manage feature requests, allowing both customers and community members to observe and contribute to the product development process. When a customer requests a feature, technical account managers log the request in these trackers with generic customer details, while the specifics remain confidential in a CRM system like Salesforce. Product managers then review and prioritize these requests, using labels and milestones to track progress. Engaging customers in this manner fosters trust and enables direct customer input, which can guide prioritization and development. GitLab encourages community contributions to feature development, aligning with their motto "Everyone Can Contribute," and offers support through Merge Request Coaches. This approach not only helps in tracking and delivering features effectively but also builds empathy and connection between developers and end users, ensuring that customer feedback is seamlessly integrated into the product team's workflow.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.