Back to resources

An Egalitarian Approach to a Disportionate Workload

Ownership
Ethics
Team Processes

16 November, 2020

Nimrod Perez
Nimrod Perez

VP of Engineering at Wobi LTD.

Nimrod Perez, CTO and VP of Engineering at Wobi LTD., explains how he solved a long-troubling problem of disproportionate workload by his simple and egalitarian approach.

Problem

Earlier in my career, I was tasked with managing a sizable team of ten developers or so -- a fairly large team with only two senior engineers. Since they had been the most knowledgeable about our software solution, all the tasks by the support team were assigned to them. The constant interruptions by Support impacted their performance. Needless to say, they found it annoying and were in general, not pleased with how the situation was dealt with.

Actions taken

One of my core beliefs, which is translated into how I organize the teams, is my profound commitment to equality. Therefore, I have compiled the list of all developers on the team and decided to create a rotation system based on this belief. Every week two developers would be assigned to help the support team.

However, this approach couldn’t yield results immediately. Support would often approach junior engineers who wouldn’t know the answer and would have to ask more experienced developers to help them. The interaction between junior and senior people on the team enhanced the competencies of juniors, and the knowledge was gradually spreading across the team. Not everyone was on the same level yet, but it helped nivellate the knowledge. Senior engineers could finally take some load off their shoulders and instantly felt relief. At the same time, junior engineers accepted their responsibilities relating to the rotation system because they understood that as a team they had to share the load.

As a big believer in equality, my approach was to ensure and repeatedly emphasize that there was no one who was above anyone else and when people see that implemented in practice they would always support it. They would intuitively understand that the system I introduced was fair and the right thing to do even when it meant more load for some people. Being driven by this belief I had never encountered any turbulence within the team.

Lessons learned

  • Simple solutions work best. This was one more example to prove the rule. If you are in doubt about what to do, go with a choice that is more simple.
  • When you introduce changes that are equally affecting everyone and are fair in its essence, hardly anyone will complain. When everyone gets to do everything and share the same amount of load, people won’t object even if that means working more. On the most fundamental level, people won’t object to things that are fair.
  • In addition, this approach helped build camaraderie because it emphasized the sharing aspect of the solution and encouraged more intensive collaboration between senior and junior engineers.

Discover Plato

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


Related stories

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.

The Optimization and Organization of Large Scale Demand

4 May

Kamal Qadri, Senior Manager at FICO, drives the importance of setting expectations when optimizing large-scale requirements.

Managing Expectations
Delegate
Team Processes
Prioritization
Kamal Qadri

Kamal Qadri

Head of Software Quality Assurance at FICO

Why Documentation Is the Key to Success

6 April

Henning Muszynski, Head of Frontend at Doist, promotes his ideas on how documentation ensures consistency, efficiency, and standardization.

Alignment
Collaboration
Productivity
Hiring
Team Processes
Henning Muszynski

Henning Muszynski

Head of Frontend at Doist

It's Time to Say 'No' to Manual Business Processes

6 April

Henning Muszynski, Head of Frontend at Doist, talks about the cost of slow and arduous processes that add up over time and how to bring the changes systematically.

Changing A Company
Conflict Solving
Internal Communication
Feedback
Team Processes
Henning Muszynski

Henning Muszynski

Head of Frontend at Doist

Typical Challenge of Scaling Teams: What to Do When Your Process Doesn’t Scale

30 March

Christophe Broult, Director of Test Engineering at diconium, focuses on how he scaled his team while building organization and management teams in place.

Scaling Team
Building A Team
Reorganization
Team Processes
Christophe Broult

Christophe Broult

Director Test Engineering at diconium

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.