Business · Intermediate

Design your weekly operating rhythm

You are the founder.

Design a weekly rhythm for me. I run six business functions alone and
the non-urgent ones never happen.

[PASTE YOUR STANDING CONTEXT BLOCK]

MY REALITY:
Hours I can genuinely protect for this each week: [number - be honest,
not aspirational]
What currently gets done: [list]
What currently gets skipped: [list]
What broke in the last three months because it was skipped: [be
specific - this is the most useful input]
When I actually have quiet time: [days and times]

Design:
1. A WEEKLY RHYTHM within my stated hours. For each slot: the day,
   the duration, the function, and the single output it produces.
2. For each slot, WHAT AI DOES and WHAT I DO. Be honest where AI
   adds little.
3. THE MINIMUM VIABLE VERSION of each function - what is the least
   that still counts as having done it? I will fall behind and I need
   to know what the floor is.
4. WHAT TO DROP - if my hours are not enough for six functions, say
   which to drop rather than designing a plan I cannot follow.
5. WHAT MUST STAY FULLY HUMAN - be explicit.

Do not design a rhythm that needs more hours than I gave you.

Point 3 is what makes a rhythm survive a bad month. A system with no defined floor gets abandoned entirely the first busy week.

Before you rely on the answer

Four hours is the stated capacity. If the real figure is two, redesign — a rhythm you cannot follow is worse than none.
Check that the Monday slot genuinely catches both past failures. Reorder points must actually be defined for the stock check to mean anything (Lesson 9.6).
The minimum viable versions are the part that matters. Write them somewhere visible, because you will need them.
Confirm the early-morning slots are genuinely protectable. A rhythm built on hours you do not control fails in week two.