Back to resources

How to Meet Strict Deadlines In An Environment of Uncertainty

Deadlines
Ownership
New Manager

8 September, 2021

Alfredo Fernandez Acuna
Alfredo Fernandez Acuna

Engineering Manager at ComplyAdvantage

Alfredo Fernandez Acuna, Engineering Manager, explains how he led his team to turn a proof-of-concept into a minimum viable product and to deliver it in Production within 6 weeks.

Problem

A research team had built a quick proof-of-concept application, and it was my job as a new EM to take ownership of this application, to form a new team to turn it into a Product, and to deliver it in Production for our clients within 6 weeks. None of the engineers who were part of that original research team would be part of my team, and therefore nobody in my team including myself knew much about what the application did nor how it was built. We had access to the source code and limited documentation about it. What are the odds that we would successfully productise the prototype and deploy it in Production within 6 weeks?

Actions taken

We started by taking ownership of the prototype. This meant getting to know what it does functionally and what problems it solves for our clients. Secondly, we investigated what are its different modules, how they interact with each other, and created technical documents. Lastly, we assessed its production readiness, so we examined it from the Quality perspective as well as its non-functional requirements (i.e. Security, Performance, and Observability).

In the Production Readiness assessment, we managed to identify all the gaps that prevented the prototype from being a product. With this list, we were able to categorise them as either mandatory for ‘go live’ or otherwise. We then performed high-level estimates for all the items in the mandatory list, which led us to conclude we couldn’t reach our deadline. With this in mind, we re-assessed the list, and through close collaboration with the Product and our Security teams we realised there were further reasonable compromises we could make. Thus, some of the items in the mandatory list were moved to a new category for items we thought were mandatory immediately after ’go live'.

Within the list of mandatory items, we had a lot of work to do in terms of Observability. We had to ensure we had all the monitoring and logging systems in place. Also, we prepared ourselves for any incidents and created a troubleshooting document on what to do if we did get any incidents. Importantly, we also prepared operating procedures for our first-level support teams to follow in case of incidents. This gave them the means to troubleshoot the easiest problems by themselves and enabled them to route to our engineers the problems that needed further investigation, with the right level of detail and the right priority.

Lessons learned

  • Working closely with Product and other stakeholders is essential, especially when you need to make tough compromises. They will be on your side if you are transparent about the constraints you are facing.
  • Put the uncertainty on paper. Assess and list in written form what it is that you don’t know, and then start a discussion about how to turn the unknowns around. Do this together with your team and your stakeholders.
  • Challenge what might seem obvious at first. If a backlog item is mandatory, ask yourself again, is it really mandatory? If so, why? What is the impact if the item does not get done? Can it be done later?

Discover Plato

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


Related stories

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

The Challenges of Becoming a New Manager Among Old Peers

22 April

Neha Saha, Manager, Software Development Engineering at Workday, illustrates the challenges of obtaining a position in management with no prior experience and the confidence it takes in order to succeed.

Leadership
New Manager
Neha Saha

Neha Saha

Manager, Software Development Engineering at Workday

The Necessary Structures of Time Management

14 April

Suryakant Mutnal, Engineering Manager at PayPal, discusses the importance of time management and the necessary structures in order to create internal consistency.

Goal Setting
Managing Expectations
Remote
Deadlines
Productivity
Roadmap
Prioritization
Performance
Suryakant Mutnal

Suryakant Mutnal

Engineering manager at PayPal

Navigating Your Role Change: From IC to Engineering Manager

13 April

Anuj Vatsa, Engineering Manager at Carta, describes his journey of becoming an Engineering Manager and shares some tips for easing into this new role.

Managing Expectations
Handling Promotion
Personal Growth
Leadership
Feedback
Career Path
New Manager
Anuj Vatsa

Anuj Vatsa

Engineering Manager at Carta

Landing a Management Position without Recent Experience

4 April

Kate Semizhon, Engineering Manager at Square, shares her experience finding a role as an engineering manager without any recent experience.

Handling Promotion
Personal Growth
Hiring
Coaching / Training / Mentorship
New Manager
Kate Semizhon

Kate Semizhon

Engineering Manager at Cash App

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.