Behavior change projects fail because they start with the wrong model of how behavior works!
Most organizations want to shift behavior, whether it's how teams collaborate, how users engage with a product, or how citizens access public services.
But behavior change is often approached with tools that weren’t designed for the complexity of real people, the realities of how motivation works, real systems, or real-world constraints.
The default mental model tends to be: cognitive biases, nudges, System 1 vs System 2. These ideas made it "famous" and helped put behavioral science on the map.
Inadvertently, they also narrowed the field in many people's eyes, as Behavior Science became associated with quick fixes or clever tricks, but as practitioners, we know these copy paste tactics often fall apart the moment you try to apply them inside an organization, a product or a policy.
What you should be interested in is something broader, and avoid using behavioral science as a tactic.
The way I use it, and I hope it is the way it comes out in the content I share, is a way to see systems more clearly, ask better questions, and design more effective solutions.
This is done by applying different lenses from psychology, systems thinking, anthropology, design, and more, not to impress with complexity, but to better match how behavior really works in context.
These lens are not about replacing what you're already doing, but to add new ways of framing the challenges, identify levers, and test solutions with more precision, especially when stakes are high or uncertainty is real.
The goal for you and your team, is to build capability, by embedding this way of thinking into your work, not just for one project, but across your practice.
Remember, real impact doesn’t come from one-off interventions, it comes when an organization can consistently think and act in behaviorally informed ways, without needing someone else to do it for them.
That’s the work we do at Aim for Behavior: partnering with teams to turn behavioral science from theory into a usable, scalable solutions and internal capability.
What’s been your biggest challenge when trying to shift behavior inside your organization?