Self-guided worksheet. This reading edition provides questions and evidence criteria. It does not calculate a score, produce a radar chart, compare peers, save answers, email results or generate a PDF.

Translate a broad transformation ambition into one observable change in how a customer job gets done. Record the baseline before proposing the improvement.

How to use it

Choose one workflow. For each question, record the answer, source, owner, date, gap and next check in your team’s document. Use “unknown” when the evidence is absent. Repeat after a material workflow change to compare your own records.

Describe the current workflow

Where does the work begin, what systems does it cross and what is the final result?

Evidence to collect: A real job with inputs, decisions, handoffs and saved effects.

Find the limiting step

Which delay, repeated correction or failure prevents the result?

Evidence to collect: Execution evidence tied to the customer’s work, with upstream causes kept separate.

Define the improvement

What would change in the agent, prompt, code or surrounding process?

Evidence to collect: A proposed revision and the failure mechanism it is intended to address.

Challenge the revision

Would the improvement survive different identities, permissions, tool states and retries?

Evidence to collect: Matched baseline/candidate runs, counterexamples and independent effect checks.

Measure the completed work

Did the customer outcome improve across comparable jobs?

Evidence to collect: Authoritative results and total human effort; a deployment alone does not establish benefit.

Turn the gaps into a bounded next step

Start with the most consequential unresolved job. Agree what would establish a better result, test the correction, and retain the source and outcome limits.

Use the reliability workflow worksheet · Explore Tensile · Discuss a concrete workflow