If the proofs are missing, you do not have a scale decision — you have enthusiasm.
Sprints create learning — if you define the proof
Prototype sprints compress discovery and build into a short window. That compression is valuable when questions are sharp. It is harmful when the sprint is only a faster way to produce slides and screenshots.
This article is not another essay on how AI writes code while engineers deliver systems. The focus is commercial proof: what the sprint must demonstrate so scaling is a rational decision rather than momentum.
Five proofs a sprint should leave behind
Write these into the sprint brief before day one.
- Bound proof: the workflow or decision still fits on one line after building.
- Operator proof: people who do the work prefer the path for defined tasks.
- Access proof: required data and tools worked under realistic permissions.
- Evaluation proof: pre-agreed measures were run on representative cases.
- Production sketch proof: ownership, monitoring, and next build steps are explicit.
What “working demo” is not enough
A demo can impress without proving operator preference, without proving access will survive security review, and without proving exceptions are visible. Scaling on demo applause recreates pilot theatre with better project management jargon.
Require a short operator trial: real cases, timed tasks, written notes on trust and friction. If operators will not use it without the project team present, you do not have proof.
Design the sprint to make stopping acceptable
A healthy sprint can conclude “do not scale yet”. That outcome should be celebrated when evidence is weak. Budget a decision meeting with stop/go criteria published in advance. Delivery assurance begins by refusing to launder weak evidence into a multi-quarter programme.
Typical Microcorem sprint shape
Clarify the bound and owner. Build the thinnest path that exercises the riskiest assumptions — often data access, exception handling, or integration. Evaluate with operators. Document the production sketch. Recommend scale, revise, or stop. AI product engineering sits inside that discipline when models are involved; the sprint still serves the operating proof.
Risks
Scope that expands daily. Stakeholders who skip operator trials. Success metrics invented at the end. Production sketches deferred “to phase two”. Each risk converts a sprint into theatre. Name them in the kickoff and assign who will block them.
A practitioner note before you spend
A final operating note for practitioners: write the workflow in one sentence an operator would recognise; name the owner who will live with exceptions; list the systems that hold truth today; decide which actions stay human because they are irreversible or commercially sensitive; choose three measures that would convince a sceptical supervisor; and only then select mechanisms — rules, integrations, assisted drafting, or models. Revisit the same checklist after the first production week. If operators invent a shadow path, the design failed even if the demo looked polished. Prefer a thinner finished path over a broader unfinished programme. Keep British spelling in documentation your UK teams will maintain. Resist invented benchmarks; report only measures you can observe in your own operations. When in doubt, reduce scope until ownership and evaluation are honest. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades. Document decisions in plain language, keep the fallback path visible, and schedule a go/no-go review with the operating owner present. Treat delivery assurance as part of the work, not an afterthought once enthusiasm fades.
Closing
Scale only what the prototype sprint proved: bound, usefulness, access, evaluation, and a production sketch. If those proofs are missing, you do not have a scale decision — you have enthusiasm. Enthusiasm is not a plan.
