AfterAgile™
Lens
Get the PDF

Definitions

Roles, Ceremonies, Actions and Tools

The whole language of AfterAgile™ in one place, in four parts – Roles, Ceremonies, Actions and Tools. These names are capitalized throughout.

Roles and Responsibilities

CX

Definer · Customer-centric

Gets to the bottom of the customer need – defines the what and the why. Identifies the most pressing customer challenge each week, weighed against level of effort and cost. Brings the customer evidence, backs the Intent at Intent Review, checks the result at Final Review, and leads The Collab. Leads on the customer as a whole, across every team. Approves the personas UX builds.

Product

Definer · The translator

Defines commercial viability – why now, and what it's worth. Translates the customer need into a business case – market viability, the competitive view, and how the business makes, saves or doesn't lose money. Defends the Intent at Intent Review, and sets the measurable success outcome.

UX

Definer · The experience

Defines the brand, the UI and the workflow. Owns the design system AI project and the content voice. Defines and refines the personas used in testing.

Engineering

Owns the guardrails

Owns the Engineering Guardrails that keep the build sound. Writes and enforces the guardrails – architecture, data, model safety, performance, observability, security and dependencies. Works in the IDE with the Definers on Coding Day, reviews what merges, and leads Crisis Mode.

Definers

The core team

CX, Product and UX. Each one Defines what "right" means for their part, then Tests the result against it.

Reviewers

Business-centric

The Business and Stakeholders who own the outcome. Internal stakeholders, team members and cross-functional interests. Challenge the Intent at Intent Review, preview the work at Final Review on Wednesday, and join hours 3 and 4 of The Collab.

Ceremonies

Set Intent

Monday AM

CX and Product shape the Intent

AI has already drafted the Intent and the business case from Thursday's Collab. CX and Product clean them up – the customer need, the problem statement, the financials, market placement, competitive analysis and product viability.

Intent Review

Monday PM

Product defends the Intent to the business, with CX

Open to every internal stakeholder, team member and cross-functional interest. CX backs it with customer evidence. This is where the KPIs and what "done" looks like are agreed. Set Intent and Intent Review repeat until there's 80% consensus with CX's position.

Coding Day + Testing

Tuesday

One IDE, the whole team

CX, Product, UX and Engineering around one shared IDE session, building with AI and testing as they go. It could take 3 minutes, 3 hours or all day.

Ship

Wednesday

Final Review in the morning, live in the afternoon

Final Review in the morning, open to every internal stakeholder, the same as Intent Review – minutes, or up to two hours. Then AI prepares and tests the rollback plan, Engineering signs off, and the flag goes on for a slice of customers.

KPI Learnings

Thursday AM

What customers actually did, read solo

Solo, no meeting. Each Definer on the core team reads their own layer – AI drafts the brief first. Product reads the KPIs, CX reads the customer voice, UX reads where customers hesitated, Engineering reads errors and load. Each layer gets a call, ready for the Collab.

The Collab

Thursday PM

Where next week begins

Moderated by AI, with prompts drawn from every past session. Hour 1, CX and Product. Hour 2, Engineering and UX join. Hours 3 and 4 – sometimes 5 – stakeholders. It ends with CX identifying the most pressing customer challenge, weighed against level of effort and cost. Friday is open.

Actions

North Star

The year's lasting vision

The North Star is the year's lasting vision. Each week's Intent serves it.

Intent

The one thing this week's work must accomplish

AI drafts · Product defends

The customer need, who it's for, the business case and how success will be measured, on one page. It starts from the customer challenge CX identifies at The Collab, and it serves the North Star, the year's lasting vision. AI drafts it, and Product defends it at Intent Review. An Intent that can't be defended doesn't reach Coding Day. There are two kinds.

  • KPI IntentMeasured by a number that should move, with a baseline and a target
  • Principle IntentThe right thing to do, with no KPI. Measured against industry standards and societal norms.

Define

Every Definer

Say what "right" means for your part

Clearly enough that a machine can build to it and a person can test against it. A successful definition has seven ingredients.

  • OutcomeWhat changes for the customer
  • EvidenceCustomer signal and usage data
  • MeasureA KPI, or the standard to meet
  • BoundariesWhat's in, and what's out
  • Done criteriaTestable, including accessibility, performance, security and edge cases
  • ContextThe design system, the voice, the house rules
  • ExamplesA good case, a bad case, the customer's worst day

Test

Every Definer

Whoever defines it, tests it

The Definers hand AI what it needs to check the work – personas, device specs and their "done" criteria – then judge the result themselves, live, in the IDE. No middle man, fewer misunderstandings, and a faster path to done.

Tools

The Dashboard

The team's single view of the week

A ticker across the top shows the Intent, each ceremony and the measures as they move. Below it, real-time customer activity, the "Was this better?" prompt, and the layered reads. It replaces the backlog board and the ticket queue.

The IDE

Coding Day

One shared AI-native development environment

CX, Product, UX and Engineering around it together.

Design System AI Project

Owned by UX

Where the design system lives

The brand, UI patterns, workflow and voice, held in an AI project that every session references. No one hand-codes it.

Session Recordings

Every ceremony

The week documents itself

AI analyzes the recording of every session into decisions, intentions and actions, with a name on every action – and generates the Intent, The Collab Brief, the decision records and the context files. Every artifact is editable live in the AI project, and its owner vets it.

AI Moderator

The Collab

Runs the room Thursday afternoon

Builds the Collab's prompts from every past session, keeps time and cites its sources. It asks, it never decides.

Feature Flag

Release

Ship without releasing

A switch that turns a change on for a slice of customers, without a new release.

One-Click Rollback

Release

Undo in seconds

Turn the flag off, or return to the last good build.

The Pipeline

Release

Quality, automated

The path from a merged change to live, running every gate along the way.