Skip to main content
WHAT IT IS

The B experience begins with the social film, continues through its scene-by-scene argument, and ends with the original web interaction.

WHY IT MATTERS

Decide which repeated service steps should become software, remain expert judgment, or disappear.

RN'S ROLE

RN conceived the question, structured the evidence boundaries, designed the experience, implemented the prototype and documented its limits.

BOUNDARY

This independent prototype demonstrates an approach; it is not a deployed client system, professional advice or proof of real-world outcomes.

HOW TO USE THIS PAGE

Watch the film first, then move through the scene-by-scene argument, then open the web interaction at the end. Each stage restates the same question at a different resolution, so the sequence matters more here than on the A side. You can leave at any stage and still have the whole argument.

WHERE TO GO NEXT

The build overview sets out the question, the purpose, the role and the evidence status in one place, and the public record behind it states what changed, what another person can reuse and what supports the system. If you want to judge how far this build should be trusted, the record is the page to read, not this one.

Build 005 — Service Path Split

DISTRIBUTABLE SOCIAL ARTIFACT

Watch the LinkedIn cut

This silent-first 4:5 film is designed for the LinkedIn feed. Its complete argument appears as on-screen text; captions, the visible transcript and the download preserve the same words.

Read the transcript
BUILD 005 — Service Path Split

SCENE 1
BUILD 005. DO NOT AUTOMATE THE SERVICE. Separate its steps first.

SCENE 2
THREE FUTURES. SOFTWARE. HUMAN. GONE. Each step earns a disposition.

SCENE 3
REMOVE. DELETE LOW-VALUE REPETITION. Do not automate waste.

SCENE 4
KEEP HUMAN. PROTECT JUDGMENT. Retain ambiguous, consequential, exception-heavy work.

SCENE 5
AUTOMATE. PROTOTYPE STABLE RULES. A candidate is not deployment approval.

SCENE 6
WORKFLOW. USE ALL THREE PATHS. Map the work before automation.

FINAL PROPOSITION
Map the work before you automate it.

INTERACTIVE MOTION STORY

Explore the motion argument

The film distributes the idea. This motion story uses the caption track as its source of truth, so every scene preserves the film text while letting you control the pace.

SCENE 1

BUILD 005. DO NOT AUTOMATE THE SERVICE. Separate its steps first.

01 / 06

RICHER WEB MASTER

Explore the interactive version

The LinkedIn cut is the shareable social artifact. The original B build below is the fuller web experience: use its controls, change its state and test the idea for yourself.

BUILD 005-B
IN THE LAB

Service Path Split

Change the conditions around repeated service work and watch the path separate into software candidates, expert judgment, and work that should disappear.

SERVICE PATH / BASELINE

One service. Three different futures.

Software is not the destination for every repeated step. Change the conditions and watch the path separate.

01Collect intakeAUTOMATE
02Interpret unusual factsKEEP HUMAN
03Copy status twiceREMOVE
04Schedule follow-upAUTOMATE
05Approve exceptionKEEP HUMAN

AUTOMATE

Collect intake

Schedule follow-up

KEEP HUMAN

Interpret unusual facts

Approve exception

REMOVE

Copy status twice

THE POINT

Do not turn the whole service into software.

Separate the repeated work first. Encode stable rules. Preserve expert judgment where consequence, ambiguity, and exceptions matter. Remove steps whose only purpose is to maintain the old process.