Skip to content

90-Day Cycle Map

This sheet manages one cycle; it is not a test of daily discipline. Keep one main question each week, one input, one output, and one transfer test. When health, work, or relationships change, adjust the plan's weight first. Do not include passwords, IDs, client data, sensitive health information, or unauthorised third-party details.

1. Cycle commitment

markdown
# 90-Day Cycle — YYYY-MM-DD to YYYY-MM-DD

Real context:
Deliverable by day 90:
Completion standard:
Three core pieces of evidence:
Weekly time and boundaries:
What must be reduced or paused:

2. Day-one baseline

ItemCurrent evidenceLargest barrierPlanned treatment
What I can do independently
Situation where I will use it
Materials, tools, and people available
Sleep, energy, and responsibility boundaries

Keep one sample made without AI doing the task: a recording, short text, reading reconstruction, code, presentation, or real conversation note.

3. Gates for three phases

PhaseDatesQuestion to answerEvidence to enter the next phase
CalibrateDays 1–14What exactly am I training, and what is the bottleneck?Baseline, three error categories, one stable time slot
StackDays 15–56Which action is becoming stable under which conditions?At least four comparable outputs and one external feedback
ShipDays 57–90Can a new listener, topic, or user still use the result?Independent, revised, and real-delivery versions

Without evidence for a gate, do not raise difficulty automatically. Shrink the task or repair prerequisites first.

4. Twelve weekly questions

WeekOne question onlyInput evidenceOutput evidenceFeedback/transfer
1
2
3
4
5
6
7
8
9
10
11
12

Write an observable question such as “Can I explain project risk in English without a script and handle one follow-up?” Do not write “be better this week”.

5. Evidence chain

DateEvidence card/toolLocation keptResult or errorNext variable
Listening / Reading / Speaking / Writing / Life Practice

Chat logs, playback time, and check-in screenshots are process traces. Key judgments should return to artifacts, recordings, reader/user feedback, and performance under a new condition.

6. Interruption and recovery

markdown
Interruption fact (no character judgment):
Main resistance: time / difficulty / energy / environment / responsibility
Task reduced to:
Smallest output possible within 24 hours:
Work I will not repay:
Review date:

Do not stay up late to repay missed work or rewrite the 90 days after one failure. When the same barrier appears three times, change the system condition instead of demanding more force.

7. Day-ninety review

markdown
Final delivery:
What genuinely changed from the baseline:
Errors that still recur:
What a real reader/user said:
Cost that proved unsustainable:
One habit to keep next cycle:
One entry point to stop next cycle:

Related chapter: 90-Day Action Plan: Return Your Life to Yourself

正文 CC BY-NC 4.0;站点与工具代码 MIT。