Production Workflow Capstone

This is where the program cashes out. Each department presents one Project, agent, or automation ready to enter controlled use the following week — not a demo of what might be possible, but a workflow with an owner, evidence, and a rollout plan. "Production-ready" means ready for your organization's real release process, not free of all future work.

The capstone package

Six parts, all built during the program — the capstone assembles rather than invents:

1. Problem and owner — user, workflow, baseline, and target, in the one-sentence format from Phase 2
2. Operating design — inputs, steps, tools, outputs, and exception paths
3. Controls — data rules, permissions map, human checkpoints, audit trail
4. Evidence — the test set, results, defects found, and remaining limitations
5. Operations — one-page guide, support path, named technical and business owners
6. Rollout — pilot group, balanced measures, review date, stop condition

Demonstrate the stop, not just the success

Show two live cases: one normal case handled well, and one case the workflow must refuse or escalate — the ambiguous ticket, the missing input, the request beyond its boundary.

The second demo is the one that earns the room's trust. Anyone can show a system succeeding; showing it stopping correctly proves you know where its edges are, and that you built the edges on purpose. Teams that cannot produce a stop case have not found their workflow's boundary — which means the boundary will be found in production, by someone else. Use real company material only where approved for the session.

What reviewers will ask

The review panel — and later, the go-live approvers — work through six questions:

• Is the business outcome worth the operational complexity?
• Are the sources current and the permissions appropriate?
• Does the workflow make uncertainty visible instead of smoothing it over?
• Are approval gates attached to the decisions that actually matter?
• Do the tests include the likely failure modes?
• Can the team operate, monitor, and — someday — retire it?

Answer them in your presentation before they are asked. A team that raises its own limitations converts skeptics; a team that waits to be caught creates them.

The go-live gate

The business owner, plus the required IT, security, privacy, legal, or functional reviewers, approve the controlled release. Unresolved critical issues send the workflow back to testing — a return that is the process working, not a failure. A workflow that enters production with a known critical hole fails later, in front of customers, with the program's name on it.

Final commitment

Before leaving the room, name four things: the first pilot users, the launch date, the 30-day review date, and the person reporting results back. Programs end; these four commitments are what carry the work into next quarter. The capstone is not the finish line — it is the first workflow of many, and the method you used to build it is the real deliverable of these fifty hours.

Definition of done

The workflow is useful, bounded, tested, owned — and moving through your company's real approval process next week, with its first review already on the calendar.