From the blog

Ideas that stick.

Short, practical writing on systems thinking, decision-making, and designing a life that doesn't depend on motivation. New posts regularly.

01

Why goals fail (and what to build instead)

Goals feel like the answer. They give you direction, a deadline, a reason to move. But most goals fail — not because the person is undisciplined, but because the structure underneath them was never built.

Read article
02

The loop you don't know you're in

Most patterns in your life aren't random. They're the output of a loop — a set of inputs and responses that repeat quietly, beneath the surface, until you learn to see them.

Read article
03

Stop managing time. Start managing energy.

Time management assumes all hours are equal. They're not. The real question isn't how many hours you have — it's what state you're in when you use them.

Read article

Goals feel like the answer. They give you direction, a deadline, a sense of purpose. But if goals worked as well as we're told they do, most people wouldn't be setting the same ones every year.

Here's something worth sitting with: the people who consistently make progress aren't necessarily more motivated. They're not more disciplined either. What they have — often without realising it — is a structure that keeps moving even when they don't feel like it.

A goal tells you where you want to go. A system determines whether you ever get there.

The problem with outcome-first thinking

When you set a goal, your attention goes to the destination. That's natural. But the destination is mostly out of your control. What you can control is the process — the inputs, the habits, the decisions you make each day. Goals focus you on the wrong end of the equation.

This is why people who hit their goals often end up back where they started. The goal was achieved, but the system was never built. Remove the target, and the behaviour collapses. Nothing holds it in place.

What a system actually does

A system doesn't replace your ambition. It gives it somewhere to live. Instead of asking "how do I achieve this?", a system asks "what process, repeated consistently, would make this result almost inevitable?"

That's a different question. It shifts your attention from the outcome — which you can't fully control — to the structure — which you can design, test, and adjust.

A writer who wants to finish a book doesn't sit down and try to feel inspired. They write 500 words every morning before checking their phone. The feeling follows the structure, not the other way around.

Where most people go wrong

Most people build goals and skip the system entirely. They decide what they want, maybe break it into steps, then rely on motivation to bridge the gap between intention and action. Motivation is real, but it's inconsistent. It arrives when conditions are good and disappears when they're not. You can't build something durable on an unreliable foundation.

The better approach is to design your environment, your routines, and your feedback loops so that the right behaviour becomes easier than the wrong one. Not through force — through design.

You don't rise to the level of your goals. You fall to the level of your systems.

A practical place to start

Pick one area of your life where you keep setting the same goal without lasting progress. Instead of asking what the goal should be, ask: what would the daily structure look like if this were already working? What would I be doing regularly? What would make it hard to stop?

Build the structure first. The results will come from the structure — not from how badly you want them.

Practical Takeaways
  • Identify one goal you've set repeatedly without lasting success
  • Ask what daily process, if followed consistently, would make the outcome likely
  • Design the environment to make that process easy and visible
  • Measure your consistency with the process — not the outcome

Most people think their biggest problems are unique to them. A tendency to procrastinate, to overthink, to stay in situations too long or leave them too fast. But look closely enough and you'll find a pattern underneath — a loop that's been running quietly for years.

A loop, in systems thinking, is a repeating cycle. An input leads to a response, which produces an output, which becomes the next input. Most of the time, we only see the output — the result, the emotion, the behaviour. We miss the structure that produced it.

Why loops are hard to see

You can't see a loop while you're inside it. You're too close to the individual moments. Someone who keeps ending up in the same kind of relationship doesn't experience it as a pattern — they experience it as a series of separate situations, each with its own story and its own explanation.

This is why self-awareness alone isn't enough. Knowing that you have a pattern doesn't automatically show you the structure behind it. You can be fully aware that you procrastinate and still not understand what's actually driving it.

The loop isn't in your behaviour. It's in the beliefs and responses that sit underneath the behaviour.

The anatomy of a loop

Most personal loops have three parts: a trigger, a response, and a consequence that reinforces the trigger. The trigger might be a feeling — discomfort, uncertainty, boredom. The response is the behaviour you default to. The consequence either relieves the discomfort or deepens it, feeding back into the next cycle.

