Plato

Login to Plato


This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Don't have an account? 

Strategic Thinking for Engineers

Leadership
Impact
Strategy

6 April, 2021

Shraddha Ladda, Tech Lead, emphasizes the importance of strategic thinking for engineers and how zooming out of one’s role and taking a holistic look on things is critical.

Problem

Not too long ago, I was in a situation where my team was suffering from somewhat of an “organizational drag.” The team velocity was low. We seemed to be doing the more tactical or band-aiding type of work to just stop the leak. Focus on delivering the business value constantly without addressing the root cause kept adding to the technical and organizational debt. Often as ICs, we focus on the technical aspect of things and try to improve them. But in this particular situation, I felt the need to come out of my comfort zone and also get the team thinking about the larger problems.
 

Actions taken

I started by asking the existential questions of Five Whys, “Why does this team exist”, followed by “What do we do”, and “How do we do it”. I decided to take a stab at answering these questions for my team from my perspective.
Our main bottleneck seemed to be stemming from a dependency on the external (platform-like) team, which had competing priorities and an extreme lack of engineering resourcing. That was causing an impedance that mismatch with our needs. Our way to address this was to build things on our own if they couldn’t, even though we knew that it was incurring tech debt.
 

There were a lot of efforts made at the leadership level to align the two teams, but the top-down approach was yielding little results. I pointed out the inefficiencies and bottlenecks I had observed in the last six months, supporting those with lots of examples. I also demonstrated in many cases how Conway’s law
(https://www.thoughtworks.com/insights/blog/applying-conways-law-improve-your-software-development) was breaking down in this particular situation.
 

Decidedly, I didn’t just want to be pointing out problems. I also laid down potential solutions, both tactical -- what we could achieve in the next couple of quarters. One of the ideas I proposed was, in lieu of adding tech debt and building solutions in our service, to contribute directly to the dependent team’s code base as they were open to contributions due to resourcing crunch. Since we were spending efforts anyway, contributing to the source of truth meant less throwaway work and also alleviating some burden from the dependent team.
 

On a strategic level, it was crucial to identify how the two teams would operate most effectively in the long term. Laying down our contract and getting buy-in from engineering orgs, stakeholders and partners were critical. We needed to get out of our “MVP first” mindset and look at the bigger picture to align organizational goals better. Having support for our features built into the platform would bring us on the paved path for engineering development. In partnership with the other team, I laid out plans on how to build foundational elements in the platform team and transition the ownership to them in a phased manner.
 

Finally, I circulated my two-pager that contained all these ideas among my peers and leaderships of both teams. The idea was well-received. I was also given the opportunity to lead this initiative. This was a win-win situation for all involved and gave me a strong sense of purpose and motivation which was very rewarding.
 

Lessons learned

  • Sometimes it is essential to zoom out of our IC roles and take an honest and holistic look at how things are working and, more importantly, not working and coming up with a game plan.
  • Too often, engineers are entangled in technical problems, including tech debt, missing on the opportunity to become more involved in organizational challenges. With their boots on the ground, many times they are better positioned to spot the bleeding and stop it.

Discover Plato

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


Related stories

Acting Quickly To Resolve an Incident
9 April

Leo Torres, Engineering Manager at Carta, speaks of his prompt response to a recent incident and how acting quickly allowed him to make a customer happy.

Leadership
Collaboration
Team processes
Leo Torres

Leo Torres

Engineering Manager at Carta

Strategic Thinking for Engineers
6 April

Shraddha Ladda, Tech Lead, emphasizes the importance of strategic thinking for engineers and how zooming out of one’s role and taking a holistic look on things is critical.

Leadership
Impact
Strategy
Shraddha Ladda

Shraddha Ladda

Senior Engineer / Tech Lead at Netflix

Using Snippets to Track Performance and Growth
2 April

Irina Stanescu, ex-Tech Lead at Google and Uber, tells how she uses “snippets” to track her performance and gain visibility on her work.

Handling Promotion
Personal growth
Impact
Irina Stanescu

Irina Stanescu

Tech Lead at Ex-Google Ex-Uber

How to Establish Yourself as a Leader
2 April

Irina Stanescu, ex-Tech Lead at Google and Uber, shares how she established herself as a leader without clinging to a title or long waiting for promotion.

Leadership
Career Path
Personal growth
Irina Stanescu

Irina Stanescu

Tech Lead at Ex-Google Ex-Uber

Leading Post-Acquisition
26 March

Ian Logan, VP of Engineering at Rose Rocket, shares what it takes to make a successful acquisition of engineering organizations.

Leadership
Changing company
Team processes
Ian Logan

Ian Logan

VP Engineering at Rose Rocket

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.