Misdiagnosis
If you've ever blamed your team for not following standard operating procedures, blamed yourself for not pushing hard enough, or blamed a culture of complacency for operational gaps, it's likely that you're looking in the wrong place. The pattern I've watched across companies is consistent: leaders try to fix execution problems with motivation interventions or more training. Two weeks of energised compliance, four weeks of drift, and by week eight the standard is back where it was before the conversation happened.
Environment shapes behaviour far more powerfully than motivation ever does. Most team leaders default to the conventional answers (training, communication, oversight, escalation), all of which lean on motivation as the underlying fuel where none of which fix the problem.
This blog walks through what the research on behaviour actually shows, why most current tools fall short of being able to apply it, and how a company that wants consistent execution can structurally engineer the environment that produces it.
The Fogg Behaviour Model
BJ Fogg at Stanford has spent more than twenty years researching how behaviour change actually works. His behaviour model, the cleanest practical framework I've come across for this, identifies three elements that need to converge for a behaviour to occur. Motivation, ability, and a prompt. He summarises it as B = MAP.¹
Behaviour happens when all three are present at the same moment. If any of them are missing, the behaviour does not happen. The interesting implication for operations is the relationship between motivation and ability. When the action is easy (high ability) and the prompt is obvious (the environment cues it), even low motivation produces consistent behaviour. When the action is difficult (low ability) and the prompt is missing or weak (the environment doesn't cue it), even high motivation often fails to produce the behaviour reliably.
For operational teams executing the same procedures repeatedly, this is where the leverage sits. You don't actually need to maximise motivation. You need to maximise ability (make the right action easy) and ensure the prompt is reliably present at the moment the action is required. Do that consistently and the behaviour follows.
Why Motivation Alone Fails
Wendy Wood's research at USC over the last two decades shows why motivation-based approaches to behaviour change keep producing the same disappointing results. Habits are context-response associations. They form when people repeat rewarding actions in stable contexts, and once they're formed, the perception of the context directly activates the response in the person's mind. The motivation that originally drove the behaviour has been replaced by the cue.² Wood's research finds that roughly 43% of what people do every day is repeated in the same context, usually while they're thinking about something else.³
The corollary is that successful behaviour change interventions don't work by changing minds. They work by changing the cues that trigger behaviour. Information campaigns are weak because they ask the person to remember the information and apply it; environmental design is strong because the right action becomes the default in the context where it needs to happen.
The work on this in operational settings produces some specific implications. Visual cues at the moment of action override willpower-based intentions. Friction in the path of the right action shifts behaviour toward the wrong action regardless of stated intent. Procedural prompts that arrive in context (at the desk, in the workflow, at the step where action is required) reliably trigger the corresponding behaviour. Procedural prompts that arrive out of context (a Slack message, a calendar reminder, an email) compete for attention against whatever the person is currently doing and frequently lose.
James Clear's Atomic Habits compresses this into a single line that captures the lived experience of every operations leader I've talked to: "You do not rise to the level of your goals. You fall to the level of your systems."⁴ The goal is irrelevant if the system that's supposed to produce it depends on motivation that won't be there on the day the action needs to happen.
The Usual Frustration
When I was in executive management, we had policies approved and signed off by leadership, filed away in the document management system. And we had compliance gaps surface in quarterly audits with a regularity that frustrated everyone involved. The conventional diagnosis was that staff weren't reading the policies, or weren't following them, or weren't motivated to follow them.
The diagnosis that turned out to be correct was simpler. The policies existed in PDFs and shared drives. Staff had to remember the policy existed, search for the current version, interpret ambiguous steps, and execute them from memory. Every step in that chain added friction. Motivation couldn't reliably overcome that much friction across a team of dozens, repeated daily, week after week. The standards were slipping because the environment wasn't supporting them.
When we built LivPro, the principle was that the right action needs to be the easiest action and the obvious one. The procedure needs to be where the work is happening, at the moment the action is required, with the cue and the information and the next step all present together. Remove the steps that depend on memory. Remove the friction. Let the environment do the work that motivation cannot do reliably.
Why Current Tools Fall Short
Most operational tools available today are not designed to apply environmental design to execution. They were built to do something else, usually well, and they get reached for by default when leaders are trying to solve an execution problem they're misdiagnosing as a coordination or visibility problem.
Project management platforms: Tools like Asana, Monday, and Jira are good at task visibility. They track what needs to be done, who is doing it, and what stage of completion it's at. What they don't do is engineer the environment in which the task is executed. They tell the user what to do. They don't make the right action easier than the wrong action, they don't reduce friction at the moment of execution, and they don't provide environmental cues that make correct execution automatic. The user still has to remember the procedure, find the relevant documents, interpret the steps, and execute them. The PM tool sits on top of all of that. It's an information system, not a behaviour system.
Documentation: Standard operating procedures, policy documents, and compliance manuals are static. They require the user to remember they exist, find the current version, interpret instructions, and apply them without guidance at the moment of action. Documentation is a reference layer. It supports execution; it doesn't shape it. The procedure being correctly documented is necessary but nowhere near sufficient for the procedure being correctly executed.
Notification-based behaviour tools: Some platforms attempt to apply behavioural science by sending reminders, notifications, or gamified prompts. The problem is that notifications operate out of context. A Slack ping or an email alert arrives at a desk that's currently focused on something else, competing for attention with whatever the user is doing. The cognitive cost of switching attention from the current task to the notification is high, and the prompt frequently loses. Gloria Mark's research at UC Irvine on interruption found that the average task takes 23 minutes and 15 seconds to resume after an unrelated interruption.⁵ Notifications are not environmental design. They're requests for motivation that arrive at the wrong moment and ask the user to switch contexts to comply.
The gap across all three categories is the same where none of these tools shape the environment at the moment of action and therefore don't impact how the actual execution is done. They provide information, visibility, or reminders, all of which are useful but none of which is environmental engineering in the sense the behavioural research describes.
How LIVPRO Applies Environmental Design
LivPro is built from the ground up to apply environmental design to operational execution. The system is structured around four mechanisms, each one targeting a specific dimension of what the research says makes behaviour reliable.
Locked workflows: Company-level processes are defined by process owners and surfaced in the user's workflow as a sequenced set of steps. The next step is presented in the environment where the work is happening. The user doesn't search for the procedure, doesn't interpret which version is current, doesn't choose which step to execute next. The right action is presented as the path of least resistance. When the right action is easier than the wrong action, the right action happens by default.
Step-level information at the moment of action: Each step includes the instructions, expert tips, checklists, reference materials, and embedded prompts the user needs to execute it correctly. Everything is present at the moment of action rather than in a separate document the user has to remember to consult. The friction of finding the information is removed. The ambiguity of interpretation is reduced. The cognitive load of holding the procedure in memory is shifted from the user to the environment.
Always-on-top behavioural prompts: When a step requires action, the LivPro modal surfaces in-context as an unmissable cue. The prompt is specific to the work happening, tied to the workflow itself rather than to a remote channel like Slack or email. This is the difference between environmental cuing (the prompt arrives in the context where the action belongs) and notification (the prompt arrives out of context, asking for attention that has to come from somewhere else). The research on habit formation is consistent that context-bound cues are what drives the cue-response association the behaviour eventually becomes.
User-created workflows: LivPro is not only for company-mandated processes. Individual users can build their own workflows, recurring routines such as daily CRM updates or weekly running of reports, and personal habits using the same step-by-step builder. The principle is that environmental design works for personal execution as well as organisational execution. When a user designs their own prompts and reduces their own friction for their own goals, adherence rises substantially compared to relying on personal motivation alone.
The combined effect across all four mechanisms is that the environment becomes the active ingredient in execution. The standard sits in the environment rather than in the user's head or the leader's communication style or the team's general motivation level. The standard holds because the environment holds it in place, day after day, regardless of which user is at the desk on any given day.
On The Change Management Concern
The most common pushback I hear when describing this is some version of "my team won't like always-on prompts. I think it will annoy them." The concern is reasonable and worth addressing honestly.
Resistance to operational change is well-documented. Kotter's work on change management estimates that roughly 70% of change initiatives fail to deliver their intended outcomes, with resistance and incomplete adoption among the leading causes.⁶ What the research also shows is that resistance is highest in the early weeks of a change and drops substantially once the new behaviour starts to become familiar. Phillippa Lally's research at UCL on habit formation found that habits take an average of 66 days to become automatic, with the first two to three weeks requiring the most conscious effort and the curve of automaticity rising steadily after that.⁷
What happens in practice is that the prompts feel like prompts in the early weeks and feel like part of the work by week eight. The behaviour they're cueing has become habitual. The cue has moved from being a noticeable feature of the environment to being an invisible component of how the work happens. This is habit formation working exactly as the research predicts. The discomfort is real but temporary, and the benefit on the other side of it is consistent execution that doesn't depend on anyone's motivation level on a given Tuesday morning.
The Standard Your Environment Is Producing
Motivation is finite. It varies by day, by season, by individual, by life event, by company pressure level. A team's standard of execution that depends on motivation will be the average of all of those variables across all of the team, which is to say it will be considerably lower than the standard the leader thinks they've set.
Environment is persistent. The cue is there or it isn't. The procedure is surfaced at the right moment or it isn't. The friction is removed or it isn't. Environmental design is the practical answer to a question every operations leader is implicitly asking: how do I get the team to execute consistently when I can't be in every workflow personally? The answer is that you engineer the environment to do the work that your personal attention can't scale to.
The question is no longer "how do I motivate my team to execute the standard?" The question is "what does the environment in which they're executing actually produce, and how do I redesign it so it produces what I want it to produce?"
LivPro is the implementation layer for that redesign. The framework is yours either way. The product is the operational answer to the question the framework forces.
Start Your Free Trial → Start Your Free Trial Now
Citations
- Fogg, B. J. (2009). A behavior model for persuasive design. Proceedings of the 4th International Conference on Persuasive Technology (Persuasive '09). Stanford University Behavior Design Lab. See also Fogg, B. J. (2020). Tiny Habits: The Small Changes That Change Everything. Houghton Mifflin Harcourt.
- Wood, W. (2019). Good Habits, Bad Habits: The Science of Making Positive Changes That Stick. Farrar, Straus and Giroux.
- Wood, W., Quinn, J. M., & Kashy, D. A. (2002). Habits in everyday life: Thought, emotion, and action. Journal of Personality and Social Psychology, 83(6), 1281–1297.
- Clear, J. (2018). Atomic Habits: An Easy & Proven Way to Build Good Habits & Break Bad Ones. Avery.
- Mark, G., Gudith, D., & Klocke, U. (2008). The cost of interrupted work: More speed and stress. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI '08), 107–110.
- Kotter, J. P. (2008). A Sense of Urgency. Harvard Business Review Press. See also Beer, M., & Nohria, N. (2000). Cracking the code of change. Harvard Business Review, 78(3), 133–141.
- Lally, P., van Jaarsveld, C. H. M., Potts, H. W. W., & Wardle, J. (2010). How are habits formed: Modelling habit formation in the real world. European Journal of Social Psychology, 40(6), 998–1009.