5x1: Stop Designing Systems for Someone You're Not | Wednesday, September 16th, 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

When we design a system for ourselves, most of us design it for a version of us that doesn't exist. A version with unlimited working memory, perfect information, infinite attention, and no emotional weather. A version that, after a long day, can still run the optimization algorithm we baked into our morning routine.

Then we wonder why the system fails.

Economist Herbert Simon coined the term "bounded rationality" in the 1950s. Our decision-making is limited by the cognitive capacity we have, the information we can access, and the time available to use it. We don't optimize. We find the good-enough answer and move on, because perfect optimization is impossible in real life.

This isn't a flaw to be overcome. It's a constraint to be designed around.

The systems that actually hold up over time aren't the ones that demand more cognitive bandwidth than we have. They're the ones that work within our bandwidth — using smart defaults, environmental cues, and structural guardrails to make the good-enough choice the easiest one available. Self-discipline is expensive and runs out. Good design is free, and it runs in the background.

If a system you've built keeps failing in the same place every time, the failure point isn't your character. It's a system that's designed to operate in a way that doesn't match your reality.

1 x Systemization Quote

"The choice is always the same. You can make your model more complex and more faithful to reality, or you can make it simpler and easier to handle." — James Gleick

1 x Reflection Question

What's a system in your life that you've been blaming yourself for not following — when really, it's a system that requires more cognitive bandwidth than any human has on a normal day?

1 x Personal System Idea

Audit Your Systems for Bandwidth Demands: Pick three personal systems you use daily — a morning routine, a planning system, a meal-decision process, a habit you’re trying to maintain. For each one, ask:

• What does this system require me to remember? Anything held in memory rather than offloaded to environment, calendar, alarm, or checklist is a bandwidth tax. The bigger the tax, the more reliably the system will fail on a hard day.
• What does this system require me to decide in the moment? In-the-moment decisions are expensive — and the cost goes up sharply when you’re tired, hungry, stressed, or distracted. Pre-deciding (“I always do X on Tuesdays”) removes the decision from the moment.
• What does this system require me to override? If the desired behavior fights against an environmental cue (the cookies on the counter, the phone next to the bed, the email tab left open), the system is asking willpower to do work that environment design could do for free.

Rule of thumb: every time you discover a hidden bandwidth demand, ask whether you can move that demand out of your head and into the structure around you. Notes apps, calendar reminders, automated transfers, visible visual cues, pre-decided defaults — all of these are ways of letting the system carry what your brain shouldn’t have to.

You’re not building a system for the version of you with unlimited mental energy. You’re building a system for the version of you who’s three days into a hard week.

1 x Business System Idea

Engineer Smart Defaults Into the Decisions That Repeat: In most solopreneur businesses, every decision still requires a fresh evaluation, every time. Pricing. Scheduling. Email responses. Project scoping. Meeting agendas. The cumulative cost of all that real-time decision-making is invisible until the day it isn’t.

Bounded rationality says: pre-decide what you can, and let the default carry you on the days you don’t have the bandwidth to choose.

A few places this pays off:

• Pricing. Don’t recalculate pricing for every new prospect. Build a tiered structure with clear defaults — “this size of project gets this price” — and only deviate consciously, not from depletion.
• Calendar defaults. Pre-decide what kinds of meetings happen on what days, what the default duration is, what the default response to a “quick call?” request looks like. Every one of those is a small decision you don’t want to be making fresh at 4pm on a Thursday.
• Email response patterns. For the ten or fifteen kinds of emails you actually receive — proposal requests, scheduling, intro requests, status check-ins — build a default opener and a default frame. Cowork is excellent for this; ask it to draft a reusable template based on your last several real responses. You’re not eliminating thoughtful communication, you’re eliminating the cognitive cost of starting from scratch.
• Project scoping. Pre-decide what you’ll always include in a scope (and what you’ll always exclude), so scope conversations don’t quietly reset every time you have one.

The point isn’t to automate your judgment. The point is to stop spending judgment on the things that don’t actually require fresh judgment — so you have it available when something does.