01 · Systems for behaviour
The nudges framework: one system instead of a dozen one-off banners
Teams kept shipping one-off nudges (cart reminders, low-stock flags, filter prompts) with no shared logic. More noise, duplicated engineering, diminishing returns.
The forkKeep shipping nudges on request, or pause and build the framework first?
- 1.9× listing → product page clicks
- +27% cart additions
- 3.2× better conversion rate
My call
Build the framework first: reusable and configurable, at the cost of short-term feature velocity.





