Keep Product Teams Shipping Faster with Successful Frontend Migrations

March 27, 2025

Impact/effort matrix with four quadrants: 'Quick wins' (high impact, low effort), 'Big projects' (high impact, high effort), 'Fill-in jobs' (low impact, low effort), and 'Thankless tasks' (low impact, high effort). Used for prioritizing work. Source: BiteSize Learning

The company wants more features, faster. You go to your boss and suggest that reducing build times could increase the team’s shipping velocity. They tell you that they aren’t willing to invest in any system migrations to allow developers to ship high quality code at a faster speed. The company also won’t hire more developers. The only option left is for the existing developers to work harder and faster, piling more debt onto a poor foundation until work comes to a relative standstill and the company’s star engineers burn out and quit.

Source: Keep Product Teams Shipping Faster with Successful Frontend Migrations

Sometimes a migration– it could be tooling, frameworks, or a variety of things–is inevitable. But how do you know when? and how do you go about it? Mae Capozzi considers the challenges.