Take perfectionism as an example. The trigger is a task that feels important. The response is delay — because starting feels like risking failure. The consequence is temporary relief, followed by pressure as the deadline approaches, which makes the task feel even more loaded next time. The loop tightens.

Finding your loop

The place to look isn't the moment of behaviour — it's the moment just before. What were you feeling? What did you believe was true in that moment? What were you trying to avoid?

If you find the same answer appearing across different situations, you've found the loop. The specific situations change. The underlying structure doesn't.

Changing the structure, not just the behaviour

Most attempts at change target the behaviour directly. Stop procrastinating. Be more confident. Think positively. But the behaviour is downstream. If the loop is still intact, the behaviour will return — because the structure that produces it hasn't changed.

To break a loop, you need to intervene at the level of the trigger or the belief. That might mean changing what you expose yourself to, how you interpret certain situations, or what response you practice in the moment that usually triggers the old one.

This takes time. Loops don't disappear overnight — they loosen, gradually, as the structure shifts. But the direction is different. Instead of fighting your own behaviour, you're redesigning what produces it.

Practical Takeaways
  • Identify a recurring pattern in your life — something that keeps happening despite your efforts
  • Look for the moment just before the behaviour: what triggers it?
  • Ask what belief or assumption is active in that trigger moment
  • Instead of fighting the behaviour, design a different response to the trigger

The standard productivity advice is built around time. Calendars, time-blocks, schedules, deadlines. Track your hours. Protect your mornings. Don't waste a minute. It's not bad advice. But it's missing something fundamental.

Time is fixed. Everyone gets the same twenty-four hours. But what you do with those hours varies enormously depending on one thing: the state you're in when you use them.

Not all hours are equal

You already know this, even if you've never said it directly. An hour of work when you're rested, focused, and clear is not the same as an hour of work when you're depleted, distracted, and pushing through. The clock says they're identical. Your output tells a different story.

Most productivity systems ignore this. They treat you like a machine — consistent input, consistent output. But you're not a machine. Your capacity fluctuates. Your focus is a resource that depletes and replenishes. Your best thinking happens at specific times, under specific conditions, and not at others.

Managing your time tells you when to do the work. Managing your energy tells you whether you'll actually be capable of doing it.

The four dimensions of energy

Energy isn't just physical tiredness or the lack of sleep, though both matter. It operates across four layers: physical, emotional, mental, and motivational. Each one affects the others. A difficult conversation can drain your mental focus for hours. A period of sustained deep work without breaks depletes your ability to think creatively. Doing work that feels pointless is exhausting in a way that hard but meaningful work isn't.

Once you see these layers, you start to notice where your energy is actually going — and how much of it is being spent on things that shouldn't require nearly that much.

Designing for energy, not just effort

The practical shift is this: instead of asking "when do I have time for this?", ask "when do I have the right kind of energy for this?"

Some tasks need your sharpest thinking — complex decisions, creative work, writing. These belong in your highest-energy windows. Other tasks — admin, routine communication, simple logistics — can happen in lower-energy periods without much cost. The mistake most people make is filling their best hours with low-stakes tasks because they feel manageable, then trying to do deep work when they're already half-spent.

Recovery is part of the system

The most overlooked productivity principle isn't a technique for doing more — it's a principle for recovering better. Sleep, movement, genuine rest, and time away from screens aren't indulgences. They're inputs into your capacity to function well.

A system that doesn't account for recovery will eventually produce diminishing returns, and then failure. You can't extract more than the system is designed to produce. Build recovery in, and your actual output — not just your hours — increases.

The goal isn't to fill every hour. It's to show up well for the hours that matter most. That's a different kind of efficiency — and a far more sustainable one.

Practical Takeaways
  • Identify your 2–3 highest-energy hours in the day and protect them for deep work
  • Match task type to energy level — save routine tasks for low-energy windows
  • Track what drains you unexpectedly: meetings, decisions, context-switching
  • Treat sleep and recovery as system inputs, not optional extras

Want to go deeper?

The System Life Series takes these ideas further — with a practical framework for applying systems thinking to the way you actually live and work.