Case Study 1 — Rebuilding Kwabena's Week: Same Food, Different Structure

Kwabena Asante is an illustrative composite. ⚠️ The failure modes, the rearrangement and the component system are drawn from patterns that recur constantly; the person is constructed.

Setup

He had been meal planning for about two years, on and off. ⚠️ Mostly off.

"I do it for three or four weeks, it starts going wrong, I stop, and then a couple of months later I decide to be organized again."

⚠️ That cycle — plan, decay, abandon, restart — is the actual pattern, and it is not what most planning advice addresses. Most advice assumes the problem is not having a plan.

His constraints, stated honestly:

⚠️ The last row is the one he had never written down.

The diagnosis session

⚠️ Not "here's a better plan." We went through the failed week line by line and asked one question of each night: was this predictable on Sunday?

⚠️ Four of five, predictable. And his partner's two shift nights had not been accounted for at all, which is where the pak choi and half the spinach went.

Kwabena's reaction:

"So I've been writing a plan for a week that doesn't exist."

⚠️ Yes. And enjoying cooking made it worse, because it made the plans more ambitious.

The rebuild

⚠️ Same seven days. Same amount of cooking. Almost the same food.

Step 1 — The map (§31.3)

⚠️ Two people, not always both. One genuinely low night. One zero. Three high.

Step 2 — The slots filled in order (§31.15)

Step 3 — The Sunday session (§31.8)

⚠️ About 100 minutes, mostly unattended:

Roast chicken (deliberately oversized) · one tray roasted vegetables · a pot of rice · a pot of lentils, plain · yoghurt-lemon-garlic sauce · a vinaigrette · a slaw.

⚠️ Everything unseasoned. Everything stored separately.

The week that resulted

⚠️ Seven of seven.

⚠️ And the waste that week: a quarter of a cabbage and some parsley. Roughly £1.50.

⚠️ What actually changed

Kwabena's own summary, and it is more accurate than most:

"I didn't cook less. I cooked about the same. I just stopped cooking at the wrong times."

💡 Aha moment. ⚠️ Total cooking time went UP by five minutes.

This is the finding that surprised him, and it is why the chapter frames the problem as structure rather than effort.

⚠️ He was not doing too much cooking. He was doing it in the wrong slots — the long cook on a Monday, the new recipe on a Friday, the ambitious plan on a night his partner wasn't home.

Rearranging the same work fixed almost everything.

What broke later, and what he did about it

⚠️ Because a case study that ends at week one is not honest.

Week 4: ⚠️ He skipped the Sunday session — a friend visited. The week partially collapsed: four of seven.

⚠️ What he'd learned by then: he did not abandon the system. He ran the bad-night meal twice and used repertoire meals for the rest.

"Before, that would have been the end of it. This time it was just a bad week."

⚠️ Which is Chapter 10 §10.4's adherence finding, and it is the actual test of a system: not whether it survives a good week, but whether it survives a bad one.

Week 9: ⚠️ Component fatigue. He was bored of the same six components.

⚠️ The fix was rotation, not abandonment: the STRUCTURE stayed — a grain, a protein, a roasted tray, a quick vegetable, two sauces — and the CONTENTS rotated. Rice became couscous became potatoes. Chicken became beans became baked tofu. The yoghurt sauce became a peanut sauce became a salsa.

⚠️ The system is the slots. The food in them is meant to change.

Month 5: ⚠️ Still running. He had added four meals to his repertoire, all from Saturday nights.

Analysis

1. ⚠️ Four of five failures were predictable on Sunday. Including the one that mattered most: his partner's shift nights, which had never been written down.

2. ⚠️ Enjoying cooking made it worse. Competence produced ambition, ambition produced novelty, and novelty on a Friday produced the pub.

3. ⚠️ Total cooking time went UP. The problem was never effort. It was slot allocation.

4. ⚠️ The bad-night meal was the highest-yield single change — it removed two takeaway nights and, more importantly, removed the mechanism by which one bad night ended the whole plan.

5. Waste fell from ~£14 to ~£1.50 ⚠️ because components share ingredients and seven unrelated recipes don't.

6. ⚠️ The system survived a skipped week — which is the only test that matters (Chapter 10 §10.4).

7. ⚠️ Component fatigue arrived at week nine and was solved by rotating contents, not by abandoning structure.

8. And the new recipes didn't disappear. ⚠️ They moved to Saturday, where he could enjoy them — which is a better outcome for someone who likes cooking than the plan that put them on a Friday.

Discussion Questions

1. ⚠️ "I've been writing a plan for a week that doesn't exist." Why is that so common? What makes Sunday-evening self so optimistic about Wednesday-evening self?

2. ⚠️ Total cooking time went up and the outcome improved. What does that suggest about how dietary advice is usually framed? Where else in this book has "more effort" been the wrong diagnosis?

3. His partner's shift nights had never been recorded. ⚠️ How much household planning failure is actually a communication failure? Design the fix.

4. ⚠️ Enjoying cooking made his plans worse. Is that a general pattern? Who else does competence make worse at something?

5. ⚠️ Week 4 was a bad week and the system survived. What specifically made the difference? Could that be designed into other kinds of plan?

6. Component fatigue at week nine. ⚠️ Is rotation a real solution or a delay? What would you expect at month twelve?

Your Turn

⚠️ Do the diagnosis before the rebuild. That order matters.

Step 1 — Reconstruct your last failed plan. ⚠️ Not this week's — a real one that fell apart.

⚠️ Count the "yes" column. Kwabena's was four of five.

Step 2 — ⚠️ Find the row you never wrote down.

Whose schedule, which commitment, or what constraint was missing from the plan entirely? ____

⚠️ For Kwabena it was two shift nights a week. There is usually one of these.

Step 3 — Map next week properly (§31.3), ⚠️ including everyone who eats.

Step 4 — ⚠️ Fill the slots in the order in §31.15. Zero night first. High night second. The night after it third.

Step 5 — ⚠️ Run it, and count.

Nights as planned: ____ / 7 Total cooking time: ____ minutes ⚠️ Longest weekday cook: ____ minutes

Step 6 — And then plan for the week it goes wrong.

⚠️ "When I skip the session, my fallback is: __"

Kwabena's answer was "bad-night meal twice, repertoire for the rest."

⚠️ A system that only works when you do it properly is not a system. It is a good week.