# The ladder

Everything on one page, in order, with the ticket pinned beside it.

**Nothing on this page can be bought.** This is a prototype of a purchase flow, not a purchase flow. The work it configures is done by people, and the team specified for it has never run.

- What it is testing: Whether seeing the whole thing at once beats being walked through it. Closest to an ordinary cart, and the cheapest to be wrong about.
- What is wrong with it: It looks like a form, and a long page of choices is a page people skim to the bottom of and price without reading.
- What it produces: one JSON brief, identical across all five prototypes

## The model behind all five

- **What is running** (multi, weight 1): Which of these is already in your environment? 10 options
- **What it was granted** (multi, weight 1): What does the credential behind each of those actually permit? 12 options
- **What it is supposed to do** (multi, weight 1): What is each of them actually authorised and expected to do? 9 options
- **What you want out of it** (multi, weight 1): Which of these should the team produce? 9 options
- **How the answers are evidenced** (single, weight 1): How much of this should be taken on your word? 3 options

## Where a total lands

- up to 8 weighted: `t1` £10 — A small estate, your own account of it, and the delta between the two halves.
- up to 18 weighted: `t2` £50 to £100 — Enough surfaces that the map is worth drawing, and the regulation slice attached to it.
- up to 34 weighted: `t3` £150 to £1,000 — Wide enough that somebody should read it with you rather than hand it over.
- up to 9999 weighted: `t4` £5,000 to £10,000 — An estate, not a project. This one starts with a conversation and a written scope.

---

This document is released under the Creative Commons Attribution 4.0 International licence (CC BY 4.0).