Module 4 · Lesson 1 of 4

Write a pilot you can actually evaluate

Define the trial's cases, boundaries, owner and decision before running it.

Go to the exercise

What you will leave with

A pilot charter with a fair comparison and a fallback.

Understand

The idea behind the work

A pilot is a bounded trial designed to answer a question. Name the useful outcome, representative work, allowed tools and actions, evaluation owner and evidence to collect. Keep the current process available while the new one is being tested. A pilot can succeed by showing that an approach should be adapted or stopped.

Write success conditions before seeing the outputs. Use the same quality checks and unit of work as the baseline. Include review, correction and failed attempts in the record. Limits should reflect the task's actual authority and available resources; do not invent a deadline, budget or approval on behalf of the business.

Inspect a worked example

Synthetic example: trial a weekly reporting workflow

This is a fictional teaching example, not a client result or a claim about Joseph Carroll's past work.

A fictional team uses approved sample exports for practice.

The starting input

One ordinary export, one export with missing conversion data and the existing report checks.

Work through it

  1. Define the question: can the new workflow produce a traceable decision brief with acceptable review effort?
  2. Allow local calculations and draft narrative only; keep circulation with the owner.
  3. Record results and corrections for both cases, and use the manual process if the workflow cannot reconcile totals.

The result

A trial that can reveal both useful output and a reason to stop.

A mistake to recognize

Calling one polished demo a pilot and omitting the difficult case.

How to recover

Choose representative inputs and record the work required to reach acceptance.

Adapt the method

What changes in your business?

The same method can serve different settings. Data, allowed actions and operational support matter more than headcount alone.

Owner-led business or small team

Use a task small enough to finish and check without new infrastructure.

Department or growing team

Agree on who evaluates the artifact and who decides whether to continue.

Large or complex organization

Run within approved systems and record the evidence needed by the actual adoption decision owners.

Try it, then inspect the result

Complete a pilot charter

Write the outcome, owner, cases, comparison, checks, allowed actions, fallback and decision to make. Leave missing values explicitly unknown.

Save the pilot in My Plan

Use a sample or a description you are allowed to share. Your answer stays in this browser when storage is available; export it to keep a separate copy. 0 / 6,000 characters.

Check your reasoning

A demo looks excellent, but its sources were hand-selected after several failed runs. What evidence is missing?

Inspect your own output

Check each statement after you look at your answer. These evidence checks apply to this visit; your answer and completion status can be saved.

To mark completion, write an answer, check the reasoning scenario and inspect every evidence statement. You can continue to another lesson at any time.

Self-reported completion does not certify competence. Open My AI Plan to review your saved work.

Sources and further practice

The lesson is Carroll Consulting's teaching synthesis. These sources support the underlying capabilities and concepts; check the current product, plan and configuration before applying them.

You can move between lessons freely. Revisit the checks whenever your answer, evidence or business context changes.