Effective 90-Day Plans Are Overrated for Senior Engineers
When Flexibility Beats Rigidity
About a year ago, while modernizing an internal agent portal for a Fortune 500 financial institution, I made the classic blunder of adhering too closely to a rigid 90-day plan. My team had laid out a detailed roadmap, confident that we could finalize user interface changes, optimize database queries, and deploy machine learning models all in a neat time frame. However, we hit a wall.
Our initial deployment was slow—over 10 seconds to load critical pages—an unacceptable figure for any internal tool. When we dug deeper, we discovered cache key collisions and a race condition that had never surfaced in our staging environment, leading us to rethink our rollout strategy.
The Importance of Adaptability
I started questioning the conventional wisdom of having a set-in-stone 90-day plan, a relic from earlier in my career. What I learned is that for senior engineers leading critical projects, the focus should be on adaptability rather than rigid timelines. In the early stages of any new role, particularly with complex, legacy systems, you can’t predict all the potential failures and technical hurdles you'll encounter.
My Approach to the First 90 Days
- Understand Existing Tech Stack: Get your hands dirty with the codebase. I spent the first few weeks diving deep into the Laravel application and SQL queries that supported different features.
- Identify Quick Wins: During my tenure delivering a modernization project for a regulated beverage portfolio, I focused on optimizing the database access patterns, reducing load time by 30% in less than a week.
- Collaborate and Communicate: Engage with team members to understand pain points and adjust priorities accordingly. Instead of enforcing the original plan, we scrapped unnecessary tasks and focused on eliminating the bugs that slowed us down.
What I Stopped Doing
One critical change I implemented was to stop obsessing over a checklist of milestones that didn't consider the realities of our work. I realized after our initial failure that my priority had to be addressing the actual performance bottlenecks and misalignments in the team's expectations.
Conclusion
In today's fast-paced engineering environments, especially those dealing with legacy systems or applied-AI integrations, the ability to adapt and pivot is key. Yes, you should have goals, but making them flexible and reactive to real-world issues is what truly leads to success.
Next time you start a new role, remember: "Rigid plans can lead to rigid failures. Stay flexible and focused on real results."