How to actually set SYSTEMS instead of goals

Building systems in life isn’t about locking in a schedule and hoping it holds. The core insight is that durable systems are designed around a goal and an identity—and they include a plan for what happens when the system breaks—so setbacks become diagnostic feedback instead of discouragement.

The framework starts with a goal, but it rejects the common “systems vs. goals” framing. Systems exist to achieve goals; without clarity on what success looks like, there’s no reason to build a system at all. The next step is identity work: before constructing routines, the person who would achieve the goal “effortlessly” is mapped out through traits and behaviors. For example, someone trying to grow a part-time business while working a full-time job needs high energy and time management, plus habits that protect focus and stamina (like exercising and eating clean). The emphasis is on self-acceptance—shaping behaviors from self-love rather than self-hatred—so the identity shift feels robust instead of punishing.

Once goal and identity are defined, the method turns to inputs, processes, and outputs. A key distinction is made between a process and a system. A process is a linear sequence of steps (step one, step two, step three). A system is self-sustaining: it includes feedback that keeps it running and adapting. In the business example, inputs might be allocating one hour per day to the venture, broken into sub-inputs like market research, defining an offer, and planning content. The process then specifies what the hour looks like in practice—phone away, tabs organized, calendar ready, and a clear flow for executing the work. After that comes outputs: the measurable results of the effort.

Feedback is treated as the first critical feedback loop. If outputs don’t match expectations—videos don’t get views, ads don’t perform, weight doesn’t drop, or family time slips—the response shouldn’t be quitting. Instead, the person should examine whether the inputs and process are wrong, whether impatience is distorting interpretation, or whether the system needs refinement. A comparison to SpaceX engineering culture is used to underline this mindset: engineers intentionally create conditions for failure so they can learn what went wrong and iterate.

The most neglected step comes last: anticipating the failure of the entire system. When routines collapse—when the person forgets the plan or stops entirely—the situation becomes an opportunity to diagnose the root cause across three areas: the goal, the identity, or the system. If the goal doesn’t genuinely motivate, it may be the wrong target or the wrong time horizon (too far away to feel real, or too close to feel trivial). If the identity is unrealistic—like expecting someone who hasn’t done push-ups in years to suddenly adopt an extreme daily standard—the identity needs to shift toward gradual, believable change. If goal and identity hold, then the system itself may be poorly supported by the environment: missing reminders, too many distractions (phone, computer), or toxic social influences.

The takeaway is an antifragile approach to habits: expect breakdowns, use failure and feedback to iterate, and treat setbacks as fuel for improvement rather than proof of personal failure.