Behaviour, standards and momentum

The problem with motivation

Most people treat performance as a motivation problem. They look at someone who is not training, not hitting their numbers, not showing up consistently, and they diagnose the problem as insufficient desire. If only they wanted it more. If only they were more disciplined. If only they cared enough.

This is almost always wrong.

The person who stops training usually still wants the outcome. The person who fails to execute usually still believes in the goal. Motivation is not absent: it is volatile. It rises on Monday morning and collapses by Thursday afternoon. It peaks after a good session and disappears the moment life becomes complicated. Treating performance as a motivation problem means perpetually chasing a feeling rather than building something durable.

There is an entire industry built on this misdiagnosis. Books about willpower, apps that push inspiring quotes, coaches who ask how badly you really want it. None of it is useless, but most of it addresses the wrong layer. The symptom is visible, someone is not doing the thing, and the diagnosis points at their internal state. The solution, then, is to fix the internal state. Top up the motivation. Restore the desire.

The actual unit of performance is behaviour. Not mindset. Not intention. Behaviour: the thing you do, or do not do, at the moment when the decision is still live.

This distinction is not semantic. It changes everything about how you design a system.

What a standard actually is

The word gets used loosely. People talk about "high standards" as if it were a personality trait: something you either have or do not have. That is not useful. A standard is specific. It is the concrete form of an expectation, expressed at the level of action.

A standard says: this is what the behaviour looks like when it is correct. Not roughly correct. Specifically correct. The training session happens at this time, lasts this long, includes this work. The meal is logged before the day ends, not approximately recalled on Sunday. The call is prepared for, not improvised. The report is filed when it was promised, not when it is convenient.

The reason most performance efforts fail is not a lack of ambition. It is a lack of specificity in the standard. When the bar is vague, "train more", "eat better", "be more disciplined", the mind has no reliable target to return to. Every decision becomes a new negotiation with yourself, and that negotiation is exhausting. Exhaustion breeds inconsistency. Inconsistency breaks momentum.

Specificity in the standard removes the negotiation. You already decided. The decision was made when the standard was set, not in the moment when you are tired and the couch looks reasonable. This is why two people with identical goals and identical motivation levels can produce entirely different outcomes: one of them has defined what the correct behaviour looks like in advance, and one of them has not.

The standard also functions as a reference point for accountability. You cannot meaningfully hold someone accountable to something vague. "Are you eating better?" is unanswerable. "Did you log your meals before 10pm every day this week?" is not. The specificity of the standard is what makes accountability possible, and what makes the feedback loop work.

The feedback loop

Behaviour and momentum have a relationship that is easy to underestimate.

A single good session does not feel like much. But it creates a small amount of evidence: evidence that you are the kind of person who does the thing. That evidence matters more than most people appreciate, because the next decision draws on it. The athlete who trained yesterday is more likely to train today, not primarily because of physical conditioning, but because the identity is reinforced. The standard was met. The chain is intact.

The inverse is also true, and this is where most systems break down. A missed session does not just mean one day of lost progress. It creates counter-evidence. It introduces a new data point: the chain can be broken. The next decision now has to overcome that. And if the next session is also missed, the evidence compounds. After enough misses, the person is no longer someone who does the thing. They are someone who used to, or who is trying to.

This is what momentum actually is. Not energy. Not enthusiasm. It is the cumulative weight of prior behaviour pressing on the current decision. Positive momentum makes the correct behaviour easier. Negative momentum makes it harder. The system's job is to build positive momentum and minimise the cost of re-entry when it breaks.

Re-entry is the critical design problem that almost no performance tool addresses well. It is easy to build something that congratulates consistency. It is hard to build something that handles a miss without turning it into a story about failure. A good system acknowledges the gap, establishes the next standard clearly, and makes it easy to take the first step back, not a full step, just the first one. The size of that re-entry step matters enormously. Making it smaller is not lowering the bar. It is understanding what momentum requires.

What this means in practice

If you are designing a performance system, be it a product, a coaching framework, or a training programme, the practical implications follow fairly directly from the above.

First: the standard must be concrete before the behaviour is required. Ambiguity at decision time is friction. Friction reduces the probability of the correct behaviour. Define the standard in advance and remove the need for real-time renegotiation.

Second: the system should track behaviours, not feelings. Logging a completed session is a behaviour. Logging how motivated you felt is a feeling. The feeling is unreliable data. The behaviour is the record. Build the record around what was done, not how it felt to do it. Systems that ask too frequently how you are feeling gradually shift the user's attention from the behaviour to the emotion, which is the wrong place to focus.

Third: streaks and chains are useful but must be handled carefully. They create momentum, but they can also create fragility. Someone who has a forty-day streak may skip rest or push through injury to protect it. The metric becomes more important than the outcome. Good systems track streaks without allowing them to become punitive. The chain matters. Breaking it is not catastrophic. The response to breaking it is what determines whether momentum rebuilds or collapses.

Fourth: accountability functions best when it is specific and timed. Telling someone you will check in "some time next week" is almost worthless. Telling someone you will ask them at 8pm on Thursday whether they completed what they said they would complete is a different intervention entirely. Specificity in accountability mirrors specificity in the standard. Both reduce the room for drift.

The early thinking behind CheekyGains

These questions, how behaviour works, what a real standard looks like, how momentum is built and lost and rebuilt, were running through early conversations about what would eventually become CheekyGains.

It was not originally a product idea. It was more a research position. The consumer fitness space in 2015 was full of tracking tools that did an excellent job of measuring things and a poor job of actually changing behaviour. Plenty of apps would show you that you had missed four workouts. Very few would do anything useful with that information beyond displaying it as a statistic. The data was good. The intervention layer was absent.

The insight, not original but important, was that measurement alone does not produce behaviour change. The gap between knowing what you should do and doing it is not closed by better data. It is closed by better structure. By making the correct behaviour easier, and the incorrect behaviour more visible. By giving someone a standard clear enough to return to, and an accountability mechanism specific enough to matter.

The coaching dimension was important from the beginning. Not prescriptive coaching that tells someone exactly what to do in a way that breeds dependency, but accountability-oriented coaching that holds the standard, notices the pattern, and asks the right question at the right moment. The question that matters most is a simple one: did you do what you said you would do? And if not: what is the first step back?

The quality of the response to that question is where the system either earns the user's trust or loses it. A coach who catastrophises a miss damages momentum. A coach who dismisses it fails to reinforce the standard. The right response acknowledges the reality, holds the standard, and makes re-entry feel possible rather than shameful.

This is still the design logic that sits underneath CheekyGains. The system is not trying to manufacture motivation. It is trying to build the conditions in which good behaviour becomes the path of least resistance, and in which a miss is handled cleanly rather than allowed to spiral.

Systems outlast feelings

The premise here is simple enough to state in a sentence: motivation is volatile, but systems are durable.

What follows from that premise is less simple. Building a durable system requires genuine clarity about what the correct behaviour is, at what frequency, to what standard. It requires infrastructure for accountability that is specific and timely rather than vague and occasional. It requires a framework for handling misses that does not catastrophise them. And it requires a feedback loop that builds the evidence of consistent behaviour over time: evidence that becomes, gradually, part of how a person understands themselves.

That is what performance is, at the level that actually matters. Not a burst of motivation. Not a month of unusual effort. A set of behaviours, held to a defined standard, sustained long enough that momentum does the work that willpower cannot.

The product that serves this well is not complicated. But it is specific. It knows what it is trying to do. And it does not confuse measurement with change.