Structuring Using Tools, Measurements, and a Spreadsheet of Expectations
10 April, 2019
The company that I am currently working for grew very quickly. We went from 150 employees to 600 in a short time and so we did not have in place a solid structure. About a year and a half ago, though, there became a need for a better structure, better guidelines, and better ways to measure our team members.
It was a complete team effort to standardize the structure. I contributed specific pieces but I certainly cannot take credit for the whole thing. We began by implementing more tools to get more metrics. For example, we measure technical debt, the amount of time it takes developers to code, the quality and efficiency of the code, etc. By having these tools and concrete metrics, we now had a solid way to track our engineers performance.
Based off of those measurements we created a spreadsheet that included the expectations for each of the various levels of engineering. We wrote out, level by level, what we were looking for if you were in the junior, middle, or senior level categories. We listed out soft skills, technical skills, communication, and strategy. Now, it was clear what we were asking for and what steps to take in order to move on to the next level. Additionally, we can see the health of our engineers in terms of efficiency, activity, how much technical debt they have introduced, how many tickets they've worked on, and the average estimate for those tickets. All of these tools and processes fit together to give structure and confidence in articulating where the engineer stands, the directions they can go, and areas that need improvement.
All of this was part of Phase I. Our next phase, Phase II, will have more to do with items that are not measurable using tools but aspects that our company definitely puts emphasis on. These aspects include collaboration, communication, attitude, and reliability.
- First of all, you need some kind of structure. It's impossible to simply say that you think an engineer is doing great. This is a non-effective subjective view. Thus, you need some way of measuring so that there is congruence throughout your organization.
- Next, be careful of how and when you rollout your new structure. It takes time to put these new frameworks in place and to be sure that they are running properly. You can't just roll it out and set it in stone. You need first to get feedback, do a couple of test runs, and then open it up company-wide. Even then it may not be perfect. In fact a testament to this is that we currently are still modifying and tweaking our structure.
- Lastly, the numbers that we measure are used to tell a story. There are no right or wrong numbers but they do give a narrative to telling the truth. For example, if I see my top engineer go from 80% efficiency to 40% efficiency during a release, then I can ask what happened. What did they work on? And really get down to the root cause of the fluctuation in numbers. The numbers provide background and present dialogue to a story. It's very useful for us to know those stories and use them to adjust so that we can do better overall. Better not just for the individual engineers, but also for planning and testing as well. It gives us a 360 degree view.
Himanshu Gahlot, Director of Engineering at Lambda School, shares how he used his own learnings to support his direct reports and help them grow in their careers.
Director of Engineering at Lambda School
Pete Murray, Principal Software Engineer at Electronic Arts, explains how he successfully solved a long-troubling problem by applying a root cause analysis.
Principal Software Engineer at Electronic Arts
Michael Mac-Vicar, CTO at Wildlife Studios, dissects how to set guardrails that would contain the exponential increase in cloud costs.
CTO at Wildlife Studios
Mason Mclead, CTO at Software.com, explains how a primary job of an engineering leader changes as a company grows and how he felt that merely managing people is not the role that fits his aspirations.
CTO at Software.com
Marian Kamenistak, VP of Engineering at Mews, explains why EMs shouldn’t be measuring the output of a team or individual engineers, but the outcome of the whole team.
VP of Engineering at Mews
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.