The single biggest accelerator we've found for shipping software isn't a new framework, a faster CI pipeline, or a magic methodology. It's organising people the right way around a problem — and trusting them to ship.
For years, we ran the conventional setup: a design team, an engineering team, and a project manager bridging the two. Handoffs happened in Figma, specs were filed in Linear, and engineers translated mockups into code. It worked, but every transition introduced friction. Designers waited on engineers. Engineers waited on clarifications. The work moved in fits and starts.
Two years ago, we restructured. Instead of departments, we built pods — three to five people per pod, each one mixing senior engineers, a product designer, and a product lead. The pod owns a slice of the product end-to-end. They scope it, design it, build it, ship it, and watch the telemetry.
The results surprised even us. Velocity nearly doubled, not because anyone worked harder, but because the round-trip latency between design intent and shipped code collapsed. A designer notices a usability problem mid-build, raises it in their pod's Slack channel, and an engineer adjusts the next morning. No tickets. No handoffs. No status meetings.
Cross-functional pods aren't a silver bullet. They demand more from individual contributors — engineers need to think about design tradeoffs, designers need to understand technical constraints, and everyone needs to communicate. But for product-focused work, especially at the 0-to-1 stage, we've never found a faster way to build.
If you're a small team feeling slow, look hard at how your handoffs work. The problem usually isn't the people. It's the boundaries between them.