Software engineering's bottleneck is no longer code

"For most of the history of software, planning was sacred. You had to plan before anyone touched a keyboard, because the cost of building the wrong thing could be so punishing, especially for startups, that getting it right upfront was the only rational strategy. Implementation was expensive, engineering time was scarce, and changing direction once the team had committed to an approach could set you back months."

"AI coding tools have collapsed the cost of turning an idea into working software. What used to take weeks of implementation can now be explored in hours. You can ask an agent to prototype three competing approaches overnight, and throw away the two that don't hold up when you wake up in the morning. You can challenge an assumption with a working demo instead of a slide deck."

"The economics have inverted: planning and process used to be cheaper than building, and now building is cheaper than the meetings you'd hold to decide what to build or how to build it. This changes everything about how engineering teams should operate. There is no such thing as a perfect plan anymore, and even if there were, the time it would take to produce one means you've already lost to someone who just started building."

"At Synthesia, we decided to test this idea in the most direct way we could. Every quarter, our product, engineering, and R&D teams come together in London to plan the next three months of work. Historically, we'd spend most of that time in rooms analyzing, debating, and prioritizing. The goal was to emerge with a plan that was good enough to justify the cost of implementation."

Planning used to be required before coding because building the wrong software was costly, engineering time was scarce, and changing direction after commitment could delay progress for months. Modern planning rituals and prioritization frameworks emerged to manage that economic reality. The cost structure has inverted as AI coding tools make it faster and cheaper to turn ideas into working software. Teams can prototype multiple approaches quickly, discard weak options, and validate assumptions with demos rather than slide decks. As a result, perfect plans are no longer feasible or advantageous, since time spent planning can be lost to competitors who start building immediately. A quarterly planning process was tested by replacing early planning days with a hackathon to accelerate execution.

Read at TNW | Opinion