Home / A day with it

Your day, week and month with it

Heavy thinking in the morning, routine during the day, nothing heavy in the evening. The difference: the morning analysis is already done when you sit down at 09:00.

Morning ritual
15-30 min
End of day
5 min
Replies
in batches
Status by hand
never
On this page

The morning starts with 15-30 minutes of reading instead of going through every chat by hand. Each meeting prep is already there when you need it, and the day closes in 5 minutes. Over the week, preps and reports stop being blocks in your calendar.

The day

Before 09:00: it works, you do not

Yesterday’s chat lands in Threads with statuses. The daily work report arrives: what happened yesterday across calendar, meetings, threads, tracker and chat, and a plan for today. Mail is collected, and reply drafts are written for everything waiting on you.

09:00: the morning ritual, 15-30 minutes

  1. Open Control Tower.
  2. Read the daily report. This replaces going through everything by hand.
  3. Open the threads with drafts. 3 moves per thread: send it (with your edits), turn it into a ticket, or defer it and write the decision into the page. Do not change the status by hand: the next collector pass moves it by the reply.
  4. Inbox in 2 minutes.
  5. Today, This Week and Overdue: pick the top 3 for the day. It is a menu, not a contract. You see the whole load together: every project, company matters, personal. If it does not fit, move something right away.
  6. Red signals: new errors from the prep, critical risks, deadlines.

Before each meeting

The prep is already in Reports about 55 minutes before: who works on what, board movement, blockers, chat topics, action items, errors over the last 24 hours, and an empty block for your own notes.

During the day: replies in batches

  • Replies in 2 or 3 batches a day. The drafts exist, so a batch takes minutes.
  • Artefacts as you go: a decision into Decisions (1 sentence, date, source), a state change into the config (the short file about the project), a risk into Risks.
  • The client asks for “just a small extra”? change-request sorts it: A is logged even when free, B costs hours, C touches data, money or security and is always a change request. At the end of the month the Extras Log shows how much goodwill went beyond scope.
  • After a meeting: drop the link, get a bilingual report with action items on the meeting page.

End of the day: 5 minutes, no thinking required

Done to Done. Inbox triage. A line on tomorrow’s top priority. No analysis: the morning report will do that.

The week

DayAutopilotYou
Mondaytopics, weekly overview, planning prepRead the weekly overview: it is the state of the world. Set the focus of the week
Tuesdaystatus prepStatus call: progress, blockers, questions
Wednesdaydaily onlyA day for deep work: investigations, documentation, strategy, people
Thursday1-1 prep, stability scan at night1-1 with the client PM: risks, decisions, a preview of next week
Fridayboard health, review prepRead the stability scan, set defect priorities. Review: done list, demo. No deploys on Friday

Preps and reports are no longer blocks in your calendar. The weekly overview becomes an input, not an output. The Friday review gets a clean board without a manual pass.

The month

WhenAutopilotYou
The 1stvelocity, client sentiment, a memory digest per project, an audit of the skillsRead the digest (the best start for the monthly report), check whether the client is cooling off, fix any skill drift
The 2nda health check per project: 8 areas, red, amber or green, with evidenceRead the top 3, decide on risk candidates
The 1st to the 5thThe monthly client report: 1 sentence to start it, proofread, send
The 15thmid-month sentimentCheck the trend against the 1st
Any dayUpdate the config the same day the state changes

Quarterly

  • Review the skill library: what has not run for 90 days, what to freeze or rename. Re-check date-stamped facts.
  • Review the cultural profile of the client team.
  • Revise the schedule against the real meeting calendar.
  • Archive finished projects with a proper closure.

If your project is smaller

No error monitoring or repositories? The rhythm shrinks to collectors, Threads, reply drafts, meeting preps, the weekly overview and Decisions. The minimal autopilot is 3 tasks: chat or mail sync, a meeting prep, the weekly overview.