Most product innovators fall into two camps: Branch-Builders, who move fast by solving for one user persona, and Root-Builders, who design deeper foundations that serve many. Branch-Builders reach market quickly but eventually struggle to scale, leading to bloated, high-burden software. Root-Builders take longer, but their systems compound, unlocking scale without the weight. Since users value lower burden above all, the future belongs to Root-Builders who can survive long enough to deliver their vision.

---

When it comes to building products, I’ve noticed there are two distinct archetypes of innovators.

The first group I’ll call Branch-Builders. These are the people who design directly for the persona in front of them. They see that a user needs a widget, imagine how that persona interacts with it, and build exactly that. Their strength is speed—they get to market quickly with something tangible. The widget solves a problem today, but usually only for that one persona in that one scenario.

Then there are the Root-Builders. These are the system thinkers, the architects. A Root-Builder hears the same request for a widget but steps back. Instead of only designing for that one persona, they ask: what are the underlying components here? How can this widget be broken down into parts that will also serve many other personas and situations? They distill the essence, build reusable foundations, and create something with the potential to grow far beyond the initial request.

This approach is powerful, but it comes with frustrations. A Branch-Builder can demonstrate value instantly. A Root-Builder’s work often looks incomplete at first. Sales teams or colleagues may ask why the widget isn’t fully optimized for the persona they were targeting. They don’t see the depth until the foundation is complete. Only then do they realize the broad utility and flexibility that was built in from the start.

I’ve experienced this tension repeatedly. When I ask for feedback early on, people struggle to see the vision. They see an unfinished widget where I see a root system that will support countless widgets in the future. It takes time—and often retracing steps backwards—for others to understand the logic of starting deep instead of wide.

The long-term payoff, however, is undeniable. Branch-Builders eventually hit a wall. The very speed that gets them to market becomes a liability when they try to expand. Their products are so tightly bound to the first persona that scaling into new markets often requires a painful rebuild. This is why so much of modern software carries a high Burden-to-Value ratio: it was built branch-first. Companies patch around the problem by acquiring other products once they capture market share, stitching them together into bloated ecosystems that frustrate users. It clearly works, but it’s also why most software today feels heavy and disconnected.

Root-Builders take longer in the beginning, but they avoid this trap. Each new widget is cheaper and faster to build because the foundation already exists. What looks like a delay at the start becomes a strategic advantage over time, unlocking scale without the weight.

And this is where the future points. Users have made it clear—time and again—that the most important thing to them in software is not the features, but the burden. They don’t particularly like software, and would rather not spend more of their lives inside it than necessary. The companies that survive long enough to deliver root-built foundations will define the next era of software. They’ll win not by dazzling users with more, but by burdening them less. The future belongs to the Root-Builders.

…