Overview
Central principle and manifesto of the Problem-Driven AI methodology.
Problem-Driven AI is a methodology that puts thinking before building — and the problem before the prompt.
The main idea
The bottleneck was never execution. It was always the same thing: understanding the problem deeply enough to deserve a solution. AI doesn't change that. It makes ignoring it more expensive.
A poorly defined problem, fed into an AI, produces a perfectly built incorrect answer, at scale, in minutes. That is not progress. It is acceleration in the wrong direction.
This methodology exists to reverse that inertia: first the problem, then the context, and only then the build.
The 3 pillars
Manifesto
The founding declaration: AI doesn't solve poorly defined problems faster — it builds them wrong, faster. The value lies in prior thinking.
Principles
The ten principles that govern every decision within Problem-Driven AI. They are the criteria to know if you're on the right track.
Phases
The complete lifecycle in five interdependent phases: from Problem Phase to Market Phase. Each phase is the precondition for the next.
A new era, new professionals
The way we build is changing at its root. It is not an evolution. It is a rupture.
The roles we knew are transforming because it no longer makes sense to organize ourselves around construction. AI builds. We have to think.
That is uncomfortable. And it makes sense that it is.
Many skills you spent years mastering will stop mattering. Knowledge that gave you security will lose value faster than you imagine. This new era leaves many of us exposed, without the technical armor that once protected us.
What remains when all of that is stripped away is the hardest and most valuable thing: the ability to truly understand a problem, to think rigorously before acting, to go to the core of your discipline and become someone who reasons, not just someone who executes.
The roles we knew — designer, developer, strategist, business — do not disappear. They reconvene around the problem, breaking down silos, thinking together, before asking AI to build.
This is not a design methodology. Designers who arrive here looking for that will feel uncomfortable. The same will happen to developers, strategists, and business professionals. No discipline finds its usual territory here. And that is exactly the point. Change does not ask permission, and embracing it is the only useful response.
That said, every professional will recognize in this methodology direct connections to the best of their discipline: the active listening of design, the systems thinking of development, the analytical rigor of strategy, the results orientation of business. Not everything you know is left behind. What is left behind is the superficial. The profound, at last, has a central place.
Problem-Driven AI is born open. It is not a closed framework or a product: it is a living proposal that wants to be adopted, questioned, and improved by teams and people who share the same conviction — that the value lies in the quality of thinking, not in the speed of execution.
If this makes sense to you, this community is yours too.