Agile was meant to help us move faster. But over time, it’s become its own source of drag. Bloated tools, rigid processes, and too many handoffs have turned what should be a nimble workflow into a bureaucratic maze.
For developers and product teams alike, that means slower delivery, less ownership, and frustration across the board.
But there's a shift happening, one that leans into AI, cuts out unnecessary layers, and puts real builders back at the center of the process. That said, I think a new role is going to be born and I like to call it the "Solution Builder".
Ok we don't need to marry with that name, I'm still working on it, but let's call it that for the rest of the article.
What is a Solution Builder?
The Solution Builder is a hybrid between a developer and a product owner. They don’t just code, they own the entire problem-solving loop. They talk directly with stakeholders, understand the business goals, propose solutions, and build the product. Instead of passing tasks between departments, they take full responsibility for delivering working software, fast.
In this model, there's no need for long chains of communication or bulky documentation. A Solution Builder has conversations with stakeholders, proposes a plan, and immediately starts building.
If the idea is complex, they might start with a quick proof of concept to test the approach. Otherwise, they begin deploying small chunks of the product and iterating daily. Feedback isn’t delayed until the end of a sprint, it happens continuously.
How It Works in Practice
The Agile Post-AI process (as I call this approach) strips away unnecessary complexity. It starts with a simple conversation between the Solution Builder and the person who has the problem.
Together, they clarify what needs to be built and agree on the next steps. From there, the Builder documents the plan in just a few lines (no multi-page specs), no formal user stories. Then they start coding.
Instead of a heavy project management system, a lightweight board (I like to use Notion, but you can use any other option) is used to track progress. Columns like "To Do", "In Progress", and "Ready for Review" are more than enough to stay organized.
The Builder deploys changes daily, and the stakeholder reviews them in real time. If something needs to change, it’s adjusted immediately. This cycle continues until the product is done.
One key difference in this workflow is autonomy. Solution Builders don’t wait for approvals or rely on long chains of command. They’re trusted to make decisions and move fast. That means fewer blockers, more ownership, and a lot less overhead.
AI as a Force Multiplier
AI plays a big role here, but not by replacing developers. Instead, it enhances them. Models like Claude Sonnet 3.7 (or choose your favorite) help speed up the coding process.
You can use similar LLMs depending of your preference to assist in shaping requirements, generating ideas, or even rewriting documentation.
Repetitive tasks like testing or refactoring can be partially automated, freeing up the Builder to focus on higher-value work: logic, UX, and stakeholder communication.
The result isn’t just faster development, it’s smarter development. Builders can focus on solving the right problems instead of wrestling with tools or chasing down vague requirements.
Why It Works (Especially for Startups and Lean Teams)
This model is especially effective for startups or small teams that need to move fast. If you’re building an MVP or testing a new feature, speed and clarity matter more than process purity. The Solution Builder approach delivers both.
You get working software in days, not weeks. You talk directly to the person building the product. And you can steer the result as it evolves, instead of waiting until the end of a sprint to realize something was misunderstood.
There’s also something powerful about simplifying the tool stack. You don’t need a wall of Jira tickets or ten different integrations to stay on track.
Most teams find that a simple board, direct messages, and daily check-ins are more than enough. Trust replaces supervision, and progress speaks louder than status reports.
A Quick Example
Let’s say a founder needs a basic customer management tool. Instead of going through the usual process—product briefs, kickoff meetings, tech spec reviews—they sit down with a Solution Builder.
They talk for a reasonable amount of time (you can adjust the time to your needs), clarify the goal, and by the next day, a first prototype is live. Over the next two weeks, the product is shaped and improved daily based on real feedback.
There are no long delays or miscommunications, just fast, iterative building. At the end of two weeks, they have a working basic product. No fluff, no friction.
The Bottom Line
The Solution Builder model is about reclaiming agility. It ditches the excess process and lets developers own the problem, the solution, and the path in between. Paired with AI, it’s a powerful way to deliver real results, quickly and cleanly.
If you're part of a startup or a lean team, this could be your edge. And if you’re working in a larger organization, a pilot project using this approach might be a great way to try something different, without committing to a full methodology overhaul.
We don’t need more frameworks. We need fewer blockers. And maybe, just maybe, we need more builders who can own the whole thing.
Top comments (2)
Great Post
Thanks much Kevin, I appreciate it