Back to resources

Thinking Long-Term When Adopting New Technology

Dev Processes
Strategy

21 June, 2021

Kushal Dalal
Kushal Dalal

Director of Engineering at Suzy

Kushal Dalal, Director of Engineering at Suzy, stresses the importance of being well-informed when collaborating with colleagues in a previous period of transition.

Problem

I expect a very high standard of service from the people who work for us. I do what I can to ensure that the goals of each initiative are laid out clearly and that everybody involved is sticking to them. When something comes up, we are able to provide our users with the highest quality experience possible.

I joined my previous company, and one of the things that I saw was that many of the people were very into politics and the status quo instead of the work to be done. After gaining some seniority, I felt comfortable challenging some of the things that I saw. Sometimes, the people I confronted were not able to come up with a satisfactory answer as to why they were behaving in the way that they were.

Actions taken

During one of these times, we were talking about technology and the possibility of upgrading our stack. We came up with our final decisions after some amount of research and deliberation. The front-end engineers, conversely, were not as engaged with the work as we were.

With technology, you always have to be learning as much as you can about new things. It makes you more adaptable as a professional. With this knowledge, you can convince your team with concrete facts that will help you all come to the correct conclusion together. These tendencies are critical when choosing a new tool or adopting a new type of technology into your company.

I took some time to reach out to these teammates, encouraging them to look deeply into all of the facts and the possibilities. I urged them not to just go with what somebody tells them to go with. I emphasized the importance of making decisions that would serve us in the long run, as well. After having this discussion, we were able to work something out that benefited everybody.

Lessons learned

  • When making long-term decisions, you should always be thinking about what the company will be needing two or three years down the line. Trends will come and go. Once you have some data, you can then start to go over those pros and cons.
  • As an engineer, you need to be able to sell the technology and methodology of your preference.
  • Take your time to do your homework and to think about the issues that may make you less confident. Then, you can go and jump into it with some sense of where you would like to go.

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.

Navigating Disagreements When It Comes to Priorities

9 May

Pavel Safarik, Head of Product at ROI Hunter, shares his insights on how to deal with disagreements about prioritization when building a product.

Innovation / Experiment
Product Team
Product
Dev Processes
Conflict Solving
Internal Communication
Collaboration
Convincing
Strategy
Prioritization
Pavel Safarik

Pavel Safarik

Head of Product at ROI Hunter

Leading Your Team in Stressful Situations

27 April

David Kormushoff, Director at Koho, recalls how he galvanized his team to tackle a time-sensitive problem, sharing his tips on how to shift chaos into calm.

Goal Setting
Leadership
Conflict Solving
Deadlines
Collaboration
Motivation
Strategy
Health / Stress / Burn-Out
David Kormushoff

David Kormushoff

Director at Koho

Why You Should Take Technology Risks in Product Development

25 April

Matias Pizarro, CTO and VP of Residents at ComunidadFeliz, recalls a time in his early career when he took a technology risk that had wide-ranging benefits to his product's user experience.

Innovation / Experiment
Product
Scaling Team
Dev Processes
Matias Pizarro

Matias Pizarro

CTO and VP of Residents at ComunidadFeliz

Implementing and Reviewing Roadmaps: Strategies for Transparency and Alignment

20 April

Mike Nuttall, CTO at MyTutor UK, puts emphasis on the importance of creating and reviewing company roadmaps to strategize growth and alignment within an organization.

Alignment
Scaling Team
Company Culture
Diversity
Roadmap
Strategy
Mike Nuttall

Mike Nuttall

CTO at MyTutor

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.