Systems for consistency

What we misattribute to willpower

Most people who are consistent do not feel particularly disciplined. Ask them and they will usually say something like: "I just do it at the same time every day" or "it would feel stranger to miss it than to do it." What sounds like remarkable self-control is often something quieter: a set of conditions that make the behaviour almost automatic.

This is worth taking seriously because the reverse is also true. The person who cannot stay consistent is rarely lacking resolve. They are usually lacking architecture. The conditions around the behaviour make it hard, effortful, or easy to forget. They fail not because they do not want the outcome badly enough, but because wanting is not the mechanism that drives behaviour under pressure.

The popular version of this insight goes back at least to William James, who argued that habit liberates the mind for more important deliberation by removing the need to decide routine actions afresh each time. But even James framed it in terms of mental training: the repetition of behaviour until it becomes automatic. What that framing misses is the role of the environment itself. You do not just train a habit. You set conditions under which a habit becomes the path of least resistance.

Environment as the real variable

The psychologist Kurt Lewin proposed what he called a field theory of behaviour in the 1940s: that action is a function of the person in their environment, not of the person in isolation. Most performance thinking ignores the second half of that equation. It focuses relentlessly on internal states, motivation, grit, mindset, whilst leaving the environment unexamined.

This matters enormously for anyone building a performance product or a personal practice. If the environment is hostile to the behaviour you want, if equipment is stored inconveniently, if the next step is unclear, if feedback arrives too late to be useful, then willpower is the wrong lever to pull. You are essentially demanding that people overcome their surroundings through force of character, repeatedly, under conditions that compound fatigue over time. That is not a recipe for consistency. It is a recipe for a good start followed by attrition.

The consistent performer has, usually without analysing it, arranged their environment so that the right behaviour is the easier one. The workout clothes are already out. The meal is already planned. The next action in the sequence is obvious. Each of those choices reduces the cognitive and physical friction between intention and action, and friction is what kills consistency more reliably than any failure of motivation.

What friction actually costs

It is tempting to think of friction as a minor inconvenience, an extra step, a small delay. But friction compounds in a way that is easy to underestimate. A behaviour that requires three additional decisions before it can begin is not slightly harder than one that requires none. It is categorically harder, because each decision point is an opportunity for the moment to pass, for tiredness to intercede, for something else to take priority.

James Clear has written about this in terms of the two-minute rule and the idea of reducing the activation energy required to begin a behaviour. Whether or not you accept the specific framing, the underlying observation is sound. The person who goes to the gym regularly is often not more motivated than the person who does not. They have simply eliminated more of the barriers between decision and action. Their gym bag is packed. They go on the way to work. The identity and the logistics are aligned.

This is the architectural insight: reduce the cost of starting, and the behaviour takes care of itself. Increase that cost even slightly, and you introduce a gap that willpower must bridge. Willpower is finite, variable, and worst precisely when you need it most.

The structure of a well-designed system

A system for consistency does not look particularly dramatic. It is not an elaborate morning routine or a colour-coded journal spread. At its core, it answers three questions reliably:

*When does this happen?* A time anchor removes the need to decide when. The decision has already been made. The behaviour occurs at a fixed point in the day or week, and the only remaining question is execution.

*What happens next?* A well-designed system has a clear sequence. After A comes B. There is no decision tree, no ambiguity about what the next step is. The person following the system is not navigating. They are executing.

*What does success look like today?* Vague intentions ("I want to get fitter") produce vague behaviour. A system replaces the intention with a specific standard that can be met or missed and evaluated honestly. That specificity is what makes reflection useful. You cannot learn from performance you cannot measure.

None of this requires sophisticated technology. A paper checklist, a fixed daily schedule, a training programme with defined sessions: these are all systems in this sense. What they share is that they shift the cognitive load from execution to design. You think hard once about the structure, so that the daily instance of the behaviour requires less thought.

The measurement problem

There is a version of this argument that goes wrong when it confuses measurement with the system itself. Tracking behaviour, logging workouts, recording meals, noting output, is useful because it makes performance visible. But a log is not a system. It is a record of what the system produced.

This distinction matters because a lot of performance products stop at tracking. They make it easy to record what happened, but they do not change what happens. The user is still relying on motivation and environment to produce the behaviour; the product is just counting it afterwards. That is not without value, but it is a long way from actually increasing consistency.

A product that genuinely supports consistency needs to address the conditions under which behaviour occurs, not just the measurement of it afterwards. That means helping users build the right time anchors, simplify their sequences, and understand what is actually driving their performance, rather than simply accumulating data points that they will eventually stop recording because the log does not close the gap between intention and action.

The CheekyGains standard

CheekyGains is the product in this portfolio that lives closest to this problem. It is a fitness and performance platform, and fitness is a domain where the consistency problem is exceptionally well-documented and exceptionally poorly solved.

Most fitness apps are, at their core, logging tools. They make it easy to record what you did. Some of them add social pressure, streaks, challenges, leaderboard positions, which produces short-term compliance but rarely durable behaviour. The streak breaks, the pressure lifts, the habit dissolves.

The standard we are working towards with CheekyGains is different. The goal is not to make it easier to log what happened. It is to make it easier for the right behaviour to happen in the first place, and to support recovery when it does not. That means thinking about how the product intersects with the user's day: not just when they are inside the app, but when they are at the decision point before the session, and when they have missed one and are deciding whether to continue.

What that looks like in practice is still being worked out in October 2015. But the design principle is clear: a performance product that wants to affect consistency must engage with the environment and the sequence, not just the record. It must make the right behaviour easier, not just more visible.

What the product cannot do

There is also an honest limit worth stating plainly. No product can substitute for genuine commitment or remove the reality that consistent behaviour over time involves real effort. The system reduces friction. It does not eliminate the work.

A well-designed environment makes it easier to do the thing you want to do. It does not want it on your behalf. The person still has to show up. The training session still has to happen. The meal still has to be prepared. The system creates the conditions for those choices to go well more often than they would otherwise, but it does not make the choice irrelevant.

This is the correct frame for a performance product. Its job is to increase the proportion of occasions on which the intention becomes the action. That is a meaningful improvement in someone's life. But it should not be oversold as the resolution of the motivation problem entirely, because that would be both dishonest and counterproductive. Agency matters. The product should increase it, not replace it.

Consistency as design

The practical conclusion is that consistency is not primarily a personal quality. It is a designed condition. The people who exhibit it most reliably are usually the people who have arranged their environments, schedules, and sequences most carefully, sometimes deliberately, sometimes through accumulated habit.

For a product builder, this is clarifying. It means that the question to ask is not "how do we motivate users to be more consistent?" but "how do we reduce the cost of consistent behaviour for them?" Those are very different problems with very different solutions, and the second one is considerably more tractable.

The environment is the interface. The sequence is the logic. The standard is the feedback loop. Build those three things well and you have a system. Everything else is commentary.