Agentic AI workbench: practise 90 days of delivery decisions

In this lesson you'll learn:

• what each part of the workbench is for, with a screenshot of each;
• how to run a simulation so that it teaches something, rather than being won;
• how to take its artefacts into your own project.

Sound familiar?#

• You have read about bars and shadow runs, and never had to make the call with a room watching.
• The last workshop taught a framework with slides, and nothing happened when anyone chose badly.
• Templates arrive empty, and nobody on the team knows what a good one looks like.

The workbench is built for all three: decisions with consequences, and every template filled in first.

What is the SkyWays workbench?#

One web page, no sign-in, and nothing you type leaves your browser. It follows SkyWays, this manual's fictional airline, through the same ninety days as the case study, and every concept in it links to where it is taught, where it is practised and the tool that applies it. The evidence pack is kept in your browser only.

Use it, step by step#

Step 1 · Start with the story#

Thirteen episodes, each opening at a moment with a number in it and closing one loop. Read them in order and the artefacts arrive in the order a real team produces them. Open the story

Step 2 · Run a simulation twice#

Each of the nine simulations is a sequence of decisions on the SkyWays case, and each option shows what it does to the steps that follow and the artefact it leaves behind. Run each one twice: once on the path that closes the loop, and once on the path that feels faster. The second run is where the lesson is.

The nine are the NFR workshop, the paper agent, build, buy or borrow, ninety days of SkyWays, the six-week deadline, the review bottleneck, the pricing-page walk, the bill blowout and the incident. All simulations

Step 3 · Replace SkyWays' numbers with yours#

Every tool arrives filled in, so the result can be read before anything is typed; replace the values with your project's and the result and the artefact change as you type. Each tool shows the formula or rule it uses.

The calculator uses the same rule as this tutorial (z = 1.96, the lower end of a two-sided 95% interval) so SkyWays' 412 of 500 reads 79.1% and 968 cases in both places. It also offers one-sided bounds, for a team that has chosen one in advance. The toolkit

Step 4 · Keep the Loop Map in view#

One picture that every page returns to: four phases drawn as a closing loop, the hand-off artefacts written on the arrows, and the eight loops numbered around it. Select a phase or a loop to see where it is worked through.

Step 5 · Collect the evidence pack#

The pack lists the documents that the product manager, the architect and the engineering lead hand to each other at the four hand-offs, marks the ones you already hold, and downloads as one markdown file that can go straight into a repository. The evidence pack

Step 6 · Go deeper by role#

Three playbooks (Solution Architect, Product Manager, and Engineering and QA) walk the same case from P0 to P3 in eighteen steps each, with the traditional practice and the agentic change side by side. The workbench's own guide suggests paths by the time you have: a 90-minute briefing, a half-day workshop or a full day. How to use the workbench

Where you'll use it#

• Before a project starts, as a rehearsal: run the ninety days, then the simulation for your riskiest step.
• In team training: one simulation per session, run twice, with the second run argued out loud.
• On a live project: open the tool for the artefact you owe next, and replace SkyWays' numbers.

Why it matters#

Decisions are learned by making them. A meta-analysis of 225 studies found that students taught with active learning outperformed those taught by lecture, and were less likely to fail. The workbench applies the same idea to delivery: a choice, its consequence, and the artefact it leaves, before the real ones.

Key takeaways#

1. Five parts: the story, nine simulations, seventeen tools, the Loop Map and the evidence pack.
2. Run each simulation twice: the path that feels faster is where the lesson is.
3. Every tool starts filled in: read SkyWays' result first, then replace the numbers with yours.

FAQ#

Is the agentic AI workbench free?#

Yes. It is a single web page with no sign-in, published with this manual. Everything runs in your browser, and nothing you type is sent anywhere.

Which simulation should I run first?#

"Ninety days of SkyWays" for the whole arc, one decision per episode, then the one closest to your next hard decision: the review bottleneck, the bill blowout or the incident.

Can I use the workbench for team training?#

Yes. Run one simulation per session, twice: once choosing the loop-closing option and once the faster one, and discuss why the consequences differ. The artefacts from the session go into the evidence pack.

Does the workbench save my work?#

The evidence pack is kept in your browser's local storage, on that device only. Download it as a markdown file to keep it or share it.

Apply it in your role#

Across the enterprise. Make the workbench part of onboarding for every role. A team that has run the incident simulation writes better postmortems, and faster.

The ten-minute workflow. A workshop plan in one prompt:

Plan a 90-minute team workshop using the SkyWays workbench's "<simulation name>" simulation. Include a
five-minute framing, two runs (the loop-closing path, then the fast one), debrief questions that connect
it to our project <describe>, and the one artefact the team should leave with.

Sources and credits#