[CCA] Saturday Reset - Issue #016 - I'm a little terrified it might actually work


Hi Reader,

Monday, a few people start a program I’ve spent two years designing.

I’m terrified it might actually work.

What I Learned Building It

The hardest part wasn’t creating content. It was cutting it.

I crafted 47 modules (yeah, I know…). I cut it to 12.

I wrote a 200-page workbook. I cut it to 40 pages.

I perfected “optional deep dives” that were actually “required reading I was too insecure to call required.” I cut those too.

Simplification is harder than addition (much harder for an architect, my type). Every cut felt like loss. But every cut made the system more survivable.

Mini Insight

The best program is the one you finish—not the one with the most content.

I kept asking: Would this work when someone’s kid is sick? When they just got laid off? When they’re running on four hours of sleep?

If no, cut it.

The Lab isn’t designed for peak performance. It’s designed for real life.

The Bet

I’m not betting on the curriculum.

I’m betting on the few very motivated people who said yes. They’re not here because they think they’ll finally find discipline. They’re here because they’ve tried discipline. It didn’t work. They’re ready to try fit instead. That’s the real experiment: what happens when you stop trying to fix yourself and start designing around yourself?

What I Don’t Know Yet

Whether restart time actually drops.

I’ll find out. And I’ll tell you.

Try-This-Now (≤5 minutes)

Look at your own system—or the one you’re trying to build. Ask: “Can someone actually finish this?”

Not “is it comprehensive?” Just: can a tired person on a hard week actually use this? If no, what could you cut?

Stop—this counts.

Your Pattern Tweak
Here’s a tweak for each type—find yours:

  • Architect: Cut 30% and see if anyone notices.
  • Surfer: Add one anchor—one thing that runs even when you don’t feel like it.
  • Keeper: Add one “survival version” of your routine.
  • Pilot: Write your promises down somewhere you’ll actually see them.

(Don’t know your type? Reply “quiz” and I’ll send you the link.)

And yes, you are one of the people I am “betting” on—looking forward to meeting you on our on-boarding call early next week. In the meantime, feel free to reach out with any questions.

Excelsior,

Pierre/
Founder, Curio Chat Academy

You're receiving Saturday Reset because you're ready to stop borrowing other people's systems. This is your weekly reminder that productivity is a practice, not a project.

40 High Park Ave., Apt. 1404, Toronto, ON M6P 2S1
Unsubscribe · Preferences

Curio Chat Academy

Stop collecting abandoned productivity systems. Saturday Reset delivers pattern-based insights for building YOUR system. For serial system-hoppers ready to work WITH their brain instead of against it.

Read more from Curio Chat Academy
Curio Chat Academy - Saturday Reset #018

Hi Reader,David’s system worked perfectly. Calendar blocked. Routines honored. Twenty years of discipline. His daughter moved 3,000 miles away anyway. The System That Worked David did everything the productivity books told him to. Morning routine: 5 AM, journaling, gym, inbox zero by 8. Weekly review every Sunday. Quarterly goals posted on the fridge. His boss loved him. Projects came in early. His calendar was immaculate. But his daughter Emma stopped inviting him to things. His wife started...

Curio Chat Academy - Saturday Reset #017

Hi Reader,I caught a nasty bug this week. Not the kind I could debug.🐜 The flu hit hard. I spent most of the week in minimum day mode—doing only what absolutely had to happen and letting everything else slide. Here’s what I learned: my system held. What Minimum Days Look Like I completed 60% of my planned intake calls for the Lab. The other 40% got notified & with their permission, we rescheduled. I didn’t fill the Lab. But I sent every invitation to the lab I planned to send and was in touch...

Curio Chat Academy - Saturday Reset #015

Hi Reader,My book “Restart Time” has a new appendix (#11!). It covers monthly, quarterly, and yearly planning—the maintenance cycles that keep a system running after you build it. Here’s how it came about. The Borrowed Systems For years, I used other people’s approaches to yearly and quarterly planning. Annual reviews. 12-week years. OKRs. Vision boards. Quarterly themes. They all work. I’m not knocking them. But they were never a perfect fit for what I was building: a system designed around...