Why this exists

Measurement loses credibility when the team treats completions or satisfaction as proof that learning changed the work.

What you should leave with
  • A cleaner way to name the system problem before the team jumps to production.
  • A one-page structure you can copy into a meeting note, document, spreadsheet, or tracker.
  • A practical next action that can happen before a bigger playbook or template is needed.
Use this when
  • A leader asks for impact but the team only has completions.
  • The program needs a realistic evidence plan before launch.
  • The team needs to say what the evidence can and cannot prove.
Systems thinking move

Start with the decision the evidence needs to support. Then choose the smallest credible signal that connects learning to readiness, behavior, adoption, workflow, or contribution.

How to use this in the next meeting

Pick the weakest evidence you have today, then move one level stronger before building a larger dashboard.

Working tool

Use the rows as a thinking aid, not a compliance form.

Signal What to do What it tells you about the system
Completion People finished the assigned item. Useful for access and compliance, weak as proof of performance.
Relevance and confidence People say the support fits their work. Useful as a design signal, weak alone as proof of learning.
Knowledge or decision check People answer questions or choose the right path in a scenario. Stronger when the scenario mirrors the work.
Practice or work sample People demonstrate the task in a realistic practice setting. Shows readiness before live performance.
Manager observation Managers use a simple rubric to observe behavior. Turns coaching into a lightweight evidence source.
Workflow signal Operational data moves in the expected direction. Shows contribution, but still needs caveats about other causes.
Three ways to act

Start with the lightest version that still changes the work.

Manual way

Write one decision, one behavior, one evidence signal, one owner, and one evidence limit on a single page before creating a report.

Microsoft 365 or Google Workspace way

Use Forms, Sheets, Excel, Lists, Power BI, Looker Studio, or a shared scorecard to collect one readiness signal and one follow-up behavior signal.

AI-assisted way

Use AI to draft evidence options, rubric criteria, manager observation questions, caveats, and leader-ready summaries from approved data. A person validates every claim.

Unconventional moves
  • Add a negative proof statement: this evidence does not prove business causation by itself.
  • Measure readiness before launch. It is cheaper to learn that people are not ready before they touch live work.
  • Use manager observation as data only when the criteria are consistent.
  • Create a rotating deep-evaluation schedule. Not every program needs the deepest evidence every time.
Copy-ready field tool

Paste this into the tool next to the work.

Evidence ladder

# Measurement Evidence Ladder

Start with the decision the evidence needs to support.

Decision:

Behavior that should change:

Weakest evidence we have today:
- Completion
- Satisfaction
- Confidence

One level stronger we can collect:
- Scenario decision check
- Practice or work sample
- Manager observation
- Workflow signal

Evidence limit:

Next review date:

Rule:
Report completions if needed, but do not call them proof of behavior change.
Prompt starters

Use AI to inspect the work, not replace the owner.

These prompts are strongest when you give the model approved source material and ask it to separate known facts, assumptions, missing information, risks, decisions needed, and next actions.

Open the model-aware prompt vault

ChatGPT GPT-5 family

Use an outcome-first prompt with the job, approved source material, constraints, and the exact artifact you want back.

I am working on Move one level stronger than completion for an L&D system problem.

Goal: Help me turn the notes below into a practical next move.

Context: Use this when the team needs a practical measurement plan that is stronger than completion data but still realistic.

Use these working fields: decision, behavior, current evidence, stronger signal, collection owner, evidence limit, follow-up date.

Rules:
- Use only the source notes I provide.
- Do not invent policy details, metrics, learner needs, compliance requirements, or business context.
- Separate known facts, assumptions, missing information, and next actions.
- Flag anything that needs requester, reviewer, leader, legal, compliance, LMS owner, or manager confirmation.
- Keep the output practical enough to review in a working meeting.

Source notes:
[paste approved notes here]

Return:
1. Decision the evidence supports
2. Current evidence strength
3. One stronger evidence option
4. Manager observation idea
5. Workflow signal option
6. Evidence limits
7. Recommended next action

Claude 4 family

Use XML-style sections so context, source material, task, constraints, and output format stay separate.

<context>
I am working on Move one level stronger than completion for an L&D system problem.
Use this when the team needs a practical measurement plan that is stronger than completion data but still realistic.
</context>

<source_notes>
[paste approved notes here]
</source_notes>

<task>
Turn the source notes into a practical next move using these working fields: decision, behavior, current evidence, stronger signal, collection owner, evidence limit, follow-up date.
</task>

<constraints>
Use only the source notes provided.
Do not invent policy details, metrics, learner needs, compliance requirements, or business context.
Separate known facts, assumptions, missing information, risks, and next actions.
Flag anything that changes scope, ownership, evidence, risk, or decision rights.
</constraints>

<output_format>
1. Decision the evidence supports
2. Current evidence strength
3. One stronger evidence option
4. Manager observation idea
5. Workflow signal option
6. Evidence limits
7. Recommended next action
</output_format>

Gemini 3 family

Use a clear task, labeled input, and one example pattern. For Obsidian context, use approved excerpts, Drive exports, Google Docs, or NotebookLM source sets.

Task: Help me make progress on Move one level stronger than completion from the notes provided.

Context: Use this when the team needs a practical measurement plan that is stronger than completion data but still realistic.

Working fields:
- decision
- behavior
- current evidence
- stronger signal
- collection owner
- evidence limit
- follow-up date

Example pattern:
Field: Missing information
Good answer: Name the specific information to confirm, who can confirm it, and why it affects the next decision.

Rules:
- Use only the source notes provided.
- If information is missing, write "Needs confirmation".
- Keep the output concise and reviewable.
- End with the next best action.

Source notes:
[paste approved notes here]

Output format:
1. Decision the evidence supports
2. Current evidence strength
3. One stronger evidence option
4. Manager observation idea
5. Workflow signal option
6. Evidence limits
7. Recommended next action

Microsoft 365 Copilot

Use goal, context, source, expectations, and output. For Obsidian context, use approved excerpts, Word summaries, OneDrive files, SharePoint pages, Teams context, or Outlook threads.

Goal: Help me make progress on Move one level stronger than completion.

Context: Use this when the team needs a practical measurement plan that is stronger than completion data but still realistic.

Source: Use the selected document, meeting notes, spreadsheet, email thread, SharePoint file, or pasted notes as the only source.

Expectations:
- Work with these fields: decision, behavior, current evidence, stronger signal, collection owner, evidence limit, follow-up date.
- Mark uncertain items as "Needs confirmation".
- Do not add facts that are not in the source.
- Separate known facts, assumptions, missing information, risks, and next actions.
- Summarize the top review questions for the team.

Output:
1. Decision the evidence supports
2. Current evidence strength
3. One stronger evidence option
4. Manager observation idea
5. Workflow signal option
6. Evidence limits
7. Recommended next action
Sources behind this tool

The research move is practical, not academic.

Work-Learning: LTEM Report

LTEM helps teams distinguish weak activity measures from stronger evidence of decision competence, task competence, transfer, and transfer effects.

Learning Guild: Beyond Kirkpatrick

Presence, attention, and learner reactions do not validate learning by themselves. Stronger evidence moves toward decisions, tasks, transfer, and effects.

Try this one thing today

Pick one program and move the evidence plan one level stronger than completion.