Clarify retention drivers in multi-capability adoption
Adoption can look like a cause when it may only be a symptom of customer maturity.
Teams often have to choose between broadening usage and understanding which customer progress actually matters.
“We’ll add more capabilities eventually, but I can’t tell what’s worth doing next.”
Kwaku Kuffour · Payments Engineering Manager
Leads a small team at a scaling marketplace that initially adopted basic card acceptance.
What pulls against what
- correlation vs. causation
- broad adoption vs. meaningful progress
- near-term signals vs. long-term retention
- data patterns vs. merchant intent
What is at stake
A compelling retention pattern may be causal, coincidental, or segment-specific. The next bet should create learning before it creates commitment
Why Stripe
At Stripe, this can matter because merchants often assemble payment capabilities at different moments in their growth.
Written for
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.