Increase in feedback from senior developers within 1 month
Increase in feedback received by more junior team members within 1 month
The engineering team at Applied comes from a huge range of backgrounds, which means that their team brings lots of different perspectives to solution design. Hew Ingram, Head of Engineering at Applied, wanted to make sure that everyone was receiving and engaging in feedback in code reviews, since knowledge-sharing in a diverse team lends itself to high-quality code and great development opportunities for the whole team. Together with Mel Schatynski, one of Applied’s senior developers, they used the Multitudes data to understand the feedback patterns on the team, set a goal, and, ultimately, increase the amount of feedback being shared.
Mel is a very experienced developer who works part-time at Applied. Given the way that their engineering team works, everyone gets pulled into larger projects – which means they’re often working through some significant coding questions. At the same time, the team values getting her input in code reviews – so she had a lot of demands on her time, and not many hours to do it all!
When Mel and Hew sat down to go through the Multitudes data together, they saw that Mel had fewer PR Comments Written than others on the team – she was writing less feedback on code reviews than others. That trend had been consistent over several months, and it held true even when they accounted for the part-time nature of her role.
We know that sharing knowledge is important for the success and development of others on the team, and it helps improve code quality – so the conversation turned to what Mel wanted to set as next steps.
Mel decided that she would like to increase the amount of feedback that she gave to others on the team. As part of her regular goal-setting practice with Hew, she set a goal to participate more in code reviews.
Because Mel had access to her own data, she was able to check in on her progress each week, and make shifts as needed.
“Multitudes gave me a better feedback loop on my role in the team – over just a couple weeks, I doubled the number of reviews I did for my peers.”
— Mel Schatynski, Applied, Senior Engineer
Mel made steady week-over-week improvement in the amount of feedback she gave: Just three weeks after they set the goal, Mel had achieved a 12x increase in the feedback she gave. In fact, she became the person giving the most feedback out of anyone in the team!
As one would imagine, this increase in feedback meant that the team’s more junior developers started to get more feedback on their work – they saw an 160% increase in feedback received over this period. Mel was mindful of giving feedback to people across the team, so this increase in feedback benefitted all the team members.
As Hew said, “Multitudes showed us how we were doing with code reviews, and made it super easy for us to see the improvement over time”.
Goal-setting based on Multitudes’ data has been hugely successful for Applied. Next, Hew could try using the Multitudes 1-on-1 guides during his 1-on-1 chats across the team to help identify things like who’s missing out on feedback, or who’s at risk of burnout. The Multitudes guides include questions to help surface more of the human context around the numbers.
Another aspect of feedback that matters is the quality – so the Applied team could dive into a new metric coming soon from Multitudes about <code-text>Specific Feedback<code-text> (which shows how often people get feedback that’s specific and, therefore, is better for development).