How LinkedIn turned to real-time feedback for developer tooling

Or Michael Berlowitz
9 min readbeginner
--
View Original

Overview

The article discusses how LinkedIn implemented a Real-Time Feedback system to enhance developer tooling and improve productivity. By transitioning from traditional surveys to real-time feedback mechanisms, LinkedIn doubled participation rates and gained more actionable insights into developer experiences.

What You'll Learn

1

How to implement a real-time feedback system for developer tools

2

Why capturing contextual information is essential for actionable feedback

3

How to increase survey participation rates among developers

Key Questions Answered

How did LinkedIn improve developer feedback participation rates?
LinkedIn improved developer feedback participation rates by transitioning from quarterly surveys to a Real-Time Feedback system, which doubled participation from approximately 15% to over 30%. This approach allowed developers to provide feedback immediately after their experiences, making it more relevant and timely.
What challenges did LinkedIn face with traditional surveys?
LinkedIn faced several challenges with traditional surveys, including developers providing feedback on tools they hadn't used recently, lack of context for feedback, and difficulty in measuring changes between surveys. These issues made it hard to gather actionable insights about developer experiences.
What is the Real-Time Feedback system?
The Real-Time Feedback system collects information about developers' actions across LinkedIn's tooling ecosystem and solicits feedback contextually, allowing developers to provide input immediately after relevant experiences. This integration into daily workflows enhances the quality and relevance of feedback.

Key Statistics & Figures

Survey participation rate
over 30%
This was an increase from approximately 15% with traditional surveys.
Feedback participation doubling
doubled
This was achieved by transitioning to the Real-Time Feedback methodology.

Technologies & Tools

Some links below are affiliate links. We may earn a commission if you make a purchase.

Analytics
Matomo
Used for logging developers' actions via internal web UIs.
Messaging
Apache Kafka
Utilized for internal logging and auditing mechanisms.

Key Actionable Insights

1
Implementing a Real-Time Feedback system can significantly enhance the quality of feedback collected from developers.
This system allows developers to provide feedback immediately after their experiences, which leads to more relevant and actionable insights compared to traditional survey methods.
2
Capturing contextual information when soliciting feedback is crucial for understanding developer experiences.
By knowing what specific actions developers were engaged in when providing feedback, tool owners can better address pain points and improve the overall tooling experience.
3
Increasing participation rates in feedback surveys requires thoughtful solicitation strategies.
LinkedIn's approach of allowing developers to choose their feedback channels and frequency helped double participation rates, demonstrating the importance of user preferences in feedback collection.

Common Pitfalls

1
Relying solely on periodic surveys can lead to outdated feedback and misinterpretation of developer needs.
Developers may provide feedback on tools they haven't used recently, making it difficult to gather relevant insights. Transitioning to real-time feedback helps mitigate this issue.

Related Concepts

Developer Experience
Feedback Mechanisms
Tooling Improvement Strategies