Different Ways to Handle Technical Debt Part 2: The Dedicated Workstream
- Lucille Tut
- Oct 28, 2025
- 3 min read
In Part 1, we established that tech debt is inevitable and can be managed as Business as Usual (BAU). But what about the big stuff? The long-term, complex changes that are too large for daily cleanup?
Remember, these approaches aren't mutually exclusive - you'll use both! Here, we dive into a case study where a major fix was tackled as a dedicated workstream.
The Big Problem: Moving to React
We had a client that needed a complete code migration to React. This wasn't a quick fix; it was a complex system change being made in an environment with tight deadlines and external dependencies. Crucially, we had high-priority business features we couldn't stop delivering.
Knowing all this upfront allowed us to set realistic expectations and build a robust, sustainable plan.
Step 1: Pinpoint the Scope
Before starting, we defined the size of the beast:
Identify: We mapped every single workflow that needed changing. This defined the size of the project.
Group & Sort: We clustered related workflows to see dependencies, complexity and ease of change.
Prioritise: We regularly ranked the workflows based on multiple factors: how simple it was, how often users touched it and how vital it was to the current business deliverables.
Step 2: Learn by Doing (Start Small)
We didn't jump into the hardest part. We started with the smallest, easiest change - maybe a single page or a simple workflow.
The goal was simple: Figure out how the migration should work. We used small wins to establish best practices and learn from early mistakes.
Step 3: The Balancing Act
You can't let tech stack improvements stop just because of business deliverables. But you also can’t stop delivering for the business. There has to be a balance.
We used a clear ratio of React tickets to business tickets to ensure steady progress. Sometimes the migration slowed down for a critical launch; sometimes it sped up. The key was that it never stopped. It was important, it added value and we treated it that way.
Lessons Learned While on the Move
As the workstream ran, we constantly adapted. Here’s what made the difference:
Time Estimates Were a Joke: Our initial timelines were wildly optimistic (we were off by about 3x!). We learned to adjust quickly, re-plan and look for efficiency gains.
Bring in the Experts: While the team learned React, we realised we needed more specialists to accelerate the migration. We successfully brought in additional dedicated React engineers who paired with our full-stack team, essentially doubling our output.
Dedicated Focus: We assigned dedicated test resources and spent time creating common templates and documentation. This made the migration repeatable and minimised friction and risk as we moved from one workflow to the next.
Keep Adapting: We held continual team reviews to re-prioritise. The more you learn, the better decisions you can make. We embraced the idea that a decision made three months ago might not be the best one today.
Celebrate Everything: In a marathon change like this, you have to acknowledge the wins. We regularly celebrated completed migrations and viewed errors not as failures but as critical learning opportunities.
Moving to Your Next Phase of Strategy
Managing large tech debt as a long-term workstream is a juggling act - balancing priorities, sharing skills, and adapting along the way. But by working methodically and sticking to an agile plan you deliver powerful, valuable change.
Ready to stop delaying your critical tech debt fixes?
If your major system overhaul is stuck in the planning phase, let's chat. We can help you define the scope, build the right strategy and keep your business moving forward while you tackle the complexity. Reach out now to discuss your next big workstream.
Comments