Carrying it out and documenting it

This lesson is still being tested: it improves with learners' feedback. If something is unclear, it is the lesson that needs fixing, not you.

By the end of this lesson, you will be able to

keep the rhythm of a project session: pick up, do, check, note;
document as you go: time, decisions, mistakes;
do a weekly check-in;
scale down without giving up, when time runs short.

Why it matters to you

For two to six weeks, your project will go through short sessions, breaks, and mistakes. What moves it forward is not intensity but consistency: each session starts from the previous one, and leaves a trace. You reread that trace to pick the work up again, and at the end you use it to present your work (lesson 3). Everything you learned in modules 5 and 6 is put to work here for a single project.

Before you start


You need	Your final project sheet (lesson 1), your journal and your handoff sheet (modules 5 and 6), your assistant or Claude Code
Cost	Depends on the tools in your project
Duration	45 minutes, then the time of your project
Reminder	Your journal is a file in your folder, but whatever the AI reads from it is sent to it: nothing from the “never” list in what you give it

Understand it in 3 minutes

A session, in five beats (based on the SAY, DISCUSS, DO, CHECK, NOTE method from module 2):

Beat	What you do	Already seen
Pick up	Your handoff sheet, or “Where were we?”	Module 6, lesson 4
Say	What you want to do today, with a criterion	Module 2
Do	One step, no more	Module 6, lesson 2
Check	The step’s criterion, at the source	Module 6, lesson 3
Note	The journal, the sheet up to date, a version if you work in files	Modules 5 and 12

What you note at every session, in a few lines:

what you did, and the time spent;
the decisions, with their reason (“6 pages instead of 8, for lack of material”);
the mistakes, with their correction (“the AI wrote a time missing from my notes: replaced with [to be completed]”).

The weekly check-in: what is done, what is decided, what is blocking, the next action. If you have the point-semaine skill (module 8, lesson 4), it prepares it from your journal.

Scale down, don’t give up. Behind? Go back to the minimum version, note the decision and its reason (module 6, lesson 5). A small finished project is worth more than a big stopped one.

Do it together

1Step 1: Prepare the project journal

In your journal folder, create one page per session, named with the date (journal/YYYY-MM-DD.md), as in module 5, lesson 3. If you haven’t done module 5, a “journal” folder on your computer, with one text file per session named the same way, is enough. The point-semaine skill (module 8, lesson 4) relies on this name to find the pages of the last 7 days. At the top: the project name, the week, the planned time.

2Step 2: The first session

Pick up your final project sheet.
Choose the first step and its criterion.
Do it, check it.
Note: done, time, decisions, mistakes. Update part 3 (the tracking) of the sheet.
Update your handoff sheet: next action.

3Step 3: The weekly check-in

At the end of the week, reread your journal, or ask Claude Code, which reads the pages in your folder:

Read the pages of my journal from this week. Give me the weekly check-in in 6 lines: done, decided (with the reason), mistakes corrected, what is blocking, time spent, next action. Use only the journal; write [to be completed] if some information is missing.

If you use a chat assistant, it does not read your folder: paste the week’s pages under the request, and keep the instruction “Use only the journal”.

Compare the time spent with the planned time. If the gap is growing, decide now: scale down, or push back an end criterion.

Your turn

Throughout your project:

Every session: pick up, say, do, check, note.
Every week: the check-in, and the decision if you need to scale down.
At the end: check each end criterion, and note the date.

Check your work

It worked if:

every session has its trace in the journal: done, time, decisions, mistakes;
every week has its check-in;
every scaling down is noted, with its reason;
the end criteria are checked and dated.

Common mistakes:

noting only what worked;
forgetting the time spent: you will not be able to say what your project cost;
doing three steps in one session, and no longer knowing which one caused the problem;
going over the time without deciding anything.

Keep it and pick it up later

Your journal and your final project sheet are the material for lesson 3: keep them complete.
After a break, start from your handoff sheet, never from memory.

Going further

optional

If your project goes through several tools, also keep the map of exchanges and the safeguards sheet from module 9.

New words

3 words explained

Word	What it means
Session	A moment of work on the project, short and regular
Weekly check-in	The summary of the week: done, decided, blocked, next action
Document	Keep a trace of what you do, decide and correct, as you go