Retention Grid Lab
Build a Sticky Feature Performance grid on a live product, including the awkward cells where usage is loud and loyalty is quiet.
Studio notes from Cadder
Tool Layergrid teaches Sticky Feature Performance as a working practice: a grid that separates first-week curiosity from the behaviour that still shows up on a Tuesday six weeks later.
From recent cohorts
“I came in expecting a new KPI. I left with a rule for when we are not allowed to call a widget ‘adopted’.”
“The lab is slower than a slide deck. That is the point. We stopped celebrating a spike that vanished by week three.”
Programmes
Build a Sticky Feature Performance grid on a live product, including the awkward cells where usage is loud and loyalty is quiet.
Clean event names, kill duplicate funnels, and agree what “returned to the feature” actually means in your logs.
Map the unglamorous repeat jobs that keep a feature in someone’s week, especially when the buyer is not the user.
Why a grid
A percentage on a dashboard can hide a feature that only power users touch, or a prompt that trains people to click once and forget. Sticky Feature Performance asks you to plot depth against return, then to write the story of each cell in plain language.
We work with GB product teams who already have analytics, and who are tired of arguing about which chart “wins”. The grid is a shared object in the room. It does not replace your warehouse. It stops the warehouse from substituting for judgement.
Next step
If you already know which surface looks busy and still does not earn a second week, write to us. If you do not, start with the lab syllabus.