After Agile

Philosophy & Timing

Why now

After Agile™ exists because two things are happening at once: the way we build software has changed, and the people who build it haven't been given a new way to work.

  • AI collapsed the cost of building. A feature scoped for a two-week sprint can ship in an afternoon.

  • The operating model didn't change with it. Most teams still run sprints, standups and backlogs designed for a world where building was slow and expensive.

  • The gap is landing on people. Some colleagues are out of work. Those still employed are being handed new roles with no playbook.

I'm writing this now because the window to help people through the shift is now, not after it settles.

Out of work, and not prepared

So many talented colleagues are out of work right now. Worse, many aren't prepared for the roles opening up on teams that build with AI.

  • These are experienced people: designers, product managers, engineers, QA leads with decades of craft.

  • The job descriptions changed faster than the training did. "Works with AI" now shows up in roles that never existed under Scrum.

  • No one handed them a model for what those teams look like day to day, who owns what, or how quality holds up at AI speed.

After Agile is meant to give them that model, so they can walk into an interview, or a new team, and speak the language of how the work is done now.

Still employed, in new roles

Anyone still employed is facing a new role, whether or not their title changed.

Role

What it was

What it is now

UX

Drawing screens and handing them off

Architects of the end-to-end experience, shaped through prompts, the design system and the customer journey

Product

Managing backlogs, writing tickets, negotiating story points

For the first time since the role began, doing actual product work: answering "why?"

Engineering

Writing most of the code

Applying their problem-solving in an entirely new arena: architecture, review of machine-written code, and the systems that keep AI on track

Each shift is an opportunity, but only if people are shown what the new job is. Right now most are figuring it out alone, mid-flight.

My philosophy

Machines own execution. Humans own intent, judgment and taste.

  • We removed the friction that forced us to think. The handoffs and reviews were slow, but that was where quality came from. After Agile puts that judgment back on purpose.

  • Structure moves from the calendar into the system. Instead of sprints and ceremonies: a written intent, a shared repository, a design system and review gates.

  • People matter more, not less. The tools can build. Only people can decide what's worth building, and whether it's right for a customer on their worst day.

  • Back to the spirit of the original manifesto. Agile started as permission to talk to each other. After Agile brings the room back together: Product, UX, Engineering and QA building side by side.

  • Customer signal drives the work. The cadence follows learning, not building. We measure what customers actually did, and that becomes the next intent.

What After Agile offers

After Agile gives people a shared map of the new work, whether they're looking for their next role or reinventing the one they have.

  • For people out of work: a clear picture of how AI-era teams operate, and the vocabulary to show they're ready for it.

  • For people in new roles: a definition of what their job is now, and how it connects to everyone else's.

  • For teams and leaders: a one-week cycle they can pilot in two weeks, without reorganizing the company.

The free playbook is the starting point. Consulting and team pilots are the next step for organizations that want help making the shift.