Path: A weekly AI office routine (email · notes · update)

Goal: Fold mail, notes, and the weekly update into a short repeatable loop—each block has an honesty boundary.

Best for: Knowledge workers who want fewer open loops, not more AI toys.

A light weekly rhythm: mail, notes→actions, Friday update—with redact habits.

Why Mon → meeting → midweek → Fri

Monday clarify fuzzy asks; right after meetings extract owners; midweek polish a few risky emails; Friday close with a short sync.

Outcome

By Friday: clearer outbound mail, action lists that do not invent owners, and one skimable status update. AI drafts; you own commitments.

Why beginners skip this

A weekly routine without fixed slots collapses mail/notes/status into Friday panic—Mon → post-meeting → midweek → Fri.

Suggested weekly rhythm

Scene: one ops week

Priya’s Monday inbox has “can you handle the launch stuff?” She runs Pack D5, gets five clarifying questions, and avoids building the wrong deck. After Tuesday’s standup she extracts actions—docs owner stays Unclear, not a fake name. Friday update is Yellow with three asks her manager can answer in Slack.

Live task this week (not a toy): apply this guide's Goal — Wire existing craft guides into a Monday–Friday rhythm you can keep without living in chat all day.
Fill with your real artifact names/files. Constraints: no invented facts; label Unknowns; stop before send/delete/pay.
Return the working prompt + one pass/fail check I can mark in a minute.

Post-meeting Pack D1 on real notes:
“Ship slipped; Maya confirms Friday; budget approved for two contractors; docs owner unclear.”
→ Decisions include budget approval; Actions list Maya; docs stays Open/Unclear—no invented owner.

Rules

• Do not invent owners or deadlines in meeting extraction.
• One Project (or folder) named “Office weekly” so context does not scatter.
• Skip agents/automation until this manual rhythm feels boringly reliable.

Close the loop

Write one line: next time the weekly routine collapses into Friday panic, I refuse empty slots.

Wed office: raw standup paste → Decisions / Open / Unclear.
No invented owners. 25-minute timer. Save winning prompt.
Context: real workstream this week (Asia/Shanghai). Name actual files/people.
Constraints: no invented metrics/owners/prices; label Unknowns; stop before send/delete/pay.
Done check: I can mark pass/fail in one minute on the output.

Live artifact this week for: Wire existing craft guides into a Monday–Friday rhythm you can keep without living in chat
Name real files/people. No invented facts; label Unknowns; stop before send/delete.
Return working prompt + one pass/fail check I can mark in a minute.

Red flag

A weekly routine without fixed slots collapses mail/notes/status into Friday panic—Mon → post-meeting → midweek → Fri.

Save this card

Card: Monday clarify · post-meeting extract · Friday sync. Tick the beat before the model run.

Wear-test: show your Save card to a teammate for thirty seconds—if they cannot restate the refuse line, tighten the card tonight and date it (Asia/Shanghai).

Before you start

Create a 25-minute calendar block titled path-office-weekly-routine. Open the live artifact for “Wire existing craft guides into a Monday–Friday rhythm you c”—bookmark alone does not count Keep the live artifact visible the whole time. If you only have a blank box, stop and fetch the real job first

How to use this week

This week run one real office job in each Monday → post-meeting → midweek → Friday slot; leave an artifact before checking off.

Close the week by quoting aloud the refuse line you actually used once. If you cannot, rerun Practice now and date the pass/fail (Asia/Shanghai).

Pitfalls

Practice now

Shutdown Fri: Friday Asia/Shanghai clear open loops list (Asia/Shanghai).

Theme day: assign one AI theme per weekday block (Asia/Shanghai).

Monday pin: pin this week’s refuse list on Mon Asia/Shanghai (Asia/Shanghai).

Friday close: 10-min AAR block on Friday Asia/Shanghai (Asia/Shanghai).

Block title: calendar block titled with the guide stem (Asia/Shanghai).

Office-routine drill: schedule one Asia/Shanghai block this week for AI assist + refuse list review (Asia/Shanghai).

Thin-spot drill: rewrite the Save card with real nouns from your work (repo, doc, inbox). Generic placeholders fail the drill.

Tonight map Mon → post-meeting → midweek → Fri slots and park one real office job in each; leave an artifact before checking off.

Habit stamp: after one live pass, write the refuse line you actually used on the Save card and date it (Asia/Shanghai).

One sentence takeaway

Mon → post-meeting → midweek → Fri four slots; leave an artifact each.

Next

Email · Notes · Update · Pack D · First 7 days

路径：一周办公 AI 例程（邮件 · 纪要 · 周报）

目标： 把一周办公里的邮件、纪要、周报收成可重复短循环：每块都有诚信边界。

适合： 想少开会、少编造、周五还能发出去周报的人。

周五十二分钟周报：状态色加不超过一百五十字；表里指不出的百分比一律删。

为什么是 周一 → 会后 → 周中 → 周五

周一先澄清含糊需求；会后立刻提炼负责人；周中打磨少数有风险的邮件；周五短同步收口。

达成效果

到周五：更清楚的外发邮件、不编造负责人的行动清单，以及一份可扫读的状态同步。AI 起草；承诺由你负责。

为什么新手跳过

收藏路径标题像进步；本周没有真产物，第七天仍是空。

建议周节奏

场景：一个运营周

Priya 周一收件箱里有句「发布的事你看着办？」她跑包 D5，得到五个澄清问题，避免做错幻灯片。周二站会后提炼行动：文档负责人留在「不明确」，没有假名字。周五周报标黄，三条求助经理能在 Slack 里直接答。

周五 12 分钟周报：
1) 把进展、风险和求助贴进包 D2。
2) 强制带状态色，全文 ≤150 词。
3) 删掉模型添上的、你在表里指不出依据的百分比。
4) 发送。

会后用包 D1 处理这份真实记录：
「发版推迟；Maya 周五确认；两个外包预算已批；文档负责人不明。」
→ 决定里只写预算已批；行动项有 Maya；文档负责人留在未决：绝不编造负责人。

规则

• 会议提炼不编造负责人或截止日期。
• 用一个名叫「办公周常」的 Project（或文件夹），避免上下文散落。
• 手动节奏稳到无聊之前，先别上智能体/自动化。

闭环

写下一行：下次周常挤成周五崩溃，我拒绝再空槽。

红旗

周常没有固定槽，邮件纪要周报会挤成周五崩溃；周一→会后→周中→周五按槽。

保存这张卡

记下：周报模板名 + 「不编百分比」红线 + 会后纪要三栏（决定/行动/未决）。

开始前

准备好本周真实进展/风险/求助素材，不要凭空开写。

本周怎么用

本周按周一→会后→周中→周五四个槽各跑一件真办公活；每槽留下产物再打勾。

常见坑

现在就练一次

今晚就练：按周一→会后→周中→周五四个槽各跑一件真办公活；每槽留下产物再打勾。

一句话带走

周一→会后→周中→周五四槽；每槽留下产物。

下一步

邮件 · 纪要 · 周报 · 包 D