How To Avoid Technical Debt

I’ll be blogging weekly, so sign up here to get notified when I post a new one.


Similarly to when I first saw the word “Techne,” when I came across the term “technical debt” it struck me as such a perfect intersection of multiple facets of my thinking and life experience.

Technical debt (also known as design debt or code debt, but can be also related to other technical endeavors), is a concept in software development that reflects the implied cost of additional rework caused by choosing an easy (limited) solution now instead of using a better approach that would take longer.”


When it comes to soccer:

“As with monetary debt, if technical debt is not repaid, it can accumulate 'interest', making it harder to implement changes. Unaddressed technical debt increases software entropy.”

Whether it’s in my own training, guiding others in their individual development, or thinking about team tactical concepts, technical debt applies to soccer. 

I strongly believe in spending time upfront to learn to do things correctly, even at the expense of early success. This approach is just one of the reasons I loved playing for Vlatko Andonovski, USWNT coach. He would focus significant time and energy on ingraining concepts into the team early on, so much so that I don’t think we ever won our season-opening game in my time playing for him. We simply weren’t ready. Rather than preparing intensely for the season’s first game, we would focus upfront on things that he knew would matter, especially later in the season. In fact, I think if the NWSL season had been a couple of months longer, it would have been even more apparent how good of a team-building system he created. I believe that this will become more and more evident in his success over time with the USWNT. 

On the field for FC Kansas City, where I was coached by Vlatko Andonovski

On the field for FC Kansas City, where I was coached by Vlatko Andonovski

Whether it’s learning to build out of the back, strike the ball with power, becoming two-footed, or rehabilitating from an injury, it doesn’t pay in the long run to rush the process or take shortcuts along the way. Yes, kicking the ball long is safer, maybe at first using your toe or only your strong foot is more effective, and you could get back for that next game, but in the long run those approaches will likely cost you significantly more time to go back and fix. Sometimes they can’t even be fixed. 

When it comes to business: 

Photo by Elias Clarke-Campbell

Photo by Elias Clarke-Campbell

I love building systems. Techne is a product, an app. Training is a process, an expertise. What I enjoy most about building my business is solving the puzzle of how to consistently make it bigger and better through scalable systems. I’ve bootstrapped the business and grown it from the ground up. Now, we are a team of six, and there’s absolutely no room for technical debt--with our technology, or any of our systems. We have to be as efficient as possible. 

I’ve also found that prioritizing quality work over getting things done quickly or cheaply is almost always a better decision in the long run. Sometimes we do something and know we’ll need to re-do it down the line, but as much as possible, I prefer to “play the long game” when it comes to business decisions, especially selecting the people I work with.



When it comes to life: 

IMG_7231 2.JPG

“Similar to monetary debt, technical debt is not necessarily a bad thing, and sometimes (e.g., as a proof-of-concept) is required to move projects forward.”

Sometimes we don’t know the best or most efficient way to learn, to do, to build something. And in those cases, I believe in just pushing forward! We can only learn by experience. It’s ignoring problems or not using enough long-term thinking that causes an accrual of technical debt. And the moment you learn another way, you take the better path. 

I’ve learned this in my soccer career and as an entrepreneur. In terms of my game, I see the importance of honestly assessing my own work. In my playing career, there were aspects of the game I didn’t attend to thoroughly enough along the way. And they cost me. I wish I had spent more time better developing myself as a well-rounded athlete and also worked more on training the mental side of my game. 

Whether in soccer, business, or otherwise, building a solid foundation is always vital. And the better your foundation — of technique, skill, processes, or systems — the higher and stronger you can build your pyramid upon it. 

Can you apply the concept of “technical debt” to something in your life? Leave a comment with your thoughts and experience!