How to redesign your architecture to reduce technical debt

Unless you started building your product in the last twelve months, you’re likely dealing with a fair amount of technical debt.

As an engineering leader, you push your teams to keep iterating on features, user experiences, channels for distribution, and other experiments that will help drive your product forward. If you execute well, you’re likely to see success.

But when you reach this point, you need to reassess whether the system architecture and organizational structure that helped you get there are still enabling success.

At Wattpad, we had been building up our technology and product for over a decade when we noticed easy things were becoming hard to do.

Join LeadDev.com for free to access this content