Help Center

Course overview

Make it work for your needs

Capture one improvement and the evidence you would use to check it.

This full-text reading copy does not save answers. Open the interactive lesson for saved browser notes.

Record one opportunity

A reader responsible for Orion wants a report with only Orion’s activity.

The report you handed off includes totals for both projects. Record an Orion-only view as a candidate improvement and keep the original CSV as its input.

Tip: Capture an opportunity in one sentence with the reader, the benefit and one check. For example, “Let the Orion lead generate a report of the four Orion entries and confirm that they total 180 minutes.”

Keep the checked baseline

Use the result you already built and reviewed.

Keep $PRACTICE/activity-report.html, its original six-row CSV and the saved check outcomes. The full report has six entries and 270 minutes.

Optional baseline text output

Use the same course environment and practice path from lesson 2 to print the full report.

baseline command

macOS/Linux — Bash or Zsh

"$COURSE_PYTHON" "$PRACTICE/project/report.py" "$PRACTICE/project/data/activity.csv"

Windows PowerShell 5.1 or 7

& $COURSE_PYTHON "$PRACTICE/project/report.py" "$PRACTICE/project/data/activity.csv"

Describe the smallest useful change

Write the outcome and its boundaries in plain language.

Write the expected results

Derive both expectations from the original CSV.

Use the same entry counts and totals for both text and HTML. These are expectations for the proposed change. The saved baseline checks describe the current program.

Bring the opportunity to your assistant

Use the saved task path and the new opportunity to prepare a draft.

Start with the generated reply from Come back tomorrow if you are opening a new conversation. Add your opportunity, the two expected results and any open decision.

change planning prompt

Prepare a draft for an Orion-only activity report from the existing six-row CSV. Orion should have four entries and 180 minutes. With no selection, the report should still show six entries and 270 minutes. Keep the input and existing checks intact. Ask me to settle the selection and unknown-project behavior. Show me the draft and checks for review, then stop.

Review the resulting draft and its checks. Agree on scope and authorize execution as separate steps when you decide to pursue the improvement.

Try the same idea for Lumen

Optional practice with one independent answer.

Suppose the reader manages Lumen. Use the original CSV to calculate the expected count and total for that project. Keep the full-report expectation intact.

Your Lumen variation

Write your answer in your own notes, or use the interactive lesson.

This optional note stays in your browser profile and site.

Check your answer

Lumen has two entries totaling 90 minutes. Development has 60 minutes and Documentation has 30.

Which evidence would support the proposed Orion filter most directly?

An unchanged six-row fixture yields four Orion rows and 180 minutes through the new option, while no selection still yields six rows and 270 minutes. Correct. Those independent outcomes exercise the new selection and preserve the existing baseline. They still need actual execution after implementation.

The baseline checks prove that a project-filter option already works. The supplied parser has no project-filter option. Baseline checks cannot establish behavior that was not implemented or exercised.

Save the next decision

Leave enough context to pick up the opportunity later.

Keep the opportunity and its two checks with your project handoff. If you return to the saved baseline task, open its current briefing and add the decision you still need to make.

For this example, the next decision is how readers choose a project and how the program handles an unknown name.

Next: Return to Turn an idea into a useful result when you want to frame another opportunity.