Back to resources

Maintaining Productivity as a Quickly-Scaling Team

Building and Scaling Teams
Team Management

26 April, 2021

Tamara Gevorgyan

Tamara Gevorgyan

Director of Engineering at PicsArt

Tamara Gevorgyan, Director of Engineering at PicsArt, found herself at the helm of a team growing rapidly. Managing them wisely became a matter of having confidence in the systems instated to keep everybody on-task.

Problem‌

 

When first joining my current company, the start-up was very small — only five or six people. Now, we are a team of four hundred, an endeavor that took place over ten years. During this time, we have overcome many challenges in relation to scaling up so quickly. Even after dividing ourselves by platform, we found that the work called for more specialized teams, each devoted to a single feature.  

As we introduced each new department, I would step in as a team-focused tech lead before moving on to build the next group. We now have a Division unit, a features-based unit, and platform-related teams that work to improve the health of the company overall, as well as to optimize developer productivity. All of these groups contain sub-units under their umbrellas.  

During this time, one of my main challenges was maintaining the productivity of our developers and to continue to realize the goals of the company as the organization took on volume.

 

Actions‌ ‌taken‌

 

I led an effort‌ called “Developer Experience”; this is the Division unit mentioned previously. It consists of two sub-teams: one handles performance, the health of the application as it exists for the user, and the other focuses on developer productivity specifically by developing reusable components. While developing each team’s strategy personally was a challenge that I enjoyed, being able to delegate in this way allowed me to manage many people at once.  

After I had been with the the DevXP department for an entire year, we were introducing new features and tools constantly. Each new team had a dedicated EM, and each department now had its own engineering manager tasked with creating processes and best practices for the work of their teams specifically. I had never led such a huge organization before, but finally felt that I was able to match our pace of growth comfortably.

 

Lessons‌ ‌learned‌

‌ 

  • You should never wait for somebody to teach you something or to show you the way. You need to research the challenge and to learn on your own. I learned to act and to avoid waiting. This gives life to all of my ideas.
  • Do not shy away from any process that may solve the problem that you are facing, even if new and unfamiliar.
  • Do not fear failure in your career. Every misstep teaches us something important. As long as we do not repeat our mistakes, there is no reason to avoid ambitions that scare us.

Discover Plato

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


Related stories

Creating and fostering a safe environment

9 May

A safe environment is where developers are empowered to learn from experiments encourages developers to take calculated risks, learn from their failures, and continuously improve their skills.

Building and Scaling Teams
Nimrod Vered

Nimrod Vered

Chief Technology Officer at Uplevel

Beware the Empathy Trap

21 March

Is it possible to be too empathetic? If you overdo it, it can be an energy sucker.

Leadership
Conflict Resolution
Team Management
Managing Stress and Burnout
Melanie Zens

Melanie Zens

Delivery & Operations / Digital Transformation / Innovation at Marais Consulting Inc

Relationships, like products, need to be designed.

7 March

3 ways leaders can cultivate relationships that lead to better products.

Leadership
Building and Scaling Teams
Career Growth
Team Management
Strategy and Vision
Guy Jenkins

Guy Jenkins

SVP Global Customer Experience at Salesforce

Inspiring Engineers with your Company's Vision

25 March

Oftentimes Engineers work in silos, developing products to specified requirements, while they remain disconnected from the most important of questions - "WHY are we building this?" We'll explore the consequences of this mindset, as well as how to connect your Engineers to the larger Company Vision.

Leadership
Communication and Collaboration
Team Management
Strategy and Vision
Eric Adams

Eric Adams

VP of Engineering at ExecThread

Providing Clarity to team

5 February

Giving confusing direction to team is perilous. But giving clarity is so very important.

Building and Scaling Teams
Kamal Raj Guptha R

Kamal Raj Guptha R

Engineering Manager at Jeavio