Back to resources

Taking Ownership of a Legacy System

Leadership
Stakeholder Management
Engineering Processes
Communication and Collaboration
Team Management

7 January, 2022

Amar Rao
Amar Rao

Sr Director of Engineering at FanDuel

Amar Rao, Senior Director Of Engineering at FanDuel, recalls his exposure of acquiring a legacy system where his team had little experience and was unsure how to create a clear map of functionalities.

Problem

My team's most recent project involved taking over a massive system and codebase where we had little experience. There was a more extensive reorganization within my company where senior engineers were moved to new products, and my team acquired the legacy business. I struggled to manage this system, in which I had to take control of support and ownership while setting my team up for success. Our new platform consisted of code and systems that were unknown to my team. We had to identify all the moving parts and unknowns and set ourselves in a position to maintain this system long-term.

Actions taken

The first step my team executed was an audit of the existing system. During the audit, we identified the current services and processes in place. We connected our findings with information from experts from the last team to try and understand the architecture, documentation, tech debt, and known problems within the system. Unfortunately, many senior engineers who previously worked on this platform were moved to complex, fast-moving projects. Because of this, my team tried to be as efficient as possible when interacting with the experts and expanding their understanding. When we could connect with a critical subject matter expert, I tried to specifically get a level of commitment to be a resource for my team. Afterward, they were present in ad hoc meetings to consult on future projects.

After creating a foundation of knowledge, we reviewed the existing architecture with the business, product, and engineering teams. We tried to adhere to Conway's Law, where the org structure and architecture align. To do so, we mapped out the function we knew the system was supposed to do and how this related to products and features. This information was organized in a logical way in which we wanted to deliver value in the future. From there, we worked to find well-reasoned team groupings that would best support our outcomes. Lastly, my team assigned clear ownership of those areas and used it for the organization moving forward.

Establish what it means to own a portion of the system with your teams. Even if it is ambiguous, understanding who is responsible for something moving forward will bridge the distance between knowledge gaps. The outcome was a clear map of all the functionalities and products that our team was responsible for. These functionalities are aligned with business and product and separate from the audit of the existing software systems. From there, we clearly understood what logical grouping owned each of these areas and who was in leadership roles.

Lessons learned

  • Don't be stuck on the current structure you are in right now. Align with business and product on how you want to deliver value in the future.
  • When taking over any legacy systems, associating with the existing subject matter experts, plan on creating clear commitments on what level of support your team can expect.
  • Clarify what it means to be responsible for a portion of a system with your team. By doing so, your team will understand the requirements to act like an owner.
  • Establish explicit dependencies between the teams. Especially as teams take over areas they do not understand, they will be less knowledgeable about all the potential hidden dependencies. Examples of this can be stakeholders or other departments a team needs to interact with to achieve an outcome.

Discover Plato

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


Related stories

4 E's of Leadership

21 March

A short overview of a very effective leadership assessment by Jack Welch, that is easily transferred to other industries is the 4Es of leadership – energy, energize, edge, and execution.

Leadership
Career Growth
Strategy and Vision
Ramesh Dewangan

Ramesh Dewangan

CEO at Quantum Vision Consulting

Performing Focused Work in a Distracted World

21 March

Based on an awesome book titled "Deep Work" by Cal Newport we provide provide a brief overview of the Rules for Focused Success in a Distracted World.

Leadership
Productivity
Communication and Collaboration
Ramesh Dewangan

Ramesh Dewangan

CEO at Quantum Vision Consulting

Beware the Empathy Trap

21 March

Is it possible to be too empathetic? If you overdo it, it can be an energy sucker.

Leadership
Conflict Resolution
Team Management
Managing Stress and Burnout
Melanie Zens

Melanie Zens

Delivery & Operations / Digital Transformation / Innovation at Marais Consulting Inc

Applying The Rules of IKIGAI for a more fulfilled life!

20 March

Learn about 10 rules from the wisdom of these long-living residents from Ogimi, a small village in Okinawa, Japan. You could interpret the rules as the lifestyle habits that enable the senior residents of Ogami to live long and enjoy their ikigai.

Leadership
Productivity
Career Growth
Communication and Collaboration
Hiring, Retaining, or Firing
Managing Stress and Burnout
Ramesh Dewangan

Ramesh Dewangan

CEO at Quantum Vision Consulting

Relationships, like products, need to be designed.

7 March

3 ways leaders can cultivate relationships that lead to better products.

Leadership
Building and Scaling Teams
Career Growth
Team Management
Strategy and Vision
Guy Jenkins

Guy Jenkins

SVP Global Customer Experience at Salesforce