Letters to Myself: My First 90 Days as Tech Lead

Dear Abigail on Day 1,
You are sitting in the Bristol office cafeteria, clutching a coffee cup and secretly panicking. Today you inherit the telemetry pipeline codebase, and you are convinced that Scott, the quiet principal architect, will dismiss every modernization initiative you propose. You spent yesterday afternoon mapping out defensive arguments because his defensive demeanor made you assume he would shoot down suggestions immediately. Meanwhile, you expect Kyle, the outgoing product manager who greeted you warmly at reception, to be your closest ally. You plan to hit the ground running by overhauling the flaky deployment script on Friday morning to prove competence. Calm down. You are about to misread every social signal in this building.

Dear Abigail on Day 30,
The honeymoon period evaporated rapidly. You made the rookie mistake of touching the deployment pipeline without running a proper listening tour first. That broken build locked twenty engineers out of staging for six hours, and you nearly created an accidental blame culture before lunch. Fortunately, Scott did not hold a grudge. Instead of lecturing you, he quietly sat beside your desk, gave you a gentle heads-up regarding unwritten server dependencies, and enabled you to course-correct before senior stakeholders noticed. What you mistook for hostility on day one was simply fatigue from previous managers who had ignored architectural debt. Meanwhile, Kyle, your supposed ally, keeps attempting to bypass backlog refinement whenever clients request half-baked features.

Dear Abigail on Day 90,
It is high time to take stock of what actually worked. You finally learned to prioritize ruthlessly instead of trying to please every vocal department. By hosting structured check-in points and a skip-level meeting every alternate sprint, you encouraged teammates to air grievances safely rather than bottle up frustration until sprint reviews. Those quick wins on pipeline stability gave your broader architecture proposal enough momentum to gain traction across leadership. Scott has become your strongest partner because you allowed him space to solve deep performance bottlenecks, whereas Kyle eventually transferred to marketing after discovering your team will no longer absorb unplanned scope without documentation.

In hindsight, leadership is rarely about entering with brilliant technical answers. It is about setting an empathetic tone, noticing the early warning sign of burnout before delivery stalls, and letting experienced engineers do their best work without micromanagement.

Read again and choose the right answer

What did Abigail mistakenly assume about Scott on her very first day?

• She assumed he would reject and dismiss her modernization ideas.
• She thought he lacked deep technical knowledge of the infrastructure.
• She expected him to advocate aggressively for immediate refactoring.

Why did Abigail's deployment script update cause trouble during her first month?

• It permanently erased staging database records.
• She pushed it without understanding hidden dependencies or consulting the squad.
• Kyle ordered her to deploy unreviewed code to satisfy a customer.

How did Scott react after Abigail broke the staging environment?

• He reported the failure directly to executive management.
• He held a grudge and refused to join future retrospectives.
• He offered helpful technical context and helped her fix the problem.

What primary lesson did Abigail discover by day 90?

• Product managers should always drive architectural decisions.
• Tech leads succeed by establishing trust, listening, and protecting focus.
• Refactoring pipelines must always occur during week one.

Sources: photo by Pixabay on Pexels