How this product is used

1. 1

   Write the procedure

   An author writes the steps in the console: the full text for a phone or tablet, and one short line for a watch. A procedure can be started from a document you upload, and what comes back is a draft. Reading and performing a procedure needs no special rights — writing one needs the author role or above, so a member cannot edit a draft.

2. 2

   Publish a version

   A publisher releases it, and at that moment the version stops being editable: its steps, their text, the documents it cites and its KPI definitions are all frozen. Correcting something later makes a new version instead, so a run recorded last month can still be read against the exact text that was performed.

3. 3

   Bring your people in

   An administrator creates an invitation and passes it on themselves — either a link, or a short code that can be read out over the phone. There is no directory of organisations and no way to find one and ask to join it, so nobody arrives that an administrator did not send for.

4. 4

   They perform it where the work is

   The full step on a phone or a tablet; the short line on a watch, for when the phone is out of your hands. A step that needs the camera is handed back to the phone, because a watch has none.

5. 5

   You see what was done

   Every run records which published version was performed, by whom, in what order, and how long each step took. Runs still going are on the live board, finished ones are in the history, and the history can be exported.

A draft is never ready by itself. If a procedure was generated from a document, somebody qualified in the work it describes has to read it in full and approve it before anybody performs it or works to it. The product will not publish a version by itself, and it does not check anybody's text for you.

1. 1

   Publish a procedure publicly

   A publisher opens one of your procedures and marks it public. You give an address readers can write to with questions about the instructions, and that address is shown to them on the page.

2. 2

   Take the code, the link and the QR

   The console mints a short code, shows the link it resolves to, and draws the QR code for that link. The QR downloads as a file you can hand to whoever prints your packaging, so it stays sharp at whatever size it is printed.

3. 3

   Put it on the product

   On the packaging, on a label, on the leaflet in the box. That printed code is the only place the procedure is findable at all.

4. 4

   Whoever scans it simply starts

   The code opens the instructions in their browser. No sign-in, no account and nothing to install. They work through the steps the way your own people do.

5. 5

   You see each reader's run

   One row for every reader who started, with a number in the place where a name would be, and how long they spent on each step. Nobody is identified, so the same person starting again on another phone is a second row rather than the same one.

• It does not translate your procedures

  The console itself speaks six languages, and that is the interface around your text. The steps you write stay in the language you wrote them in — in the console, on a watch, and behind a printed code. A procedure in another language is a procedure somebody writes in that language.

• The phone and watch apps do not open public procedures

  That is a decision rather than something missing: a code printed on a box has to work for somebody who will never install an application, so the public way of working is the browser and only the browser.

• It does not measure one person against another

  Each run is recorded on its own, and a period can be compared with the organisation's own recent record. There is no screen anywhere that puts two people's step times side by side, and nothing here scores, ranks or passes judgement on anybody.