Back to resources

How to Transition Your Employee Into a Better Role

Coaching / Training / Mentorship
Career Path
Performance

26 November, 2020

Kevin Perko
Kevin Perko

Head of Applied Research / Data Science at Scribd

Kevin Perko, Head of Applied Research and Data Science at Scribd, discusses how he made his employee successful by helping them transition into a more suitable and challenging role.

Problem

I recently hired an employee who I felt was promising, but who struggled immensely and had a hard time adjusting for a number of months. I was determined, nevertheless, to get them to become a successful and high-performing employee that I believed they could be. After I changed the type of work they were doing and expanded the challenges, they suddenly started to blossom.

Actions taken

I initially tried to provide additional one-on-one coaching which didn’t bring the desired results in terms of unlocking their potential and improving the performance. Then I decided to put them on different tasks and track their progression.

First I tried to put them on more business-oriented tasks that included intensive communication with business stakeholders. However, they were not making any significant progress and I later realized they lacked the specific business context that would enable them to communicate smoothly with business stakeholders. This particular task required mastering nuances captured in business communication that they weren’t familiar with. My first experiment obviously failed and created frustrations on both sides. At that moment, I thought I was stuck.

Then, I tried having them work on some smaller, well-defined projects and I was glad to notice that they were doing decently. I wanted to step up the difficulty level and introduce some harder projects. Yet, I was cautious because when I tried doing that with business-related tasks that had put us back.

Finally, I decided to assign them a much harder machine learning-focused task. It was a huge leap in complexity and open-ended ambiguity. To my surprise, they were ready to handle it with minimal guidelines. The more arduous challenge helped motivate them and unlock their full potential.

At that time another person was working on a machine learning recommendations model that was taking too long and didn’t bring satisfactory results. I asked my promising employee to go through the code and they managed to break it down and optimized it in a very short time. Nothing made sense to me because it was not a gradual progression of complexity but a huge leap forward, entirely non-linear. This person excelled at ambiguous, ill-defined projects, working on the deeper technical, ML projects that included deeper programming. Once given more onerous challenges they began to shine.

After my experience with this particular person, I had to reevaluate my approach. I would still start with smaller tasks but I wouldn’t hesitate to move them to more complex tasks even if they struggled with smaller tasks. To put it simply, it seems that the two are not correlated.

I would have them work on multiple projects before drawing any consistent signals or conclusions. I would need at least three projects to understand where my employees are in terms of their abilities and performance. One project is almost never enough to make any final assessment because there are too many external variables that could confound the signal. However, the length of the project assigned matters greatly; three days would certainly give you less signal than three months.

If there is something that gives them a hard time, I should uncover that and precisely define it. Is it the technical or communication part or is it about the deliverables or timeliness -- I would try to extract that out and work with them to identify knowledge/skill gaps.

Lessons learned

  • Separate different areas of performance when you are onboarding someone. Establish with the greatest detail how they are performing in all of those different areas -- are they performing well in terms of communicating with stakeholders or doing the work on time.
  • Add gradually a more specific type of work. Learn about their background and what they have done in the past and expose them to different types of tasks and levels of complexities.

Discover Plato

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


Related stories

Assessing the Performance of Your Team

20 August

Parallels between Work and Sport.

Goal Setting
Different Skillsets
Coaching / Training / Mentorship
Performance
Ron Pragides

Ron Pragides

SVP Engineering at Trustly Group AB

Leaving Room to Say Things Suck — Leadership Lessons from “Ted Lasso”

17 August

A major sign of trust, comfortability, and vulnerability is for someone you lead to be able to say something sucks.

Building A Team
Company Culture
Leadership
Coaching / Training / Mentorship
John Hartley

John Hartley

Senior Engineering Manager at Curology

How to Enter QA With a Non-Technical Degree

2 August

Lewis Prescott, QA Lead at Cera Care, explains his journey from a degree in psychology to learning test automation and computer programming.

Handling Promotion
Personal Growth
Coaching / Training / Mentorship
Career Path
Lewis Prescott

Lewis Prescott

QA Lead at CeraCare

How Product Management Chose Me

23 June

My accidental journey into product management

Product
Personal Growth
New PM
Career Path
Michael Castro

Michael Castro

Sr. Manager, Product Management at Capital One

How to Help Employees Find Their Strengths and Passions

22 June

Łukasz Biedrycki, VP of Engineering at BlockFi, talks about the importance of building on your strengths and finding your passions to maximize your impact. He dives into the tactics that managers can use to support their teammates in this pursuit.

Different Skillsets
Personal Growth
Leadership
Motivation
Career Path
Performance
Łukasz Biedrycki

Łukasz Biedrycki

Head of Engineering at Spectral Finance