AfterAgile™
Lens
Get the PDF

Monday – Set Intent and Intent Review

Clean up the AI drafts, then defend them until 80% consensus

MTWThF

Monday – Set Intent and Intent Review

Monday has two parts. In the morning, CX and Product clean up what AI has already drafted. In the afternoon, Product defends it to every internal stakeholder. Monday repeats until there's 80% consensus with CX's position.

Monday AM · CX and ProductSet Intent

Nobody starts from a blank page. AI analyzed Thursday's Collab, and the Intent work is already drafted when CX and Product pull it up.

Drafted by AI · cleaned up by its owners

The Intent

  • The customer need, in customers' words – CX
  • The evidence behind it – CX
  • Who it's for – UX
  • The success measure – Product
  • Market landscape and competitive viability – Product

Drafted by AI · cleaned up by Product

The Business Case

  • The problem statement
  • The target demographic
  • Financials – how the business makes, saves or doesn't lose money
  • Market placement
  • Competitive analysis
  • Product viability
  1. CX and Product open both drafts in the AI project.
  2. CX corrects the customer need and evidence – anything AI misheard, overstated or missed. UX confirms who it's for.
  3. Product checks the numbers, sharpens the market placement and competitive view, and confirms it's viable.
  4. AI updates both drafts live as they talk.
  5. By lunch, both are ready to defend.

Monday PM · open to every internal stakeholderIntent Review

Open to all stakeholders, team members and cross-functional interests – Finance, Support, Sales, Marketing, Legal, Engineering, UX and anyone else with a stake. Internal only. This is the session that arrives at the KPIs and what "done" looks like.

  1. Product defends the Intent and the business case.
  2. CX backs it with customer evidence and usage data.
  3. The room challenges it, sharpens it and re-scopes it.
  4. Together they set the KPIs – the measure, the baseline, the target and the layer it's read in.
  5. Each Definer says what "done" looks like for their part. Engineering flags anything that touches data, payments or logins.
  6. If it won't fit in one Coding Day, it's split into smaller Intents.

For Your Consideration at Intent Review

CX

  • Is the customer challenge grounded in evidence?
  • Do we know exactly who it's for?

Product

  • Why now?
  • Is it viable in the market, and what are competitors doing?
  • Does the business make, save or not lose money – or is it a Principle Intent?
  • Is there one success measure, and a layer to read it in?

UX

  • Do we know how this should look, feel and flow?
  • Does the design system cover it, or does it need something new?

Engineering

  • Does it touch data, payments or logins?
  • Will it cross any Engineering Guardrail?

Stakeholders

  • Should we build this at all?
  • What's out of scope?
  • Will it fit in one Coding Day?
  • Has each Definer said what "done" means?
Goes in
The AI-drafted Intent and business case, built from Thursday's Collab
Comes out
An aligned Intent with its KPIs and what "done" looks like
Done when
There's 80% consensus with CX's position

Generated and Iterated Monday

Nothing on Monday starts from a blank page. AI drafts every artifact from the decisions, actions and context captured at Thursday's Collab, and the Definers shape it – each in their own lane.

  1. Set IntentCX and Product shape the draftsCX defines the Intent.
  2. Intent ReviewThe platform opens to stakeholdersProduct defends, the Definers agree "done."
  3. Feeds TuesdayEvery Coding Day promptTraces back to what was decided here.
ArtifactDrafted fromShaped byUsed next
IntentThe Collab's decisions, actions and contextAI, shaped by CX (the need and evidence), UX (who it's for) and Product (the measure and market)Intent Review, then every Coding Day prompt
Business caseThe Collab, plus market and financial dataAI, shaped by ProductIntent Review
KPIs and "done"Intent ReviewAI, shaped by Product (the KPIs) and each Definer (their own "done")Tuesday's tests, Thursday's KPI Learnings
Split IntentsIntent ReviewAI, shaped by CX and ProductThe live queue of customer concerns
Intent Review decision recordIntent ReviewAI, confirmed by ProductCoding Day, and the repository
Actions, with ownersSet Intent and Intent ReviewAI, with an owner on every actionTuesday