Measuring & Communicating Team Success
16 April, 2018
As our organization has grown, it's been fairly straightforward to measure how our Sales or Client Services teams were doing by looking at sales numbers, churn indicators and factors, etc. The Product and Engineering organization, however, did not have the luxury of such immediate factors, but we needed an objective way to demonstrate how we were doing to the executive team and CEO.
While not everything in our organization was measurable, if we took the time to use third party tools like SonarQube, data available from AWS, and the like, we found that there was in fact a lot of objective things we could measure. As such, I created a "Monthly Report" to share with both our team and the company's leadership measurable data as well as qualitative content based on reflection from myself and senior members of my team. In each report, we have a brief executive summary, highlights and goals for the month, and then sections focused on capital expenses, performance & uptime, product development & quality (including workload, firefighting, resources, task verification and QA, technical alerts, user-visible regressions, technical debt, and code quality). With each section, we have visual charts and graphs, as well as a small note describing qualitatively what's going on in the graphs and why. This has not only been a great way to communicate how we're doing, but it's been an excellent way for me to force myself to be regularly on top of what is going well (or not well) with the team.
Even if there aren't clearly measurable quantitative metrics to evaluate your team, there usually are good approximation which, when enhanced by a qualitative analysis, can be very illuminating. By keeping a regular cadence of these reports, and reminding yourself (e.g. via a monthly or quarterly calendar reminder), you can work with the leaders on your team to produce these reports in an efficient way that doesn't consume a great deal of their time while still giving you and the leaders of your company the visibility that is needed to maintain trust.
Marc LeBrun, VP of Engineering at Flow Kana and a co-creator of the Apple Mac, delves into the importance of understanding different personality types in the workplace and explains why the traditional Golden Rule -- treat others as you want to be treated -- doesn’t always apply.
VP Engineering at Flow Kana
Marc LeBrun, VP Engineering at Flow Kana, shows the value in establishing a collaborative relationship with a withdrawn but highly-capable employee. We can then use that bridge to draw the person back into the team and elevate everyone’s performance.
VP Engineering at Flow Kana
Kowsheek Mahmood, Principal and CTO at ArchetypeTech, explains how he adapted an ineffective team by determining and implementing team-evaluation processes to better align the team on product delivery.
Principal & CTO at ArchetypeTech
Viacheslav Bessonov, Chief Technology Officer at Algalon Capital, outlines how he improved communication internally - with his fully distributed team, while also improving communication with the customer - located across various time zones.
Chief Technology Officer at Algalon Capital
Alessandro Pintaudi, Product Management Director at Payfit, talks about how teams need to focus more time on building the right things and how to keep doing it with scale.
Product Management Director at PayFit
You're a great engineer.
Become a great engineering leader.
Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.