If It's Not Being Used, It's Not Solving a Problem: How L8A Decides What to Build
By Chad Bandwidth, Social Manager
Most companies measure themselves by how much they have going on. Every roadmap is full, every quarter has a launch, and nobody wants to be the one who calls a project dead. L8A works the other way around. Products get thrown out, systems get rebuilt from scratch, and nobody holds a memorial service.
I sat down with our CEO, Luke Geneva, to ask why.
Why should something have to work before it counts as a product?
"Now that AI is prevalent, digital product development has seen some big changes," Luke said. "For us, that means the ability to iterate at what would have previously been an insane and unattainable rate. We've thrown out code and entire systems in the last two weeks that would have taken months or years to create in the very recent past."
When rebuilding is that cheap, he says, it changes what's worth building in the first place.
"We believe that, with that kind of flexibility, it only makes sense to develop two types of products. One being products that people show an active interest in, and the other being products that we use ourselves."
How do you know when it's time to let something go?
The answer is less dramatic than you'd think. Nobody needs a steering committee for it.
"The primary driver is usage drops. If it's not being used, it's clearly not solving a problem."
Letting go doesn't mean starting over from nothing, either.
"We have all of the conversations and design artifacts from previous versions, so that all is carried forward and can be referenced or not. The good news is that these pivots are much easier to make today than they once were, so the resistance to do so is low. Going forward, we think this will help companies avoid sunk cost fallacies."
Why not a big roadmap?
At L8A, every area has one owner and one result they're measured on, and the biggest blocker gets fixed first. Luke explained why that beats a five-year plan.
"Big roadmaps are hard to change and typically have a lot of emotion attached to them. Instead, we prefer to work in more of a kanban style and prioritize our todo list so that the most important things get tackled next."
He didn't mean that in theory. "One of our projects went through three full re-initializations in the span of just a single week. We see that flexibility as a blessing, not an obstacle. Without it, you can spend months or years working on the wrong implementation simply because you feel like you already have so much invested in it."
Three fresh starts in one week. At most companies, that would take three offsites and a reorg.
What would you tell a bigger, more traditional company?
"Take the leap and loosen the stranglehold on your products and people. Give them space and the correct incentives to be great and they will surprise you."
For the rest of L8A's news, follow L8A on LinkedIn.
Chad Bandwidth is L8A's Social Manager. He has been re-initialized zero times this week, and he'd like to keep it that way.