Mitchell Growth System← All documents

Normal, field, and minimum-viable day modes.

14 — Daily Playbooks (Three Modes)

Prepared 2026-07-22. Figures verified as of this date unless marked otherwise.

Three day-modes so Mitchell never improvises a day's structure. Pick the mode by 8:00 AM using the decision rule below. All outbound calls/texts inside 9:30 AM–6:00 PM. Reserved-personality rules apply in every mode: prep before every call, recovery after every high-social block, analytical anchor early.


Mode decision rule (run at 8:00 AM, takes 60 seconds)

Ask in order — first "yes" picks the mode:

  1. Is there a scheduled open house, office visit tour, workshop, or community event today?FIELD DAY
  2. Are ≥2 live files at critical stages (docs due, conditions, closing this week) OR is energy honestly ≤4/10?MINIMUM VIABLE DAY (Say it out loud in the debrief later — no shame, no drift: MVD is a tool, not a failure. But 3+ MVDs in one week triggers a Version-B week discussion at Friday's pipeline review, per file 13.)
  3. OtherwiseNORMAL DAY

Tie-breaker: field commitment beats MVD triggers only if the field event involves another person who is counting on him; otherwise reschedule the field event, run MVD.


MODE 1 — NORMAL DAY

The file-13 baseline day. Skeleton:

Time Block
7:30–8:00 Morning routine: rates, scenario inbox first (SLA), top-3, mode check
8:00–9:00 Analytical anchor: product study + role-play, or live files (per weekday, file 13)
9:00–9:30 Call prep — never dial cold
9:30–11:00 Outreach sprint (prepped, 60–90 min, then stop)
11:00–11:30 Recovery + logging
11:30–12:15 Lunch
12:15–1:45 Scenario Desk / live-file block (analytical mid-day anchor)
1:45–3:15 Agent conversations / borrower calls / content batch (per weekday)
3:15–4:15 Second-priority block + buffer
4:15–4:45 Debrief (template below)

The 3 non-negotiables: 1. Scenario inbox checked by 8:00 AM and every request acknowledged ≤1 business hr, brief ≤4 business hrs. 2. One completed outreach sprint (prepped, logged). 3. Every live file touched and statused.

What gets dropped first (in order): golf/chess/community extras → content batch → AI/system work → second conversation block → new-outreach portion of the sprint (follow-ups survive). Never dropped: the 3 non-negotiables, debrief, recovery blocks.


MODE 2 — FIELD / OPEN-HOUSE DAY

For Saturdays with open houses, weekday office-visit tours, workshops, or chamber events. High social cost — the day is built around ONE main field block, bracketed by prep and recovery, with everything else lightened.

Time Block
7:30–8:00 Morning routine: scenario inbox, rates, mode check
8:00–9:00 Live files to clean state (nothing chases him in the field)
9:00–10:00 Field prep (non-negotiable): research every person/listing he'll meet — price points, DPA eligibility angles, two questions per person; pack approved flyers (his own only — RESPA). Field talk track = process, DPA program structure, tax anatomy, and "I'll send you the compliant worked example" — NO live rate/payment quoting in the field (red-team M5.3): payment illustrations exist only through the F3 approved-assumptions process (file 18)
10:00–10:30 Drive / transition
10:30–1:00 Field block 1 (open house #1 / office tour / workshop). Goal: be useful, collect one scenario ask per stop
1:00–1:45 Lunch ALONE — deliberate recovery, no calls
1:45–3:15 Field block 2 (second open house / second office) — max 2 field blocks/day, ever
3:15–3:45 Drive / decompress
3:45–4:30 Log everything while fresh: names, files promised, follow-ups with dates; send same-day thank-you texts/emails (before 6:00 PM)
4:30–4:45 Debrief (short)

The 3 non-negotiables: 1. Field prep block completed BEFORE the field block — no walking in cold. 2. Scenario SLA still honored (acknowledge from phone; brief may use the 4-hr window; if received after 2 PM in the field, ack now + deliver next business morning, flagged as such). 3. Same-day logging + thank-yous — field value evaporates if not captured within hours.

What gets dropped first: outreach sprint (the field IS the outreach) → content → learning block → all system work. Live files got their hour at 8 AM; anything new waits unless closing-critical.


MODE 3 — MINIMUM VIABLE DAY (low-energy or file-heavy)

Two triggers, one skeleton: protect the promises already made, shed everything discretionary, end early without guilt. On file-heavy MVDs the freed time goes to files; on low-energy MVDs it goes to rest.

Time Block
8:00–8:30 Morning routine: scenario inbox, rates, declare MVD (note trigger: energy vs files)
8:30–10:30 Live-file block: every active file advanced and statused; this is the day's spine
10:30–11:00 Recovery
11:00–12:00 Scenario Desk: honor SLA on anything inbound; no drills
12:00–1:00 Lunch, away from desk
1:00–2:00 Committed touches only: follow-ups already promised to a named person today + anything time-fatal (rate-lock expirations, condition deadlines). No new outreach
2:00–2:30 Reschedule everything else honestly: move (don't delete) dropped blocks to specific future slots; notify anyone affected
2:30–2:45 Debrief (short) — then STOP. A real stop, not "monitoring email until 6"

The 3 non-negotiables: 1. Scenario SLA honored (ack + brief, or ack + explicit revised delivery time communicated). 2. Every live file safe: nothing expires, nobody is waiting on him unknowingly. 3. Promises kept or renegotiated the same day — dropped ≠ ghosted; a 1-line "moving our call to Thursday 10 AM" text protects the reputation the whole plan runs on.

What gets dropped first (i.e., pre-dropped by the mode): new outreach, content, learning, AI/systems, community — all of it. The MVD keeps only service and promises. The debrief is never dropped, because MVD frequency is itself a KPI (3+/wk → Version-B conversation).


End-of-day debrief — 10 minutes, every mode

Template (keep as a running doc or scorecard tab; one entry per day):

DATE: [date]   MODE: Normal / Field / MVD (trigger: ____)
1. Non-negotiables hit?  [ ]#1  [ ]#2  [ ]#3  — if any missed: why + tomorrow's fix
2. Numbers: dials __ / conversations __ / scenarios in __ / briefs out (in SLA? Y/N) __ /
   apps moved __ / follow-ups completed __ of __ due
3. Best moment (what worked — do more): ____
4. Grind moment (what dragged — change or drop): ____
5. Tomorrow's top-3 (written now, not at 7:30 AM): 1)__ 2)__ 3)__
6. Anything for Friday's pipeline review or the compliance log? ____
Energy at close (1–10): __

AI-assisted debrief (optional, 5 of the 10 minutes): paste the day's entry into the standing Claude project ("Mitchell Daily Debrief" — see ai_stack.md; no borrower PII, initials only, per the Never-Automate/AI SOP) with the standing prompt:

"Here's today's debrief. In under 150 words: (1) one pattern across the last 5 entries I should notice, (2) one thing to do differently tomorrow, (3) challenge one assumption I'm making. Be direct."

Weekly, the seven entries feed the Saturday after-action review — the AAR reads the debriefs, so the AAR takes 45 minutes instead of two hours.

PreviousSteady-State Weekly CalendarNextRealtor Targeting Strategy