5x1: The Systems That Get Better When Things Go Wrong | Wednesday, May 13th, 2026

by Monti Pace

The​ 5x1 newsletter​ is a concise and insightful resource around a simple concept: systems achieve goals.

sys·tem [ˈsistəm]
a set of things working together as parts of a mechanism or an interconnecting network.
a set of principles or procedures according to which something is done; an organized framework or method.

1 x Principle of Systemization

Nassim Taleb coined the term to name something English didn't quite have a word for. We have "fragile" — things that break under stress. We have "robust" or "resilient" — things that survive stress and return to their original state.

There's a third category: things that improve under stress, becoming stronger because of the stressor, not despite it. Bones under mechanical load. Muscles under resistance training. Immune systems trained by exposure. Resilient businesses during downturns.

This is anti-fragility — and it's the most underused concept in personal and business systems design.

We assume that in most personal and business systems is that stress is the enemy. The implicit goal is robustness: design the schedule, the routine, the process so it can withstand whatever the day throws at it. That's a defensive posture. It produces stability, but stability is its ceiling. Robust systems can't get better from being tested. They can only avoid getting worse.

Anti-fragile systems are different. They're designed so that the very thing that would break a fragile system feeds them. A business that learns from every difficult client gets sharper with every difficult client. A career built around small, bounded experiments gets information from each one — including the failures. A skill practiced under varying difficulty develops range that smooth practice can't produce.

The trick is that anti-fragility usually requires a barbell shape. Most of the system stays conservative — protected, predictable, robust. But a small portion is deliberately exposed to controlled stress, where the downside is bounded but the upside is open. The conservative part keeps you in the game; the exposed part is where the system actually improves.

Most people are designing for the wrong thing. Build the parts of your life and business that should be robust to be robust. But identify the parts where you actually want to grow, and stop protecting them from the stress that would teach them how.

1 x Systemization Quote

"Antifragility is beyond resilience or robustness. The resilient resists shocks and stays the same; the antifragile gets better." — Nassim Taleb

1 x Reflection Question

Most of us treat stress and disorder in our work and life as friction to minimize. But friction is also free information about where our systems are brittle. What's one persistent stressor you've been trying to eliminate — and what is it actually telling you about a system you've designed to be robust where it should be designed to grow?

1 x Personal System Idea

The Friction Conversation: Most people carry a low-grade backlog of conversations they’ve been postponing — the contractor whose work was sloppy, the friend who keeps cancelling, the colleague whose behavior you’ve been silently absorbing. Each one is small. Together, they accumulate. The avoidance gets heavier than the conversation would have.

Antifragility shows up here in a specific form: the system gets stronger only when you engage with the friction it would otherwise route around.

1. Once a week — same day, same time — initiate one previously-postponed conversation. The recurring practice is the system; the topic is incidental.
2. Pick by friction, not importance. The one you keep almost-bringing-up. That’s the signal.
3. Set the bar at initiating, not resolving. Your job is to put it on the table. The response is not your responsibility.
4. After, write 1–2 sentences in a running note: what you said, what they said, what you noticed.

The first three are hard. By the twentieth, you’ve built a capacity for hard conversations most people don’t have — and a relationship texture that doesn’t carry the weight of all the things never said.

Avoided friction compounds. Engaged friction strengthens.

1 x Business System Idea

The 1000 Nos Challenge (h/t @gracefullygabbie): Most outreach is built around minimizing rejection — perfect the cold email, only ask the most likely yes, qualify aggressively before pitching. The result is fewer rejections AND fewer surprising yeses. The 1000 Nos approach inverts the goal: count rejections as the win, treat each one as data, and let the volume produce the yeses no qualified-only approach would have surfaced.

Reframe what “success” looks like: a no this week is a yes for the system. Each rejection contains specific signal — about positioning, audience fit, the ask itself.

1. Pick one outreach domain for the next quarter: sales asks, podcast pitches, partnership proposals, big-ask emails. One only, so data accumulates in one place.
2. Set a no-quota, not a yes-quota. Aim for 25 rejections this quarter — roughly two per week. Track each in a doc with three columns: who, what you asked, the response (or silence).
3. Send. Each ask is bounded — single message, no follow-up loops eating your time.

Use AI two ways: to generate shot ideas (“Given my niche, offer, and current goals: [paste]. Give me 10 specific ‘shoot your shot’ opportunities this week — people, pitches, partnerships I’d usually disqualify myself from.”) and to track the cadence (“Here’s what I shot for this week: [paste]. Am I on pace for my no-quota? Where am I avoiding? What pattern do you see in what I’m not asking for?”).

No AI? Brainstorm shots with a friend; track the count in a notebook.

Implementation rule: the count is the system. Track it weekly. The yeses are a byproduct of how many nos you can stomach asking for.