Software Engineering’s Bottleneck is No Longer Code
For most of software history, planning was sacred. You had to plan before anyone touched a keyboard, as the cost of building the wrong thing could be punishing, especially for startups.
Implementation was expensive, engineering time was scarce, and changing direction once the team had committed to an approach could set you back months.
The entire modern software development apparatus—roadmaps, prioritization frameworks, quarterly planning rituals—emerged as a response to this single economic fact. That fact is no longer true, and most engineering organizations haven’t caught up.
AI coding tools have collapsed the cost of turning an idea into working software. What used to take weeks can now be explored in hours. You can prototype three competing approaches overnight and discard the two that don’t hold up in the morning. You can challenge assumptions 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.
This changes everything about how engineering teams should operate. There’s 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 directly. 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 analyzing, debating, and prioritizing.
During our most recent meeting, we flipped the sequence. We replaced the first two days of planning with a hackathon. 200 people from across engineering, product, design, legal, research, and talent formed 70 teams and built for 28 hours straight. The brief: take an idea, build it, turn the result into a two-minute demo video. No detailed specs, no over-planning – just build.
What happened surprised us.
One of the winning teams, a group of five engineers, completely rebuilt our video editor from scratch. The video editor provides a PowerPoint-like interface where users create videos with AI avatars. The engineers delivered a full reimagining of the product, focused on interactivity, branching narratives, and multi-avatar storytelling.
This wasn’t an outlier; across all 70 teams, the same pattern emerged: when you give people focus and remove friction, they can move far faster than anyone expected.
The lesson we took from this experiment is that execution is no longer the constraint—judgement is.