Your Cowork Routine

Five lessons, one habit

You now have the pieces. A sense of what this product is and what its approval step is for. A way to sort jobs into hand over and keep. A four part brief with a gap rule in it. A position on what your files may and may not be used for. And a review method for work you did not watch.

What you do not have yet is a rhythm, and without one all of the above decays into good intentions. This lesson turns it into something repeatable.

Build this outside the site

LearnAI has no accounts and stores nothing about you. No sign up, no password, nothing of yours sitting on somebody else's server. That is deliberate, and it means this site cannot hold your routine for you.

So the capstone lives in your own document. Open whatever you actually use, a note on your phone, a page in your work wiki, a plain text file on your desktop, and paste the blocks below into it. Then keep it wherever you keep your briefs, because a routine and the briefs it runs belong in the same place.

The weekly rhythm

Five steps, and the fourth one is not optional.

Brief. Once per job, not once per week. Written properly, with a gap rule and stated boundaries, then reused and improved rather than retyped.

Run. This is where the cloud earns its place. A job can start on your laptop, carry on in the background and be waiting when you next look. Scheduled work can run while your device is offline entirely. None of that requires your attention, which is the entire point.

Review. The pass from lesson five. Assumptions first, then what could not be found, then three high consequence items traced to source. Not a read-through.

Approve. Claude asks for your review and approval before shipping the work. Your job is to make that gate mean something. Approving is a decision, and a decision you make in four seconds while walking is not really a decision at all.

Log. One line. What ran, what you fixed, what you would change in the brief. This is the step everybody drops and it is the one that compounds, because your briefs only improve if you remember what went wrong last time.

MY COWORK ROUTINE
WHAT RUNS
Job 1: [name]   Brief lives: [where]   Reads: [named folder]
Produces: [the finished thing]   Sends: nothing
Job 2: [name]   Brief lives: [where]   Reads: [named folder]
Produces: [the finished thing]   Sends: nothing
Job 3: [name]   Brief lives: [where]   Reads: [named folder]
Produces: [the finished thing]   Sends: nothing
WHEN I REVIEW
Day and time: [a real slot in your week, at a desk]
How long: [20 minutes is usually enough for three jobs]
MY REVIEW PASS
[ ] assumptions read first, before the output
[ ] what it could not find, read second
[ ] three highest consequence items traced back to source
[ ] asked what is missing that nobody would notice was missing
[ ] approved, or sent back with the brief amended
RUN LOG
[date]  [job]  [what I fixed]  [what I changed in the brief]

[ ] Nothing reaches another person without me reading it first.
[ ] Nothing with legal or financial consequence goes beyond a draft.
[ ] I read the run report before I approve, every time, no exceptions.
[ ] High consequence items are checked in full, not skimmed.
[ ] Every brief carries a gap rule. Missing is always a valid answer.
[ ] No client data, and nothing under a policy or an agreement, goes in.
[ ] I do not approve consequential work from a phone in a corridor.
[ ] If I could not spot an error in the output, I do not hand the job over.

Once a month, ask four questions about the routine, not the jobs.
1  Which output did I approve without genuinely reading it?
Fix the brief so it is reviewable, or stop running it.
2  Which output did nobody act on?
Stop running it. An unread document is a cost with no benefit.
3  Which brief did I mentally correct for the second time?
Correct the brief instead. That is where the fix belongs.
4  Has anything crept into a job's folder scope that I did not intend?
Look in the folder. Do not assume you know what is in it.

The Cowork Ready badge

Finish this lesson and the Cowork Ready badge is yours. It stands for something narrower and more useful than knowing your way around a product, which would be worthless anyway given how fast this one is moving. It stands for being able to hand over a whole job, define what finished looks like before it starts, keep the wrong material out of it, and review the result properly when you did not see it happen.

That last part is the one that will still matter in five years. The tools will keep changing. The features will get renamed and merged. The discipline of not approving work you have not understood outlives all of it.