What the customer receives

Thabo Mokoena example advisory memo

This Organization does not sell a long report. It sells one person's judgment on one question, and the useful part is usually that the problem is not where it shows up.

A complete sample document, written the way Thabo Mokoena writes one. The customer, the numbers and the sources are illustrative.

Thabo Mokoena Advisory memo

Decision Call · USD 190

The Monday problem is a Thursday problem

60 minute call, 26 January. Reviewed and signed off by Thabo Mokoena on 28 January.

Prepared for
Deborah Achebe · Operations Director, Pennant Print, 68 staff
Reference
JW-M-30128
Issued
28 January 2027
Settlement
$OPSADV · USDC on Base

You asked how to stop Monday overruns. Mondays overrun because Thursday's press schedule is built before Friday's proofs come back, so every Monday starts with a plan made on incomplete information two working days earlier.

Move the scheduling meeting from Thursday to Friday afternoon

Eleven of the last thirteen Monday overruns trace to a job that was scheduled on Thursday and changed by a proof returned on Friday. Moving the scheduling meeting three hours later in the week costs nothing, needs no system and no headcount, and on the record would have prevented nine of the eleven.

13 Monday overruns in 6 months
11 Trace to a Friday proof
9 Would have been prevented
USD 0 Cost of the fix
1

The question

What was asked, and what was reviewed

As you put it: "Mondays are chaos. We have tried starting earlier, adding a shift and a new scheduling board. Nothing has worked."

ReviewedSource
Press schedule and actuals, 26 weeks Supplied
Job records for 13 overrun Mondays Supplied
Proof return timestamps Supplied. This is where it was
The scheduling meeting agenda and attendees Supplied
Overtime records Supplied
The three previous attempted fixes Discussed on the call
2

The chain

What actually happens

  1. Scheduling meeting sets next week's press plan

    Press time allocated job by job, for the whole week.

  2. Proofs go out to customers

    Typically eight to twelve jobs.

  3. Proofs come back

    Median return 15:40 Friday. About a third carry changes.

  4. Nobody reschedules

    The meeting has happened. Changes are noted and absorbed.

  5. Press starts on a plan made on Thursday

    Two or three jobs are not what the plan assumed.

  6. The day is rebuilt while it runs

    Which is what everyone experiences as the Monday problem.

3

Evidence

The thirteen, checked individually

Cause of the Monday overrunCountWould a Friday meeting have caught it?
Proof returned Friday with changes 9 Yes
Proof not returned at all by Friday 2 Yes. It would have been rescheduled
Stock shortage found Monday 1 No
Press breakdown 1 No

Eleven of thirteen originate on Friday. Two are genuinely Monday problems and no scheduling change addresses them, which is the right expectation to set before making the change.

4

Next

What to do

  1. Move the scheduling meeting to Friday 16:00. After the median proof return, before the end of the day.
  2. Keep the Thursday slot for two weeks as a provisional plan, so the change is additive rather than a leap.
  3. Chase outstanding proofs at Friday 12:00, as a standing task with a named owner. It is the other half of the fix.
  4. Track the same 13-cause breakdown for eight weeks. If Monday overruns do not fall by roughly two thirds, the diagnosis was wrong.
  5. Do not add anything else at the same time. If you change three things, you will not know which one worked, which is what happened with the previous attempts.
JW-M-30128 · reviewed by Thabo Mokoena, 28 January 2027 · $OPSADV · 28 January 2027 Thabo Mokoena · $OPSADV
The order behind this document
Format

A short memo from a scoped call: the question, where the failure actually starts, and the cheapest intervention.

Back to Thabo Mokoena →