How it works

You declare the situation. It builds the path, then walks it with you.

Automateagile is not a reading list. It is a guided loop. You tell it where the transformation actually is, it sequences a route through the method, it walks you move by move, and it re-sequences every time you report back what really happened.

1 Questionnaire → 2 Roadmap → 3 Guided walk → 4 Adapt

The guided loop

Four steps, then it loops

Steps one to three get you moving on the right block. Step four is the reason it is a roadmap and not a printout. You finish a step, you report what happened, and the route ahead changes.

Step one

A short questionnaire captures your situation

A few honest questions, not an audit. Where are you in the programme, what is the shape of the org, and which symptoms are actually stinging right now. Standups that drag on, a release that needs three teams to align, an exec asking for a feature roadmap, a sponsor you cannot find. You declare the problems in your own words.

Nothing here is graded and nothing is shared. It is the input the rest of the loop reasons over, so the more honest you are, the sharper the route.

What the coach sees

Plain-language prompts about stage, structure and the symptoms you are hitting
A running picture of your situation you can edit later, never a locked form
No sign-up and no upload; what you type stays in this browser

Step two

It generates a roadmap, a sequenced path through the method

The method underneath is the Definition-and-Judgment Stack: the scarce human work of a transformation, written down so it holds still. Your declared situation routes your symptoms onto the blocks that actually fix them, then orders them. A symptom of a coordination tax routes to eliminating dependencies before it touches funding. No real customer evidence routes to framing the outcome first.

You get a path tailored to what you declared, not the same nine chapters in the same order for everyone. The block that matters now sits at the top.

What the coach sees

An ordered route of blocks, the one next-right block highlighted
Why each block is where it is, traced back to the symptom you reported
The reasoning is legible; you can disagree and re-order, it is your programme

Step three

It walks you through it, step by step

Each step on the roadmap opens into the concrete coaching moves for that block, not a definition to memorise. What to do before the room, what to hold during it, and what good looks like after. The moves are the ones I run on real teams, phrased so you can take them into a standup or a sponsor conversation the same week.

You work one block at a time. The companion holds the rest of the route quietly so the current move has your full attention.

What the coach sees

The before, during and after moves for the block you are on
The done-when-X for the step, so you can tell when you are actually finished
An optional prompt to bring the AI sparring layer onto this exact plan

Step four

You report what happened, and the roadmap re-sequences

This is the loop. After a step, you say what really happened. The conflict surfaced, or it did not. The sponsor showed up, or the mandate is still unprotected. That report changes the route. A new tension you name pulls its block forward; a block you closed drops away; the next-right block is recomputed from where you actually are, not where the plan assumed you would be.

Over the months this is what makes the companion yours. The route is a record of your specific transformation, and that accumulated context is the reason it keeps getting more useful to you, not a claim about other people's accounts.

What the coach sees

A short report-back per step that re-weights the route, not a status form for someone else
The path visibly change: blocks move, the next-right one updates
A history you can scrub, so the memory is proven by reconstruction, not asserted

The sparring layer

Grill me on this plan, on your own key

At any step you can hand your current plan to an optional AI sparring layer and ask it to attack the thinking. It is opinionated and it leans LeSS: it will push you toward fewer, broader teams and real feature ownership, and it will name the coordination you are about to install instead of remove. It argues with the plan so the room does not have to.

Bring your own key

The sparring layer runs on your own API key. You hold the key, you hold the spend, and it is entirely optional. The guided loop works without it.

Opinionated, not neutral

It takes a LeSS-leaning position on purpose. A sparring partner that agrees with everything is not sparring.

On your real plan

It grills the step you are actually on, with your declared situation as context, not a generic prompt.

It is a sparring partner, not an oracle. The judgment about whether to take its advice stays yours, which is exactly the scarce work the loop is built to protect.

A deliberate choice

Why a roadmap, not a checklist

A checklist assumes the order is known in advance and that nothing you learn along the way should change it. Transformations are not like that. The thing you discover in week three is supposed to re-order weeks four through twenty. A static list cannot do that; it just sits there while reality moves.

A checklist

Fixed order, set once. You tick boxes in sequence. What you learn doing the work has nowhere to go, so you either ignore it or quietly abandon the list.

This roadmap

Re-sequences from what you report. The next-right block is recomputed each loop, so the plan stays honest about where you actually are. The order is an output, not a constraint.

Every engagement starts with done-when-X. Because the loop reasons over your real situation, it can tell you when to refuse work that just installs more coordination, and how to prove the exit instead of expanding the contract.

Start the loop

Answer a few questions and get your first route.

It is free for the independent coach, runs in your browser, and takes a few minutes to your first next-right block. Built by a practising Head of Agile Enablement at MediaMarktSaturn, a major European retailer, on real transformations rather than theory.

Start free → See the method

First-person results elsewhere on this site, time-to-value down 25% in two quarters and delivery reliability from 60 to 78% in six months, are from my own teams, not a guarantee for yours.