Plato Elevate Winter Summit has been announced (Dec 7th-8th)


Back to resources

Building an Exponential High-Performing Team

Building A Team

2 August, 2020

Peter Fedoročko

Peter Fedoročko

Director of Engineering at Workday

Peter Fedorocko, Director of Engineering at Workday, explains how to build a technically robust team with limited resources -- an exponential high-performing team.


At the startup stage, we were constrained with limited resources and inadequate HR capabilities. However, our every hire had to be a perfect match capable of generating added value to the team. What I’ve noticed before was that most managers tend to hire people who resemble them -- they will look for potential candidates at their previous company or look for an ideal type of candidate -- and will often prioritize this over the skills or data. I found this approach to be narrow-minded and biased. What I tried to do was to build -- what I named -- an exponential team where each new person adds a different skill set and expertise, so they can exponentially contribute to the team.

Actions taken

I set up a hiring process guided by this principle and hiring people with different skill sets, backgrounds, knowledge, vision, and preferences. By doing so, every new person who would join our team would challenge our preexisting understanding of things, approaches, technology, organizational structure, etc. For example, if there were three Python developers adding one more would only result in the job being done faster, but if you add a Java developer that could shift the perspective of how things are done. Therefore, instead of a narrow focus, I would rather have a team with broad competencies that would enable me to try new technologies, modify processes quickly, and choose from a variety of perspectives.

One of the biggest challenges of this approach was that there was no duplicity which was a risk in itself. If a person was on sick leave or even a holiday, a gap would appear. The solution is to think about duplicating the roles as soon as you have reached a certain number of people. While it is good to have five diverse people, it is probably not a good idea to have 50 diverse people. At that point, the dissonance of their opinions could result in chaos, but at a very early stage, I would always advocate for the first 5-10 people on the team to be diverse.

Also, it would be very hard for an EM to deal with all those diverse people since it would be always much easier to manage people with the same skills, experience, and vision. However, people with different skills and backgrounds would also bring in different opinions and perspectives, and managing them would require more investment on an EM part, but the value the diversity could bring would make the investment worthwhile.

The way I would approach creating a diverse group would start with seniority and background. I would mix up senior people who were experienced but reluctant to learn and explore new things with juniors who were more enthusiastic but lacked the experience. Also, I would mix up people with a corporate background (who would replicate the rigidity of corporate procedures) with the startup people who would be all about trying new things but not much committed to keeping track and relying on metrics. I found the technology, exposure to the process and cultural competencies to be very important for creating a diverse team -- for example, local vs. global experience or a nice blend of extroverts and introverts.

Lessons learned

  • When constrained with limited resources never go with like-minded people (though that seems to be a prevalent approach) but look for diversity that can generate more added value.
  • Don’t make clones from your employees. Respect their differences and understand how they can contribute to the overall enhancement of the team.

Discover Plato

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

Related stories

Delegate successfully as a first time manager of Product Managers

24 November

Andrew Tsui, a Product Leader, works to build great teams that are independent, demonstrate mastery of their domain, and fully commit to their purpose.

Scaling Team
Building A Team
Coaching / Training / Mentorship
Psychological Safety
Cross-Functional Collaboration
New Manager
Andrew Tsui

Andrew Tsui

Director of Product at Startup

Managing New Team Members

6 October

Harsha Shekar, Engineering Manager at Atlassian Corporation Plc, explains how he brought up and eased new members into his team, while navigating through multiple challenges.

Building A Team
Harsha Shekar

Harsha Shekar

Engineering Manager at Atlassian

Building an Organization From the Ground Up

19 September

Arpan Dalal, Sr. Director Engineering at RepairPal, speaks of his effort to build an organization from the ground up in a brand new domain of the mom-and-pop gardening space.

Building A Team
Arpan Dalal

Arpan Dalal

Sr. Director Engineering at RepairPal

Scaling Teams to Make Better Decentralised Decisions via Documents and Tenets

6 September

Kirsten Zverina, Head of Product at Abethos Ventures, shares some decision-making mechanisms like FAQs and tenets, that can help reduce the pain of scaling teams.

Product Team
Scaling Team
Building A Team
Team Processes
Kirsten Zverina

Kirsten Zverina

Head of Product at Abethos ventures

Getting Ready for a Cold Start

25 August

Alex Oleinikov, Software Engineering Manager at, shares how he started a team from scratch and what he had to put in place before the first hires began to arrive.

Mission / Vision / Charter
Building A Team
Alex Oleinikov

Alex Oleinikov

Software Engineering Manager at

You're a great engineer.
Become a great engineering leader.

Plato ( 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.