01
A person as a system.
Why “user” in product analytics is too coarse a unit of analysis. States, behaviour, environment. We unpack your own product as a behavioural system.
Group practice / September 21—27 / online
Neuroscience for product development.
What we will do
We will take familiar product questions — activation, conversion, retention, engagement — and go one layer below metrics: to the mechanisms that produce human behaviour.
Why did a person click? Why did they return? Why did they form a habit? Why did two people in the same interface behave completely differently?
And most importantly: what exactly can we change in the system to change the likelihood of the next action?
We will approach neuroscience not as a collection of entertaining brain facts, but as an engineering tool for product development.
A small group. Participants’ real products. A week of practical workshops.
The central metaphor
You do not choose a user’s specific destiny. You change the probability distribution of their next states.
One week / five workshops
Five sessions to move from product and metrics to the behavioural architecture of real systems.
01
Why “user” in product analytics is too coarse a unit of analysis. States, behaviour, environment. We unpack your own product as a behavioural system.
02
Attention, perception, memory, valuation, reward, prediction, affect. Not a full neuroscience 101 — only the mechanisms that create engineering variables.
03
Interface, copy, timing, friction, defaults, notifications, social mechanics, rewards. What each element does to the human system.
04
Why every session cannot be viewed independently. Learning, reinforcement, habituation, accumulated state. Today’s product changes tomorrow’s user.
05
We take participants’ real cases and try to design a transition.