APEX: Software Development Methodology for the AI era

Introduction

Today I'm releasing APEX - a software development methodology built for the AI era. It's built on a simple premise: the competitive advantage in software development has shifted. It no longer belongs to organizations best at managing large teams. It belongs to small teams of experts amplified by AI, working with accountability and precision, moving with expedience.

Most development methodologies were designed for the opposite problem. They're built for coordination at scale — which is precisely the thing AI is making less necessary. They slow you down.

APEX is designed to get out of the way.

This post introduces the methodology. The full manifesto is available below if you want to read deeper.

Process Died in 2024

Agile was right when it mattered. It pushed software development away from waterfall's crushing rigidity and toward something real: working software, actual feedback, human judgment. That was the fight we needed to win.

We won it. Then we broke it.

What replaced waterfall rigidity is ceremony rigidity. Two-week sprints because the calendar demands them. Standups announcing busyness. Retrospectives about having retrospectives. Backlogs that grow faster than they shrink. Scrum Masters managing the appearance of velocity while actual delivery slips quietly to the right.

Meanwhile, the world changed.

A skilled engineer with AI can today do what required a team two years ago. The leverage available to small, focused teams is unprecedented. And yet most development methodologies were designed for the opposite problem - how to coordinate work across large groups. They're optimized for the thing AI makes less necessary.

They're getting in the way.

APEX Is Built For Now

APEX is a methodology for this moment. It rests on a simple belief: in the AI era, competitive advantage belongs to teams that are small, accountable, precise in their understanding, and relentlessly focused on delivery. Not teams that are best at managing process.

It has four principles:

Accountable - Every piece of work has one owner. They make the call. They carry the outcome. Shared responsibility is responsibility that belongs to no one.

Precise - Know exactly who you're building for and what they actually need before a line of code is written. Imprecision is the most expensive thing in software development. AI makes it more expensive, not less—it just moves in the wrong direction faster.

Expert-led - AI is the most capable assistant software teams have ever had. It is not a developer, not a decision-maker, not accountable for anything. It produces output. Experts produce judgment. The human with domain knowledge directs the work, evaluates the output, and owns the result.

eXpedient - Every process step, meeting, and artifact exists only if it serves delivery. When it does not, it is removed. Ceremony destroys the speed advantage that expert AI-augmented teams have. The methodology gets out of the way.

The Values

We value outcomes over activity. Ownership over consensus. Precision over completeness. Expert judgment over generated output. Delivery over documentation. Simplicity over flexibility. Honest feedback over comfortable process.

Teams operating under APEX use AI to accelerate work that is well understood, to surface options the expert then evaluates, to handle repetitive tasks. They do not use it to substitute for understanding, to produce output nobody can evaluate, or to diffuse accountability.

Who This Is For

APEX is for teams that are done pretending process is the same as progress.

It's built for small, expert teams where individual leverage is high. For industrial and domain-specific software where precision and accountability are not optional. For organizations that have outgrown the coordination overhead of scaled Agile and want to work differently. For teams that want a methodology honest about the AI era rather than one that ignores it.

Read the Manifesto

The full manifesto goes deeper on each principle, explores what APEX is not, and explains the values that guide it.

Read the APEX Manifesto (Full) — The complete methodology with detailed explanation of each principle, the values, and what APEX is built for.

Read the APEX Manifesto (Summary) — The condensed version: four principles, seven values, one page.

APEX is a methodology developed by Erno Vuori. It's designed for this moment, by someone who's lived through the broken state of scaled Agile and the emergence of AI-assisted development. It's not a reaction. It's defined by what it produces: accountable teams, precise understanding, expert judgment amplified by AI, and expedient delivery of things that actually work.

If this resonates, read the manifesto. If you're working under APEX, let's talk about how it's going.