Back to resources

How to Make Evaluations a Level Playing Field

Managing Expectations
Product
Handling Promotion
Feelings Aside
Diversity
Coaching / Training / Mentorship
Career Path

9 April, 2018

Jack Danger
Jack Danger

VP of Engineering at Pathstream

Jack Danger talks about how he made his process for evaluating team members less subjective and more objective in order to ensure that all of his team were treated fairly.

Problem

When I was working at a small startup we hired someone as a full-time developer. She had been at companies in the past where she was consistently overlooked for promotion. Because of this, she asked me straight away about how I would be fair in making sure that she would get ahead at the same rate as everyone else. She said she didn't want any special favors, she just wanted the exact same treatment as everyone else. The problem was, I didn't know how to prove to her or to myself that I was evaluating her and the rest of her teammates in exactly the same way.

Actions taken

After talking to various members of the team, I realized that they all wanted the same thing - they all wanted the system of evaluation to be something they could read, something they could decide on together, and something they could objectively measure independently. Basically, they wanted to know that my gut instincts and subjective opinions had no say at all in the evaluation of their performance. I wanted that too. I reserved the right to have my gut tell me what type of work we should be focusing on as a team and how to best encourage people. But as far as promotions, compensation, and evaluation, we used a very structured system. We started using the Radford levels of IC contributions. They use a rope-making analogy - level one can make basic knots with help, and level six invented nylon. Engineers are somewhere along that scale. We used this to come up with ways to describe breadth of influence. We then talked about what specific behaviors and influences a person will have at different levels, and how we were going to distribute work and how projects would be selected. Through this process, we realized we had a real bias in our system, where anybody who was confident got to do all the best work, as they would just start doing it. We moved away from this, so that if we identified any work that needed to be done, we would post about it in our public Slack channel and would then talk about who would be best at it. The woman who had originally asked for assurance of fairness never actually changed in terms of level. However, she was happy as she could see clearly that the systems we had put in place were fair.

Lessons learned

One of the most practical steps I took to make my team safe for a person who was a minority was to give her the rubric for how she would be evaluated, and to ensure it was clear and fair and that she bought into it. It's really hard work to make your gut instinct about how someone is doing objectively measurable but it's worth it. Ultimately, it cut down on my workload, as team members didn't come to me anymore wondering if they would get promoted, because the system we had in place made it very clear what they needed to do to be promoted.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

10x engineer or 10x impact?

26 May

Hiring 10x engineers is hard for most companies. It’s a tough battle out there for talent. So how should most companies approach building their team?

Building A Team
Leadership
Hiring
Coaching / Training / Mentorship
Vaidik Kapoor

Vaidik Kapoor

VP Engineering - DevOps & Security at Grofers

The Art of Asking Why: Narrowing the Gap Between Customers and Users

24 May

Jord Sips, Senior Product Manager at Mews, shares his expertise on a common challenge for product managers – finding root causes and solutions.

Customers
Innovation / Experiment
Product
Personal Growth
Leadership
Stakeholders
Users
Jord Sips

Jord Sips

Senior Product Manager at Mews

Streamlining Product Processes After a Reorganization

16 May

Snehal Shaha, Lead Technical Program Manager at Momentive (fka SurveyMonkey), details her short-term technical strategy to unify processes among teams following an acquisition.

Acquisition / Integration
Product Team
Product
Building A Team
Leadership
Internal Communication
Collaboration
Reorganization
Strategy
Team Processes
Cross-Functional Collaboration
Snehal Shaha

Snehal Shaha

Senior EPM/TPM at Apple Inc.

Managing Culturally Diverse Remote Teams

11 May

Tom Hill, Engineering Manager at Globality, Inc., shares how he works with a culturally diverse team based within a thirteen-hour time gap.

Scaling Team
Handling Promotion
Remote
Onboarding
Hiring
Cultural Differences
Tom Hill

Tom Hill

Engineering Manager at Torii

Navigating Disagreements When It Comes to Priorities

9 May

Pavel Safarik, Head of Product at ROI Hunter, shares his insights on how to deal with disagreements about prioritization when building a product.

Innovation / Experiment
Product Team
Product
Dev Processes
Conflict Solving
Internal Communication
Collaboration
Convincing
Strategy
Prioritization
Pavel Safarik

Pavel Safarik

Head of Product at ROI Hunter

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.