We've just launched plato for individuals

🔥

login


Google Sign inLinkedIn Sign in

Don't have an account? 

A shared technical vision to manage your technical debt

Productivity
Sharing the vision

8 February, 2019

Simon Jones discusses how building a shared technical vision can increase the engagement & productivity of a team, and help manage technical debt.

Problem

When developing software at any company, there are times when compromises are made in order to get valuable features to market. As a result, technical debt inevitably accrues. Managing and technical debt can be difficult. There is almost always a tradeoff to be made between continuing to build product features and taking time out to address it. It is also not always obvious what the correct technical direction should be for a company, and finding time to define this can be challenging. The engineers themselves may not hold a unanimous opinion on what needs to be done. To solve these issues, it is important find time to create and pursue a shared technical vision, which every engineer can buy into, and which can be justified to other areas of a company by showing its long-term contribution to the business.

Actions taken

  • Give the people on your team a voice for where they think that you should be taking things. Consider finding time to facilitate sessions for the team to talk about their views on what they think is and isn't working with the technology stack as it stands today. People can be very vocal when they are given the opportunity to propose ways to improve the technology they are working with, and this can help you shape your strategy.
  • Look at your product roadmap and determine which features are going to grow your business, and whether there are any which are going to be impacted by unaddressed technical debt. Always be looking ahead not only for what is going to impact you today, but more importantly what impact it is going to have three to six months down the line. Focus on addressing technical debt which will hold back your business in the future.
  • Establish a decision-making framework to help make the process as objective as possible. Write out architectural decisions in a structured way. It doesn't have to be reams of documentation, just a one-page summary that both formalizes the decision-making process and also acts as a record of conversations and decisions that you have made. Try to cover the key problems that you are trying to solve, the options that you have considered for each of those problems, their respective merits, and the decisions you have arrived at.

Lessons learned

  • You don't hire great people to then tell them what to do. You hire great people to tell you what to do. So, raise and discuss the topics or decisions that you are struggling with, and use your team as a valuable asset to help formulate your own opinions.
  • Managing technical debt always works best when it is an ongoing process. It's not beneficial to anyone to let the technical debt build up and then spend a month going back and fixing it all, because then your business is at a standstill.
  • As teams and the company mature, the decision making process will shift. Newly-formed teams tend to need decisions explicitly made or facilitated. As your team gets to know one another and become more comfortable with each other's working styles, it is more likely to run itself, thus allowing you to step back and afford them more autonomy.
  • Steer your team towards understanding the business, and detail how their work and your vision contributes to profitability and customer acquisition. This will help the team reach their own conclusions about which technical tasks are the most important. The most successful engineering teams understand the business they are working in.

Related stories

Getting From What to Why
27 September

Pete Murray, Principal Software Engineer at Electronic Arts, explains how he successfully solved a long-troubling problem by applying a root cause analysis.

Dev Processes
Productivity
Impact
Pete Murray

Pete Murray

Principal Software Engineer at Electronic Arts

Setting Guardrails and Containing an Increase in Cloud Costs
21 September

Michael Mac-Vicar, CTO at Wildlife Studios, dissects how to set guardrails that would contain the exponential increase in cloud costs.

Dev Processes
Productivity
Michael Mac-Vicar

Michael Mac-Vicar

CTO at Wildlife Studios

Outcomes Before Outputs: Measuring Engineering Performance
14 September

Marian Kamenistak, VP of Engineering at Mews, explains why EMs shouldn’t be measuring the output of a team or individual engineers, but the outcome of the whole team.

Impact
Productivity
Marian Kamenistak

Marian Kamenistak

VP of Engineering at Mews

Get More Done by Working Less
14 September

David La France, VP of Engineering at Kenna Security, explains how managers can level up their skills and scale in their roles by learning to work less, but smarter.

Personal growth
Delegate
Impact
Productivity
David La France

David La France

VP Engineering at Synack

Architecture Council: An Idea for Advancing Organizational Strategic Orientation
28 August

Brad Henrickson, CTO at Scoop, shares how by establishing the Architecture Council he advanced strategic thinking of the engineering team and overall strategic orientation of his organization.

Impact
Productivity
Feedback
Brad Henrickson

Brad Henrickson

CTO at Scoop

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.