Delivering Clarity: What Comes After Agile

For 25 years, Agile has been my favorite tool for leading engineering teams. Sprints, standups, retros. I've run them on three continents and I'd defend most of them today.

But I've started to notice something. The thing Agile was built to manage is disappearing.

Agile was a cost-control system for code

Agile worked because of one simple truth: building software was slow and expensive. We couldn't afford to build the wrong thing for long, so we worked in short cycles, shipped often, and corrected course.

Every sprint, every standup, every retro was a way to manage the cost and uncertainty of writing code.

That truth is changing under our feet.

The bottleneck moved

My teams now ship working software in days. Agents handle the planning, the architecture, the first draft of the code. Senior engineers review, steer, and deploy. What used to be a quarter is now a couple of weeks.

So where does the time go now?

Waiting. Waiting for a customer to try the thing. Waiting for someone to tell us the truth about it. Waiting for a decision from a room full of people with opinions and no data.

You can't fast-forward a conversation with a customer. You can't compress the time it takes a real person to use a product and decide if they care. The bottleneck moved from technical to human.

Shipping fast is no longer an advantage if you don't know what's worth shipping.

Agile, turned inside out

I'm calling the response Delivering Clarity.

It keeps what made Agile work: short, iterative loops. But it points them at a different target. Customer contact instead of code delivery.

• Agile optimized for engineering time, which was scarce. Delivering Clarity optimizes for honest customer feedback, which is now the scarce thing.
• Agile built its cadence around sprints that ship code. Delivering Clarity builds it around cycles of customer conversation.
• Agile delivered a feature each cycle. Delivering Clarity delivers a decision: what to build next, and for whom.

The loop is simple. Talk to customers. Build in days. Put a working version in their hands. Watch what they do, not what they say. Decide. Repeat.

From developing software to developing businesses

Here's the bigger shift. Agile was a method for developing software. Delivering Clarity is a method for developing businesses. When building is cheap, the whole game becomes knowing what to build and for whom.

Back in January I wrote that vibecoding made building easy, and the hard part is still customers. Delivering Clarity is my answer to that hard part.

It also changes who does what:

• Teams get tiny. I've written about building companies with three-person teams. That's not a cost-cutting trick anymore. It's the shape the work wants.
• The engineer becomes a product manager. When code is cheap, the person closest to the code has to be close to the customer too.
• The founder drives directly. No layers between the idea and the people paying for it.
• The skills shift. Listening. Validating early and often. Gathering feedback from people who disagree with each other. Positioning what you learned.

Opinions are cheap. Evidence is expensive.

The most common failure I see right now isn't slow engineering. It's a team stuck debating opinions. My onboarding versus yours. This tagline versus that one. Everyone has a valid view and nobody has a user.

Delivering Clarity ends that debate the only honest way: put both versions in front of real people and let their behavior decide.

It starts inside

Part of delivering clarity to customers is having clarity yourself. A steady mindset. A clear sense of purpose. The discipline to control your own thinking before you try to shape a product.

Sloppy thinking that a human team quietly absorbs, an AI agent faithfully amplifies. The clearer you are, the better everything downstream gets.

What's next

This is the foundation I'm building Ruby Growth Labs on. I'm also writing it down as a book, drawn from what we've learned building and growing digital products. The method is being refined in the open, with real customers, on real businesses.

I wrote two pieces on LinkedIn that go deeper:

• Agile Was About Developing Software. Delivering Clarity Is About Developing Businesses. The core idea, from my perspective as an engineering leader.
• We Can Build Your App in Weeks. That's Not the Hard Part Anymore. What it looks like when Ruby Growth Labs works with you.

If you have a business idea or a product that needs to find its customers, let's talk. Let's see if we can help you deliver clarity.