Get the Cowork Day-One Playbook

Three weeks of using Claude Cowork wrong. Pasted screenshots every session. Re-explained my role every morning. Fought it when it drifted. Then I figured out — Cowork is not a chat box. It is a shared operating system. This is the 8-page Day-One Playbook. RULE 01 STOP TREATING COWORK LIKE A CHAT BOX — upload the brief / brand voice / customer list ONCE; the workspace inherits them on every turn; pasting is amateur, uploading is operator. RULE 02 NAME PROJECTS LIKE OPS TICKETS, NOT TOPICS — vague names ("pricing", "marketing", "website") produce vague output; sharp scoped names ("Q2 Pricing Teardown — Enterprise Plan", "Black Friday Email Sequence — Cart Abandoners", "Landing Page Rewrite — Cold Traffic") are free system prompts; the project name is the scope Claude reads on every turn. RULE 03 PIN ONE OPERATING CONTEXT DOC PER PROJECT — the single highest-leverage move; 5 lines (WHO I AM · WHAT WE SELL · VOICE · QUARTER GOAL · CONSTRAINTS) pinned at the top of the project kills the "remind-me-of-context" tax forever; this one doc is the difference between Claude-as-intern and Claude-as-operator. RULE 04 ITERATE ON THE ARTIFACT, NOT THE CHAT — ask for the final deliverable up front ("write me the email as an artifact"), refine in the artifact panel directly ("tighten the second paragraph", "change the CTA"); chat = drafts, artifact = ship. RULE 05 BRANCH, DON'T BACKTRACK — when Claude veers wrong, most people argue and bury the mistake deeper in the thread; operator move = fork from the last good message, run two directions in parallel, pick the winner; the killer Cowork feature nobody uses. Plus the DAY-ONE CHECKLIST — 10 numbered actions to graduate from chat-box-user to Cowork-operator in 1 week. Full credit to the day-one mistakes that earned every rule on this page.

By submitting, you'll be subscribed to the Hyperautomation AI Report newsletter — one practical AI email per week. Unsubscribe anytime.

Free. No spam. Unsubscribe anytime.