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 with everyone who registered.

One of those is inside my control. One isn’t.

Mini Insight

You can’t control outcomes. You can control process. Track the second one.

Outcome goal: “Fill the Lab with 8 people.”
​Process goal: “Send all planned invitations.”

I hit 100% on my process goal. And 60% on my outcome goal. By the old scoreboard, I failed. By the new one, I did exactly what I said I would—and life happened.

This is the difference between “I failed” and “I did what I could, and the rest wasn’t up to me.”

Your Pattern Tweak (Process Goals Edition)

Each type has a different trap with process goals:

• Architect: Designs the perfect tracking system, never starts tracking.
• Surfer: Sets goals when energy is high, forgets them when it dips.
• Keeper: Tracks religiously but won’t adjust when it’s not working.
• Pilot: Commits to too many processes, tracks none.

The Opening

Because I was sick, the Lab didn’t fill.

That means I still have room for 2-3 people who want in.

I extended enrollment to Monday midnight EST.

If you’ve been on the fence—if you’re tired of outcome-based scorecards that make you feel like a failure every time life happens—this is your opening.

The Lab isn’t about perfect weeks. It’s about building a system that survives the imperfect ones.

Join us: https://curiochat.com/lab/

Excelsior,

Pierre/​
Founder, Curio Chat Academy

P.S. Process goals aren’t about lowering the bar. They’re about putting the bar where you can actually reach it—even when you’re running on 60%.