CIO vs. CTO: Strategic Partners in Technology Leadership
Introduction
All the engineering teams that I have dealt with are faced with technical debt. Although there are different causes or factors that lead to its accretion, some organizational cultures are prolific in the creation of technical debt at an unsustainable pace. These toxic patterns are vital in understanding of how any technology leader intending to create sustainable systems can understand them fully. Any reduction efforts would eventually be fruitless unless it is done with the underlying culture that causes technical debt. The debt will keep on increasing at rate greater than the rate at which you will be able to pay off.
Typical Cultural Patterns that create technical Debts
Technical debt does not occur in isolation. The existence of certain cultural tendencies and habits in engineering organizations propagate the conditions under which the low quality of code, shortcuts, and the presence of accrued complexity is the rule, but not an exception.
Culture of Sloppiness
Teams that are not careful of craftsmanship standards will always come up with low-quality code. Engineers do not write tests, do not pay attention to edge cases and do not test cross-browser interoperability. This practice provides redundant code, and substandard structural foundation. The solution: inculcate a sense of craftsmanship in the team. Help engineers engage in the work proudly and set the proper quality standards which all people adhere to.
Unprofessional Mindset
Not all engineers consider themselves professionals who are equal to lawyers or accountants. They do not have the internal motivation to do the things right because that is the standard practice as a professional. The remedy: Build a professional self among members of the team. In order to have the title; engineer, they have to accept the duties and requirements that come along with it.
Tolerance of Limited Skills
It is one thing to be an unskilled person but it is quite another thing to continue being an unskilled person and be happy because of that. When the focus on growth and learning is not presented, teams are bound to acquire a technical debt with bad decisions and implementation. The solution: foster a culture of constant learning and acquisition of skills. Offer growth prospects and set professional development clear expectations.
External Pressure
The engineering managers and the developers are the ones who are aware of what is right and what is achievable within the time limit but succumb under pressure. They transmit stress downwards to their teams instead of giving pushback when appropriate. The fix: Train managers should be trained to make judgment as to when to pressure and when to resist unrealistic demands.
Pattern Organizations
In many cases, project abandonment results in organizations initiating many projects, appearing to be active, and discarding them in favor of projects that appear more important. This results in half-complete features, half-complete database migrations, partial framework upgrade, and half-write-offs. The fix: Build a culture of wholeness. Consider before embarking on new ventures, and, when commenced, to the last when they are not exciting any more.
Project abandonment creates significant technical debt through half-complete implementations and partial migrations.
Technology Trend Chasing and Ownership Issues
Technology Trend Chasing
Teams find it very easy to jump into a new technological trend and leave behind them the results of technological rubble yards. Applications naturally take various tech stacks on various components and have more frameworks than developers. The remedy: Love but do not embrace new glitzy technologies. Only introduce new tools when there is an apparent, and substantial difference between them and the current solutions.
Absence of ownership
Engineers are not responsible or accountable towards the long term impacts of their code. When technical debt has come up, the answer is frequently "I did not do that!" The remedy: Have accountability and ownership set. Empower the team members to make decisions and pose questions such as "What would you do?" rather than telling them what to do.
Hero Culture Worship
Organizations that rely on and admire heroes generate a continuum crisis in which heroic actions are sought. This culture leaves a trail of technical debt in its wake; these dramatic saves are adored by the management. The answer: delegate to the team and long-term outcomes. Although it is important to acknowledge individual contributors, it is necessary to highlight that software development is successful under the team work.
Lack of Technical Vision
The lack of technical vision or strategy causes the teams of people to work in circles, doing the best possible but by inadvertently participating in technical debt by creating architectural decisions and approaches that are conflicting. The solution: Formulate and share an elaborate technical vision and strategy. Lead by example by demonstrating the way to excellence in engineering.
Transform Your Engineering Culture Today
Break free from technical debt cycles with proven cultural transformation strategies.
Contact UsDeveloping Automatic Management Culture
The final objective is to develop what I refer to as automatic management - a place where engineers can always make the right decisions without a close supervision or a comprehensive guideline. It is advisable to eliminate the cultural elements that drive the technical debt before embarking on the highly expensive technical debt reduction efforts. Otherwise, you will be combating the systemic problems with uphill battle. This cultural change needs to be reinforced with time. It entails:
- Setting professional lines of clarity
- Establishing accountability
- Promoting continuous learning
- Creating systems that appreciate good work rather than quick fixes
The Path Forward
Technical debt reduction is not merely a technical issue but it is essentially a leadership and cultural issue. With these toxic patterns identified and resolved in your organization, you provide the foundation of sustainable engineering practices.
Cultural change is a time-consuming and laborious process. Begin by identifying what patterns are present in your organization, and then strategically address all problem areas.
Investment Benefits
Investment in cultural transformation will not only be a payoff in terms of technical debt reduction. You will:
- Create more robust teams
- Develop superior products
- Come up with engineering practices that will be scaled when your organization expands
Cultivate responsibility and professionalism as a part of your company culture that ensures long-term technical superiority.
Tags
Introduction
All the engineering teams that I have dealt with are faced with technical debt. Although there are different causes or factors that lead to its accretion, some organizational cultures are prolific in the creation of technical debt at an unsustainable pace. These toxic patterns are vital in understanding of how any technology leader intending to create sustainable systems can understand them fully. Any reduction efforts would eventually be fruitless unless it is done with the underlying culture that causes technical debt. The debt will keep on increasing at rate greater than the rate at which you will be able to pay off.
Typical Cultural Patterns that create technical Debts
Technical debt does not occur in isolation. The existence of certain cultural tendencies and habits in engineering organizations propagate the conditions under which the low quality of code, shortcuts, and the presence of accrued complexity is the rule, but not an exception.
Culture of Sloppiness
Teams that are not careful of craftsmanship standards will always come up with low-quality code. Engineers do not write tests, do not pay attention to edge cases and do not test cross-browser interoperability. This practice provides redundant code, and substandard structural foundation. The solution: inculcate a sense of craftsmanship in the team. Help engineers engage in the work proudly and set the proper quality standards which all people adhere to.
Unprofessional Mindset
Not all engineers consider themselves professionals who are equal to lawyers or accountants. They do not have the internal motivation to do the things right because that is the standard practice as a professional. The remedy: Build a professional self among members of the team. In order to have the title; engineer, they have to accept the duties and requirements that come along with it.
Tolerance of Limited Skills
It is one thing to be an unskilled person but it is quite another thing to continue being an unskilled person and be happy because of that. When the focus on growth and learning is not presented, teams are bound to acquire a technical debt with bad decisions and implementation. The solution: foster a culture of constant learning and acquisition of skills. Offer growth prospects and set professional development clear expectations.
External Pressure
The engineering managers and the developers are the ones who are aware of what is right and what is achievable within the time limit but succumb under pressure. They transmit stress downwards to their teams instead of giving pushback when appropriate. The fix: Train managers should be trained to make judgment as to when to pressure and when to resist unrealistic demands.
Pattern Organizations
In many cases, project abandonment results in organizations initiating many projects, appearing to be active, and discarding them in favor of projects that appear more important. This results in half-complete features, half-complete database migrations, partial framework upgrade, and half-write-offs. The fix: Build a culture of wholeness. Consider before embarking on new ventures, and, when commenced, to the last when they are not exciting any more.
Project abandonment creates significant technical debt through half-complete implementations and partial migrations.
Technology Trend Chasing and Ownership Issues
Technology Trend Chasing
Teams find it very easy to jump into a new technological trend and leave behind them the results of technological rubble yards. Applications naturally take various tech stacks on various components and have more frameworks than developers. The remedy: Love but do not embrace new glitzy technologies. Only introduce new tools when there is an apparent, and substantial difference between them and the current solutions.
Absence of ownership
Engineers are not responsible or accountable towards the long term impacts of their code. When technical debt has come up, the answer is frequently "I did not do that!" The remedy: Have accountability and ownership set. Empower the team members to make decisions and pose questions such as "What would you do?" rather than telling them what to do.
Hero Culture Worship
Organizations that rely on and admire heroes generate a continuum crisis in which heroic actions are sought. This culture leaves a trail of technical debt in its wake; these dramatic saves are adored by the management. The answer: delegate to the team and long-term outcomes. Although it is important to acknowledge individual contributors, it is necessary to highlight that software development is successful under the team work.
Lack of Technical Vision
The lack of technical vision or strategy causes the teams of people to work in circles, doing the best possible but by inadvertently participating in technical debt by creating architectural decisions and approaches that are conflicting. The solution: Formulate and share an elaborate technical vision and strategy. Lead by example by demonstrating the way to excellence in engineering.
Transform Your Engineering Culture Today
Break free from technical debt cycles with proven cultural transformation strategies.
Contact UsDeveloping Automatic Management Culture
The final objective is to develop what I refer to as automatic management - a place where engineers can always make the right decisions without a close supervision or a comprehensive guideline. It is advisable to eliminate the cultural elements that drive the technical debt before embarking on the highly expensive technical debt reduction efforts. Otherwise, you will be combating the systemic problems with uphill battle. This cultural change needs to be reinforced with time. It entails:
- Setting professional lines of clarity
- Establishing accountability
- Promoting continuous learning
- Creating systems that appreciate good work rather than quick fixes
The Path Forward
Technical debt reduction is not merely a technical issue but it is essentially a leadership and cultural issue. With these toxic patterns identified and resolved in your organization, you provide the foundation of sustainable engineering practices.
Cultural change is a time-consuming and laborious process. Begin by identifying what patterns are present in your organization, and then strategically address all problem areas.
Investment Benefits
Investment in cultural transformation will not only be a payoff in terms of technical debt reduction. You will:
- Create more robust teams
- Develop superior products
- Come up with engineering practices that will be scaled when your organization expands
Cultivate responsibility and professionalism as a part of your company culture that ensures long-term technical superiority.
